Property talk:P2696

From Wikidata
Jump to navigation Jump to search

Documentation

FIG gymnast licence number
gymnast's identifier at the database of the International Federation of Gymnastics
Associated itemInternational Gymnastics Federation (Q379079)
Applicable "stated in" valueFIG database (Q106711852)
Has qualitynumeric identifier (Q93868746)
Data typeExternal identifier
Corresponding templateTemplate:FIG (Q8342800)
Template parameter|lic= in en:Template:FIG
Domainhuman (Q5) (note: this should be moved to the property statements)
Allowed values[1-9][0-9]*
ExampleAly Raisman (Q238663)13822
Jana Bieger (Q98055)67
Lucas Fischer (Q15391946)5443
Manrique Larduet (Q21283053)12347
Sourcehttps://gymnastics.sport/site/athletes/lic_view.php
Formatter URLhttps://gymnastics.sport/site/athletes/bio_detail.php?id=$1&type=licence
Robot and gadget jobsEdgars2007's bot can import values from Wikipedias
Tracking: usageCategory:FIG template using Wikidata (Q23727146)
See alsoUSA Gymnastics athlete ID (P3671), IGHOF athlete ID (P4469), The Gymternet gymnast ID (P5788), FIG gymnast biography number (P7440), Czech Gymnastics athlete ID (P8932), Swiss-Gym Male ID (P8829), Swiss-Gym Female ID (P8830)
Lists
Proposal discussionProposal discussion
Current uses
Total2,647
Main statement2,48393.8% of uses
Qualifier40.2% of uses
Reference1606% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Item “instance of (P31): human (Q5): Items with this property should also have “instance of (P31): human (Q5)”. (Help)
List of violations of this constraint: Database reports/Constraint violations/P2696#Item P31, hourly updated report, search, SPARQL
Format “[1-9][0-9]*: value must be formatted using this pattern (PCRE syntax). (Help)
List of violations of this constraint: Database reports/Constraint violations/P2696#Format, hourly updated report, SPARQL
Single value: this property generally contains a single value. (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/P2696#Single value, 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/P2696#Unique value, hourly updated report, SPARQL (every item), SPARQL (by value)
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/P2696#Entity types
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/P2696#Scope, SPARQL
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).
List of violations of this constraint: Database reports/Constraint violations/P2696#Item P106, search, SPARQL
Item “FIG gymnast biography number (P7440): Items with this property should also have “FIG gymnast biography number (P7440)”. (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/P2696#Item P7440, search, SPARQL

Discussion

[edit]

URL format

[edit]

As discussed with Epìdosis, I expanded the URL format for supporting the case id=ID_NUM&type=licence, which is always different from just id=ID_NUM.

The problem is that here and here the new URL appears to be broken, as the & and = symbols are encoded (or better, double-encoded!) with URL entities.

As you may see from here (and from the examples in the #Documentation), the data itself is perfectly fine, the ony problem is the automatic URL-encoding within namespaces 0 and 120. --Horcrux (talk) 08:31, 7 October 2019 (UTC)[reply]

@Horcrux: OK ... so what can be done? --Epìdosis 08:37, 7 October 2019 (UTC)[reply]
Isn't this a different type of ID that should use another property? --- Jura 08:43, 7 October 2019 (UTC)[reply]
@Jura1: It definitely is. Just found two different items for the same athlete (with and without &type=licence) using the internal search engine. So, I guess this edit should be rollbacked and a new property should be created. Anyway, the URL problem should eventually be fixed. --Horcrux (talk) 09:23, 7 October 2019 (UTC)[reply]
@Epìdosis, Jura1: Here you can find the items for which the new property is necessary. --Horcrux (talk) 16:13, 7 October 2019 (UTC)[reply]
@Jura1, Horcrux: See Wikidata:Property proposal/FIG gymnast (no licence) identifier. --Epìdosis 19:16, 7 October 2019 (UTC)[reply]
I'd rather keep this property working for all current values and create a new one for new values. I don't fully understand which ones are which though and how they are called. --- Jura 08:25, 8 October 2019 (UTC)[reply]

@Horcrux: FIG gymnast biography number (P7440) has been created, you can start replacing. Thank you very much! --Epìdosis 08:17, 16 October 2019 (UTC)[reply]

✓ Done --Horcrux (talk) 09:35, 16 October 2019 (UTC)[reply]