Platform(s): NA, applies to the GBIF export and the GBIF search
URLs (aka web addresses) of any pages, if relevant: see below
Description of need:
On iNat, users are identified by their user id (unique, a number), their user login (unique, often a casual nickname), and their user name (not necessarily unique, often a real name). When iNat sends records to GBIF, they send the non-unique user name, which is searchable in the GBIF interface, for example https://www.gbif.org/occurrence/search?dataset_key=50c9509d-22c7-4a22-a47d-8c48425ef4a7&recorded_by=Tony%20Iwane. This field has some issues because user names are not unique (and also not permanent – users can change them). For example, https://www.gbif.org/occurrence/search?dataset_key=50c9509d-22c7-4a22-a47d-8c48425ef4a7&recorded_by=John%20Smith contains results for both cicadadayz and also sqeeaawk408, both with user name John Smith on iNat. A very small fraction of iNat users have set an ORCID, which makes their records uniquely tied to them, for example: https://www.gbif.org/occurrence/search?dataset_key=50c9509d-22c7-4a22-a47d-8c48425ef4a7&recorded_by_id=https://orcid.org/0000-0002-1096-6066. But outside the users with ORCIDs set, there is no unique, permanent field in GBIF to identify the observer.
Feature request details:
In the same field where iNat sends the ORCID (the DwC recordedByID term), please add the iNat user id. This field can take multiple values, so for most users, it would read something like https://inaturalist.org/users/28, and for users with an ORCID, it would read https://orcid.org/0000-0002-1096-6066 | https://inaturalist.org/users/1138587. If that were added, in addition to the already valid search
https://www.gbif.org/occurrence/search?dataset_key=50c9509d-22c7-4a22-a47d-8c48425ef4a7&recorded_by_id=https://orcid.org/0000-0002-1096-6066
you would also be able to use
https://www.gbif.org/occurrence/search?dataset_key=50c9509d-22c7-4a22-a47d-8c48425ef4a7&recorded_by_id=https://inaturalist.org/users/1138587
to find the same observations.
This would allow searches for observations by iNat users who have changed their user name, or who have a non-unique user name.
I think it’s rarer that people use the identifiedByID field (in part because it only holds the ID of the first identifier, not all identifiers), but it would be reasonable to also populate this field at the same time.
Why this rather than asking GBIF to honor the existing inaturalistLogin field?
As discussed in this earlier thread, iNat already exports the user login as foaf:nick (inaturalistLogin), but GBIF doesn’t currently ingest that term. The natural “ask GBIF to add foaf:nick support” approach has two problems compared to populating recordedByID:
- Logins are mutable — users can change their iNat login, the numeric user id never changes.
recordedByIDalready works end-to-end in GBIF — parsing, faceting, and search are all live today. Adding the iNat user id to that field requires no coordination with GBIF.