Property talk:P2369

From Wikidata
Jump to navigation Jump to search

This property is being considered for deletion. Please share your thoughts on the matter at this property's entry on the Properties for deletion page.


Soccerway player ID
player id on the Soccerway website
RepresentsSoccerway (Q24192203)
Data typeExternal identifier
Corresponding templateTemplate:Soccerway (Q13234327)
Template parameter|1= or |id= in en:Template:Soccerway; equivalent templates in other language Wikipedias
Domainhuman (Q5) (note: this should be moved to the property statements)
Allowed values[a-z\-]+\/\d+
ExampleJavier Saviola (Q186071)javier-saviola/121
Höskuldur Gunnlaugsson (Q20990682)hoskuldur-gunnlaugsson--/194453
Formatter URL$1/
Tracking: sameCategory:Soccerway template with ID same as Wikidata (Q25813636)
Tracking: differencesno label (Q25813639)
Tracking: usageCategory:Pages using Wikidata property P2369 (Q25813640)
Tracking: local yes, WD nono label (Q25813637)
See alsoScoresway soccer person ID (P3043)
Proposal discussionProperty proposal/Archive/41#P2369
Current uses66,149
Search for values
[create] Create a translatable help page (preferably in English) for this property to be included here
Format “[a-z\-]+\/\d+”: value must be formatted using this pattern (PCRE syntax). (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P2369#Format, SPARQL, SPARQL (new)
Single value: this property generally contains a single value. (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P2369#Single value, SPARQL, SPARQL (new)
Distinct values: this property likely contains a value that is different from all other items. (Help)
List of this constraint violations: Database reports/Constraint violations/P2369#Unique value, hourly updated report, SPARQL (every item), SPARQL (by value), SPARQL (new)
Item “instance of (P31): human (Q5): Items with this property should also have “instance of (P31): human (Q5)”. (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P2369#Item P31, search, SPARQL, SPARQL (new)
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.
List of this constraint violations: Database reports/Constraint violations/P2369#Item P21, search, SPARQL, SPARQL (new)


occupation (P106)[edit]

I assume, it could also have association football manager (Q628099) as a valid statement. At least, the two at Constraint violations are. --Edgars2007 (talk) 12:08, 10 December 2015 (UTC)

Constraint has been updated. Mbch331 (talk) 13:08, 10 December 2015 (UTC)
Thanks. --Edgars2007 (talk) 16:16, 10 December 2015 (UTC)
@Edgars2007, Mbch331: I'm not sure the best approach here. The issue is that it looks like soccerway uses the same identifier for players. managers, and referees, and the link still works, but the "canonical" link (that you get by searching the website) for managers has "coaches" instead of "players". For example one of the exceptions was Hilda Ordoñez (Q16214549), and the link generated by the formatter url is [1], but the one we get by searching the website is [2]. It seems there are 2 approaches:
  1. Create three properties for manager, player and referee id, each with their own formatter url. The disadvantage is it would be extra work to verify which is "correct" (by searching the website), and it makes little difference as using the "wrong" link still works, and we would miss merge candidates with the same id, if one is a manager id, and one a player id.
  2. Use this property for all three, change the name to soccerway person id, and allow any manager or referee to have their soccerway id included. The slightly disadvantage is that the links are a bit weird for managers, although they still work, and you get more possible merge candidates, and it's very straightforward to check if an id is valid just by following the link. Also, the canonical link can change, but with the same id. I assume Gary Neville had a players link before he took over as Valencia manager, but he now has a coach one [3].

I'm inclined towards 2. as it seems a lot more practical. Silverfish (talk) 23:20, 14 December 2015 (UTC)

@Silverfish, Mbch331: A third option is to use the website instead of Soccerway. I came upon this in an email exchange with Soccerway; the website is made by the same company, and uses the same IDs for players (and refs and managers), but without the name part of the URL. So David Beckham is 182 and Hilda Ordoñez is 324939. The name part of the URL in Soccerway is basically meaningless since you can put anything there and get the same results, so shortening the property to just use the numeric ID and linking to Scoresway instead could be easier. Or we can shorten the values and just use a generic link to link to Soccerway, if it is deemed important to keep the link going to Soccerway instead of Scoresway. Jon Harald Søby (talk) 00:22, 15 December 2015 (UTC)

Is this property necessary?[edit]

This is practically the same database as Property:P3043, just two different sites using the same data. For any url based on P2369 (e.g. an equivalent can be created also with P3043 ( I think it is useless two have the duplicate and suggest deleting this property. --Wikijens (talk) 14:09, 14 April 2017 (UTC)

@Wikijens: You may start a discussion at WD:PFD. However, users mentioned that we will need to retain it. Matěj Suchánek (talk) 10:02, 14 May 2017 (UTC)


Right now we use as URL, while will do too. Then we could just use the number as identifier. Is this a good idea? Edoderoo (talk) 19:13, 9 July 2018 (UTC)