Property talk:P1843

Documentation

taxon common name
common or vernacular name of a biological taxon

Represents

common name (Q502895)

Data type

Monolingual text

Domain

According to this template: taxon (Q16521)

According to statements in the property:
taxon (Q16521) or organisms known by a particular common name (Q55983715)

When possible, data should only be stored as statements

Allowed values

.+

Example

House Sparrow (Q14683) → House Sparrow
Quercus robur (Q165145) → common oak

Source

http://www.soortenbank.nl/
http://plants.usda.gov/core/profile?symbol=PSME
https://www.dyntaxa.se/taxon/info/2000976

Tracking: usage

Category:Pages using Wikidata property P1843 (Q118496174)

Lists

Proposal discussion

Current uses

Total	770,009
Main statement	769,998	>99.9% of uses
Qualifier	11	<0.1% of uses

Explanations [Edit]

Guidelines by language

French

The first word of compound names and the following words are uppercaseed 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.

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

Item “taxon name (P225)”: Items with this property should also have “taxon name (P225)”. (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#Item P225, SPARQL

Format “.+”: value must be formatted using this pattern (PCRE syntax). (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#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.)

Strange property

Many times it simply repeats label and aliases. --Infovarius (talk) 17:41, 29 June 2016 (UTC)[reply]

And this is strange? Why, Infovarius? --Succu (talk) 20:46, 29 June 2016 (UTC)[reply]

Because it is duplication. --Infovarius (talk) 18:35, 5 July 2016 (UTC)[reply]

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)[reply]

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)[reply]

So what? Having a source for labels/aliases (some of them are abstruse) is inconvenient? --Succu (talk) 19:32, 5 July 2016 (UTC)[reply]

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)[reply]

Adding a case sensitivity constraint ?

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)[reply]

Searching for taxon_common_name using SPARQL and retaining the language

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)[reply]

@Tobias1984, Brya, Succu, Daniel Mietchen, Pigsonthewing: Any help appreciated. --89.206.112.11 14:59, 3 June 2023 (UTC)[reply]

@Petermr: Use LANG(). --Succu (talk) 15:07, 3 June 2023 (UTC)[reply]