Property talk:P2369

From Wikidata
Jump to navigation Jump to search

Documentation

Soccerway player ID
person identifier on the Soccerway website
Associated itemStats Perform (Q7394692)
Applicable "stated in" valueSoccerway (Q24192203)
Data typeExternal identifier
Corresponding templateTemplate:Soccerway (Q13234327), Template:Soccerway coach (Q22714642), Template:Soccerway referee (Q115483957)
Template parameter|1= or |id= in en:Template:Soccerway; equivalent templates in other language Wikipedias
Allowed values[1-9]\d{0,6}
ExampleHöskuldur Gunnlaugsson (Q20990682)194453
Javier Savioler (Q186071)121
Luka Modrić (Q483837)365
Sourcehttps://int.soccerway.com/players/
Formatter URLhttps://int.soccerway.com/players/-/$1/
https://jp.soccerway.com/players/-/$1/
https://kr.soccerway.com/players/-/$1/
https://nl.soccerway.com/players/-/$1/
https://it.soccerway.com/players/-/$1/
https://fr.soccerway.com/players/-/$1/
https://gr.soccerway.com/players/-/$1/
https://el.soccerway.com/players/-/$1/
https://pl.soccerway.com/players/-/$1/
https://br.soccerway.com/players/-/$1/
https://ru.soccerway.com/players/-/$1/
https://pt.soccerway.com/players/-/$1/
https://tr.soccerway.com/players/-/$1/
https://ro.soccerway.com/players/-/$1/
https://th.soccerway.com/players/-/$1/
https://ar.soccerway.com/players/-/$1/
https://es.soccerway.com/players/-/$1/
https://uk.soccerway.com/players/-/$1/
https://au.soccerway.com/players/-/$1/
https://ca.soccerway.com/players/-/$1/
https://de.soccerway.com/players/-/$1/
https://id.soccerway.com/players/-/$1/
https://cn.soccerway.com/players/-/$1/
https://us.soccerway.com/players/-/$1/
https://gh.soccerway.com/players/-/$1/
https://ke.soccerway.com/players/-/$1/
https://za.soccerway.com/players/-/$1/
https://ie.soccerway.com/players/-/$1/
https://sg.soccerway.com/players/-/$1/
https://my.soccerway.com/players/-/$1/
https://ng.soccerway.com/players/-/$1/
https://nr.soccerway.com/players/-/$1/
Tracking: sameCategory:Soccerway template with ID same as Wikidata (Q25813636)
Tracking: differencesCategory:Soccerway template with ID different from Wikidata (Q25813639)
Tracking: usageCategory:Soccerway template using Wikidata (Q25813640)
Tracking: local yes, WD noCategory:Soccerway template with ID not in Wikidata (Q25813637)
See alsoSoccerway team ID (P6131), Soccerway match ID (P7494), Soccerway venue ID (P8775)
Lists
Proposal discussionProposal discussion
Current uses
Total121,823
Main statement120,73699.1% of uses
Qualifier3<0.1% of uses
Reference1,0840.9% 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)
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/P2369#Single value, 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/P2369#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/P2369#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/P2369#Item P21, search, SPARQL
Format “[1-9]\d{0,6}: value must be formatted using this pattern (PCRE syntax). (Help)
List of violations of this constraint: Database reports/Constraint violations/P2369#Format, hourly updated report, 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/P2369#Entity types
Item “occupation (P106): Items with this property should also have “occupation (P106)”. (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/P2369#Item P106, 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/P2369#Label in 'en' language, search, SPARQL
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/P2369#Scope, SPARQL
Pattern ^.*/(\d+)/?$ will be automatically replaced to \1.
Testing: TODO list
This property is being used by:

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

Discussion

[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)[reply]

Constraint has been updated. Mbch331 (talk) 13:08, 10 December 2015 (UTC)[reply]
Thanks. --Edgars2007 (talk) 16:16, 10 December 2015 (UTC)[reply]
@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)[reply]

@Silverfish, Mbch331: A third option is to use the website Scoresway.com 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)[reply]

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. http://nr.soccerway.com/players/javier-saviola/121/ an equivalent can be created also with P3043 (http://nr.soccerway.com/players/x/121/). I think it is useless two have the duplicate and suggest deleting this property. --Wikijens (talk) 14:09, 14 April 2017 (UTC)[reply]

@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)[reply]

URL-form

[edit]

Right now we use http://int.soccerway.com/players/devi-venema/278016/ as URL, while http://int.soccerway.com/players/ANYTHING/278016/ 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)[reply]

Yeah, I really think we should ditch the firstname-lastname/12345 format and just use 12345. Recently I’ve seen the id also being added as -/12345 (there's even an autofix that does 12345-/12345), so technically we could have firstname-lastname/12345 in one item, -/12345 in second and whatever/12345 in third and there would be no distinct value constraint violation, which makes identifying duplicates more difficult. On the other hand, I think a lot of Wikipedias use the firstname-lastname/12345 format and changing the format here might make using tools like Harvest Templates impossible, but I’m sure we could utilize bots for importing purposes. –Kooma (talk) 12:14, 18 April 2020 (UTC)[reply]
MisterSynergy Thierry Caro Vanbasten_23 Malore Сидик из ПТУ Mathieu Kappler Lee Vilenski Erokhin Dandilero Blackcat Looniverse

Notified participants of WikiProject Sports – After almost two years, I would rekindle this discussion here, since property P3043 (P3043) was deleted from MSGJ. As a result of the deletion, it might now make sense to adjust the regular expression and thus also the URL formatter and the URL match pattern for this property. The two users Edoderoo and Kooma showed almost two years ago that the current regular expression can also be shortened. I would therefore customize the regular expression, URL formatter, and URL match pattern in the following way:

I hope that I didn't make a mistake, especially with the statement about property URL match pattern (P8966). If so, I would ask that my mistakes be corrected. Unfortunately, I haven't had that much experience with the P8966 property. Do you agree with this revision of the three statements? With a bot you can probably easily fix the changes in relation to the regular expression. --Gymnicus (talk) 08:57, 7 February 2022 (UTC)[reply]

To update on this, I have gone through all instances of Template:Soccerway (Q13234327) which rely on Soccerway player ID (P2369) and changed the code to also support a numerical ID. I therefore have updated the formatter URL, format constraint, and the autofix. S.A. Julio (talk) 08:47, 6 March 2024 (UTC)[reply]