We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In GitLab by @fred.lpo07 on Apr 6, 2021, 00:12
Data UUIDs are now available in the faune-france API, they should be used preferably if available.
path: item #>> '{observers,0,uuid}'
item #>> '{observers,0,uuid}'
The text was updated successfully, but these errors were encountered:
In fact, created UUID are stored in import.uuid_xref table. I am not sure this has been really used to transmit observations.
import.uuid_xref
The pseudo_id_sighting in observations table is an encoding of the sightings id: encode(hmac(NEW.id::text, '{{ cfg.db_secret_key }}', 'sha1'), 'hex').
pseudo_id_sighting
id
encode(hmac(NEW.id::text, '{{ cfg.db_secret_key }}', 'sha1'), 'hex')
I propose to :
Sorry, something went wrong.
mentioned in commit fd7f077
No branches or pull requests
In GitLab by @fred.lpo07 on Apr 6, 2021, 00:12
Data UUIDs are now available in the faune-france API, they should be used preferably if available.
path:
item #>> '{observers,0,uuid}'
The text was updated successfully, but these errors were encountered: