Duplicate observations seen while doing ID's in Moth Week 2022 Project

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): iMac

App version number, if a mobile app issue (shown under Settings or About):

Browser, if a website issue (Firefox, Chrome, etc) : Safari 15.5

URLs (aka web addresses) of any relevant observations or pages: https://www.inaturalist.org/observations?page=2&place_id=1&project_id=135055&quality_grade=needs_id&verifiable=any

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.):

This issue was noted numerous times starting on the evening of July 26 and continuing through evening of July 27. Groups of observations appeared twice - separated by other observations. On evening of July 26 there appeared to be some “reset” that removed some of the duplicate observations and the total number of observation and observations “Needing ID” decreased.

Step 1: go to https://www.inaturalist.org/projects/national-moth-week-2022

Step 2: on the circle showing observations click on the yellow portion (“Needs ID”)

Step 3: say observations that repeated either in another area of that page or on another page. These observations had the same reference link (e.g. https://www.inaturalist.org/observations/128202694) and any action taken was saved and could be seen by clicking on either copy of the observation.

I see this duplication thing happen when I look in the explore page, regardless of the project, for many many months now. I believe this issue was pointed out in the past.

2 Likes

https://forum.inaturalist.org/t/observations-displayed-multiple-times-when-scrolling-in-grid-view/504

3 Likes

Yeah, it’s a known bug. Refreshing the page often fixes it. I’m going to close this bug report.