Property talk:P3581

Documentation

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

Pro Football Hall of Fame ID (old)
identifier for American football players in the Pro Football Hall of Fame

Represents	Pro Football Hall of Fame (Q778412)
Data type	External identifier
Corresponding template	Template:Profootballhof (Q14397355)
Template parameter	en:Template:ProFootballHOF
Domain	people (note: this should be moved to the property statements)
Allowed values	\d+
Example	Dick Butkus (Q715511) → 39 Jack Ham (Q507024) → 86
Formatter URL	https://www.profootballhof.com/hof/member.aspx?PlayerId=$1
Robot and gadget jobs	From Wikipedia
Tracking: usage	Category:Pages using Wikidata property P3581 (Q28648853)
Related to country	United States of America (Q30) (See 682 others)
See also	Pro Football Hall of Fame ID (P6930)
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 Database reports/Constraint violations/P3581 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 527 Main statement 286 54.3% of uses Qualifier 2 0.4% of uses Reference 239 45.4% of uses
Search for values

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

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/P3581#Unique value, SPARQL (every item), SPARQL (by value)

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/P3581#Single value, SPARQL

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/P3581#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/P3581#Item P31, hourly updated report, search, SPARQL

Item “occupation (P106)”: Items with this property should also have “occupation (P106)”. (Help) List of violations of this constraint: Database reports/Constraint violations/P3581#Item P106, hourly updated report, 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/P3581#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/P3581#Scope, SPARQL

Item “sport (P641): American football (Q41323)”: Items with this property should also have “sport (P641): American football (Q41323)”. (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/P3581#Item P641, search, SPARQL

This property is being used by: it:Template:Collegamenti esterni Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Import

I've now imported ~200 of these values from en.Wikipedia. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:49, 3 February 2017 (UTC)

Change format?

@GZWDer, ArthurPSmith, Thierry Caro, Pigsonthewing: Hi all! Would you agree in changing the format from numbers (\d+; e.g. "39" -> https://www.profootballhof.com/hof/member.aspx?PlayerId=39) to letters (e.g. "dick-butkus" -> https://www.profootballhof.com/players/dick-butkus/)? If so, we can update the format and than the existing 260 values. --Epìdosis 10:21, 16 May 2019 (UTC)

General a number is a better identifier than a string just because it's unlikely to change; however in this case it looks like they are supporting the string form better (with a better URL?) I don't have a strong opinion here. ArthurPSmith (talk) 12:17, 16 May 2019 (UTC)

@ArthurPSmith: I agree about the fact that numbers are generally better than strings ... however, in this case I see no clear way to find the numeric equivalent of the string for any entry. I've found about 60 pages on en.wikipedia which have the new string ID in en:Template:Infobox NFL biography, so there are many pages that aren't already matched to Wikidata, and the only way I see to add new matches is to change the format from number to string. Or is there any way to find the numeric equivalent of the string? --Epìdosis 18:03, 16 May 2019 (UTC)

@Epìdosis: In order not to discard potentially useful data, why don't we keep also numerical ids tagging them as deprecated? In this way the single-value constraint (Q19474404) shouldn't be violated (e.g. here we don't get any warning). --Horcrux (talk) 14:11, 30 May 2019 (UTC)

@Horcrux: OK, let's go in this way. --Epìdosis 14:19, 30 May 2019 (UTC)

@Epìdosis: Nope, this won't work because the url patterns for numerical and non-numerical ids are different. Do you know some qualifier (such as series ordinal (P1545) or others) through which we could save the number or it doesn't worth? --Horcrux (talk) 09:50, 31 May 2019 (UTC)

@Horcrux: I don't know any qualifier ... in my opinion we could keep the old numerical IDs as deprecated even if the URL doesn't work with them. Otherwise, if we remove them, they could still be found in page history. --Epìdosis 10:11, 31 May 2019 (UTC)

• The normal way to go is to create a new property for the new identifier and just deprecate the formatter url from this one. --- Jura 10:20, 31 May 2019 (UTC)

@Jura1: OK; is it necessary a new property proposal? --Epìdosis 10:36, 31 May 2019 (UTC)

Yes. One could mostly do a copy-and-paste of the previous one. --- Jura 10:48, 31 May 2019 (UTC)

Proposal created: Wikidata:Property proposal/Pro Football Hall of Fame ID (new). --Epìdosis 10:57, 31 May 2019 (UTC)

@GZWDer, ArthurPSmith, Thierry Caro, Pigsonthewing, Jura1: @Horcrux:  Done Pro Football Hall of Fame ID (P6930) created and all old values of this property have been associated with values of the new property. --Epìdosis 16:15, 29 June 2019 (UTC)