search

silknow / converter

SILKNOW converter that harmonizes all museum metadata records into the common SILKNOW ontology model (based on CIDOC-CRM)
Apache License 2.0
1 stars 0 forks source link

General: We need a property for sourcing the museum object in the Graph #45

Closed tschleider closed 4 years ago

tschleider commented 4 years ago

Currently, the museum is just retrievable by its named graph URI, but not as a direct property inside the graph. Once we replace the internal UUID generation from filename to internal museum ID we also need an information about the original JSON file name inside the graph.

pasqLisena commented 4 years ago

What about schema:publisher or dcterms:publisher or dcterms:creator attached to the E31_Document entities?

rtroncy commented 4 years ago

+1 for using schema:publisher or dcterms:publisher!

But why attaching this property to E31_Document? There is only the Joconde museum that seems to have instances of this class. I would attach it to the E22_Man-made_Object entity.

pasqLisena commented 4 years ago

Well, formally the museum is not the publisher of the E22_Man-made_Object but of the record describing it. It is surprising to me that there is no E31_Document in general.

rtroncy commented 4 years ago

You're absolutely right, the museum should not be the publisher of the E22_Man-made_Object but of the D1_Digital_Object which is materializing the record (French notice)

pasqLisena commented 4 years ago

Ah right, Digital Object!

tschleider commented 4 years ago

We now have a property dc:publisher attached to D1 objects pointing to the museums identified by http://data.silknow.org/organization/ + DATASET_NAME