i can see this as being useful the first time you look at a particular set of observations – say, by a particular location or by a particular taxon – but what happens if you look at the same set a week later to look for new disagreements?
for example, if there were 15 observations with disagreements found the first time and 16 found the second time, is there a good way to figure out which observation has the new disagreement?
i know that there is the reviewed flag that can be used, but what if the new disagreement happens on an observation that you’ve previously reviewed? or what if you didn’t mark all the observations as reviewed the first time you went through them? is sorting by date updated the best way to sort of get an idea of what might be new?
i’ve been using my own thing to periodically find disagreements in my area (based on GET /v1/identifications in the API). I think it handles that sort of maintenance workflow well, but it’s always been limited by its inability to filter by observer and project (since it’s not possible to filter identifications by observer or project, although it handles taxon and place just fine).
i like the fact that the new disagreements filter parameter on observations can be used with tons of other filter parameters (including observer and project), but i’m having a hard time visualizing a good workflow for using it to periodically find new disagreements in a set of observations.
i think the only reliable way to do exactly this is to search identifications, not observations. for example: https://jumear.github.io/stirfry/iNatAPIv1_identifications?per_page=100&disagreement=true&observation_taxon_id=47157&taxon_id=514918&observation_lrank=complex. however, this method comes with some of the limitations that i mentioned above.