Change wording used by the system when downgrading an observation to an higher level taxa

I’m one of some :)

but really, as long as you have considered all viewpoints and then formed your own position with those considered, and then apply that position fairly and considerately, what more can anyone expect!


I think as you have done in some of these cases, asking observers if they have excluded confusion species is a good way to start. If they haven’t even heard of the confusion species because it’s not shown in field guides (or don’t respond after a reasonable period), then rolling it back to genus makes sense. Then someone who really knows the species - if they turn out to be at all possible to distinguish from photos - can comment and move the ball forward again in the future. If observers feel strongly their ID is right, they should be ready to explain why (or, less ideal, they can always opt out of community ID for that observation).


Thanks to everyone who contributed thoughts here. We’ve discussed this at length internally this week. There’s no question our past communication about this has been poor and inconsistent as was our understanding of how people ‘disagree’. We just fixed a few bugs and posted a blog post that tries to clarify how things are working now and lays out a plan for how to improve things

There’s a lot of other threads relevant to this topic. Should I chime in on those with a link to the post, or do you think people will find it via this thread?


i think the proposed solution in the blog post could be just as potentially confusing as the current implementation. in your blog example, suppose B’s ID comes after everyone else’s IDs. so A says it’s 7-spotted while C,D, and E say it’s Asian. when B makes his class-level Insecta ID, suppose all he knows is that’s not 7-spotted, though it might be Asian, Lady Beetle, or some other insect. What disagreement choices will the system prompt him with after the proposed change has been implemented?

In the example you describe, the Community Taxon would be Asian Lady Beetle before B’s ID

So if B thought its not Seven-spotted but maybe Asian, he should not disagree with the Community Taxon.

But if B were to add an ID of Insects, the disagreement choices would be in regards to Asian Lady Beetle (not Seven-spotted Lady Beetle). In this example, neither would immediately impact the Community Taxon, but a ‘branch disagreement’ would add some additional disagreements to taxa like ‘Lady Beetles Family’ and ‘Seven spotted Lady Beetles’

while a ‘leading disagreement’ would not

so B would ‘branch disagree’ if they though the observation couldn’t be identified finer than Class Insects and would ‘leading disagree’ if they thought it was not Asian Lady Beetle but could be some other insect

1 Like

Extreme disappointment from me on this… I read it as saying “experts” should be bumping CID back if THEY can’t id, which to me goes against the whole concept of community ID. You may as well implement a reputation system…

1 Like

Thats why were planning the changes @kiwifergus - its now clear to us that ‘leading disagreements’ are more commonly used and less controversial than ‘branch disagreements’.

All we’re saying is that since we originally built ancestor disagreements (both when it was implicit and then explicit) the system has been interpreting them as ‘branch disagreements’ based on how the Community Taxon is tallying ancestor disagreements. (and obviously we did a very poor job of communicating this as all the ongoing confusion has demonstrated)


in your blog example, are the titles of the Leading Disagreements and Branch Disagreements diagrams correct? (if they’re wrong, i think that explains some of my confusion.)

They are as far as I can tell. Can you point out whats confusing you?

here’s what i’m looking at:

three things that confuse me:

  1. the highlighted text talks about branch disagreement, but the diagram is labeled leading disagreement
  2. what’s the difference between community taxon and observation taxon?
  3. if the leading disagreement diagram is correct, if at the time B makes the Insecta ID, the only other ID is A’s 7-spotted, how does the system determine that the observation taxon is Lady Beetle (family) as opposed to Coccinella (genus) or Beetles (order)?

ah - good catch. I had the Figure 15 where Figure 16 should have been and vice-versa. I just fixed them. Thanks for catching that and apologies for the confusion

ok. that addresses confusing thing #1, but what about #2 and #3?

re: #2, I added this to the first section of the blog post to clarify:

In contrast, the Observation Taxon is the finest ranked taxon with at least one agreement that has no disagreements. The Observation Taxon will match the Community Taxon if: (a) there are no taxa with agreements and no disagreements finer than the Community Taxon, or (b) the taxa with agreements an no disagreements finer than the Community Taxon is of rank subspecies. If the observer opts out of the Community Taxon, the Observation Taxon will always be the Observer's identification.

re: #3, in the cartoon taxonomy there is no genus or order, just family. But the observation taxon is the finest taxon with at least one agreement and no disagreements, so if there were other nodes like genus in the taxonomy finer than Lady Beetle Family with no disagreements the observation taxon would be set to that

sorry for the confusion

i don’t like the proposed behavior re: #2 and #3. suppose our example taxonomy does include genus and order. in your Leading Disagreements example then, i would assume the Observation Taxon would be Coccinella after B’s ID. what if B knows it’s not Coccinella? how does B disagree with that genus? does he have to disagree twice? (once to get it to genus, and then again to disagree with the genus?)

i think it would make more sense for the observation taxon after B’s ID with Leading DIsagreement to be Insecta.

If I am reading it correctly, just disagreeing to family with the new option would achieve what you are asking.

no, in my interpretation / modification of the example, B was sure it was not 7-spotted, but thought it could be another lady beetle or another insect. if he IDs family and disagrees at that level, that doesn’t take into account the other insects he thinks it could be.

here’s a more real-world example that i deal with frequently. i monitor the genus Pisum (peas) worldwide. a lot of people around the world will classify any member of family Fabaceae (legumes) as Pisum or even any plant that vaguely resembles a legume as Pisum sativum. Fabaceae has subfamilies, tribes, and genera defined in iNaturalist’s taxonomy. there are only two species within Pisum, and they are fairly distinctive. a lot of the time, i’ll be able to tell the plant is not genus Pisum, but i won’t be able to tell you if it’s even Fabaceae or not because i don’t know every plant in the world. in the current system, most of the time in such a case, i’ll just leave a comment saying it’s not Pisum. i might make a suggestion based on similar looking plants in the area, but i won’t make an ID because i don’t want to do a “branch disagreement” up to Dicots (class Magnoliopsida). (if i do a branch disagreement up to Dicot, i’ll just have to come back and remove it after someone makes a better ID.)

the proposed “leading disagreement” option offers a potential solution, but according to @loarie’s explanation of how they plan to implement it, if the existing ID is species Pisum sativum and i ID as Magnoliopsida with Leading Disagreement, the effect of that will be that the Observation Taxon goes to genus Pisum, even though i know very well it’s not Pisum. so effectively, the solution is ineffective at best and makes things even more confusing at worst.

if they implement “leading disagreement” in the way that i say makes more sense to me, if i ID as Magnoliopsida with Leading Disagreement, then after my ID, the Observation Taxon will go to Magnoliopsida. in either case, if you come later and ID as genus Vicia, then i believe the Observation Taxon will go to tribe Fabeae, which is fine. but in the period between my ID and yours, i would rather the Observation taxon show as Magnoliopsida rather than Pisum.

or consider that Observation Taxon is Pisum after my ID, and you disagree with it, too. You ID as Magnoliopsida because you’re not sure what it is either. what does the system present to you to disagree with? does it ask you if you disagree with species Pisum sativum? does it ask you to disagree with a non-existent genus Pisum ID, or does it not offer a chance to disagree because your ID is the same as mine (even though the Observation Taxon is at genus)?


Unless I am reading something wrong, I don’t think this is correct. In this case, your leading disagreement would bump the community ID to Magnoliopsida (provided there are not more than 2 agreements at species level, of course.)

1 Like

yes, the Community Taxon goes to Magnoliopsida, but the Observation Taxon goes to Pisum according to my reading of @loarie’s diagram and comments.

I don’t think Observation Taxon really matters, though (I’ve always been confused as to its purpose/function). Community Taxon is what shows up in the data and in searches, as far as I am aware.

no, observation taxon is what shows up on the observation header. community taxon is what shows up in the little community ID box. you can see this when someone rejects the community ID.

1 Like