Property talk:P2696
Documentation
gymnast's identifier at the database of the International Federation of Gymnastics
List of violations of this constraint: Database reports/Constraint violations/P2696#Single value, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P2696#Entity types
List of violations of this constraint: Database reports/Constraint violations/P2696#Scope, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P2696#Item P641, search
List of violations of this constraint: Database reports/Constraint violations/P2696#Item P106, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P2696#Item P7440, 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]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)
- @Horcrux: OK ... so what can be done? --Epìdosis 08:37, 7 October 2019 (UTC)
- Isn't this a different type of ID that should use another property? --- Jura 08:43, 7 October 2019 (UTC)
- @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)- @Epìdosis, Jura1: Here you can find the items for which the new property is necessary. --Horcrux (talk) 16:13, 7 October 2019 (UTC)
- 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)
- @Jura1: It definitely is. Just found two different items for the same athlete (with and without
- Isn't this a different type of ID that should use another property? --- Jura 08:43, 7 October 2019 (UTC)
@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)
- Done --Horcrux (talk) 09:35, 16 October 2019 (UTC)
- All Properties
- Properties with external-id-datatype
- Properties used on 1000+ items
- Properties with constraints on items using them
- Properties with format constraints
- Properties with single value constraints
- Properties with unique value constraints
- Properties with entity type constraints
- Properties with scope constraints
- Sports properties