Property talk:P496: Difference between revisions

From Wikidata
Jump to navigation Jump to search
Content deleted Content added
mark constraints without violations
Laddo (talk | contribs)
Used new "subject item" field
Line 1: Line 1:
{{Property documentation
{{Property documentation
|description = {{Q|51044}} : Identifier for researchers and academic authors/contributors
|description = [[Q51044|Open Research Contributor ID]] : Identifier for researchers and academic authors/contributors
|subject item = Q51044
|infobox parameter = [[:en:template:authority control]] : ''ORCID''
|infobox parameter = [[:en:template:authority control]] : ''ORCID''
|datatype = string
|datatype = string

Revision as of 20:08, 15 October 2014

Documentation

Please remove the following deprecated parameters: datatype, proposed by.

DescriptionOpen Research Contributor ID : Identifier for researchers and academic authors/contributors
RepresentsORCID iD (Q51044) (note: this information should be moved to a property statement; use property Wikidata item of this property (P1629))
Associated itemORCID, Inc. (Q19861084)
Applicable "stated in" valueORCID iD (Q51044)
Has qualitycheck digit (Q1337960)
Data type
According to this template: string
According to statements in the property:
External identifier
When possible, data should only be stored as statements
Corresponding templateTemplate:ORCID (Q14937479), Template:Authority control/ORCID (Q14934655)
Template parameteren:template:authority control : ORCID
Domain
According to this template: People
According to statements in the property:
human (Q5)
When possible, data should only be stored as statements
Allowed values
According to this template: four four-digit groups separated by dashes
According to statements in the property:
\d{4}-\d{4}-\d{4}-\d{3}[\dX]
When possible, data should only be stored as statements
Usage notesFour groups of four digits, separated by dashes ("-")
Example
According to this template: Mike Taylor (Q8134165) has ORCID 0000-0002-1003-5675
According to statements in the property:
Mike Taylor (Q8134165)0000-0002-1003-5675 (RDF)
Josiah S. Carberry (Q6290611)0000-0002-1825-0097 (RDF)
United States Geological Survey (Q193755)0000-0001-8994-2210 (RDF)
When possible, data should only be stored as statements
Source
According to this template: http://orcid.org
According to statements in the property:
https://orcid.org/
When possible, data should only be stored as statements
Formatter URLhttps://orcid.org/$1
Robot and gadget jobsUser:VIAFbot will import this from enwiki, possibly other wikis, and potentially external DBs.
Tracking: usageCategory:Pages with ORCID identifiers (Q8709081)
See alsoRinggold ID (P3500), Authorea author ID (P5039), NARCIS researcher ID (P7449), ISNI (P213), VIAF ID (P214), ACM Digital Library author ID (P864), IEEE Xplore author ID (P6479), MR Author ID (P4955)
Lists
Proposal discussionProperty proposal/Archive/7#P496
Current uses
Total2,369,797
Main statement1,821,579 out of 11,496,507 (16% complete)76.9% of uses
Qualifier28,5931.2% of uses
Reference519,62521.9% of uses
Search for values
Explanations [Edit] Guidance is available at en:WP:ORCID (or via Wikimedia:ORCID (Q17378190)).
Single best value: this property generally contains a single value. If there are several, one would have preferred rank (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/P496#single best value, SPARQL
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/P496#Unique value, SPARQL (every item), SPARQL (by value)
Format “\d{4}-\d{4}-\d{4}-\d{3}[\dX]: value must be formatted using this pattern (PCRE syntax). (Help)
List of violations of this constraint: Database reports/Constraint violations/P496#Format, hourly updated report, SPARQL
Item “occupation (P106): Items with this property should also have “occupation (P106)”. (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/P496#Item P106, search, SPARQL
Scope is as main value (Q54828448), as reference (Q54828450): 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/P496#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/P496#Entity types
Single value: this property generally contains a single value.
List of violations of this constraint: Database reports/Constraint violations/P496#Single value, hourly updated report, SPARQL
Distinct values: this property likely contains a value that is different from all other items.
List of violations of this constraint: , hourly updated report, SPARQL (every item), SPARQL (by value),
Format: value must be formatted using this pattern (PCRE syntax).
0000-000(1-[5-9]|2-[0-9]|3-[0-4])\d\d\d-\d\d\d[\dX]
List of violations of this constraint: Database reports/Constraint violations/P496#Format, hourly updated report, SPARQL

Template:Constraint:Person


Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)


The property is missing the link to the archive where the proposal is stored. I can't find it in the archive either. --Tobias1984 (talk) 11:29, 8 May 2013 (UTC)[reply]

Oops, I had removed it from proposal but forgot to readd it. --Zolo (talk) 08:38, 15 May 2013 (UTC)[reply]

Possible constraint refinement

According to [1] "Initially ORCID iDs will be assigned between 0000-0001-5000-0007 and 0000-0003-5000-0001". The latter might perhaps read "0000-0003-4999-9997" for the last included ORCID iD. And the harder part will be to formulate a complementary constraint for Property:P213 (ISNI). -- Gymel (talk) 16:14, 4 June 2013 (UTC)[reply]