Was wondering if there was a method to bulk add common names for organisms.
What I am currently doing is going to species and adding its “Local common name” in Hindi, Transliterated English and adding to each specific locations.
As an example
I have a list of say some 350 bird names already with this transliteration and the local names in the local language. But the prospect of Individually navigating to each species and adding the data seems daunting and also very time consuming whereas it would , probably, be a simple job to just upload the data with the correct paramenters
Scientific Name Local Name, Language, Location 1, Location 2 etc.
I understand the first step would be to access a list of the “species” and make sure the correct names appear against the current and correct Scientific Name.
Am taking the liberty of asking some follow up questions
What is meant by source in this regard. What kind of “sources” are acceptable for common names. Esp one that may be very regional. How does one cite a common name that does not appear anywhere else except in oral traditions.
***Make a separate file for each source of common names.*** Each file of common names must come with a citation, preferrably one with a URL that we can use to spot check some of the names. We will not batch import names without sources. Each file should only include names from a single source.
The template does not have any column for “location” . Being Common names some of them are quite specific to say either a State or County. How does one include that.
The document names say that the taxon names should also match. So how does one download the latest / accurate taxon names. (I could download say all the bird species observed in the state - but that may or may not cover all the species for which common names may / may not be available)
it doesn’t look like there are many names set up for Hindi, and even fewer that are set up with India as the place ID (which i think is the only way to get them to show up properly until Hindi is more fully translated).
If you are adding names are specific to a place and not a lexicon, e.g. English names that are only used in Canada, not the US or the UK, please include the URL of the place in question when submitting this file.>
So does it mean for each common name (say I have multiple common names) I would need to make a separate file for each location
Example # House Sparrow Passer domesticus
Common Name in Lexicon Hindi - - गौरैया - Location India
Common Name in Lexicon Hindi - - ग्यांर - Location Uttarakhand, India
Common Name in Lexicon Hindi - - ग्यांर - Location Pithoragarh County, Uttarakhand, India
Kindly note that the name in 1 refers to the common Hindi name applicable only to the hindi speaking parts of India. That is spread across multiple states. Would then it be better to have this refined further to have the common name individually identifed to the “many” hindi speaking states
Importantly, an account set to a descendent place will not display the name for the ancestor place, it will display the global default. So an account set to Uttarakhand will show House Sparrow, not गौरैया because there is currently no name for Uttarakhand.
However, once a common name is entered, anyone can use that common name in searches, regardless of their place or language settings.
There are plenty of species with common names set to be used in Canada. If I set my use names from to Canada, I see the Canadian names. Likewise if I set it to the Canadian province of Ontario, which has no common names set to be used in it, but is a child of Canada, I still see the Canadian names.
@ram_k I amend my previous statement – users with accounts set to state/county level will see the country level name if either (1) the bug I reported gets fixed or (2) the site gets translated to Hindi and the user is running the site in Hindi
If names are collected from oral traditions, we recommend publishing something online covering who, how, and where. It can be something informal like a blog post or iNaturalist journal post, but you may want to consider sharing with some kind of more formal language repository for posterity. The idea is to be able to point to additional context for the origin of the names.
When it comes to bulk imports, yes, each place should have a separate file of names.
In this example, what is the difference between 2 and 3? You should not need to specify the same common name and lexicon for Pithoragarh County (3) because it is in Uttarakhand (2). Maybe I am missing something here?
The state if Uttarakhand is divided into two administrative regions (Kumaon / Garhwal)- whose originals are cultural . The state also has multiple languages and dialects. In this case the common name for the House Sparrow in Pithoragarh District (Kumaon) would / may differ from the common name in say the in a district in Garhwal
Secondly even within Kumaon there are difference s in local names.
So in order to keep that granular data I could choose to have the common name (which may be different than in the example) to show a different name in the county along with the more common name across the state.
Kindly note that inaturalist does not have provisions to accommodate the Administrative divisions of Kumaon and Garhwal.