Property talk:P8286

Documentation

• Start a query
• Current uses
• Statistics by class
• String length
• List of qualifiers
• Count

Olympedia people ID
identifier for an athlete (sportsperson), coach, referee, etc. at Olympedia.org

[create Create a translatable help page (preferably in English) for this property to be included here]

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

Single best value: this property generally contains a single value. If there are several, one would have preferred rank (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/P8286#single best value, SPARQL

Type “human (Q5), architectural firm (Q4387609), ministry of the Kingdom of Italy (Q26243694), commune of Italy (Q747074), group of humans (Q16334295)”: item must contain property “instance of (P31)” with classes “human (Q5), architectural firm (Q4387609), ministry of the Kingdom of Italy (Q26243694), commune of Italy (Q747074), group of humans (Q16334295)” or their subclasses (defined using subclass of (P279)). (Help)

List of violations of this constraint: Database reports/Constraint violations/P8286#Type Q5, Q4387609, Q26243694, Q747074, Q16334295, hourly updated report, SPARQL

Scope is as main value (Q54828448), as reference (Q54828450): the property must be used by specified way only (Help)

List of violations of this constraint: Database reports/Constraint violations/P8286#Scope, hourly updated report, SPARQL

Qualifiers “subject named as (P1810), alternative name (P4970), archive URL (P1065), archive date (P2960), reason for deprecated rank (P2241), occupation (P106)”: this property should be used only with the listed qualifiers. (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/P8286#allowed qualifiers, 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/P8286#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). Known exceptions: Turin (Q495), Holabird & Root (Q2309614), Lockwood, Greene & Co. (Q6665872), Zantzinger, Borie & Medary (Q8066296), Ministry of War (Q26844984), Delano & Aldrich (Q45153580)
List of violations of this constraint: Database reports/Constraint violations/P8286#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/P8286#Label in 'en' language, search, SPARQL

Without participation (P1344)
Item with a Olympedia people ID (P8286) identifier should have a participant in (P1344) claim for their Olympic participation (Help)
Violations query: SELECT DISTINCT ?item WHERE { ?item wdt:P8286 ?id . MINUS { ?item wdt:P1344 [] } } ORDER BY ASC(xsd:integer(STRAFTER(STR(?item), 'Q')))
List of this constraint violations: Database reports/Complex constraint violations/P8286#Without participation (P1344)

Human without occupation (P106)
Human items with an Olympedia people ID (P8286) identifier should have a occupation (P106) claim (Help)
Violations query: SELECT DISTINCT ?item WHERE { ?item wdt:P8286 ?id; wdt:P31 wd:Q5 . MINUS { ?item wdt:P106 [] } } ORDER BY ASC(xsd:integer(STRAFTER(STR(?item), 'Q')))
List of this constraint violations: Database reports/Complex constraint violations/P8286#Human without occupation (P106)

This property is being used by: de:Vorlage:Olympedia en:Template:Olympedia fi:Malline:Olympedia es:Plantilla:Olympedia, es:Plantilla:Olympedia/zona de pruebas it:Template:Collegamenti esterni, it:Template:Olympedia uk:Шаблон:Olympedia ja:Template:Olympedia ru:Шаблон:Olympedia nl:Sjabloon:Standaardlinks tennisser simple:Template:Olympedia als:Vorlage:Olympedia ar:قالب:مرجع أولمبيديا, ar:قالب:أولمبيديا et:Mall:Olympedia fa:الگو:Olympedia pt:Predefinição:Olympedia ro:Format:Olympedia sv:Mall:Olympedia hu:Sablon:Olympedia-profil zh:Template:Olympedia sr:Шаблон:Olympedia id:Templat:Olympedia lld:Template:Olympedia bn:টেমপ্লেট:Olympedia, bn:টেমপ্লেট:অলিম্পিডিয়া ur:سانچہ:اولمپیڈیا uz:Andoza:Olympedia th:แม่แบบ:Olympedia tr:Şablon:Olympedia gsw:Vorlage:Olympedia dag:Tɛmplet:Olympedia pa:ਫਰਮਾ:Olympedia sh:Šablon:Olympedia, sh:Šablon:Infokutija biatlonac arz:قالب:Olympedia bs:Šablon:Infokutija biatlonac, bs:Šablon:Infokutija biatlonac/Igralište mk:Предлошка:Olympedia ast:Plantía:Enllaces deportista/atleta Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Discussion

Import coming

As already indicated on the property proposal page, I have received a complete mapping table "Sports-Reference ID <-> Olympedia ID" from the Olympedia team in March this year via email; the mapping table has been compiled by them to help us Wikimedians to migrate weblinks away from Sports-Reference to a new, available database; fortunately, it is in excellent shape. I am going import the matches, roughly 130,000 identifiers, based on the current Sports-Reference.com Olympic athlete ID (archived) (P1447) claims within the next days. Thus, you do not need to look up thousands of identifiers now… —MisterSynergy (talk) 18:44, 4 June 2020 (UTC)

This import has more or less been finished now and there are almost 131,000 Olympedia identifiers mapped to Wikidata items. Quite some of the remaining ~34,000 identifiers can be matched to items without a Sports-Reference.com Olympic athlete ID (archived) (P1447) identifier, but my mapping table is exhausted and the rest needs to be done manually. —MisterSynergy (talk) 13:37, 6 June 2020 (UTC)

Hi, first, vielen dank @MisterSynergy:, großartige Arbeit hast du geleistet. I have two questions. What about the remaining ~34,000 identifiers, who can program a bot to import them? Second, is it possible to protect this property to avoid not specialized users (IP's, novice users and so on) vandalized it in all the elements in it is employed, for example this? I have not a large experience in Wikidata, all my experience is in Spanish Wikipedia, so I don`t know if it is possible to protect globally a property. Leonprimer (talk) 01:50, 12 June 2020 (UTC)

The remaining identifiers need to be matched individually, since they do not have a Sports-Reference counterpart which we could use for the matching. Maybe I'll try to come up with some script-based mix-n-match in the future as I did in the past with other properties, but this does not have high priority. I also do not expect that all of the missing Olympedia IDs already have Wikidata items which wait for the identifiers to be added.
The property values in items cannot be protected without a full protection of the items, and that would not be covered by the Wikidata:Page protection policy. However, since identifiers are usually not much of a target for vandals, I would not worry about this too much. We also have the constraints system to spot quite a lot of vandalism scenarios involving this identifier, and I will also occasionally compare all existing identifiers against the mapping table again (offline). ---MisterSynergy (talk) 10:12, 12 June 2020 (UTC)

@MisterSynergy: Is it possible to do a rest-mix'n'match ? Allthough I have added some few ID's manually for some speed skating related biographies (including some referees, youth olympic athletes and some head of national olympic committées). Best regards Migrant (talk) 00:53, 14 June 2020 (UTC)

I assume you refer to the Mix'n'match tool, right? Based on the mapping table that we received, we can't create a dataset for Olympedia in that tool. We really only have bare "SR-ID <-> Olympedia ID" pairs for those Olympedia-IDs which have a SR counterpart. There is no information about names or dates of birth/death in that mapping table, and Olympedia-IDs which were not published in SR are also missing. I need to figure out how to proceed with the remaining ~35.000 identifiers. —MisterSynergy (talk) 09:25, 14 June 2020 (UTC)

Yes, @MisterSynergy:, that's the tool I am thinking of. I was thinking when you have 2 databases of ID's which are about the same theme, but one of them (SR-ID) are mainly included in the other (Olympedia ID) so if you remove the ID's that are in the other ones from the bigger database (Olympedia ID) and make a mix'n'match of the rest-ID's from the bigger database. Best regards Migrant (talk) 10:04, 14 June 2020 (UTC)

I currently do not have a full list of valid Olympedia IDs, unfortunately. I only know the ones with a Sports-Reference counterpart. For mix-n-match to be useful, we also need at least names and a year of birth, right. —MisterSynergy (talk)

That's making sense to me too, @MisterSynergy:. Another question: Is it okay to manually add ID's from Olympedia for Youth Olympic athletes and Referees or sports officials/leaders of sporting organisations that have an wikipedia-article ? Best regards Migrant (talk) 10:16, 14 June 2020 (UTC)

Yes, sure it is okay to add identifiers manually. Whatever we will try to match automatically will always consider the status quo, and at best also try to verify it. This is an identifier property as all others, we were just lucky to receive enormous help by the Olympedia team for the initial setup of 80% of all values. —MisterSynergy (talk) 10:33, 14 June 2020 (UTC)

2022 Winter Olympics profiles

I just noticed that Olympedia has made several new profile-pages for this upcoming winter games in Beijing. Any mass-import organized or planned ? Do you know of something? User:MisterSynergy Best regards Migrant (talk) 18:02, 31 January 2022 (UTC)

No plans yet. For the 2020 Games, this mix'n'match catalog was quite helpful. I still have the script that I used to crawl the input to make the catalog. However, it only really works if event pages and athlete profiles are already available at Olympedia on a large scale, which does not seem to be the case for 2022 yet. —MisterSynergy (talk) 18:57, 31 January 2022 (UTC)

Here's 2 pages for the dutch roller skater and speed skater Merijn Scheperkamp (Q99509848) roller skater -> https://www.olympedia.org/athletes/2503654 and speed skater -> https://www.olympedia.org/athletes/148677 Best regards Migrant (talk) 22:04, 31 January 2022 (UTC)

Yes, but the Games edition page is still pretty empty. As far as I remember, they will add/update the pages during the Games and in the weeks after. A large scale import is only feasible once everything is pretty much there. —MisterSynergy (talk) 22:20, 31 January 2022 (UTC)

Okay... Thanks for your answers. I gave the site a feedback about this double-profile though. --Migrant (talk) 00:54, 1 February 2022 (UTC)

Those have been merged to the latter one here -> https://www.olympedia.org/athletes/148677 . Best regards Migrant (talk) 22:21, 2 February 2022 (UTC)

Improvement suggestions

With this query, items can be found that are in de:Kategorie:Teilnehmer_an_Olympischen_Spielen, but have no P8286. Similarly this can be done for the english wikipedia, which will probably also bring items without identifier to the surface.
Furthermore, the complex contraint regarding the participation should be improved to apply specifically for olympic participations. Currently, any other participation also leads to items not being listed in the constraint report. Steak (talk) 15:50, 19 January 2021 (UTC)

This is probably the dewiki Petscan query you are looking for. I think most of them are either participants of the ancient Olympics, alternate athletes, or YOG participants that have not been part of Sports-Reference.com/Olympics previously.
The participation constraint needs to be a "complex constraint" based on a SPARQL query. We do have items for all events of the modern Olympics, so this should technically be possible immediately. However, since Olympedia event ID (P9055) was recently approved, I think it would be more useful to populate event items with that new Olympedia event identifier first, in order to make the participation claim management in athlete items easier. I plan to import Olympedia event ID (P9055) in the next weeks, but there is a pile of other stuff waiting for my attention as well. —MisterSynergy (talk) 16:38, 19 January 2021 (UTC)

Future of Olympedia uncertain

Update by Bill Mallon via Twitter: https://nitter.net/bambam1729/status/1740775538460107156 (I am not directly linking to Twitter in order to allow reading access for those without a Twitter account.)

Basically the thing belongs to the IOC (since 2016), but it has been updated by the same group of enthusiasts since then that has created the database long before 2016. The contract has not been renewed for 2024 by the IOC, so as of now there will not be updates by the group of volunteers anymore. It is unclear what the IOC will be doing with it, and whether it will remain publicly accessible after all. —MisterSynergy (talk) 23:03, 14 January 2024 (UTC)