Last refreshed: 2026-07-06
Source: Linked Art Code and Tools resource list, with project-local summary and implementation notes. This is a project summary; the upstream resources remain authoritative.
Purpose
Linked Art has a small but useful ecosystem of libraries, platforms, validators, modeling aids, and data-cleaning tools. This page records the resources most relevant to Meta Museum so future implementation, validation, and evaluation work can choose from known Linked Art-oriented tools instead of starting from scratch.
Libraries
- Crom - Python library for working with resources as class instances with properties rather than directly manipulating a graph.
- LinkedArt.js - JavaScript library for working with Linked Art JSON.
- Linked.Art.Net - C#/.NET library for Linked Art.
Platforms
- LUX - open source implementation behind Yale LUX, a Linked Art-based cross-collection discovery platform.
- Arches - cultural heritage linked data management platform that can be used to implement Linked Art-oriented data systems.
- Ogee - Arches package from Getty that implements the Linked Art data model and vocabulary support for Arches-based deployments.
Documentation And Modeling Aids
- Zellij - semantic data pattern library with Linked Art patterns in a compositional, reusable format. Useful for learning the standard and generating derivative data management products such as queries, mapping templates, and display templates.
Validators
- Linked Art JSON Validator - online validation service using the official Linked Art JSON Schemas.
Visualization And Cleaning
- Simple Dynamic Modelling Linked Art example - dynamic data-model visualization with a Linked Art example.
- Mermaid Live Editor - diagramming tool useful for sketching model relationships and implementation flows.
- OpenRefine - data-cleaning and reconciliation tool for tabular collections data.
Meta Museum Notes
The most immediately useful resources for this project are the JSON Validator for quick external shape checks, LinkedArt.js for possible JavaScript-side inspection utilities, Crom for Python-based import/export experiments, OpenRefine for provider-data cleanup workflows, and Zellij for mapping-template or evaluator-facing pattern references.
Arches, Ogee, and LUX are better treated as architectural comparison points rather than dependencies. They are useful evidence that Linked Art can support production cultural heritage systems, but Meta Museum's locked stack stays Next.js, TypeScript, Postgres, Solr, and GraphDB unless the architecture decision record changes.
Test Ideas
- Keep validation notes linked to the official JSON Validator and local JSON Schema tests.
- Compare Meta Museum dataset/search surfaces against LUX-style cross-collection discovery expectations without copying platform internals.
- Use OpenRefine-oriented cleanup notes when provider mappings need reconciliation or normalization outside the app.
- Treat library adoption as an explicit dependency decision, not an implicit requirement from the resource list.