Thereâs no direct method that I know of, but you could create two separate projects. One for value X and one for value Y. Then you can either search by âincluded in projectâ or group them under an umbrella project to use as your overview or ID module.
Would be my approach, I think.
It doesnât work the same way as it does with place IDs or so. Sadly. (To the comment above// edit: itâs gone lol)
how does having this on the same page help you? it looks to me like âflower mineâ brings back 2 observations, and âstem mineâ brings back 1 observation. for such small sets, you could just do something like id=1,2,3, but there might be better options, depending on why youâre trying to do this.
observation fields are different from most other filter parameters. when i talked about doing something like id=1,2,3 thatâs using the observation id parameter, not an observation field parameter.
I might be able to tweak something I already have. Itâs a little app I wrote for fishing Lifelists. It allows you to toggle between different âfish observation methodsâ⌠which correspond to individual values for that observation field. If you hover over âmethodâ at this link, what itâs displaying is observations for each individual value for that obs fieldâŚ
I think this is kinda sorta close to what ur asking for. it makes u toggle tho. It also expects a project so Iâm just passing it the project for all of europe.
This was just an example really, If you want specifics I was trying to find out if this could be done before implementing a field that I could add to many observations (hydrozoa gonophore presence) to help filter out hydromedusae from hydroid colonies and their different levels of gonophore reduction, which is where the ability to search for multiple at the same time would be helpful. I would just add a simple âmedusoid or hydroidâ field but this would be inaccurate and would miss many edge cases.
This is a cool project! - but you could just change the inaturalist search URL between the multiple field values, similarly to this? Iâd really want to be able to use this in the identify page on iNaturalist tooâŚ
Hereâs another option (this one looks better on a pc than a phone). Iâd need to modify it to allow selection of different plant minesâŚ. Otherwise youâd need to Page through to find the mine youâre looking for to click on.
also ~ not sure what you mean by âuse this in the identify pageââŚ
iâm not sure i fully understand what youâre describing regarding edge cases, but if you have a field f that has only two possible values v1 and v2, then filtering for (f=v1 OR f=v2) would be equivalent to filtering for the presence of f. the syntax for that filter would be field:f.
if you need to also record and filter by level of gonopore reduction, then you probably should add a second field.
i donât understand this stuff, but it still sounds to me like you need 2 fields:
medusoid or hydroid
level of gonopore reduction
the way i think youâre describing things, the second observation field f2 essentially would be a subcategory of f1=medusoid.
so if you have the setup described above, you would be able to differentiate at a high level between medusoid vs hydroid using f1 and/or by a single level (range) of gonopore reduction using f2.
Yeah that makes more sense and is easier than any other workaround so far, having both a colloquial field and a specific field.
Still though there are observations with focus on both the medusoid and hydroid (i.e.), so a âmedusoidâ or âhydroidâ field would need a third option for âboth medusoid and hydroidâ, then youâre back to needing to search for two field conditions at once: i.e. âhydroidâ OR âboth medusoid and hydroidâ.
I still donât think it supports field:medusoid=yes and field:hydroid=yes for the third option for âboth medusoid and hydroidâ. but maybe iâm misreading something. thereâs no way to and the two obs fields together when they both have values of âyesâ.