Step 3: The feed shows “Chipe Rabadilla Amarilla”, but the observation page shows “Chipe Coronado”. Note the inconsistency. I’ve seen such inconsistencies on other observations too. If you identify this bird and someone else later identifies it, it’ll appear in your feed.
Step 4: Look at the taxon page. “Chipe coronado” is crossed out.
I don’t know if this is a bug or a curation fault, so I’m flagging the taxon as well.
Yeah, seems like is_valid=false on the name in combination with position=1 is inconsistently implemented from page to page. The desired behaviour is for the lowest position number with is_valid=true to be chosen from the Spanish lexicon for Spanish users, which should be the next one down, but that one is at position=5so apart from it being marked invalid would not normally be shown in the title.
Therefore, apparently the pages where the OP is seeing the crossed-out name only consider the position and ignore is_valid
If I’m not misremembering, at one time we couldn’t mark common names invalid, only scientific names. I bet when support for invalid common names was introduced, some pages were simply overlooked.
As you say, it could be dragged down below other common names so it will never get selected, but I’ve left it as-is so devs can see the problem.
