search

netwerk-digitaal-erfgoed / dataset-knowledge-graph

Pipeline that generates the NDE Dataset Knowledge Graph
European Union Public License 1.2
3 stars 0 forks source link

Terminology sources that share a prefix cannot be identified #29

Open coret opened 1 year ago

coret commented 1 year ago

I've made a Network visualization of the terminology sources used by datasets: https://data.netwerkdigitaalerfgoed.nl/coret/-/queries/kg-termen-netwerk/

In this network I see several datasets using KB's Brinkman Thesaurus, among others by the Gouda Timemachine ("13000" GTM). But, as can be seen by quering the source @ GTM)%0A%7D), the Brinkman isn't used by the GTM; thesauri NBT, DBNL and NTA (all KB) are used by the GTM.

I haven't checked, but I suspect other datasets aren't using the Brinkman either, but one (or more) of the other KB thesauri.

ddeboer commented 1 year ago

Possibly due to multiple terminology sources sharing a URI prefix, in this case http://data.bibliotheken.nl/id/thes/, which is shared between Brinkman, NTA and STCN. Unfortunately, for datasets that don’t have their own unique prefixes, it’s very hard to produce reliable results.

ddeboer commented 12 months ago

@EnnoMeijers will try to figure out if we can distinguish http://data.bibliotheken.nl/id/thes/ prefixes based on their p… identifier.

Other examples of shared prefixes include:

EnnoMeijers commented 11 months ago

I did some checking and there is no way to distinguish between the KB prefixes based on the 'p' identifier. The only option would be to do an additional query on the KB endpoint to find the specific source, something like this: select ?datasetName { ?thes_id schema:mainEntityOfPage/schema:isPartOf ?datasetName } But to do this for each KB link will probably be too expensive.

ddeboer commented 11 months ago

That‘s unfortunate. Then my proposal is to eliminate all prefix matches that match more than one terminology source, and keep only the prefixes that uniquely match a source.

That way we will lose data, but that may be preferable to providing confusing data, as described in this issue’s first post.

Additionally, however, I would like to add a requirement: https://github.com/netwerk-digitaal-erfgoed/requirements-terminologiebronnen/issues/5.

EnnoMeijers commented 11 months ago

Couldn´t we at least register the prefix without a further resolution to a specific source from a particular organization. In this way we could type Brinkman, NTA and STCN all as a subclass of a KB-thesaurus.