Explore: taxon search for particular locality finds out-of-scope taxa

Platform: Web

Browser: Firefox, probaby others too

Description of problem:

Step 1: search for subfamily or subtribe

Step 2: specifiy geographic area

Step 3: taxa of different subfamilies or subtribes are shown

Apparently a search for a subfamily finds taxa of a different subfamily of the same family:

https://www.inaturalist.org/flags/786946

Same with subtribes: taxa of different subtribe of the same tribe are shown:

https://www.inaturalist.org/flags/787685

https://www.inaturalist.org/flags/787684

https://www.inaturalist.org/flags/787683

1 Like

this is likely just an issue where the index didn’t get updated after some sort of change. i added and then removed a DQA metric flag on 2 of 3 observations noted in the link in the flag, and those observations no longer show up in the the results. these are very old observations, and i suspect the best course of action is just to do the same thing to the last observation, and then call it a day.

i didn’t look at the other flags, but you could also try seeing if you can force the observations to reindex to fix the problem in those cases, too.

3 Likes

If this seems to be affecting an entire species (or a lot of observations of one species), you can reindex all the observations by inactivating and reactivating the species.

2 Likes

The inactivating and reactivating doesn’t seem to work. Tried it with Celastrina neglecta, with a quite uneasy feeling (thousands of observations), and it’s still found when searching for the sister subtribe Lycaenopsina in the eastern U.S. (Celastrina is in Celastrinina).

Related to this above-mentioned flag: https://www.inaturalist.org/flags/787683

Edit: Apparently it did work with C. neglecta, but the search still finds Celastrina (probably cannot be inactived because it has children) and another species of the genus.

1 Like

Larger groups can take a few hours to reindex. Depending on how big the genus is, you can inactivate all the species to reindex the genus. Or you can reindex each observation individually.

That genus has around 30 species. Since this is probably a more widespread issue, by chance detected by two users who also reported it, there possibly needs to happen some general reindexing of the entire iNat taxonomy.

Yes it is fairly widespread. Staff said they fixed it years ago, and maybe it doesn’t happen anymore, but I’m not sure the old ones got fixed.

https://forum.inaturalist.org/t/limiting-and-scheduling-large-taxonomy-ancestry-changes/25486/7?u=thomaseverest

The confusion here is due to Celastrinina and Lycaenopsina being synonyms. Celastrinina has priority, though both names are widely used, and somehow both are now active on iNaturalist.

1 Like

Celastrina was only regrafted about a month ago (and the Celastrina observations left in a Lycaenopsina search included relatively recent ones), so this is still happening.

looks like Celastrina and Udara were manually regrafted last month from Lycaenopsina to Celastrinina (perhaps because those are the only two genera represented in the region covered by the Pelham Catalog?), but the job wasn’t finished by swapping the subtribe (in order to transfer the remaining genera and subtribe-level IDs); see this flag.