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 taxa filter on project observations search #204

Closed
loarie opened this Issue Dec 13, 2013 · 2 comments

Comments

Projects
None yet
2 participants
Contributor

loarie commented Dec 13, 2013

Problem:
An expert on an obscure group of beetles starts a project. All of these observations in her project have observation.taxon_ids of 'beetle' because the owner doesn't know what they are (and the soon to be community_id #88 is also 'beetle' because the community also lacks expertise in this group). But the expert has ID'd all of them all to species.

Within the project,the curator would want to filter these observations and explore them based on her curator_ids. This is currently not possible.

Solution:
I propose that we add a 'curator ID' setting to the project observation search UI (analogous to how muir proposed we deal with owner ids vs. community ids #88).
screen shot 2013-12-13 at 2 24 13 am
Under this setting, a search for a taxon would return all obs where:
obs.quality_grade = research AND obs.community_id = taxon AND obs.project_obs.curator_id = nil
OR
obs.project_obs.curator_id = taxon
in other words, the curator ID would override the community ID. Thus a search on 'bear' would return these 4 observations:
screen shot 2013-12-13 at 2 27 20 am
Also, just as we have a search filter for the curators to filter observations they've curated:
screen shot 2013-12-13 at 2 27 29 am
it would be very useful to be able to search for observations where curator_id exists & curator_id != community_id, so curators know where there expertise might be needed to settle disagreements
screen shot 2013-12-13 at 2 27 33 am

Owner

kueda commented Dec 16, 2013

I don't love this, since it just adds further clutter to the sucky, cluttered observation filtering interface, and all OR queries are slow, but whatever, if you think a handful of project owners will benefit, I don't think the rest will even notice.

Contributor

loarie commented Sep 29, 2015

decided not to do this

@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