yeah… i don’t totally understand what’s going on with the preferred places for common names. i would have expected that the preferred places would apply only within the context of a particular language (and this seems to confirm that this should be the case: https://forum.inaturalist.org/t/how-to-add-a-common-name-to-a-taxon/9792), but that may not be true. i don’t have curator access to the taxon setups though. so it’s hard for me to see exactly how the taxon names are set up to understand this issue better.
here’s an example of something that seems odd to me. i’ve set my language to English, and the names place to China. i would have expected all names to be English, but i see some that are in Chinese, such as Pomacea maculata. it’s almost as if the preferred place name is applied regardless of which language is selected (perhaps to address the use case mentioned here: https://forum.inaturalist.org/t/run-job-to-associate-translated-common-names-to-places/3964):
i don’t understand the strange taxon page header for your example either. for English + China, this is what i see:
…
if it is intentional to allow preferred place to drive names regardless of language selected, then i think this should only be the case when name is associated with a language for which the system has not been translated. in other words, find the appropriate name based on this logic:
- is there a name in a language that the system has not been translated into which matches the user’s preferred place? if yes, then use that; if no, then go to 2.
- is there a name set up for the user’s selected language? if yes, go to 3; if no, then return the scientific name.
- is there a name for the selected language and place that matches the user’s preferred place? if yes, then return that; if no, then return the highest priority name for the selected language.
maybe this is similar to what this other discussion is about: https://forum.inaturalist.org/t/select-language-for-common-names/5430.