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

Distinguish observations from managed individuals #225

Open
damianooldoni opened this issue Apr 24, 2023 · 2 comments
Open

Distinguish observations from managed individuals #225

damianooldoni opened this issue Apr 24, 2023 · 2 comments
Assignees

Comments

@damianooldoni
Copy link
Collaborator

This feature was a feedback of a user during the meeting of Apr 20.
I think it's a valid request: managers are sometimes not interested to have information on already managed animals/plants. Or at least they would like to know if it is an observation or a captured animal/eradicated plant.

Of course, the challenge is mapping: do all GBIF datasets containing management information map management in the same way? Probably not. WIthin LIFE RIPARIAS we should try to be consistent. Notice that we use the field samplingProtocol, see https://github.com/riparias/vmm-rattenapp-occurrences/blob/ae0926997e9a01e66dbf9a62f4bc7d0f112e07b3/sql/dwc_occurrence.sql#L16-L20

@mcoupremanne showed also interest in such way of mapping and was going to implement it for Wallonian data: am I right, @mcoupremanne?

For this reason, we should think about:

  1. adding samplingProtocol to the observation page
  2. thinking about a selector for samplingProtocol

Any other idea is welcome.

@niconoe
Copy link
Member

niconoe commented Apr 24, 2023

Yep, same idea than #43: there is no technical difficulty to display the observation status (managed or not), and add filtering for this, but if we want that to be effective the experts and data publishers should first agree and implement non-ambiguous rules and vocabularies so a dumb computer can immediately make the distinction.

Once this is done, I suggest that you assign me the issue so I can implement it in the alert tool!

@mcoupremanne
Copy link

Hi ! Indeed still in about fixing this important point! I only have one issue : raw exports I receive include both managed populations and survey points on which the species is just absent (they look for it but do not find). With some sources I can make the distinction, but not with most of them (CRS I think). Most of the records are captured when surveying sites or already managed populations, with no infos about the actions taken.
So not sure that the info will be disponible for all records but it's worth a try. Should we could go for a structure like this ?

Case OccurrenceStatus SamplingProtocol
survey site with no observation 'absent' 'site survey'
species observed, not managed 'present' 'site survey'
species observed, managed 'present' 'eradicated'
revisiting a managed population, no return 'absent' 'eradication survey'
revisiting a managed population, species came back 'present' 'eradication survey'

@niconoe niconoe self-assigned this Oct 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants