We need a proper, shareable URL for a given occurrence about gbif-alert HOT 5 CLOSED

Yes, I agree.

from gbif-alert.

From a user standpoint, we'll expose the GBIF ids (at least for occurrences) to the user (on webpage, URLs, emails, ...) rather than our internal IDs (which we will be necessary for technical reasons).

from gbif-alert.

Update: I asked more questions to GBIF about what we can expect from GBIF ids: gbif/pipelines#604

from gbif-alert.

Update: due to a higher risk of GBIFIDs changing (for example if the if the institution code gets updated), we're actually leaning to another solution: generation our own stable occurrence identifier by using a hash function that takes the datasetKey and occurrenceNumber as an input.

This is a different issue in itself, but one of the consequences is that it's that identifier that would be part if the URL for the occurence page. The GbifId field is important and should still be shown to the user, but not considered as a stable identifier.

from gbif-alert.

We now have this thanks to the stable_id field and associated mechanism.

from gbif-alert.