Implement a new filter for observations that opt out of community ID

This has been discussed before, but I don’t think anyone has officially made a feature request for this. So here it is:

Please add a new filter for observations that opt out of community ID in both the Explore and Identify pages (and in the API wherever observations are the underlying item being returned). I don’t have any preference whether this operates as opt_out=true/false/any or exclude_opt_out=true/false. (The former would offer a way to search for opt-out observations only, but I’m not entirely sure how folks would use that except in ways that would potentially annoy folks who opted out.)

Also, in the Identify page, by default, filter out observations that opt out of community ID. (While there are legitimate use case for opting out, since opting out is in many cases effectively a “leave my observation alone” flag, I think a reasonable consequence is that opt-out observations should get filtered out by default in the Identify page, which is were many power identifiers go to make identifications. Identifiers could still search for opt-out observations by undoing the filter.)

I would note that changes to how the Explore page works aren’t currently being considered, as it’s already undergoing a revamp. This seems more like a request for a new parameter / API endpoint though, so I let it through.

Also, it may be best to split the discussion as to whether such a feature should be made default / sticky / etc to a linked thread.

I would prefer this to be a personal setting.
I’d rather not see any opted out obs. If the reasons are valid, I probably am unable to help move the ID forward. Would rather keep ploughing thru the thousands that need ID. And we are coming up to the Southern Bioblitz - when my Needs ID will explode

While acknowledging that some have good reasons, and do respond to discussion by opting in later.

1 Like

I think a lot of the mis-use (I’m not sure if that’s the word that I want) of the opt-out option comes from a misunderstanding of what it means, kind of like the amount of times that people mis-use the can or cannot be improved buttons, or the captive/cultivated button, or setting the location to private, or leaving the ID as unknown but putting an ID in the description, I think many of these are just from not understanding what those things mean.

I have seen several opt-outs that very clearly were “leave me alone” observations, but it would be a pity to ignore all of the ones that just made a mistake, and correcting them can at least send them on the way to being listed casual. And when people opt-out for a real reason like someone put a clearly wrong ID on an observation, they want it to go back into needs id in the hopes that more ID’ers will properly ID it, this would potentially make opting-out useless. I have only had to opt-out once, but it was useful to have it in the needs ID at a lower taxon.

1 Like

Observers with an opted-out observation that they think has been incorrectly IDed and want to fix could still solicit feedback from specific users with comment mentions (which is usually the best way to get observations like this addressed currently anyways) even if the observation isn’t appearing in the Identify results.

I’m definitely in favor of having this option exist and being “sticky” (so it remains in my Identify filters unless I manually change) though I’m ambivalent on having it being the default for all identifiers.

2 Likes

True, and I do recommend making use of tags, but with that you run into another problem of misunderstanding and that’s how to use the leader board, even people who show up in a leader board for a particular taxon/area may not be comfortable placing an ID.

I’m not against making this change, I’m just pointing out a potential problem of missing observations that weren’t “go away” observations.

1 Like

i wanted to start with a full description of where i thought this should ultimately go. if the iNat staff prefer to implement just the parameter in the API and allow URL filtering in Explore and Identify without any GUI / visual changes to those pages (perhaps following up with GUI changes later), then I’m okay with that.

i’m also okay if there ultimately are never any GUI changes in the Explore page, if that’s going to be the stumbling block. i think the main conflict that arises due to opt out between observers and identifiers can mostly be resolved by implementing GUI changes in the Identify screen only.

I think this would be fine as an option, but as has been pointed out, some opted-out observations should remain visible to identifiers. I would prefer that it not affect Identify by default.

1 Like

Well, our ids don’t change community taxon on such observations, so you can’t correct them, there’re other ways to get out of “ignorant” ids situation, and not letting community to say something isn’t the best one.

2 Likes