Carrie, here is a big "Case 1" example: When I was in the Jack-in-the-Pulpits dividing out the
Arisaema quinatum 5-leaved Jacks, I found this one plant photographed 8 times by 8 observers in a bio-blitz: (note all timestamps are between 11:50 and 12 noon)
https://www.inaturalist.org/observations/5089814 RG:3
https://www.inaturalist.org/observations/5089816 RG:4
https://www.inaturalist.org/observations/5089826 RG:3
https://www.inaturalist.org/observations/5089837 RG:4
https://www.inaturalist.org/observations/5089838 RG:3
https://www.inaturalist.org/observations/5089840 RG:3
https://www.inaturalist.org/observations/5090047 RG:3
https://www.inaturalist.org/observations/5091739 RG:4
(we have enough views there to generate a 3-D model and print one!)
So I had to pester a lot of people a lot of times to get those flipped into RG as the new species, esp. b/c many of the blitzers are no longer around...
Now, I'm reasonably sure the AI can't be asked to link these, b/c they don't all get a species level ID immediately, and that would be the only way to match them up...,
But we humans can certainly do this.
I'm imagining that a single user's single observation remains inviolate, but that if we see a blitz-like observation like this, we make a new "thing", a "pooled/group observation".
you hit a button, and enter a list of of observation #'s, and these are checked by the computer to ensure they are:
1) within a 1hr time span of the others in the group,
2) within a 50 meter (pick something) range (to account for GPS variances, like those is TX)
(There would also be a note "Please be SURE to link ONLY if you are certain this is the same physical organism")
Each observation (on iNat) would get an Is_member_of_Group=Group.id number (most would be empty)
When someone views an observation, they have a button to "See the Group Observation" this belongs to, that would go to a page showing all users who contributed to the observation, all the observed images on one page, with links to the member observations, and (if we got one added wrongly), a way to remove a member observation.
Another use of this Group Obs, could be for time-lapse growth observations. Take a new observation of a growing plant every day, and then you can add each subsequent new obs to your Grouped Obs, and then people could see the development over time.
We could also use this to solve the 1 user makes 5 observations of one thing, one image each, we add them all to a Group Obs, and they all get the community ID of the consensus of all IDs given each.