Property talk:P3537

From Wikidata
Jump to navigation Jump to search

Documentation

FootballDatabase.eu person ID
identifier for a person at FootballDatabase.eu
Applicable "stated in" valueFootballDatabase.eu (Q17589204)
Data typeExternal identifier
Corresponding templateTemplate:FootballDatabase.eu (Q15654952)
Template parameter|id= or |1= in en:Template:FootballDatabase.eu
Domainhuman (Q5) (note: this should be moved to the property statements)
Allowed values^[1-9]\d{0,7}(-\S+)?$
ExampleGeoffrey Mujangi Bia (Q10781)25579
Oh Jae-suk (Q166238)161185
Gregory van der Wiel (Q201367)23349
Álex Collado (Q50709615)303535
Sourcehttps://www.footballdatabase.eu/en/
https://www.footballdatabase.eu/fr/
https://www.footballdatabase.eu/es/
https://www.footballdatabase.eu/pl/
https://www.footballdatabase.eu/id/
Formatter URLhttps://www.footballdatabase.eu/en/player/details/$1
https://www.footballdatabase.eu/pl/zawodnik/szczegoly/$1
https://www.footballdatabase.eu/es/jugador/detalles/$1
https://www.footballdatabase.eu/fr/joueur/details/$1
https://www.footballdatabase.eu/id/pemain/detail/$1
Tracking: sameCategory:FootballDatabase.eu template with ID same as Wikidata (Q55423021)
Tracking: differencesCategory:FootballDatabase.eu template with ID different from Wikidata (Q55423658)
Tracking: usageCategory:FootballDatabase.eu template using Wikidata (Q28548387)
See alsoFootballDatabase.eu team ID (P7351)
Lists
Proposal discussionProposal discussion
Current uses
Total217,973
Main statement217,866>99.9% of uses
Qualifier4<0.1% of uses
Reference103<0.1% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Single value: this property generally contains a single value. (Help)
List of violations of this constraint: Database reports/Constraint violations/P3537#Single value, hourly updated report, 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/P3537#Unique value, hourly updated report, SPARQL (every item), SPARQL (by value)
Format “[1-9]\d{0,7}(-\S+)?: 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/P3537#Format, 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/P3537#Item P31, hourly updated report, search, SPARQL
Item “sex or gender (P21): Items with this property should also have “sex or gender (P21)”. (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/P3537#Item P21, 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/P3537#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/P3537#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/P3537#Item P641, search, SPARQL
Label required in languages: en: Entities using this property should have labels in one of the following languages: en (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/P3537#Label in 'en' language, search, SPARQL
Pattern ^([1-9]\d{0,7})(-\S+)$ will be automatically replaced to \1.
Testing: TODO list

Constraints[edit]

Discussion[edit]

new structure of the internetsite http://www.footballdatabase.eu[edit]

Please investigate on how this property will have to be adapted in order to comply with the footballdatabase.eu V3 which is live by now.Robby (talk) 08:25, 12 June 2018 (UTC)[reply]

Indeed I noticed that the url's chnaged like this for Deennis Renie the previous Url on the website of footballdatabase.eu was http://www.footballdatabase.eu/football.joueurs.dennis.rennie.9539.en.html while under the new structure of their internetsite this corresponds to http://www.footballdatabase.eu/en/player/details/9539-dennis-rennie . so it will be quite tricky to guess from the new type of url that the parameter in the corresponding template should be dennis.rennie.9539. Who knows how to change the corresponding template so it would as well work for a parameter like 9539-dennis-rennie ? Many thanks to all that can help with this issue. Robby (talk) 17:27, 12 June 2018 (UTC)[reply]
@Robby: the current Url still works (using redirection). This property is used on several hundreds of items. So if we changed the URL format, we would need to convert all the "old" link by new one. Do we have a bot for that? For now I think it is better to stay with the current URL format. Pamputt (talk) 20:40, 12 June 2018 (UTC)[reply]
@Pumputt: Indeed for now everything is working fine. We will have to monitor this, in order not to be surprised once the redirect will no longer work. Robby (talk) 21:09, 12 June 2018 (UTC)[reply]
from your example it looks like very easy to convert old to new ones ("name.id" to "id-name"). Ping me if the redirects doesn't work. --Edgars2007 (talk) 06:15, 13 June 2018 (UTC)[reply]
@Pumputt, Robby: forgot to ping --Edgars2007 (talk) 06:16, 13 June 2018 (UTC)[reply]
It seems like a substantial change. Maybe it's better to add the new format to a new property.
--- Jura 06:39, 13 June 2018 (UTC)[reply]
Dunno. We have always converted the old property. --Edgars2007 (talk) 15:32, 15 June 2018 (UTC)[reply]
I noticed that the new URL format also works when only using the numeric portion of the player ID:
-- Zyxw (talk) 05:06, 20 June 2018 (UTC)[reply]
@Robby, Pamputt, Edgars2007, Jura1, Zyxw: I have shortened all the IDs to their numerical part during the past couple of days. Our formatter URL (P1630) has been changed accordingly and the different Wikipedias supposed to use the property have been warned through the talkpage of all the different versions of Template:FootballDatabase.eu (Q15654952). Thierry Caro (talk) 04:44, 21 July 2018 (UTC)[reply]
Note that we now have 57 constraint violations due to multiple items using the same ID. Can someone check this? Thierry Caro (talk) 04:52, 21 July 2018 (UTC)[reply]