Property talk:P2369
Documentation
person identifier on the Soccerway website
Associated item | Stats Perform (Q7394692) | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Applicable "stated in" value | Soccerway (Q24192203) | ||||||||||||
Data type | External identifier | ||||||||||||
Corresponding template | Template: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} | ||||||||||||
Example | Höskuldur Gunnlaugsson (Q20990682) → 194453 Javier Savioler (Q186071) → 121 Luka Modrić (Q483837) → 365 | ||||||||||||
Source | https://int.soccerway.com/players/ | ||||||||||||
Formatter URL | https://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: same | Category:Soccerway template with ID same as Wikidata (Q25813636) | ||||||||||||
Tracking: differences | Category:Soccerway template with ID different from Wikidata (Q25813639) | ||||||||||||
Tracking: usage | Category:Soccerway template using Wikidata (Q25813640) | ||||||||||||
Tracking: local yes, WD no | Category:Soccerway template with ID not in Wikidata (Q25813637) | ||||||||||||
See also | Soccerway team ID (P6131), Soccerway match ID (P7494), Soccerway venue ID (P8775) | ||||||||||||
Lists |
| ||||||||||||
Proposal discussion | Proposal discussion | ||||||||||||
Current uses |
| ||||||||||||
Search for values |
List of violations of this constraint: Database reports/Constraint violations/P2369#Single value, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P2369#Item P21, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P2369#Entity types
List of violations of this constraint: Database reports/Constraint violations/P2369#Item P641, search
List of violations of this constraint: Database reports/Constraint violations/P2369#Item P106, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P2369#Label in 'en' language, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P2369#Scope, SPARQL
Pattern ^.*/(\d+)/?$ will be automatically replaced to \1. Testing: TODO list |
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)
- 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:
- Thanks. --Edgars2007 (talk) 16:16, 10 December 2015 (UTC)
- 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.
- 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 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)
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)
- @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)
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)
- 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)
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:
- Soccerway player ID (P2369)formatter URL (P1630)https://int.soccerway.com/players/-/$1/
- Soccerway player ID (P2369)URL match pattern (P8966)^https?:\/\/(?:us{{!}}int)\.soccerway\.com\/players\/-\/\d+
- Soccerway player ID (P2369)format as a regular expression (P1793)\d+
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)
- Support Сидик из ПТУ (talk) 09:00, 7 February 2022 (UTC)
- Support - if it works, no reason to use a longer form. Lee Vilenski (talk) 09:15, 7 February 2022 (UTC)
- @Zyxw: your insight would be welcome — Martin (MSGJ · talk) 10:07, 7 February 2022 (UTC)
- Soccerway is one of a number of sites where the ID contains the person's name and a number, but people have discovered that only the number is needed to form a working URL. Another example is https://www.national-football-teams.com/player/11881/Brad_Davis.html and https://www.national-football-teams.com/player/11881.html where both URLs work, so National-Football-Teams.com player ID (P2574) only stores the number (although with NFT the second URL redirects to the first URL, which is a nice feature that Soccerway does not have). The main benefit of converting Soccerway player ID (P2369) to a number would be that it becomes easier to find and merge duplicate Wikidata items. The main drawback would be the possibility that some future software change at Soccerway requires the full URL https://int.soccerway.com/players/brad-davis/7302/ and causes https://int.soccerway.com/players/-/7302/ to stop working (though I know it has worked for almost five years because I updated en:Template:Soccerway to handle numeric IDs in August 2017). Before changing the IDs in this property to numbers, we should check the other 54 Wikipedias with a copy of Template:Soccerway (Q13234327) and make sure those which use Wikidata can generate working links for both
first-last/12345
and12345
. For example, uk:Шаблон:Soccerway is transcluded on over 14,000 articles at Ukrainian Wikipedia (Q199698) and changing this property to a number would instantly break many of those links because that template does not handle numeric IDs and it gives preference to the ID in Wikidata over the ID in the template. An alternative that would not require checking and updating templates is to replacefirst-last/12345
with-/12345
. -- Zyxw (talk) 11:57, 7 February 2022 (UTC)- @Zyxw: Then we should probably take a look at the templates in the individual language versions so that we can convert the shortening to purely numeric IDs. There are no longer 54 language versions to be checked, but only 53. For the submission in the German-language Wikipedia, only the numerical ID has been used for a long time and Wikidata is not used. Regarding the Ukrainian example, I have a question, is it only accessing the ID from Wikidata or also the URL formatter? I'm assuming just accessing the id and using the url formatter from the template right? --Gymnicus (talk) 10:22, 12 February 2022 (UTC)
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)
- All Properties
- Properties with external-id-datatype
- Properties used on 100000+ items
- Properties with single value constraints
- Properties with unique value constraints
- Properties with constraints on items using them
- Properties with format constraints
- Properties with entity type constraints
- Properties with label language constraints
- Properties with scope constraints
- Sports properties