Property talk:P599
Documentation
identifier for a tennis player at the International Tennis Federation (ITF) website
List of violations of this constraint: Database reports/Constraint violations/P599#Single value, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P599#Item P569, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P599#Entity types
List of violations of this constraint: Database reports/Constraint violations/P599#Item P8618, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P599#Item P641, search, SPARQL
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
Exception edit
George Marshall (Q1132948) should be included as exception for the occupation (P106) check. --Edgars2007 (talk) 19:55, 15 December 2015 (UTC)
- Why don't we add P106: tennis player for him? --Stryn (talk) 20:02, 15 December 2015 (UTC)
- @Stryn: I just have impression, that it won't be correct for him, based on what Sports reference says. --Edgars2007 (talk) 10:16, 16 December 2015 (UTC)
- I see, so the French Wikipedia article about him contains wrong information, also fr:Simple messieurs de tennis aux Jeux olympiques d'été de 1896. But I would say ITF is more accurate source than sports-reference. --Stryn (talk) 15:53, 16 December 2015 (UTC)
Same as IPIN? edit
It seems this is not different from IPIN (International Player Identification Number (Q47546365)). What do you think? In either case, how to indicate that? --- Jura 12:56, 30 July 2019 (UTC)
URL is not working edit
Notified participants of WikiProject Tennis "Happy" news, not only WTA changed URL format, ITF with a new number as well. --Kacir (talk) 13:04, 3 December 2019 (UTC)
- For the WTA I am working on a python script to fix this, give me a few days. For the ITF we need to study how we can get the new identifier working. For WTA someone created a spreadsheet with the old & new values, if this exists for ITF too, I can work it out from there. Please keep me posted. Edoderoo (talk) 13:25, 3 December 2019 (UTC)
- I can get working on a spreadsheet for this too, once I figure out the format the ITF are using. Iffy (talk) 13:40, 3 December 2019 (UTC)
- I've had a look,
but unfortunately the ITF are using brand new IDs, so I can't create a spreadsheet the way I did for the WTA change.Thankfully the ITF kept the old IDs working, we don't have to do anything here. Iffy (talk) 21:24, 4 December 2019 (UTC)- Yeah, the old ID's work for now, but new players do not have an old ID, and you can't look them up either. We need to fix something somehow. Edoderoo (talk) 17:59, 7 December 2019 (UTC)
- So what can we do with this issue? Openbk (talk) 00:42, 21 January 2020 (UTC)
- Yeah, the old ID's work for now, but new players do not have an old ID, and you can't look them up either. We need to fix something somehow. Edoderoo (talk) 17:59, 7 December 2019 (UTC)
- How can I add working link to 800550536 for Paolo Maldini (Q483027)? Сидик из ПТУ (talk) 08:01, 11 December 2019 (UTC)
- Same issue with Kirsten Robsahm (Q19800708), I had to link with 80017425 Jmax (talk) 05:00, 19 April 2020 (UTC)
- @Edoderoo: do you know if this is fixable via a script? --Wolbo (talk) 16:48, 25 April 2020 (UTC)
- The issue is, as far as I know, that the WikiData URL-builder that is defined in the property is wrong, it works now with old ID's. The biggest issue for us, is that the WTA is making huge changes without prior notification once in a year. It can be that all their ID's are AGAIN different tomorrow. Or next month. Or both.
- I can only repair it by script, if the current data is wrong, and we can automatically get the right data from somewhere. Before a script can do something, we should be able to fix it manually. Then the script can make it easy repeatable. Edoderoo (talk) 17:24, 25 April 2020 (UTC)
- @Edoderoo: do you know if this is fixable via a script? --Wolbo (talk) 16:48, 25 April 2020 (UTC)
I suggest the creation of an additional property, to be called something like 'ITF player ID 2020'. Its value needs to have the format helena-vildova/800647823/cze according to my belief. The remainder of the URL (/wt/s/overview/) turns out to be unneeded to get at the player's profile page. The bulk of the players, enjoying a working ITF redirect on the old number, won't need this; at least not straightaway. The new property can be used for new players, for old players with unknown old number, and for old players where the redirect does not work, such as Helena Vildová (Q3129670). Perhaps we can migrate the bulk later. Pommée (talk) 11:35, 1 August 2020 (UTC)
Additional clarification
The plan is as follows: the existing ITF player ID before 2020 (archived) (P599) keeps its URL unchanged (https://www.itftennis.com/procircuit/players/player/profile.aspx?playerid=$1
); the second property needs to have the new ITF URL (https://www.itftennis.com/en/players/$1
). This allows the tennis community to have a migration period in which the new player id's are gradually entered. Highest priority will have those players who are relatively new, and have no (known) old id – specifying their new id makes their ITF profile page at long last available. At the same time, the thousands (>7000) of existing players don't lose their access through the old id (which is fortunately redirected by ITF). It is crucial that the old id remains operational, because several wikipedia's depend on the P599 property to provide the ITF profile page link on their tennis players' wikipedia articles. These include: nl:Sjabloon:Standaardlinks tennisser, en:Template:Sports links, fr:Modèle:Bases sport, de:Vorlage:ITF, and several other languages. Individual language wikipedia's will make an addition to their template, showing the new link if specified, otherwise the old link. After this has been done, the international tennis community has ample time to edit the wikidata item of existing players, adding the new id to it. (There is some evidence here (in Dutch) that no automated script is possible; as a consequence every player must be treated manually.) Strong recommendation: leave the old id intact; don't remove it. It will forever remain useful to search the old version of the ITF profile page at the Internet Archiver – this is crucial to find player data that is no longer shown on the current ITF player profile page (such as birth date and birth place, and a few others), for which often a source reference is still required, either on wikidata or on some language wikipedia.
Notified participants of WikiProject Tennis – Does this plan have some support from other wikipedia's? Pommée (talk) 11:38, 13 August 2020 (UTC) (speaking on behalf of the Dutch wikipedia)
- Go ahead Pommée. I myself don't have much of an idea of the matter, but your explanation looks very reasonable!--Siebenschläferchen (talk) 22:27, 13 August 2020 (UTC)
- Support. Openbk (talk) 14:16, 17 August 2020 (UTC)
- Sounds good. Stryn (talk) 15:29, 17 August 2020 (UTC)
- Has there been any progress made on this? I just ran across the same issue today with the URL mismatch. Steel1943 (talk) 07:58, 8 September 2020 (UTC)
- On 20 August 2020, I requested (here) the creation of abovementioned property that is needed to make further progress. We are waiting for the Wikidata authorities to execute this. There seems to be nothing that plain users can do to make the next step in this process. Pommée (talk) 19:24, 8 September 2020 (UTC)
- Thanks for pushing this forward. The new property was created as ITF player ID 2020 (P8618). However, I would like to see the reasoning for that no automated script is possible. When you navigate to the legacy identifier, you are redirected to the new url. So as long as this redirect is reproducible via a script, the migration should be smooth. --Matěj Suchánek (talk) 08:20, 29 September 2020 (UTC)
- Update: Having tried it myself, I believe the web has some kind of protection from data-mining (not quite what Edoderoo suggested with JavaScript, the site yields HTTP redirects for requests in browser). So indeed, this is likely for humans. --Matěj Suchánek (talk) 09:05, 9 October 2020 (UTC)