Property talk:P1843
Add topicLatest comment: 9 months ago by Jarekt in topic Common names are often stored as labels and not P1843
Documentation
- Start a query
- Current uses
- Statistics by class
- String length
- Language of strings
- List of qualifiers
- Count
taxon common name
common or vernacular name of a biological taxon
common or vernacular name of a biological taxon
Explanations [Edit]
Guidelines by language
[edit]French
[edit]The first word of compound names and the following words are uppercased only if they are proper names or species names, but not the adjectives.
Correct examples: "Grand Boucage", "Cyclamen à fleur immaculée", "Cyclamen à feuille de Lierre" and "Cyclamen de Perse", etc.
Please note this is different from the title and labels of regular items, which are normally in lowercase.
Type “taxon (Q16521), organisms known by a particular common name (Q55983715)”: item must contain property “instance of (P31)” with classes “taxon (Q16521), organisms known by a particular common name (Q55983715)” or their subclasses (defined using subclass of (P279)). (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Capitalsaurus (Q3493327)List of violations of this constraint: Database reports/Constraint violations/P1843#Type Q16521, Q55983715, SPARQL
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P1843#Item P225, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P1843#Item P225, search, SPARQL
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P1843#Format, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P1843#Format, SPARQL
Scope is as main value (Q54828448): the property must be used by specified way only (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). List of violations of this constraint: Database reports/Constraint violations/P1843#Scope, SPARQL
Allowed entity types are Wikibase item (Q29934200): the property may only be used on a certain entity type (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). List of violations of this constraint: Database reports/Constraint violations/P1843#Entity types
|
This property is being used by:
Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||
Inconsistency in the use in species versus higher order taxa (at least for birds)
[edit]On the species level, there is usually many taxon common name (P1843) for many languages, which seem to reflect the labels in the different languages---see, e.g., Great Tit (Q25485). When you go to parent taxa, this seems to disappear---for example Paridae (Q168473), there is taxon common name (P1843) only for two languages. Should the label be reflected also for orders, families, ...? And if not, why is the situation different for species?
Strange property
[edit]Many times it simply repeats label and aliases. --Infovarius (talk) 17:41, 29 June 2016 (UTC)
- And this is strange? Why, Infovarius? --Succu (talk) 20:46, 29 June 2016 (UTC)
- Because it is duplication. --Infovarius (talk) 18:35, 5 July 2016 (UTC)
- If taxon name (P225) repeats labels and/or aliases because taxon common name (P1843) is present this is not strange, Infovarius? --Succu (talk) 18:38, 5 July 2016 (UTC)
- taxon name (P225) has mostly single (or a few) values, it's standardized. This property can have hundreds/thousands of values, several per each language. Which are already at labels/aliases. --Infovarius (talk) 19:18, 5 July 2016 (UTC)
- So what? Having a source for labels/aliases (some of them are abstruse) is inconvenient? --Succu (talk) 19:32, 5 July 2016 (UTC)
- taxon name (P225) has mostly single (or a few) values, it's standardized. This property can have hundreds/thousands of values, several per each language. Which are already at labels/aliases. --Infovarius (talk) 19:18, 5 July 2016 (UTC)
- If taxon name (P225) repeats labels and/or aliases because taxon common name (P1843) is present this is not strange, Infovarius? --Succu (talk) 18:38, 5 July 2016 (UTC)
- I do not appreciate and understand the "so what". It is duplication. The notion of sources of labels has been shot down in the past so this is that same discussion through the back-door. There is no point to them so imho this property is superfluous. Thanks, GerardM (talk) 12:08, 15 October 2017 (UTC)
Adding a case sensitivity constraint ?
[edit]Is there any way to configure this so entries that simply use different case structures are not considered separate entries ? There is no reason why there should be separate entries for house sparrow, House Sparrow and House sparrow under EN language for example. CanadianCodhead (talk) 16:26, 10 February 2021 (UTC)
Searching for taxon_common_name using SPARQL and retaining the language
[edit]I want to search for `taxon_common_name` using SPARQL. At present this returns a list of names but the language is not retained although it is given in brackets in the Wikidata display. How can we obtain the names and the language using the Wikidata SPARQL query service? Petermr (talk) 09:50, 10 May 2021 (UTC)
- @Tobias1984, Brya, Succu, Daniel Mietchen, Pigsonthewing: Any help appreciated. --89.206.112.11 14:59, 3 June 2023 (UTC)
- @Petermr: Use LANG(). --Succu (talk) 15:07, 3 June 2023 (UTC)
Common names are often stored as labels and not P1843
[edit]I was looking lately at c:Module:Wikidata4Bio on Commons. I noticed that it gets Common names of organisms mostly by scanning for labels on Wikidata which are different than taxon name (P225) and not from P1843. For example that is the case of Q473939. I wonder if it would make sense to do some mass transfer of such common names from labels to P1843. Jarekt (talk) 15:11, 4 July 2025 (UTC)
Categories:
- All Properties
- Properties with monolingualtext-datatype
- Properties used on 100000+ items
- Properties with constraints on type
- Properties with constraints on items using them
- Properties with format constraints
- Properties with scope constraints
- Properties with entity type constraints
- Taxonomy properties
- Person properties