chin-rcip / collections-model

Linked Open Data Development at the Canadian Heritage Information Network - Développement en données ouvertes et liées au Réseau canadien d'information sur le patrimoine
Creative Commons Zero v1.0 Universal
12 stars 1 forks source link

Issue #3 - Handling Sources #3

Closed chin-rcip closed 4 years ago

chin-rcip commented 4 years ago

Philippe Michon 8:34 AM We are currently managing the sources on each statement. In other words we can't say that all these statements are done by this insitution. This is something possible but I don't know exactly how for the moment. We could probably use a CIDOC CRM extension or named graphs. We still need to investigate. I think both approaches are working but we need to decide based on the performance (option 1 creates a lot of triples) and the easier querying process of the more specific sources statements.Also, it's important to include AiC as a source so perhaps we are going to manage two sources for the AiC records (AiC and the provider). To discuss.

Stephen Hart 2 months ago Indeed, as now I think more about it, with our model it is easy to know where an information comes from, but it is verz difficult (if not impossible) to query all the information from just one institution, as it is fragmented into the model. That is a serious question, as to what our model is for. Would it be like in libraries, to search information in specific institutions )for example I jsut want to look the data from the museums in Montreal); or is it more like wikipedia, where all the information is gathered and linked together to add more knowledge?

Philippe Michon 2 months ago We could probably reconstruct the record by querying all the p140 and p141 values of e13 events of a specific e39. Also we would have to use the e55 (CIDOC CRM property type) on the e13 to identify the right property. Long shot you will say, I know.

Stephen Hart 2 months ago To complicate things,as we discussed with Philippe this morning, there is also the possibility to have Named Graphs, which is a way to add meta data to parts or the whole data graph of MiC. With Named Graph, we could name and expression the source of the data from each museum. The problem is that neither me nor Philippe knows how Named Graph could be modeled, and if it would complicate the queries. I'll work on that. If we would use Named Graphs, that would replace the E13 solution for sourcing (otherwise that would complicate the model for no new information)

chin-rcip commented 4 years ago

Named graphs have been implemented in the v1.5 of the TM