Research Grade with only one ID at that rank

Also, the community ID is still at genus-level. I think that’s what’s actually “research-grade”. It’s just that the observation’s ID is finer. It’s just that the page design isn’t built well for the uncommon situations when there’s a disconnect between the community ID and the observation ID.

1 Like

Somebody clicked “Yes, it can be,” cancelling out the “No.” Problem solved for this observation.

This is a well known problem – but sometimes it’s not a problem. If somebody ID’s an organism to subspecies and I add a species ID, it goes to RG with the subspecies name. That’s fine with me.

But if you look at “community ID” on those, I think it’ll only be “Research Grade” to species, not subspecies.

2 Likes

Yes, the CID determines Research Grade, but unfortunately it is the Observation ID that is sent to GBIF, not the CID. This means that observations can effectively be sent to GBIF with only one user agreeing on the more specific ID.

1 Like

We discussed this today. From my understanding as a non-engineer, a fix would probaby require a change to how the observation taxon and community taxon work, or even potentially just using the community taxon for both, which would also have its drawbacks. A change like that would probably require extensive reindexing, potentially of every observation on the site, so that they are evaluated and index according to this new rule, which would probably mean a downtime of several days. So it’s not a simple fix.

2 Likes

What if we changed this to work like the IDs do?
Either 2 agree.
Or simply 3 against 1 votes.

That might help to prevent confusion - why won’t this obs go to RG (because someone clicked Can Be Improved, or the the newbie used it to mean - my ID is as good as I can)

Instead of a single vote having such a major and disconcerting impact.

Since Community Taxon is clearly labelled as such. Perhaps the ‘Observation (display ID visible at the top) Taxon’ should have its own clear label to make it obvious that there are TWO different things there.

Especially since the 2 sometimes agree, and other times don’t. And either way RG is visually attached to the (wait there are TWO IDs?!) wrong one.

And it should generate a notification as Annotations and Observation Fields do. That would also help to make it clear to us what is happening to That Obs.