Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Make curator IDs override observation.taxon_id for generation of listed_taxa on project lists #205

loarie opened this Issue Dec 13, 2013 · 2 comments


None yet
2 participants

loarie commented Dec 13, 2013

For Lists, listed_taxa are generated from obs.taxon_id for all obs
For Checklists, listed_taxa are generated from obs.taxon_id for RG obs
After community IDs #88 are built, Checklist listed_taxa will rather be generated from obs.community_id for RG obs

For Project lists, listed taxa are currently generated the same way they are for lists. This creates a problem because its easy for bad IDs to generate errors in the project count, for example, if someone reports a penguin from a SF bioblitz project, a listed taxon for penguin is generated and counted based on obs.taxon_id

A partial solution would be to switch to generating listed_taxa from community IDs of RG obs (as in checklists), but a problem remains that if a project observation isn't research grade it won't be counted. For example imagine a SF bioblitz has obs representing 10 species of birds that were never photographed, the project list/count should reflect this if the project curators 'vouch for them'

Thus, I propose having project checklists generate listed taxa from (RG obs with community_ids AND no project_obs.curator_id) OR (obs with project_obs.curator_ids). The presence of curator IDs is a way project curators can override RG community IDs for things they want counted (or not)

For example, the following observations would generate 2 listed taxa
screen shot 2013-12-13 at 2 36 32 am


kueda commented Dec 16, 2013



loarie commented Sep 29, 2015

was done and then I believe undone by popular demand

@loarie loarie closed this Sep 29, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment