-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Terminology sources that share a prefix cannot be identified #29
Comments
Possibly due to multiple terminology sources sharing a URI prefix, in this case |
@EnnoMeijers will try to figure out if we can distinguish Other examples of shared prefixes include:
|
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: |
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: netwerk-digitaal-erfgoed/requirements-terminologiebronnen#5. |
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. |
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, 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.
The text was updated successfully, but these errors were encountered: