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

gbif:recordedByID #34

Closed
dagendresen opened this issue Apr 7, 2020 · 7 comments
Closed

gbif:recordedByID #34

dagendresen opened this issue Apr 7, 2020 · 7 comments

Comments

@dagendresen
Copy link

Why were two new terms minted gbif:recordedByID and gbif:identifiedByID when Darwin Core already has two existing corresponding terms dwciri:recordedBy and dwciri:identifiedBy ?

... to enable concatenating IDs separated by pipe | ?

@timrobertson100
Copy link
Member

timrobertson100 commented Apr 7, 2020

A couple of reasons.

Firstly, the IRI terms aren't compatible with the simple Darwin Core (i.e. a CSV with a header row) or the way the IPT provides data mappings in the schemas as neither are namespace-aware and you get collisions on the labels.

Secondly, the IRI terms are intended to resolve to a non-literal object and used in RDF. Here, like you note the new terms allow multiple identifiers, which may or may not resolve or be IRIs.

It is also the case that many typical search APIs have been developed with Darwin Core fields, again ignoring the namespace to be intuitive. The GBIF API is one of them, and extending it to allow e.g. &recordedByID=... is intuitive to users.

There are related discussions here and here and both terms were proposed for inclusion to Darwin Core before being added to the GBIF namespace. They can move namespace in the future of course.

@timrobertson100
Copy link
Member

Closing due to inactivity, please reopen for further discussion/change requests etc.

@Archilegt
Copy link

@timrobertson100 , why the term identifiedBy is not appearing anymore in the advanced version of GBIF Occurrence search? Please, bring it back, I need it.

@MortenHofft
Copy link
Member

MortenHofft commented May 28, 2020

@Archilegt identifiedBy has never been part of the API or the interface as far as I know. I might be mistaken, but it must be many years ago if so.

IdentifiedById was added recently and is still available in api and interface

@Archilegt
Copy link

@MortenHofft , maybe I got confused with an identifier that is often misrecorded in datasets as collector: Karl Kraepelin. I do remember seeing at least three spellings of Kraepelin's name in a recent search, I just don't remember the parameters. As he is primarily an identifier, I thought that the field disappeared from the options. Then my request would be: Please, made the field "identifiedBy" available in the advanced search.
P.S.: The newly added recordedByID field displays properly in the English interface but in the Spanish interface it displays with the same label than recordedBy: both read "Registrado por". So it looks like a field replication even when it is not. It should read "Registrado por ID". The newly added identifiedByID displays as "Identificado por" but it should read "Identificado por ID".

@timrobertson100
Copy link
Member

Thanks @Archilegt (and @MortenHofft)

I've logged the feature request here and we'll fix the translations too. Thank you.

While that is open, a workaround might be to download the data in Darwin Core Archive format to see the identifiedBy values.

@Archilegt
Copy link

@timrobertson100
Many thanks! I hope that everything is going well in CPH!
Kind regards,
Carlos

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

No branches or pull requests

4 participants