I have in mind a new feature/filter option for the platform.
As this would be a rather substantial addition, before putting this as a feature request I wanted to gather some feedback and suggestions.
The issue:
I would like to see iNaturalist becoming a better place for finding information about how to ID taxa.
– ‘But this is something that has been proposed so many times before’ I hear you say.
Indeed!
This comes up every other day in a forum comment that (apart from better onboarding) we need some information, e.g. on the taxa pages, about important ID features, about similar species to be confused with, having ID keys, a warning sign that this taxon is tricky,… etc.
But the thing with iNaturalist is:
It covers any organism, and worldwide!
Other websites and platforms, focused on a certain region and/or taxon group, can much easier prepare and curate such ID help pages.
But on iNat, you cannot simply walk go to a taxon page and expect to find information for your local area or find a key covering only the species of your region. To provide this information would be a herculean task for a small amount of curators, shouldn’t it remain merely a patchwork of few taxa covered. It would also require regular reviews, to update information or remove non-working links, etc. And it would need to be applied on the various taxonomic levels, e.g. covering the genus and all or a subset of downstream species.
A lot of work, while also not easy to access for non-expert iNat users.
But the cool thing is: so much information is already there on the platform!
IDers leave a lot of valuable information as comments under observations or explain ID features in journal posts. Alas, it is not easy to find currently.
Say, I want to ID a tricky hoverfly genus, and I know there were some expert comments provided under a bunch of observations. I could either reach out to those experts or go through observations of this genus one by one until I find something helpful:
My suggestion:
Have the option to mark observations containing valuable ID information, by implementing a second ‘favorite’ button. Something like this:
Thus, anyone can mark an observation as containing valuable information, and new filter options would be available (tick box and/or ‘sort by’ field):
Using the standard filter options (such as taxon & location) can be used to narrow down the search. The more votes, the higher ranked the observation will be.
For example, I photographed a hoverfly in France and the CV suggests several species from the genus Chrysotoxum. I could then filter for observations from France for that genus and check if any observation shows up that contains an ‘ID-vote’. If not, I might widen my search to Europe, or just draw a larger rectangle on the map.
Advantages:
-
With the simplicity of this voting system, it would be a low threshold for the community to participate and I expect that tons of valuable tips and links can be quickly put together this way.
-
It might also incentivize IDers to write more comments or even to publish more journal posts.
-
It also would make it easier – as leaderboards can be misLEADing – to find ‘true’ experts for a certain taxon in an area
The process of finding ID help via this filter is of course a bit of a hit-or-miss at times, but on the other hand you might find information that you didn’t expect to find and also something that is normally not found in standard ID keys and more focused on IDing of living organisms.
To have a certain degree of curation (e.g. when links are non-functional or information is outdated), and to counteract misuse, I am imagining curators having the rights to remove votes from an observation.
Also, I was thinking about possibilities to tweak and refine the system even more, by deliberately having observations stuck at a higher taxon level (e.g. Syrphinae or Ortotrichales mosses) via opting out of community ID, thus providing links and general (regional) information for higher taxa.
Lastly, the ribbon at the bottom of the observation page might also show (nearby) observations of relatives with ID tips.
So, instead of
We get this:
While I am not sure this is something that can easily be implemented, I think this would be an elegant solution to an oh-so-often requested feature and would smoothly fit into how the platform is already been used.
Curious to hear your thoughts!