Property talk:P4023

From Wikidata
Jump to navigation Jump to search

Documentation

German Football Association person ID
identifier for players, manager and referees in the datacenter of the German Football Association (Deutscher Fußball-Bund, DFB)
Associated itemGerman Football Association (Q154191)
Applicable "stated in" valueno label (Q105070980)
Data typeExternal identifier
Corresponding templateTemplate:DFB (Q42363984)
Template parameter
Allowed values[^ ]+[^/]+
ExampleBastian Schweinsteiger (Q44298)3201
bastian-schweinsteiger
Dzsenifer Marozsán (Q450592)106623
dzsenifer-marozsan
Carsten Sträßer (Q123844)9225
carsten-strasser
Uwe Rösler (Q566127)28733
uwe-rosler
Bibiana Steinhaus (Q60321)48991
bibiana-steinhaus-webb
Sourcehttps://datencenter.dfb.de/datencenter/personen
Formatter URLhttps://datencenter.dfb.de/en/profile/$1
https://datencenter.dfb.de/profil/$1
https://www.dfb.de/datencenter/personen/$1/trainerin
https://www.dfb.de/en/data-center/people/$1/referee
https://www.dfb.de/datencenter/personen/$1/trainer
https://www.dfb.de/datencenter/personen/$1/schiedsrichter
https://www.dfb.de/en/data-center/people/$1/coach
https://www.dfb.de/datencenter/personen/$1/spieler
https://www.dfb.de/datencenter/personen/$1/spielerin
https://www.dfb.de/en/data-center/people/$1/player
https://www.dfb.de/datencenter/personen/$1/schiedsrichterin
Tracking: usageCategory:Pages using Wikidata property P4023 (Q30127395)
Related to country Germany (Q183) (See 362 others)
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/Constraint violations/P4023
  • Map
  • Random list
  • Proposal discussionProposal discussion
    Current uses
    Total8,098
    Main statement8,03999.3% of uses
    Qualifier100.1% of uses
    Reference490.6% 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/P4023#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/P4023#Item P31, hourly updated report, search, SPARQL
    Format “[^ ]+: value must be formatted using this pattern (PCRE syntax). (Help)
    List of violations of this constraint: Database reports/Constraint violations/P4023#Format, hourly updated report, SPARQL
    Format “[^/]+: 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/P4023#Format, 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/P4023#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/P4023#Scope, SPARQL
    Item “sport (P641): association football (Q2736): Items with this property should also have “sport (P641): association football (Q2736)”. (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/P4023#Item P641, search, SPARQL

    IDs are reused

    [edit]

    I just want to document this here: The ID 103038 was used until the weekend for Klaus Peschel (Q1745544) (see Google Cache). I wrote to the DFB on saturday that Peschel has two IDs. Today I discover that this ID was reused for Fabien Robert (Q2712686) (without sending any reply to me). I call this very bad data keeping. Steak (talk) 14:21, 11 September 2017 (UTC)[reply]

    different ID for en/de

    [edit]

    Nowadays that DFB uses text IDs, the german and english profile IDs are different when the name has an Umlaut. I. e.:

    • German https://www.dfb.de/datencenter/personen/'''thomas-hoerster'''/spieler
    • English https://www.dfb.de/en/data-center/people/'''thomas-horster'''/player

    or:

    • German https://www.dfb.de/datencenter/personen/'''rudi-voeller'''/spieler
    • English https://www.dfb.de/en/data-center/people/'''rudi-voller'''/player

    How to handle this? If the number ID is still existing there's no problem, but how to find out the number as it's no part of the link anymore? --Hadibe (talk) 10:27, 18 September 2019 (UTC)[reply]

    The number can be found out by looking at the source code. For example, for this profile, in the source code it says "data-indexer-attributes="P_352879", therefore, the ID is 352879. Steak (talk) 12:25, 14 November 2019 (UTC)[reply]
    If there is a working numeric for every entry, it should be changed to it and a format constraint added. At the moment it is a really bad mix between German, Engish and numeric identifiers, resulting in overflown maintanance categories. LockaPicker (talk) 19:50, 23 May 2024 (UTC)[reply]
    Notified participants of WikiProject Association football LockaPicker (talk) 19:57, 23 May 2024 (UTC)[reply]
    Notified participants of WikiProject Germany LockaPicker (talk) 20:15, 23 May 2024 (UTC)[reply]
    Names with an umlaut added from the german url won't work on the default formatter URL which uses english as standard. So the person's name as it is in the URL is not an unique identifier. For persons with identical names the numerical ID is appended, so that should be unique. If there are no objections, I will make the numerical ID the default standard. German Wikipedia has to figure out on its own, if they want to keep using names or switch to numeric IDs. --Sotho Tal Ker (talk) 14:05, 22 September 2024 (UTC)[reply]