Read Time:1 Minute, 48 Second
More on the database/triple store issue
- objectJSONLD.py & artistJSONLD.py – script used to create JSON-LD files from CSV (using Python application PyLD)
- Is it better to just focus on the CSV files rather than the MySQL database?
- Either CSV files or SQL could be used to generate triples. Does it make more sense to just generate and host JSON-LD files, or continue Joshua’s dual PHP/JSON-LD method?
- Used to have a Google Refine plugin (seems to be dead now that Google Refine is OpenRefine)
Ontologies
Carnegie Museum
- Prof. Miller suggested looked at the Carnegie Museum’s modeling of provenance:
- I had previously looked at the visualization project they did related to this (http://hyperallergic.com/234563/carnegie-museum-of-art-makes-its-provenance-accessible-and-interactive/). Not sure if a similar idea would work for the Whitney, since the Founding Collection objects largely did not travel far from where they were made.
- Although CIDOC is more complicated to understand than the schema.org ontology, I am thinking it might make more sense for the Whitney, given that it is both the museum world standard, and that it has an event-based structure.
Modeling
- Prof. Pattuelli suggests diagramming attributes using Gliffy to allow for deeper analysis of whatever data model ends up being used, as well to provide a visual for how everything is set up. She provided me with the login info for Linked Jazz’s account.
Visualizing Provenance
- I’m thinking of doing a geotagging/geography related project based on some of the Linked Jazz data for Prof. Miller’s class, specifically constituent location data beyond place of birth/death. I would then apply similar methodology to Whitney acquisition-related constituents if successful.
- The Photographers’ Identities Catalog (PIC) project at NYPL is a good resource for looking at possible data sources to query for non-birth/death places, although many of these are not in linked data form.