Property talk:P8990
Documentation
identifier for a person in the database of World Rowing (FISA)
World Rowing UUID (P8990) was a simple authority control property to link Wikidata items to entries in the World Rowing athlete database (Q21008628). This database is operated by World Rowing (Q684885) (formerly known as FISA), the international governing body of rowing (Q159354), and contains the most complete set of data about international rowing persons and rowing events which is publicly available.
On 17 December 2020, World Rowing (Q684885) relaunched their website and issued a new Universally Unique Identifier (Q195284) for all rowers; these may be found in the Wikidata property World Rowing UUID (P8990).
On 9 January 2021, World Rowing (Q684885) returned to using the previous numeric identifier (Q93868746) for all rowers, these may be found in the Wikidata property World Rowing ID (P2091).
Add this property edit
To use this property, you need to determine the identifier in the World Rowing database: let’s consider the example of the Olympic champion Kim Brennan (Q576663); the profile about her can be found at
- https://web.archive.org/web/20210108095753/https://worldrowing.com/athlete/3901879a-7bd1-46c5-89ba-3d8ef2fb45aa
- https://world-rowing-api.soticcloud.net/stats/api/person/3901879a-7bd1-46c5-89ba-3d8ef2fb45aa
The yellow part is the identifier to use within this property, while the remaining part of the URL is defined within the property page World Rowing UUID (P8990) using the formatter URL (P1630) property. The new World Rowing identifiers technically have the format of pseudo-random Universally Unique Identifiers (UUIDs).
FISA maintains a pretty nice database which comprises data of around 42 000 persons (as of December 2020); however, in roughly 1–2% of the cases there are multiple entries for the same person (amount estimated). This means that one needs to add multiple values for this property within an item, which in turn violates the single-value constraint (Q19474404) defined by a property constraint (P2302) statement on Property:P8990. In case of multiple IDs for one person, qualify each identifier with a subject named as (P1810) qualifier using the database entry title (do not use the all-uppercase family names from the database). We want to avoid using exception to constraint (P2303) qualifiers to the single-value constraint (Q19474404).
In case of multiple values it is also important to set proper ranks for the individual claims. If all important information about a person is contained within a single profile out of the available profiles, then mark the important claim with preferred rank. There are cases, however, in which this is not possible and the information is distributed across multiple important profiles. All of them should use the normal rank. Deprecated rank should not be used at all for any value that has been valid in the past.
Please also add empty profiles which often do not contain much more than a person’s name. We do not know whether FISA will start to add content to database entries which are still (almost) empty.
Use this property edit
Within Wikidata this property is used to link against FISA’s database and to identify multiple items per person (via the distinct-values constraint (Q21502410), defined by a property constraint (P2302) statement on Property:P8990). Identifiers can also be queried using the common query tools for applications outside Wikimedia.
On Wikipedias, there are typically templates available (such as Template:World Rowing (Q14334032) and others, see {{ExternalUse}} template on Property talk:P8990) which either store the same identifier locally within the Wikipedia, or take the data from Wikidata by using the {{#property:P8990}} or {{#statements:P8990}} parser function or more sophisticated functions of Module:Wikidata (Q12069631) and others. In case of the existence of a local value, one can also compare it to the Wikidata value and make use of maintenance categories, which are linked from the {{Property documentation}} template on Property talk:P8990. However, be aware that in case of an item with multiple claims, of which none is the primary one marked with preferred rank, you also might get multiple values if you pull this information from Wikidata.
See also edit
This property is maintained by WikiProject Rowing.
List of violations of this constraint: Database reports/Constraint violations/P8990#single best value, SPARQL
[0-9a-f]{8}\-[0-9a-f]{4}\-4[0-9a-f]{3}\-[0-9a-f]{4}\-[0-9a-f]{12}|”: value must be formatted using this pattern (PCRE syntax). (Help)
List of violations of this constraint: Database reports/Constraint violations/P8990#Entity types
List of violations of this constraint: Database reports/Constraint violations/P8990#Item P641, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P8990#Item P2091, 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
IDs have been modified edit
TherasTaneel mentionned on my talk page that ID does not point to the good person. For example, bcb7936e-9f2e-4319-9c96-022fee09144a previously pointed to Hamish Bond (Q1321253) but now points to Nicolas Ablain (no item yet for him in Wikidata). Does someone know how to manage this? @MisterSynergy, Schwede66, Sic19, UWashPrincipalCataloger, Trade: ping people involved in the property creation. Pamputt (talk) 16:16, 13 February 2022 (UTC)
- I’ve seen this back in November, but I am procrastinating to deal with it. WorldRowing messed this up badly.
The old numeric identifiers World Rowing ID (P2091) for the very same database are still there, and they work actually. —MisterSynergy (talk) 16:49, 13 February 2022 (UTC)- Related: the UUID identifiers are apparently still in use, in some form, for the WorldRowing API. However, I cannot find them in use for website URLs. I have thus changed the formatter URL to point to the API (hosted at their technical provider Sotic), so that editors and data users can still verify correctness of the UUID identifiers. For URLs, the old numeric identifiers of World Rowing ID (P2091) should be used instead. —MisterSynergy (talk) 09:36, 22 March 2022 (UTC)
- Some more findings:
- Apparently no UUIDs have been reassigend to other athletes. It "just" happens to be the case that the website expects numeric identifiers (again) in the URLs—those as in World Rowing ID (P2091)—and it interprets everything as a numeric identifier in a special way. For example, the above mentioned "bcb7936e-9f2e-4319-9c96-022fee09144a" is interpreted as "22", which happens to be the profile of Nicolas Ablain. Everything after the last hyphen is interpreted as a numeric identifier, as long as numbers show up; leading zeros are being removed.
- It also seems that they have added UUIDs for all numeric identifiers that had been in the database before the migration took place. Initially after the migration, the database had shrunk by ~20% (number of profiles) as many empty profiles had disappeared. They are now back, and apparently every numeric_id has an UUID counterpart. All of these pairs are in Wikidata (as of today). If anyone is interested, I can provide a full mapping table of both identifiers.
- The UUIDs are still in use internally; they use it to make API calls with javascript. Thus, this property should definitely be kept.
- —MisterSynergy (talk) 22:58, 25 March 2022 (UTC)
- Some more findings:
- Related: the UUID identifiers are apparently still in use, in some form, for the WorldRowing API. However, I cannot find them in use for website URLs. I have thus changed the formatter URL to point to the API (hosted at their technical provider Sotic), so that editors and data users can still verify correctness of the UUID identifiers. For URLs, the old numeric identifiers of World Rowing ID (P2091) should be used instead. —MisterSynergy (talk) 09:36, 22 March 2022 (UTC)