Platform(s), such as mobile, website, API, other: Website (not sure how this would be possible on mobile)
URLs (aka web addresses) of any pages, if relevant: Any observation page
Description of need:
Many forum posts have covered new users not understanding captive/cultivated vs wild. It’s so common it’s in the Frequent Responses page at https://www.inaturalist.org/pages/responses#notwild . This page tells users HOW to use the DQA setting, but not when to use it. iNat’s captive/cultivated definition (the individual’s origin for plants, the individual’s current status for animals) is on a separate page, the Help page at https://www.inaturalist.org/pages/help#captive .
Feature request details:
It might be helpful if the DQA itself had a link to all the examples on the help page.
Mockups:
I would not want to see tooltips next to each DQA question. I suppose we could link to the FAQ page in that large info pop-up, but I wouldn’t be for it.
OK. I’d be interested in knowing a bit more about why. The confusion around this DQA question is persistent and consistent, with real implications for data quality - or at least it looks that way to me. It seems to me that this is about addressing an identified problem related to a specific aspect of the interface, not a precedent for hanging links off every toggle. I realize that you have insights into how things work that the rest of us mostly lack but I’m puzzled by the resistance to what seems like a simple enough step to help clarify a quirky feature.