{"id":"linked-art/LinkedArtAppFeatures","relativePath":"linked-art/LinkedArtAppFeatures.md","title":"🏛️ Art Explorer: Linked Art Application & Ecosystem","markdown":"# 🏛️ Art Explorer: Linked Art Application & Ecosystem\n\n**Comprehensive Technical Features & Architectural Design Plan**\n\n**Project Overview:** A full-stack, microservice-driven Linked Open Data (LOD) ecosystem designed to bridge the gap between rigorous digital humanities research, museum data infrastructure, and undergraduate art history pedagogy. Built strictly on **CIDOC-CRM** and **Linked Art JSON-LD** standards, this platform solves industry-wide challenges regarding legacy data mapping, uncertainty modeling, and semantic web accessibility.\n\n---\n\n## ⚙️ 1. Core Architecture & Technology Stack\n\nThe system utilizes a decoupled, API-first architecture combining microservices for heavy data processing with micro-frontends for modular user interfaces.\n\n- **Backend / Data Layer (The Engine):**\n \n - **Primary Language:** Python (FastAPI) & Node.js.\n \n - **Graph Database:** Neo4j or Stardog (native RDF/Graph storage) + PostgreSQL (JSONB) for application state.\n \n - **LOD Libraries:** Crom (Python) for Linked Art instantiation, PyLD for JSON-LD framing/compaction.\n \n - **ETL Orchestration:** Apache Airflow or Dagster for tracking data lineage and provenance.\n \n- **Frontend / UI Layer (The Interface):**\n \n - **Framework:** Next.js 15+ (React) with TypeScript (SSR/SSG for SEO and performance).\n \n - **Styling:** Tailwind CSS / Chakra UI.\n \n - **Visualization:** D3.js, Visx, and Cytoscape.js (for force-directed graphs).\n \n - **Mapping:** ReactFlow (for visual ETL mapping) and Leaflet/Mapbox (for geospatial).\n \n- **Infrastructure & CI/CD:**\n \n - Docker containerization for isolated microservices.\n \n - GitHub Actions with automated **SHACL validation** scripts to ensure data integrity.\n \n\n---\n\n## 🧩 2. The 4 Core Modular Tools (Micro-Frontends)\n\nTo solve the \"skills gap\" in the GLAM sector, the application provides a suite of low-code/no-code tools for curators and researchers.\n\n### 🛠️ Tool 1: Visual ETL Mapper (CSV-to-Linked-Art)\n\n- **Purpose:** Allows non-technical staff to map messy legacy CSVs to complex CIDOC-CRM event graphs.\n \n- **Features:** Node-link drag-and-drop canvas (ReactFlow). Users drag a \"Donor Name\" column and connect it to the transferred_title_from node in an Acquisition event.\n \n- **Reconciliation:** Built-in API calls to Getty AAT, ULAN, and Wikidata to reconcile string data into URIs before export.\n \n\n### 📝 Tool 2: Linked Art Form Builder (Middle-Tier Editor)\n\n- **Purpose:** A \"Goldilocks\" data entry form that looks simple but outputs strict JSON-LD.\n \n- **Features:** Vocabulary-driven input (auto-fetches Getty URIs). Uses pattern-based generation (e.g., user types \"Artist\", backend builds the produced_by → carried_out_by → Person graph).\n \n- **Validation:** Real-time domain-specific feedback (e.g., warns if an object's creation date predates the artist's birth).\n \n\n### 🕸️ Tool 3: Dynamic Graph Explorer (Interactive Debugger)\n\n- **Purpose:** A progressive-disclosure visualization tool for debugging dense Linked Art graphs.\n \n- **Features:** Force-directed layouts (Cytoscape.js). Drill-down expandability to prevent node-clutter. Contextual JSON inspector side-panel for developers.\n \n\n### 🧱 Tool 4: Reusable UI Component Library\n\n- **Purpose:** Abstracting repetitive JSON-LD traversal logic into plug-and-play React components.\n \n- **Components:**  (parses artist/technique),  (auto-mounts OpenSeadragon via digitally_shown_by),  (renders custody timelines).\n \n\n---\n\n## 🧠 3. Data Modeling & Semantic Patterns\n\nThe application strictly adheres to Linked Art patterns while addressing edge cases like uncertainty and contested histories.\n\n- **Activity/Event Pattern:** Direct relationships are avoided. Artworks are connected to Artists via a \"Creation Activity,\" allowing the attachment of Time, Place, and Technique to the event itself.\n \n- **Uncertainty & Contested Attributions:** Robust modeling for \"probably by X, possibly by Y.\" Utilizes the AttributeAssignment class to expand upon previous or contested attributions without breaking the primary graph.\n \n- **TimeSpan Pattern:** Implements begin_of_the_begin and end_of_the_end ISO 8601 timestamps alongside human-readable strings to handle approximate historical dates.\n \n- **Statement Pattern:** Uses LinguisticObject to capture nuanced curatorial notes and complex provenance narratives that cannot be fully structured into triples.\n \n\n---\n\n## 📊 4. Advanced Visualization & Discovery Suite\n\nTransforming complex Linked Art datasets into readable, interactive visual formats for analysis and presentation.\n\n- **Interactive Provenance Timelines:** Visualizing ownership chains chronologically. Includes visual indicators (shaded ranges/gradient bars) for timeline uncertainty.\n \n- **Geospatial Time-Sliders:** Maps tracking object movement across cities, exhibitions, and collections, animated over time.\n \n- **Faceted Browsing:** Search powered by Getty AAT classifications (medium, time period, style) with auto-suggest powered by alternate names and identifiers.\n \n- **Complexity Toggling (Art Tracks Model):** UI gracefully handles complexity. Shows basic info by default, with a \"See full scholarly details\" toggle for researchers.\n \n\n---\n\n## 🎓 5. Pedagogy, Storytelling & Accessibility\n\nEngineered to lower the barrier to entry for undergraduate students and the public.\n\n- **Narrative Storytelling:** Integration with frameworks like StoryMapJS to build multimedia narratives from Linked Art data.\n \n- **Pedagogical Scaffolding:** Pre-built modules (e.g., \"The Provenance of a Renaissance Painting\") to introduce students to linked data concepts.\n \n- **Export & Citation:** One-click exports to CSV (for Gephi network analysis), JSON-LD, and Zotero integration for seamless citation management.\n \n- **Multilingual & Inclusive Access:** Leverages the _label property and multiple Name objects for screen-reader compatibility and multilingual support.\n \n\n---\n\n## 🚀 6. Phased Development Roadmap\n\n### **Phase 0: Foundation & Standards (Weeks 1-2)**\n\n- Define strict Linked Art JSON-LD patterns (Creation, Acquisition, Exhibition).\n \n- Set up Docker infrastructure, Neo4j graph database, and API Gateway.\n \n- Establish GitHub Actions for automated SHACL validation.\n \n\n### **Phase 1: Core Data Engines & APIs (Weeks 3-5)**\n\n- Build the **Validation & Production Microservice** (Python/FastAPI + Crom).\n \n- Build the **Authority Reconciliation Microservice** (Getty/Wikidata API wrappers).\n \n- Develop the core ETL Transformation scripts for legacy data ingestion.\n \n\n### **Phase 2: Micro-Frontends & Tooling (Weeks 6-9)**\n\n- Develop the **Shared UI Component Library** (, ).\n \n- Build the **Visual ETL Mapper** (ReactFlow drag-and-drop interface).\n \n- Build the **Linked Art Form Builder** and **Dynamic Graph Explorer**.\n \n\n### **Phase 3: Assembly, UI & Pedagogy (Weeks 10-12)**\n\n- Develop the Next.js **Dashboard Shell** (Single Page Application).\n \n- Integrate the micro-frontends into the shell via Module Federation.\n \n- Build the public-facing discovery UI (Search, Timelines, Maps).\n \n- Implement Zotero exports, StoryMap integrations, and \"Student Mode\" toggles.","sections":[{"level":2,"heading":"⚙️ 1. Core Architecture & Technology Stack","anchor":"1-core-architecture-technology-stack"},{"level":2,"heading":"🧩 2. The 4 Core Modular Tools (Micro-Frontends)","anchor":"2-the-4-core-modular-tools-micro-frontends"},{"level":3,"heading":"🛠️ Tool 1: Visual ETL Mapper (CSV-to-Linked-Art)","anchor":"tool-1-visual-etl-mapper-csv-to-linked-art"},{"level":3,"heading":"📝 Tool 2: Linked Art Form Builder (Middle-Tier Editor)","anchor":"tool-2-linked-art-form-builder-middle-tier-editor"},{"level":3,"heading":"🕸️ Tool 3: Dynamic Graph Explorer (Interactive Debugger)","anchor":"tool-3-dynamic-graph-explorer-interactive-debugger"},{"level":3,"heading":"🧱 Tool 4: Reusable UI Component Library","anchor":"tool-4-reusable-ui-component-library"},{"level":2,"heading":"🧠 3. Data Modeling & Semantic Patterns","anchor":"3-data-modeling-semantic-patterns"},{"level":2,"heading":"📊 4. Advanced Visualization & Discovery Suite","anchor":"4-advanced-visualization-discovery-suite"},{"level":2,"heading":"🎓 5. Pedagogy, Storytelling & Accessibility","anchor":"5-pedagogy-storytelling-accessibility"},{"level":2,"heading":"🚀 6. Phased Development Roadmap","anchor":"6-phased-development-roadmap"},{"level":3,"heading":"**Phase 0: Foundation & Standards (Weeks 1-2)**","anchor":"phase-0-foundation-standards-weeks-1-2"},{"level":3,"heading":"**Phase 1: Core Data Engines & APIs (Weeks 3-5)**","anchor":"phase-1-core-data-engines-apis-weeks-3-5"},{"level":3,"heading":"**Phase 2: Micro-Frontends & Tooling (Weeks 6-9)**","anchor":"phase-2-micro-frontends-tooling-weeks-6-9"},{"level":3,"heading":"**Phase 3: Assembly, UI & Pedagogy (Weeks 10-12)**","anchor":"phase-3-assembly-ui-pedagogy-weeks-10-12"}],"html":"

🏛️ Art Explorer: Linked Art Application & Ecosystem

\n

Comprehensive Technical Features & Architectural Design Plan

\n

Project Overview: A full-stack, microservice-driven Linked Open Data (LOD) ecosystem designed to bridge the gap between rigorous digital humanities research, museum data infrastructure, and undergraduate art history pedagogy. Built strictly on CIDOC-CRM and Linked Art JSON-LD standards, this platform solves industry-wide challenges regarding legacy data mapping, uncertainty modeling, and semantic web accessibility.

\n

---

\n

⚙️ 1. Core Architecture & Technology Stack

\n

The system utilizes a decoupled, API-first architecture combining microservices for heavy data processing with micro-frontends for modular user interfaces.

\n
  • Backend / Data Layer (The Engine):
\n
  • Primary Language: Python (FastAPI) & Node.js.
\n
  • Graph Database: Neo4j or Stardog (native RDF/Graph storage) + PostgreSQL (JSONB) for application state.
\n
  • LOD Libraries: Crom (Python) for Linked Art instantiation, PyLD for JSON-LD framing/compaction.
\n
  • ETL Orchestration: Apache Airflow or Dagster for tracking data lineage and provenance.
\n
  • Frontend / UI Layer (The Interface):
\n
  • Framework: Next.js 15+ (React) with TypeScript (SSR/SSG for SEO and performance).
\n
  • Styling: Tailwind CSS / Chakra UI.
\n
  • Visualization: D3.js, Visx, and Cytoscape.js (for force-directed graphs).
\n
  • Mapping: ReactFlow (for visual ETL mapping) and Leaflet/Mapbox (for geospatial).
\n
  • Infrastructure & CI/CD:
\n
  • Docker containerization for isolated microservices.
\n
  • GitHub Actions with automated SHACL validation scripts to ensure data integrity.
\n

---

\n

🧩 2. The 4 Core Modular Tools (Micro-Frontends)

\n

To solve the "skills gap" in the GLAM sector, the application provides a suite of low-code/no-code tools for curators and researchers.

\n

🛠️ Tool 1: Visual ETL Mapper (CSV-to-Linked-Art)

\n
  • Purpose: Allows non-technical staff to map messy legacy CSVs to complex CIDOC-CRM event graphs.
\n
  • Features: Node-link drag-and-drop canvas (ReactFlow). Users drag a "Donor Name" column and connect it to the transferred_title_from node in an Acquisition event.
\n
  • Reconciliation: Built-in API calls to Getty AAT, ULAN, and Wikidata to reconcile string data into URIs before export.
\n

📝 Tool 2: Linked Art Form Builder (Middle-Tier Editor)

\n
  • Purpose: A "Goldilocks" data entry form that looks simple but outputs strict JSON-LD.
\n
  • Features: Vocabulary-driven input (auto-fetches Getty URIs). Uses pattern-based generation (e.g., user types "Artist", backend builds the produced_by → carried_out_by → Person graph).
\n
  • Validation: Real-time domain-specific feedback (e.g., warns if an object's creation date predates the artist's birth).
\n

🕸️ Tool 3: Dynamic Graph Explorer (Interactive Debugger)

\n
  • Purpose: A progressive-disclosure visualization tool for debugging dense Linked Art graphs.
\n
  • Features: Force-directed layouts (Cytoscape.js). Drill-down expandability to prevent node-clutter. Contextual JSON inspector side-panel for developers.
\n

🧱 Tool 4: Reusable UI Component Library

\n
  • Purpose: Abstracting repetitive JSON-LD traversal logic into plug-and-play React components.
\n
  • Components: <LinkedArtAttribution /> (parses artist/technique), <IIIFCanvasViewer /> (auto-mounts OpenSeadragon via digitally_shown_by), <ProvenanceStepper /> (renders custody timelines).
\n

---

\n

🧠 3. Data Modeling & Semantic Patterns

\n

The application strictly adheres to Linked Art patterns while addressing edge cases like uncertainty and contested histories.

\n
  • Activity/Event Pattern: Direct relationships are avoided. Artworks are connected to Artists via a "Creation Activity," allowing the attachment of Time, Place, and Technique to the event itself.
\n
  • Uncertainty & Contested Attributions: Robust modeling for "probably by X, possibly by Y." Utilizes the AttributeAssignment class to expand upon previous or contested attributions without breaking the primary graph.
\n
  • TimeSpan Pattern: Implements begin_of_the_begin and end_of_the_end ISO 8601 timestamps alongside human-readable strings to handle approximate historical dates.
\n
  • Statement Pattern: Uses LinguisticObject to capture nuanced curatorial notes and complex provenance narratives that cannot be fully structured into triples.
\n

---

\n

📊 4. Advanced Visualization & Discovery Suite

\n

Transforming complex Linked Art datasets into readable, interactive visual formats for analysis and presentation.

\n
  • Interactive Provenance Timelines: Visualizing ownership chains chronologically. Includes visual indicators (shaded ranges/gradient bars) for timeline uncertainty.
\n
  • Geospatial Time-Sliders: Maps tracking object movement across cities, exhibitions, and collections, animated over time.
\n
  • Faceted Browsing: Search powered by Getty AAT classifications (medium, time period, style) with auto-suggest powered by alternate names and identifiers.
\n
  • Complexity Toggling (Art Tracks Model): UI gracefully handles complexity. Shows basic info by default, with a "See full scholarly details" toggle for researchers.
\n

---

\n

🎓 5. Pedagogy, Storytelling & Accessibility

\n

Engineered to lower the barrier to entry for undergraduate students and the public.

\n
  • Narrative Storytelling: Integration with frameworks like StoryMapJS to build multimedia narratives from Linked Art data.
\n
  • Pedagogical Scaffolding: Pre-built modules (e.g., "The Provenance of a Renaissance Painting") to introduce students to linked data concepts.
\n
  • Export & Citation: One-click exports to CSV (for Gephi network analysis), JSON-LD, and Zotero integration for seamless citation management.
\n
  • Multilingual & Inclusive Access: Leverages the _label property and multiple Name objects for screen-reader compatibility and multilingual support.
\n

---

\n

🚀 6. Phased Development Roadmap

\n

Phase 0: Foundation & Standards (Weeks 1-2)

\n
  • Define strict Linked Art JSON-LD patterns (Creation, Acquisition, Exhibition).
\n
  • Set up Docker infrastructure, Neo4j graph database, and API Gateway.
\n
  • Establish GitHub Actions for automated SHACL validation.
\n

Phase 1: Core Data Engines & APIs (Weeks 3-5)

\n
  • Build the Validation & Production Microservice (Python/FastAPI + Crom).
\n
  • Build the Authority Reconciliation Microservice (Getty/Wikidata API wrappers).
\n
  • Develop the core ETL Transformation scripts for legacy data ingestion.
\n

Phase 2: Micro-Frontends & Tooling (Weeks 6-9)

\n
  • Develop the Shared UI Component Library (<LinkedDate />, <IIIFViewer />).
\n
  • Build the Visual ETL Mapper (ReactFlow drag-and-drop interface).
\n
  • Build the Linked Art Form Builder and Dynamic Graph Explorer.
\n

Phase 3: Assembly, UI & Pedagogy (Weeks 10-12)

\n
  • Develop the Next.js Dashboard Shell (Single Page Application).
\n
  • Integrate the micro-frontends into the shell via Module Federation.
\n
  • Build the public-facing discovery UI (Search, Timelines, Maps).
\n
  • Implement Zotero exports, StoryMap integrations, and "Student Mode" toggles.
","updatedAt":"2018-10-20T01:46:40.000Z","checksum":"e23b890ecd2a6791d3fe70d6da8b5ac136edbd0764df0e880b0ab3c3963449d4","checksumPrefix":"e23b890ecd2a","anchorCount":14,"lineCount":162,"rawUrl":"/api/docs/content?path=linked-art%2FLinkedArtAppFeatures.md","htmlUrl":"/docs?doc=linked-art%2FLinkedArtAppFeatures.md","apiUrl":"/api/docs/content?path=linked-art%2FLinkedArtAppFeatures.md"}