Mine appeared to be already set to Off, but based on the above conversation, I just turned them to On and then back to Off again, and Saved it.
Probably just doing the Save without toggling the switch would have the same effect.
Infrahybrids are below species in iNat’s hierarchy, but looking at your account settings from the back end I see that you have notifications for infraspecies IDs and Non-disagreeing Ancestor IDs turned on, so a notification for that ID is expected. If you want them turned off, your Notifications preferences page should look like this:
Only concern here is if a person has id’d to species level, and a expert id’s higher up (because it may be impossible to ID to species level from a photo), you may not get a notification, unless the expert leaves a comment.
I am not against the new notification rules. I think they do have place and merit. Identifiers must just note that they must leave a comment to draw the observers attention to it.
1 Like
If they believe it is not possible to ID to species level based on the evidence, they should be adding a disagreeing ancestor ID, and all people following the observation will be notified.
10 Likes
Interesting. I looked at them earlier today (after reading what cthawley said above) and they were set to off at that time, but you’re right–just now they say “on”. I will turn them off.
1 Like
This is an excellent addition! I hope word spreads about this. Adjusting your notification settings is the best way to maintain your sanity if you use iNaturalist often.
3 Likes
If you ID’d something as Genus species, and someone else adds an ID of Genus species subspeciesA, then Genus species gets split into Genus speciesA and Genus speciesB, the original subspecies ID isn’t a disagreeing ID. It depends on how the taxon split is committed, but if there’s only one expected subspecies in range, your original ID would probably change to match the expected subspecies. If there’s multiple subspecies possible in that area, your original ID might change to Genus speciesA/Genus speciesB, or maybe just Genus.
Either way, I don’t think a notification is ever going to be automatically generated by a taxon split
1 Like
Thanks, I’ve updated this FAQ.
1 Like
I was referring to the other situation:
I ID someting as Genus species, then someone else refines it to Genus species subspeciesB (that is, not the nominate subspecies).
It doesn’t matter if it’s the nominate subspecies or another named subspecies, the process will work the same either way.
Not the way I was thinking. If there is a species-level ID, followed by an ID as the nominate subspecies, then elevating the subspecies to a full species will not resuult in a species-level disagreement.
Whereas if there is a species-level ID, followed by an ID as a non-nominate subspecies, then elevating the subspecies to full species will result in a species-level disagreement.
Given your reply,
This is not a problem in the first scenario, but it is a problem in the second.
To use a real world example, say you photograph a bird and ID it as a Yellow-rumped Warbler Setophaga coronata. Someone else comes along and ID’s it as a non-nominate subspecies, Audubon’s Warbler Setophaga coronata auduboni. If the species is ever split into two species (which will most likely happen eventually), then your ID won’t automatically change to the nominate subspecies, (Myrtle Warbler, Setophaga coronata coronata). Depending on how the taxon split is commited, it’ll either be change to just a genus level ID, or automatically changed to Setophaga coronata auduboni, if the observation was within the breeding range of that subspecies. The only way there would be a taxon disagreement would be if you photographed it in the normal breeding range of the nominate subspecies, and that taxon split automatically changed your ID to the nominate subspecies.
1 Like