Please fill out the following sections to the best of your ability, it will help us investigate bugs if we have this information at the outset. Screenshots are especially helpful, so please provide those if you can.
Platform (Android, iOS, Website): WEBSITE (on Android tablet)
Browser, if a website issue (Firefox, Chrome, etc) : CHROME
Screenshots of what you are seeing (instructions for taking a screenshot on computers and mobile devices: https://www.take-a-screenshot.org/):
i canât explain why the string search doesnât bring back that observation, but if youâre trying to look for all beetles, searching by taxon seems like the better way to search.
In this case, I agree. But this isnât the only instance where expected observations donât appear in the search. It was just the best example to show the problem.
I canât remember off-hand, but there have been several occasions where I know Iâve got an observation for a particular species, do a search on a word in the common name, and nothing comes up. I thought I was doing something wrong at first, but when nothing came up for beetle, I knew something was wrong with the search. It may be that all of the incorrect searches involved the word âbeetleâ - I honestly canât remember. Iâll keep a more watchful eye out from now on to see if I can identify any other occurrences.
Hereâs more weirdness. My observation of the Common Shelduck shows up for âcomâ (but no other âCommonâ names appear in this search) but not for âcommonâ.
There are also many of my observations which have âCommonâ in the name but donât appear in the âcommonâ search. I stopped counting after 10 or so.
eg
Common Plume Moth
Common Starling
Common European Ambersnail
etc
q = Search query. Note that this is largely intended to be used on its own and may yield unexpected or limited results when used with other filters. If youâre trying to retrieve observations of a particular taxon, taxon_id and taxon_name are better options.
Allowed values: any string
in this case, you would be filtering by both your user_id and q, not q on its own. so it seems like this is a known behavior (that is unlikely to be changed), and if youâre trying to find a particular taxon, itâs better to filter by taxon, not a string.
someone could dig through the code to figure out exactly whatâs happening, but the queries that you provided examples for seem to be fundamentally taxon-based queries, and so i think you should just filter by taxon.
This is a pretty old page, and mostly to be used for the Batch Edit functionality. If you want to search through your observations and intending to batch edit them, I recommend clicking on Your Observations in the header and use the Explore page to search.