Please fill out the following sections to the best of your ability, it will help us investigate bugs if we have this information at the outset. Screenshots are especially helpful, so please provide those if you can.
Platform (Android, iOS, Website): Website
App version number, if a mobile app issue (shown under Settings or About):
Browser, if a website issue (Firefox, Chrome, etc) : Chrome
URLs (aka web addresses) of any relevant observations or pages: https://www.inaturalist.org/observations/6422112
https://www.inaturalist.org/observations/5811820
https://www.inaturalist.org/observations/6593779
https://www.inaturalist.org/observations/6422112
Screenshots of what you are seeing (instructions for taking a screenshot on computers and mobile devices: https://www.take-a-screenshot.org/):
Description of problem (please provide a set of steps we can use to replicate the issue, and make as many as you need.):
Step 1: Observation is originally identified to species level, specifically Eulithis sp.
Step 2: A user disagrees with the species-level identification and provides a genus-level identification, specifically Eulithis.
Step 3: The Community ID is reduced to subfamily level, specifically Larentiinae. It should have remained at genus-level, specifically Eulithis.
Step 4: Community ID can be corrected by switching DQA votes on/off (re-indexing?). I have not done so (yet) for the above links so that you can see the issue.
Although this is easily resolved, I wanted to bring it up because I can’t imagine what the original cause may have been. There don’t seem to be any Taxon swaps involved, though even so, any disagreement between a species and the genus of that species shouldn’t reduce it to subfamily-level.