Property talk:P1364

From Wikidata
Jump to navigation Jump to search

Documentation

World Table Tennis player ID
6-digit identifier for a table tennis player at the World Table Tennis (WTT) website
Associated itemInternational Table Tennis Federation (Q661379), World Table Tennis (Q97276586)
Data typeExternal identifier
Corresponding templateTemplate:WTT player (Q25824154)
Template parameter
Allowed values[1-9]\d*
ExampleXu Xin (Q2520617)110267
Liu Shiwen (Q443175)105482
Sourcehttps://worldtabletennis.com/playerslist
Formatter URLhttps://worldtabletennis.com/playerDescription?playerId=$1
Robot and gadget jobsDeltaBot does the following jobs:
  • Add new claim P106:Q13382519
  • Tracking: usageCategory:WTT player template using Wikidata (Q27829286)
    Lists
  • Items with the most statements of this property
  • Count of items by number of statements (chart)
  • Count of items by number of sitelinks (chart)
  • Items with the most identifier properties
  • Items with no other external identifier
  • Items with no other statements
  • Most recently created items
  • Items with novalue claims
  • Items with unknown value claims
  • Usage history (total)
  • Chart by item creation date
  • Map of people by place values:
  • January 1st dates
  • Database reports/Humans with missing claims/P1364
  • Database reports/Constraint violations/P1364
  • Map
  • Random list
  • Proposal discussionProposal discussion
    Current uses
    Total1,752
    Main statement96555.1% of uses
    Qualifier20.1% of uses
    Reference78544.8% 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)
    List of violations of this constraint: Database reports/Constraint violations/P1364#Unique value, hourly updated report, SPARQL (every item), SPARQL (by value)
    Single value: this property generally contains a single value. (Help)
    List of violations of this constraint: Database reports/Constraint violations/P1364#Single value, hourly updated report, SPARQL
    Format “[1-9]\d*: value must be formatted using this pattern (PCRE syntax). (Help)
    List of violations of this constraint: Database reports/Constraint violations/P1364#Format, hourly updated report, SPARQL
    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/P1364#Item P31, hourly updated report, search, SPARQL
    Item “sex or gender (P21): Items with this property should also have “sex or gender (P21)”. (Help)
    List of violations of this constraint: Database reports/Constraint violations/P1364#Item P21, hourly updated report, search, SPARQL
    Item “date of birth (P569): Items with this property should also have “date of birth (P569)”. (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/P1364#Item P569, 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/P1364#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/P1364#Scope, SPARQL
    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/P1364#Item P641, search

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

    Discussion[edit]

    new ID[edit]

    A new 8 digit long ID seems to pop up on the ITTF webpage. But the 6 digit long ID is still required to access the ranking of a player. Does somebody have any more details about these two IDs? @Løken, Edgars2007, Tsor: --Pasleim (talk) 21:05, 19 April 2016 (UTC)[reply]

    @Pasleim: discusion can be found here. --Edgars2007 (talk) 21:18, 19 April 2016 (UTC)[reply]

    ITTF stat id[edit]

    Hello, I'm collaborating on the WikiProject TableTennis, and I'm just discovering wikidata.

    The link of the ITTF id on this wikidata are still not working. I guess that it would be better to include the ITTF ID of the player providing all the player statistics. As an example, for Timo Boll the id is 810, and the direct link to his statistics is http://www.ittf.com/ittf_stats/All_events3.asp?ID=810.

    If this is ok for you we should replace the wikidata ID ITTF for all the players.

    Let me know. Cialo (talk) 13:27, 28 September 2016 (UTC)[reply]

    Apparently it works by changing in the URL ID= with Player_ID= --193.205.81.201 13:35, 28 September 2016 (UTC)[reply]
    The ITTF webpage is a bit crap. There are at last 3 IDs for Time Boll: 810, 25476212, 101222. My bot uses the 6 digit long ID to update the monthly ranking. If one can access the monthly ranking also with one of the other IDs I can adjust the bot. --Pasleim (talk) 15:07, 28 September 2016 (UTC)[reply]

    It's broken[edit]

    @Pasleim: Do you know how to fix it? Thierry Caro (talk) 11:18, 22 October 2017 (UTC)[reply]

    The ITTF webpage is currently redesigned and URLs are changing all the time. I've added a new one but don't know for how many days it will work. Fortunately, they keep the players ID. --Pasleim (talk) 14:34, 22 October 2017 (UTC)[reply]
    It seems it's dead. --Rashinseita (talk) 15:43, 18 June 2018 (UTC)[reply]
    I've added a new URL... I hope they keep it that way now... --Rashinseita (talk) 15:49, 18 June 2018 (UTC)[reply]