I wonder if there is a way to crowdsource new common names for animals that don’t have one, and for unofficial use. Especially when the animal itself is not uncommon and distinct but undescribed, it helps for the local community to have a name for it.
I am sure that communities do this on their own organically. Many species/taxa probably don’t have common names because no one (other than a few specialists who would use the scientific name) has ever really noticed them/needed to talk about them before.
On a side note since it is a common issue encountered by curators, just noting that common names should not be coined on iNat/crowdsourced here as a way to try to create them for taxa that don’t have them.
For sure, one example from my local area is WildSingapore. The creator has been doing marine for decades and helped popularise many names for common animals. Some of the common names on iNat or otherwise also make little sense, but I do find it helps make something more memorable.
Some species do not have common names, but the local common name has already been in use for years. Not sure if I should add that common name, since the species can be found elsewhere too?
I get the reason for the rule, but it strikes me that anyone who wants to coin a common name will just create it somewhere else on the internet, maybe set up a few links on various websites, and then point to these external references to support getting the name into iNat. That’s what I’m planning to do…
If it’s a common name that’s actually in use, then it’s fair game as far as I’m concerned. It doesn’t matter if folks in some other place use a different common name - that’s how common names work. There can be more than one, and whichever one is “catchier” will eventually dominate. Or not. I don’t think anybody with any sense wants there to be a committee dictating what the “official” common names should be (yes, I know that these things exist. I think they’re a bad idea).
Staff have clarified that this practice is not ok several times (though I don’t know on the forum; I won’t link to specific flags on iNat so I don’t call out individuals). Real-life examples include users adding names on Wikipedia and/or Bugguide and then adding those names to iNat citing those references. Names found added by these approaches have been deleted on iNat and the users doing this warned.
I agree that in cases where
that it is fair game to add to iNat. I would note that really general common names (which very local names sometimes are) probably shouldn’t be added though, even if they are in use, due to the potential to cause confusion. For instance “bluebird” is a common name for specific taxa, but could be a common name used locally for many species. Adding it to many species would cause confusion and mis-IDs.
A related issue occurs when a species has no common name, and a general one gets added (so no other name is available to be prioritized as the default). This can also lead to confusion. An example could b something like “brown jumping spider.” That species may be the only brown jumping spider in some specific place, so people there refer to it that way informally. But if “brown jumping spider” becomes the default common name on iNat, it can lead to users saying “Oh, I have a brown jumping spider, that must be it” and IDing for a taxon that is clearly wrong. See a very recent example: https://forum.inaturalist.org/t/inat-ettiquette-repeated-text-comment-for-frequent-id-mistakes/85343/22
If users think that might be the case for a specific name, it is good to check what names are already present in iNat and see if there are any conflicts, or users can always raise a flag for curators proposing adding the name to see if there might be any downstream issues. The general principle is that common names are there to increase the platform’s usability for its users, so sometimes different approaches have to be weighed for names that might cause issues.
I call them Thickness Bees. :)
Chonk-bees :)
I’ve named a few plants new to science, and besides bestowing their new scientific names, it has become frequent (if not customary) practice in botany for the author(s) of a scientific name to also suggest a suitable common name for the new species. The couple of times I did this, the names stuck, maybe for lack of anything better despite the justifications I offered at the time. But my suggestions could just as easily have been ignored if they were deemed unsuitable by others, or inferior to other suggestions.
Baby ducks are called ducklings.
Duck → duckling
Baby geese are called goslings.
Goose → gosling
So, the principle is: if the vowel is short, keep it. If the vowel is long, shorten it.
Therefore, baby coots should be called cotlings and baby grebes should be called greblings.
…this has not caught on.
I sometimes call houseflies com’mes (somewhat like com-mees) and Parthenimus beetles parries. idk why but yes.
I also call Sarcophaga(s) Sarc’s (a bit like sharks haha).
This “neelam wasp” looks like it has a gem embedded in it, and it is particularly similar to some varieties of Blue sapphire which is called neelam (pronounced nee-lum) in Hindi.
I actually use that name for it between me and my brother.