Property talk:P4793

Distinct values: this property likely contains a value that is different from all other items. (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/P4793#Unique value, SPARQL (every item), SPARQL (by value)

Single value: this property generally contains a single value. (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/P4793#Single value, SPARQL

Type “Wikidata property (Q18616576), identifier (Q853614)”: item must contain property “instance of (P31)” with classes “Wikidata property (Q18616576), identifier (Q853614)” 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).
List of violations of this constraint: Database reports/Constraint violations/P4793#Type Q18616576, Q853614, SPARQL

Format “[A-Za-z\d][A-Za-z\d_.]+”: 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/P4793#Format, SPARQL

Allowed entity types are Wikibase property (Q29934218), 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/P4793#Entity types

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/P4793#Scope, SPARQL

@ChristianKl, Lucas Werkmeister (WMDE), Matěj Suchánek: @Smalyshev (WMF), ديفيد عادل وهبة خليل 2, JakobVoss, ArthurPSmith: On further investigation, a formatter URL of http://identifiers.org/$1/ (e.g. genewiki) is available; the datatype should therefore be "external-id". Sorry for not noticing sooner.Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:40, 5 February 2018 (UTC)[reply]

Yes, this looks like external-id. Smalyshev (WMF) (talk) 20:53, 5 February 2018 (UTC)[reply]

Oops! Can we get the datatype changed or should I request to delete and re-add? ArthurPSmith (talk) 21:13, 5 February 2018 (UTC)[reply]

@ArthurPSmith: It's possible for developers to change properties from string to external-id and vice versa (other changes aren't possible). The standard progress for requesting that is through Wikidata:Contact the development team ChristianKl ❪✉❫ 21:36, 5 February 2018 (UTC)[reply]

I've obtained some data from idenftifers.org and Magnus has kindly loaded it into Mix'n'Match. As can be seen from the automated matches:

https://tools.wmflabs.org/mix-n-match/#/list/1035/auto

the descriptions at that site refer to databases or projects rather than the identifiers themselves. for example, "The Pfam database contains..." and "The PeptideAtlas Project provides a publicly accessible database...".

All the examples on this property are of other Wikidata properties; I think we should also match identfiers.org entities to Wikidata items. However, I had envisaged these would be items about properties ([[1]]), rather than databases or projects.

I also note that identifiers.org also has a UID for each entity, for example for PeptideAtlas (Q24884023) it is MIR:00000053.

• @ChristianKl, Lucas Werkmeister (WMDE), Matěj Suchánek: @Smalyshev (WMF), ديفيد عادل وهبة خليل 2, JakobVoss, ArthurPSmith: from the property proposal. How should we proceed? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:39, 28 February 2018 (UTC)[reply]

See Wikidata:Identifiers#Identifier items: there is no consensus and I doubt we will have. Some identifier systems have a Wikidata property, some have a Wikidata item, some have no item but their database, organization, and/or knowledge organization system (Q6423319) has an item. And all combinations of these mixed. If there is no priority where to attach this property, we cannot ensure unique value constraints. -- JakobVoss (talk) 12:13, 28 February 2018 (UTC)[reply]

@Pigsonthewing: actually the Gene Wiki example is an example of an item rather than property. If we have a property we should match these id's to that property I feel; if not then to an appropriate item, generally the id in question. ArthurPSmith (talk) 17:02, 28 February 2018 (UTC)[reply]

@ChristianKl, Lucas Werkmeister (WMDE), Matěj Suchánek: @Smalyshev (WMF), ديفيد عادل وهبة خليل 2, JakobVoss, ArthurPSmith: for HGNC, it's better to put the identifiers.org prefix on the property rather than the item, because there are two identifiers.org prefixes ("hgnc" and "hgnc.symbol") associated with the item. It's more useful to attach "hgnc" to Property:P354 and "hgnc.symbol" to Property:P353.--Ariutta (talk) 17:42, 25 July 2019 (UTC)[reply]