Property talk:P4793

Documentation

identifiers.org prefix
code used in front of an identifier, as supported by identifiers.org and n2t.net
Applicable "stated in" valueIdentifiers.org (Q16335166)
Data typeExternal identifier
Domain
According to statements in the property:
Wikidata property (Q18616576) or identifier (Q853614)
When possible, data should only be stored as statements
Allowed values[A-Za-z][0-9A-Za-z_]+
ExampleGene Wiki (Q5531528)genewiki
PeptideAtlas (Q24884023)peptideatlas
Ensembl Plants (Q27927711)ensembl.plant
Foundational Model of Anatomy ID (P1402)FMA
UBERON ID (P1554)UBERON
Gene Ontology ID (P686)GO
PDB structure ID (P638)pdb
Formatter URLhttps://registry.identifiers.org/registry/$1
Lists
Proposal discussionProposal discussion
Current uses
Total274
Main statement266 out of 630 (42% complete)97.1% of uses
Qualifier72.6% of uses
Reference10.4% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
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

Datatype

edit

@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 ChristianKl21:36, 5 February 2018 (UTC)Reply

Property for identifiers vs. property for databases/ projects

edit

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.

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
Return to "P4793" page.