-
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
some records have no linkage, but id is a link #9
Comments
this happens with records imported from cordis/openaire, the record has an identifier (typically a DOI), but no reference to the item itself in Dublin Core a typical approach is to add link to the described item as a dcterms:reference (pycsw will pick it up if advertised in this way) suggestion is to add identifier also as a dcterms:reference |
the doi linkage has been added to the Cordis harvested records, @DajanaSnopkova can you verify this operates as expected? |
I am not sure, how to look only for Cordis records... But when I try to search by documents, for example this records' link: https://soilwise-he.containers.wur.nl/cat/collections/metadata:main/items/10.1002/2016WR020175 shows "Exception item not found". |
Hi @pvgenuchten, I tried to find documents from Cordis via a Sparql query Iin the read.me of the Cordis folder in the harvester: https://github.com/soilwise-he/harvesters/tree/main/cordis: PREFIX eurio:< I ran this at the endpoint: https://cordis.europa.eu/datalab/sparql-endpoint/en when I try some of the articles from the retrieved records: I can find a link for the records at the bottom of the detailed record: several have a working doi, but a second link that doesn't seem to work:
and I found one without a working link: |
randomly looking at other documents I find a link at the bottom of the detail of the record that doesn't seem to work. Does this mean they do not originate from Cordis and, if so, can we also add a link for these records? |
the problem you're pointing to is related to #10, we're going to solve it seperately |
some records extracted from DOI and ESDAC do not have linkage to a resource, however the identifier itself is a linkage to the resource
in such cases, the UI should display the identifier as a link,
however with the recent workaround the http protocol was stripped from identifier links, so you can't detect anymore if it is a link by evaluating if identifier starts with http
see for example https://soilwise-he.containers.wur.nl/cat/collections/metadata:main/items/esdac.jrc.ec.europa.eu/content/Soil_erosion_by_wind
The text was updated successfully, but these errors were encountered: