Property talk:P597

Item “occupation (P106): tennis player (Q10833314), wheelchair tennis player (Q18814798)”: Items with this property should also have “occupation (P106): tennis player (Q10833314), wheelchair tennis player (Q18814798)”. (Help)

List of violations of this constraint: Database reports/Constraint violations/P597#Item P106, hourly updated report, search

Item “sex or gender (P21): female (Q6581072), trans woman (Q1052281)”: Items with this property should also have “sex or gender (P21): female (Q6581072), trans woman (Q1052281)”. (Help)

List of violations of this constraint: Database reports/Constraint violations/P597#Item P21, hourly updated report, search

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/P597#Unique value, hourly updated report, SPARQL (every item), SPARQL (by value)

Format “\d+”: 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/P597#Format, SPARQL

Type “human (Q5)”: item must contain property “instance of (P31)” with classes “human (Q5)” or their subclasses (defined using subclass of (P279)). (Help)

List of violations of this constraint: Database reports/Constraint violations/P597#Type Q5, hourly updated report, SPARQL

Conflicts with “instance of (P31): career statistics (Q20054355)”: this property must not be used with the listed properties and values. (Help)

List of violations of this constraint: Database reports/Constraint violations/P597#Conflicts with P31, hourly updated report, 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/P597#Entity types

Item “ITF player ID 2020 (P8618)”: Items with this property should also have “ITF player ID 2020 (P8618)”. (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/P597#Item P8618, 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/P597#Scope, SPARQL

Item “sport (P641): tennis (Q847)”: Items with this property should also have “sport (P641): tennis (Q847)”. (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/P597#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.)

List of properties

I didn't know where to add this to the list of properties. Where is ATP player ID (P536) listed? --Tobias1984 (talk) 09:22, 5 June 2013 (UTC)[reply]

URL was not working

Notified participants of WikiProject Tennis Item is not working (URL's new format), we need to fix it.--Kacir (talk) 02:18, 14 November 2019 (UTC)[reply]

Yeah, last monday the WTA again did change the format. The new layout of the site is also very hard to read :-( Edoderoo (talk) 06:47, 14 November 2019 (UTC)[reply]

I'm afraid we also need to change the data of some/many wikidata-items, as the 6-digit-ID is not enough to get the working URL, as the name of the player is added to this. On many of the Dutch articles there is a working link available now, maybe this can be used to update WikiData with a python script. Edoderoo (talk) 08:11, 14 November 2019 (UTC)[reply]

Perhaps we should wait a little while. After the previous upset, 2 1/2 years ago, we went to a lot of handwork to enter the number plus name information into this property. Then WTA website personnel added a website directory www.wtatennis.com/player-profile/ providing us with the necessary redirects. So we took the name part away. I guess that an en-wiki colleague with WTA connections convinced them to do that. This may happen again. @Wolbo: Are en-wikipedians in the process of influencing the WTA? Pommée (talk) 09:55, 14 November 2019 (UTC)[reply]

I have found relevant section on En Wiki Tennis Project.--Kacir (talk) 12:47, 14 November 2019 (UTC)[reply]

This is a big mess, as the WTA has Chinese player's names swapped to Western order, and the WTA treats diacritic's inconsistently, with some being simplified, and others being replaced with hyphens in the URL. I wish we at enwiki had the influence to convince the WTA to abandon using names as identifiers. I've already created a spreadsheet with the new URLs from this Wikidata property fixing the aforementioned issues as well as can be done with limited manual review. Iffy (talk) 13:39, 14 November 2019 (UTC)[reply]

I can create a script to upload/update the new formatted WTA identifier, for the items where the new format is known. If there is a database/spreadsheet/template/etc available, please let me know. I know that we have about (the top) 450 players available on the Dutch wiki, thanks to user Pommee. It is indeed a big mess, but to be honest, the whole WTA-IT-department seems to be a big mess. Hopefully we can fix this without too much manual effort, though. Edoderoo (talk) 17:00, 14 November 2019 (UTC)[reply]

@Edoderoo: [1] is what I've done, these should be the correct ID for most players. Iffy (talk) 10:18, 15 November 2019 (UTC)[reply]

Next week we have a TechStorm, after that I will put some time in this ... this looks pretty promising. Edoderoo (talk) 10:28, 15 November 2019 (UTC)[reply]

List looks good. Is it possible to create a list of players who cannot be updated automatically so those can be worked on manually? --Wolbo (talk) 11:14, 16 November 2019 (UTC)[reply]

I'd rather fix all of them first, and then deal with any errors on a case by case basis. I've just found a few issues where players whose names needed to be swapped were missing country data, which I've fixed in my spreadsheet. Iffy (talk) 11:52, 18 November 2019 (UTC)[reply]

Can someone get around to fixing these IDs soon? ~~The ITF have just broken their IDs Property:P599, so right now, no female tennis player has working URLs.~~ Thankfully the ITF fixed their IDs themselves, why couldn't the WTA do this? Iffy (talk) 13:38, 3 December 2019 (UTC)[reply]

ping User:Iffy, a script is right now running to fix the first top450 players. After that I will see to do a lot more based on the above mentioned Google Sheet. Edoderoo (talk) 18:43, 5 December 2019 (UTC)[reply]

Thank you! How long do you think it will take to do them all? Iffy (talk) 23:16, 5 December 2019 (UTC)[reply]

The Top450 are now done, that should ease the daily use of this property a lot. This weekend I'll concentrate on the rest from the Google Sheet, that should be an easy job after all. What will be left afterwards is gonna be manual fixing, but I guess that will be for a small list of players that are not anymore active. Edoderoo (talk) 07:59, 6 December 2019 (UTC)[reply]

I finished them yesterday. About ten were left to be done manually. Edoderoo (talk) 12:39, 8 December 2019 (UTC)[reply]

Strictly numerical vs. named identifiers

@Gymnicus, Kacir: Recent changes invalidated many identifiers. For example, Petra Kvitová (Q30812) has got 314206/petra-kvitova, for which https://www.wtatennis.com/players/314206/petra-kvitova/name is generated, which does not work. If it was a single case, I would fix it myself, but there are almost 3 thousand similar identifiers. Only the numerical ones work, but there are less of them. I see there two formatter URLs as well as two regexes, but obviously there is no built-in way to choose (Wikidata does not work this way).

Please elaborate the motivation for your changes, and let's find a solution. --Matěj Suchánek (talk) 09:47, 19 July 2021 (UTC)[reply]

Thanks for the analysis and trying to fix it.--Kacir (talk) 18:59, 19 July 2021 (UTC)[reply]

@Matěj Suchánek: The problem with it was that my stack probably caused an error with Quickstatement or was too big or whatever. I do not know exactly. At least the end result was that only a fraction of the statements were improved and not all of them, as I had intended. In the meantime, however, the problem has been resolved. --Gymnicus (talk) 19:40, 19 July 2021 (UTC)[reply]

Indeed. The queries now confirm all identifiers are strictly numerical. --Matěj Suchánek (talk) 08:32, 20 July 2021 (UTC)[reply]

Property talk:P597

Contents

Documentation

List of properties

URL was not working

Strictly numerical vs. named identifiers

Navigation menu