Property talk:P1663

Latest comment: 6 years ago by Mbch331 in topic Format

Documentation

ProCyclingStats cyclist ID
identifier on the website ProCyclingStats (www.procyclingstats.com)
DescriptionIdentifier on the website ProCyclingStats (www.procyclingstats.com)
Applicable "stated in" valueProCyclingStats (Q21745613)
Data typeExternal identifier
Corresponding templateTemplate:ProCyclingStats (Q20742687)
DomainPersons (note: this should be moved to the property statements)
Allowed values([1-9]\d{0,6})
ExampleFabian Cancellara (Q188197)140846
fabian-cancellara
Ellen van Dijk (Q241961)140857
ellen-van-dijk
Sourcehttps://www.procyclingstats.com/rankings.php
Formatter URLhttps://www.procyclingstats.com/rider/$1
Robot and gadget jobsSome bots could import IDs from the database.
Tracking: usageCategory:ProCyclingStats template using Wikidata (Q21978957)
See alsoProCyclingStats race ID (P2327), ProCyclingStats team ID (P2328), Cycling Archives cyclist ID (P1409), CQ Ranking male cyclist ID (P1541), CQ Ranking female cyclist ID (P2709), CycleBase cyclist ID (P4508), Mémoire du cyclisme cyclist ID (P4516)
Lists
Proposal discussionProposal discussion
Current uses
Total27,779
Main statement27,68099.6% of uses
Qualifier4<0.1% of uses
Reference950.3% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Format “([1-9]\d{0,6}|[a-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). Known exceptions: André Coppers (Q64431227)
List of violations of this constraint: Database reports/Constraint violations/P1663#Format, SPARQL
Distinct values: this property likely contains a value that is different from all other items. (Help)
List of violations of this constraint: Database reports/Constraint violations/P1663#Unique value, hourly updated report, SPARQL (every item), SPARQL (by value)
Item “instance of (P31): human (Q5): Items with this property should also have “instance of (P31): human (Q5)”. (Help)
List of violations of this constraint: Database reports/Constraint violations/P1663#Item P31, hourly updated report, search, 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/P1663#Entity types
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/P1663#Scope, SPARQL

Format edit

What format should we use? This used to be only numbers, but most of the values are names now. Sjoerd de Bruin (talk) 10:41, 23 August 2016 (UTC)Reply

@Sjoerddebruin: I had in my plans change current name IDs to numerical ones. But that will happen, when I'll have time. --Edgars2007 (talk) 04:52, 24 August 2016 (UTC)Reply
@Mbch331: maybe you can make this a periodical task of your bot? The numeric ID is visible on various parts, like the report link. Sjoerd de Bruin (talk) 18:19, 18 July 2017 (UTC)Reply
@Sjoerddebruin: I currently don't have the time to adjust my bot for this. Mbch331 (talk) 19:23, 18 July 2017 (UTC)Reply
Return to "P1663" page.