-
Notifications
You must be signed in to change notification settings - Fork 28
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
Make DwC term otherCatalogNumbers searchable #664
Comments
Multiple values Response format |
Multiple values Response format |
Regarding response format please see this comment #662 (comment) in short: to avoid a breaking change we should keep the response format a string. Even if it is searchable as individual values |
Deployed to PROD. |
It's crucial that the DarwinCore term otherCatalogNumbers (http://rs.tdwg.org/dwc/terms/otherCatalogNumbers) is made searchable.
Many institutions around the world are merging as are their cataloging systems. For many such mergers the adoption of a novel institution-wide catalog numbering system is not uncommon.
Legacy catalogue numbers ("alternate catalog numbers") are typically mapped to this otherCatalogNumbers field and many researchers/curators and collection managers can attest to the "old" numbers being referrred to in a large body of older literature.
Attempts at doing a free text search on an alternate catalog number has turned out to be problematic due to the stemming algorithm used by your systems. For instance search on old catalog number "ZMUC-R771281" on one of our datasets is fruitless, as you can see here:
https://www.gbif.org/occurrence/search?q=ZMUC-R771281&dataset_key=8c834f97-c5df-4280-9623-86594979f91a
In one concrete case, we are currently trying to persuade our own Botany department to migrate their data to Specify so this data can be shared via GBIF. They're currently limited to sharing data via JSTOR. It will be easier to convince them if we can show them that their legacy catalog numbers will remain useful to search on in this new data integration via GBIF.
The text was updated successfully, but these errors were encountered: