You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When checklists are developed, we would like all types of data to be considered for the development of checklists, including private and sensitive data.
It is not a problem for people to know that species occur in a park.
Our understanding is that currently when a checklist is made it does not include consideration of private and sensitive data. We want all data to be considered. i.e. if a species is only known from private or sensitive data then it should still be included on the checklist with the source specified.
People who do not have access to the private or sensitive data will not be able to see or download that private or sensitive data, but they should be able to see that that species occurs in a park. i.e. private and sensitive data setting should not affect inclusion of the species and the source in the checklist.
From SANPakrs:
We had a problem with it, and we had to change our data to public for it to be included in checklists. i.e. the only way sources were included in checklists was when they were public. Otherwise, they weren’t included.
The text was updated successfully, but these errors were encountered:
helendallas
changed the title
Private and sensitive uploaded sources being brought into the checklist csv
All Private and sensitive data plus public data sources should be used for creating the checklist csv and pdf
Nov 25, 2024
When checklists are developed, we would like all types of data to be considered for the development of checklists, including private and sensitive data.
It is not a problem for people to know that species occur in a park.
Our understanding is that currently when a checklist is made it does not include consideration of private and sensitive data. We want all data to be considered. i.e. if a species is only known from private or sensitive data then it should still be included on the checklist with the source specified.
People who do not have access to the private or sensitive data will not be able to see or download that private or sensitive data, but they should be able to see that that species occurs in a park. i.e. private and sensitive data setting should not affect inclusion of the species and the source in the checklist.
From SANPakrs:
We had a problem with it, and we had to change our data to public for it to be included in checklists. i.e. the only way sources were included in checklists was when they were public. Otherwise, they weren’t included.
The text was updated successfully, but these errors were encountered: