This list breaks down the essential UI widgets needed to render Linked Art JSON-LD effectively. These are categorized by complexity, ranging from "Atomic" (small text formatting helpers) to "Macro" (full interactive visualizations).
\nThese are the building blocks used to parse specific, deeply nested Linked Art fields into human-readable strings.
\nLinkedDate
\n• Purpose: Converting complex TimeSpan objects into readable dates.
\n• Functionality: Handles begin_of_the_begin, end_of_the_end, and display_label. It should gracefully degrade from specific dates ("May 12, 1890") to ranges ("1890–1900") to uncertainties ("Circa 19th Century").
\nLinkedDimensions
\n• Purpose: flattening the Dimension array into a standard physical description string.
\n• Functionality: Concatenates height, width, and depth values with their units. Example output: "24.5 x 30 cm".
\nLinkedAttribution
\n• Purpose: Generating the standard "Artist line."
\n• Functionality: Traverses the produced_by path to find carried_out_by (the actor). It should combine the Actor's _label with their role (e.g., "Painter") to display: "Vincent van Gogh (Painter)".
\nMaterialTechniqueList
\n• Purpose: Displaying the "Medium."
\n• Functionality: Aggregates made_of (materials) and technique fields. Example output: "Oil on Canvas".
\nThese are standard "preview" components used in search results, lists, or "related items" sidebars.
\nObjectCard
\n• Purpose: The standard grid item for a search result.
\n• Elements: * Thumbnail image (from digitally_shown_by).
\n• Truncated Title (_label).
\n• Creation Date (using LinkedDate).
\n• Artist Name.
\n• Status Badge (e.g., "On Display").
\nActorCard
\n• Purpose: A summary of a person or group (Artist, Donor, Manufacturer).
\n• Elements:
\n• Portrait/Image.
\n• Name.
\n• Birth/Death Dates.
\n• Nationality (from residence).
\n• Role summary (e.g., "Sculptor", "Collector").
\nPlaceCard
\n• Purpose: A summary for a geographical location found in the data.
\n• Elements:
\n• Map thumbnail.
\n• Place Name.
\n• Relationship (e.g., "Place of Production").
\nThese components handle the complex graph relationships in a visual way.
\nProvenanceTimeline
\n• Purpose: Visualizing the history of ownership (the provenance activity).
\n• Functionality: A vertical or horizontal stepper showing the sequence of Acquisition or Transfer of Custody events.
\n• Interactivity: Clicking a node shows the Buyer, Seller, Price, and Date of that transaction.
\nExhibitionHistoryList
\n• Purpose: Showing where the object has been displayed.
\n• Functionality: A chronological list of used_specifically_in (Exhibition) events. Should group exhibitions by venue or date.
\nGeoMapViewer
\n• Purpose: Placing the object in physical space.
\n• Functionality: A map (Leaflet/Mapbox) rendering pins for distinct spatial data points: produced_at (creation), current_location (storage), and moved_to (tours).
\nDeepZoomViewer (IIIF Wrapper)
\n• Purpose: High-resolution image exploration.
\n• Functionality: Consumes the digitally_shown_by IIIF manifest. Includes controls for zooming, panning, and toggling between multiple views (recto/verso).
\nHeirarchyTree
\n• Purpose: Navigating sets and collections.
\n• Functionality: Visualizing members_of relationships. Useful for albums, portfolios, or archival boxes to show the "Parent" object and "Sibling" objects.
\nDetailed blocks usually placed below the main image on an object page.
\nClassificationsBlock
\n• Purpose: Displaying taxonomies and types.
\n• Functionality: Renders classified_as fields (e.g., AAT terms) as clickable tags or pills that link to search results for that term.
\nReferenceList
\n• Purpose: Showing bibliography and academic sources.
\n• Functionality: Lists items in referred_to_by (Citation). Displays the text snippet and the publication source.
\nIdentifierBlock
\n• Purpose: Managing various ID numbers.
\n• Functionality: Lists the Accession Number, ULAN IDs, Wikidata IDs, and internal system IDs found in identified_by.
\nTools specifically for the "Participatory" aspect of your team's mission, allowing user interaction with the data.
\nAnnotationOverlay
\n• Purpose: Allowing users to comment on specific regions of an image.
\n• Functionality: Draws standard W3C Web Annotations on top of the IIIF canvas.
\nCrowdCorrector
\n• Purpose: Letting users suggest edits to data.
\n• Functionality: A "Suggest an Edit" button next to specific fields (like Date or Author). It opens a modal pre-filled with the current value, allowing the user to submit a proposed change.
\nStoryBuilder
\n• Purpose: Creating narratives around objects.
\n• Functionality: A drag-and-drop container where researchers can pull in ObjectCards and TextBlocks to create a linear "Exhibition" or "Story" page.
\nSuggested Next Step
\nWould you like me to generate the React/Javascript code for one of the "Atomic" components (like LinkedDate or LinkedAttribution) to demonstrate how to parse the JSON-LD structure?
","updatedAt":"2018-10-20T01:46:40.000Z","checksum":"b39911c7d97d558d7f77d9a149aa8c2a66637ee1ead4c6c7ec5ad170366e0046","checksumPrefix":"b39911c7d97d","anchorCount":0,"lineCount":160,"rawUrl":"/api/docs/content?path=linked-art%2FLinkedArtWidgets.md","htmlUrl":"/docs?doc=linked-art%2FLinkedArtWidgets.md","apiUrl":"/api/docs/content?path=linked-art%2FLinkedArtWidgets.md"}