i could, but i’m not going to change this page, since every workflow is different, and different things are important to different people, and i can’t possibly handle every potential workflow. just for example, i mentioned earlier that cases where ID Taxa @ Desc(endant) > 1 (even where ID Count @ Obs > 0) could be a sign that there’s not a branch disagreement here. so for me, i would tend to open up those observations, too, to see what’s going on.
(you could also adapt my page or else code your own thing to do the additional filtering in a more automated way. even just extracting the results of my page into Excel so that you can sort records based on the various ID statistics might be enough to help you handle the manual filtering a little more efficiently.)
this may be true, but i kind of feel like when you try to find the last few percent of cases that might be interesting, you often end up jumping through hoops anyway. for example, even if your proposed parameter was implemented, you still wouldn’t be able to automatically filter for that case that i mentioned just above, where there is an improving Tabanidae ID that is not a branch disagreement. but scanning through the ID statistics on my page, you’ll be able to find those cases relatively quickly.
(if you extracted the observation IDs of interest from the results, you could always still use the Identify screen view that set of observations. for example, if you saw that obs IDs 104597268, 104028794, and 101923664 might be interesting, you could view them in Identify using this URL: https://www.inaturalist.org/observations/identify?id=104597268,104028794,101923664 .)