by 
0
0
GraphDB
I received some overly-aggressive sales emails from GraphDB after downloading a free version of the app which have kind of put me off from using them. Basically, when I downloaded the free version of the desktop app, someone in the sales department at GraphDB (which is apparently based in Bulgaria) used my name and registration email to look me up on LinkedIn and discovered I was working at the Whitney. This sale rep then emailed me suggesting a phone call with someone else on the GraphDB team, presumably so they could get me to convince the museum to buy a subscription. I basically told the guy I was in the very preliminary stages of my project, and that I had no budget for my project or say in the museum’s software/database system purchases, but that I would keep them in mind for the future. I assume these kinds of emails are typical with museum vendors, but having no personal experience with them, I was really taken aback.
Ontologies
http://erlangen-crm.org/ – CIDOC-CRM ontology mapped onto OWL; used at British Museum
Possible predicate properties for indicating provenance:
CIDOC-CRM doesn’t seem to have a lot of terms related to acquisition, so maybe it would make sense to stick to Joshua’s use of schema.org?
Person/Organization
https://schema.org/acquiredFrom
https://schema.org/sourceOrganization
https://schema.org/DonateAction
Next Steps
Next week – work on joining the object and acquisition-related constituents files in Python.
Join on Object ID/Constituent ID, presumably
Also work on MySQL stuff
Do acquisition-related constituents go into the Person table, or do Object-Related and Acquisition-Related Constituents get separated?
How to make more interesting:
Try to map onto Whitney Studio Club materials on DPLA: Would be cool to connect objects to paperwork related to their purchase.
