Property talk:P4731

Documentation

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

The Baseball Cube player ID
identifier of a baseball player at thebaseballcube.com

Applicable "stated in" value	The Baseball Cube (Q21470099)
Data type	External identifier
Corresponding template	Template:Baseball-Cube (Q22778099)
Template parameter	cube at en:Template:Baseballstats
Allowed values	\d+
Example	Brian Johnson (Q4964224) → 158314 Ramón de los Santos (Q7290582) → 10589 Miguel Socolovich (Q3313005) → 128439
Formatter URL	http://www.thebaseballcube.com/players/profile.asp?ID=$1
Tracking: usage	Category:Pages using Wikidata property P4731 (Q47165331)
Lists	Items with the most statements of this property Count of items by number of statements (chart) Items with the most statements Items with the fewest statements Count of items by number of sitelinks (chart) Items with the most sitelinks Items with the most sitelinks, but no link to one Wikipedia (sample: Welsh Wikipedia, cywiki) Items with the fewest sitelinks Most linked wikis Items with the most identifier properties Items with no other external identifier Items with no other statements Most recently created items Items with novalue claims Items with unknown value claims Usage history (total) Usage history (main statement) Chart by item creation date Map of people by place values: place of birth educated at work location residence place of death place of burial January 1st dates People with date of birth on January 1 People with date of death on January 1 People with both dates on January 1 Mix'n'match (Report) Database reports/Constraint violations/P4731 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 24,185 Main statement 22,773 94.2% of uses Qualifier 3 <0.1% of uses Reference 1,409 5.8% of uses
Search for values

[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)

Format “\d+”: value must be formatted using this pattern (PCRE syntax). (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#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, SPARQL

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/P4731#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/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: it:Template:Collegamenti esterni ja:Template:MLBstats Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Discussion

Broken - thebaseballcube.com has changed its identifiers

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 -

John Vandenberg (talk) 04:17, 28 November 2013 (UTC)
Bill william compton
--►Cekli829 23:32, 31 January 2014 (UTC)
VicVal (talk) 17:14, 24 October 2015 (UTC)
AmaryllisGardener ^talk 19:03, 24 April 2016 (UTC)
Tubezlob (🙋) 16:06, 6 October 2016 (UTC)
Sannita - not just another it.wiki sysop 17:24, 14 July 2017 (UTC)
Jmmuguerza (talk) 03:34, 24 August 2017 (UTC)
MisterSynergy
Xaris333
Migrant
Mad_melone
Сидик из ПТУ
Laszaroh
Habst

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)

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.

1. http://www.thebaseballcube.com/players/R/Cal-Ripken.shtml
2. http://www.thebaseballcube.com/profile.asp?P=Cal-Ripken
3. http://www.thebaseballcube.com/players/profile.asp?ID=550

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)