Property talk:P4731
Jump to navigation
Jump to search
Documentation
The Baseball Cube player ID
identifier of a baseball player at thebaseballcube.com
identifier of a baseball player at thebaseballcube.com
[create Create a translatable help page (preferably in English) for this property to be included here]
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/P4731#Single value, SPARQL
Distinct values: this property likely contains a value that is different from all other items. (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/P4731#Unique value, SPARQL (every item), SPARQL (by value)
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/P4731#Format, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P4731#Format, SPARQL
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/P4731#Item P31, hourly updated report, search, SPARQLScope 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/P4731#Scope, SPARQL
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/P4731#Item P106, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P4731#Item P106, 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/P4731#Entity types
Item “sport (P641): baseball (Q5369)”: Items with this property should also have “sport (P641): baseball (Q5369)”. (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/P4731#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.) |
|
Discussion
[edit]Broken - thebaseballcube.com has changed its identifiers
[edit]Babe Ruth Q213812 -> babe-ruth now links to an error - http://thebaseballcube.com/players/profile.asp?ID=babe-ruth The new value is 17474 - http://thebaseballcube.com/players/profile.asp?ID=17474
Pinging editors involved in creation discussion -
Notified participants of WikiProject Sport results @GZWDer, Pigsonthewing, Pasleim, ChristianKl, יונה בנדלאק, Matěj Suchánek:
-- Cabayi (talk) 10:50, 20 November 2018 (UTC)
- If this happens to all identifiers of this property and if this is a persistent change in the external database, the way to fix this problem is:
- propose a new property for this external database; make sure you clearly mention the problem with this old property
- once it is created, add new identifiers to items; maybe you can obtain a mapping table somewhere
- deprecate the formatter URL of this old property, and mark it as "obsolete" in labels
- items will have the old and the new identifiers after this is done, i.e. we intentionally do not remove the old identifiers even if there is no link/database access any longer
- Sorry, there is no simple solution to such problems. —MisterSynergy (talk) 11:05, 20 November 2018 (UTC)
- @MisterSynergy:, You're overestimating the extent of my interest in this problem. I was trying to steer the discussion at en:Template talk:Baseballstats#Retrosheet added to sandbox template towards using wikidata.
- The possibility of this breaking change happening was mentioned in the property's creation discussion and it was decided to press on regardless - I presume one of the participants at that discussion had/has a plan. Cabayi (talk) 11:15, 20 November 2018 (UTC)
- No problem, please read "you" as "whoever is interested to fix this" :-) The problem does not show up for the first time, so we do have some experience with it. Unfortunately the best-practice recipe is not know to everybody, thus I wanted to leave it here.
In case you have a mapping table of old and new identifiers, please let us know here at Wikidata as well. In that case, I’m sure we find someone to set this up for you. —MisterSynergy (talk) 11:21, 20 November 2018 (UTC)
- No problem, please read "you" as "whoever is interested to fix this" :-) The problem does not show up for the first time, so we do have some experience with it. Unfortunately the best-practice recipe is not know to everybody, thus I wanted to leave it here.
Pasleim did point to this [1] which may offer a way of getting at that mapping. Hope that helps, Cabayi (talk) 11:31, 20 November 2018 (UTC)
- I did some work on this at en:Template:Baseballstats and found that the old IDs will redirect to the new numeric IDs if the correct formatter URL is used. Below are three URLs for the TheBaseballCube.com's page on Cal Ripken. The first two examples redirect to the third example.
- Out of 8,193 uses of this property, only 10 were using the new numeric format. Therefore I changed the formatter URL to
http://www.thebaseballcube.com/profile.asp?P=$1
which works with the other 8,000+ uses of this property. The 10 numeric IDs, plus three other incorrect IDs, have been changed to work with that URL. As suggested by MisterSynergy above, a new property could be created for the numeric IDs. -- Zyxw (talk) 05:15, 29 December 2018 (UTC)
Kategorien:
- All Properties
- Properties with external-id-datatype
- Properties used on 10000+ items
- Properties with single value constraints
- Properties with unique value constraints
- Properties with format constraints
- Properties with constraints on items using them
- Properties with scope constraints
- Properties with entity type constraints
- Sports properties