Skip to content
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

NMVW redirect does not work #1407

Open
rschalkrce opened this issue Aug 8, 2024 · 5 comments
Open

NMVW redirect does not work #1407

rschalkrce opened this issue Aug 8, 2024 · 5 comments
Assignees

Comments

@rschalkrce
Copy link
Contributor

Thesaurus Nationaal Museum van Wereldculturen URI's are not displayed on the NMWV website when using 'Bekijk bij bron'.

E.g.: https://hdl.handle.net/20.500.11840/termmaster2670

Should probably be fixed by NWVW

@EnnoMeijers
Copy link
Contributor

Maybe related to the recent work on the NMVW collections @sdevalk or @GertjanFi?

@sdevalk
Copy link
Contributor

sdevalk commented Aug 9, 2024

Thanks! I'm not sure if this is related to the recent work on Wereldmuseum's collections, but I do know that the IRIs of terms in the NMVW thesaurus have been broken for several months now. By the look of things terms have been assigned new IRIs 😱. For example:

  1. If I search for "pantserdoorborende granaten" in the Network of Terms [1], then the IRI "https://hdl.handle.net/20.500.11840/termmaster19066" is being returned. But the IRI resolves to an HTML page on the museum's website with the message "No results found for your query."

  2. However, if I search for "pantserdoorborende granaten" in the museum's website [2], then two terms are being returned, including the term I'm looking for, "pantserdoorborende granaten". That term has the IRI "https://hdl.handle.net/20.500.11840/termmaster10067950". That IRI also resolves to an HTML page on the museum's website, but this time with the metadata of the term.

Note the difference between the IRIs: https://hdl.handle.net/20.500.11840/termmaster19066 versus https://hdl.handle.net/20.500.11840/termmaster10067950. The SPARQL endpoint on [3], unlike the SPARQL endpoint on the NDE data platform [4], contains the latest IRIs.

[1] https://termennetwerk.netwerkdigitaalerfgoed.nl/?q=pantserdoorborende+granaten&datasets=https://data.netwerkdigitaalerfgoed.nl/NMVW/thesaurus/sparql
[2] https://collectie.wereldmuseum.nl/thesaurus
[3] https://data.colonialcollections.nl/nmvw/thesaurus
[4] https://data.netwerkdigitaalerfgoed.nl/NMVW/collectie

@ddeboer
Copy link
Member

ddeboer commented Aug 10, 2024

@sdevalk So should we switch to the https://data.colonialcollections.nl/nmvw/thesaurus endpoint in the Network of Terms? It’s always welcome to move away from the NDE Triply instance, which after all was intended to be a temporary solution. 😆

While that would resolve the issue for future searches, it doesn’t solve the problem where collections have linked to NMVW terms using their old IRIs. Is it possible to introduce a redirect from the old to the new IRIs on the NMVW side?

Note that the NoT currently uses https://data.netwerkdigitaalerfgoed.nl/NMVW/thesaurus/sparql, which looks older but equivalent; not https://data.netwerkdigitaalerfgoed.nl/NMVW/collectie, which is much larger. As an aside, can https://data.netwerkdigitaalerfgoed.nl/NMVW/collectie be phased out in favour of https://data.colonialcollections.nl/nmvw/collection-archives or is the latter a different dataset altogether?

@sdevalk
Copy link
Contributor

sdevalk commented Aug 12, 2024

@ddeboer Good questions! I cannot answer them, though: I am no longer involved in the Colonial Collections project. @GertjanFi Could you have a look?

@GertjanFi
Copy link

GertjanFi commented Aug 20, 2024

First of all @sdevalk you are as much not involved as I am not involved and you know that very well 😝

@ddeboer I am currently working with @sdevalk and @EnnoMeijers to phase out both the NMVW thesaurus and NMVW collectie in data.netwerkdigitaalerfgoed.nl and migrate to data.colonialcollections.nl the switch willen happen soon. I have contacted @rschalkrce today to ask him to update termennetwerk to the new instance.

I am aware there have been issues in the past with the IRIs but was under the conviction that had been solved. Since @sdevalk and myself are currently no longer involved with the project (development efforts have been concluded) I suggest we take a look together and see what the problem is and figure out a course to solve stuff (and find out who). I'll get back to this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants