Property talk:P4937

Documentation

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

Japan Rugby Football Union player ID
identifier for a rugby union player on the Japan Rugby Football Union website

Associated item	Japan Rugby Football Union (Q764417)
Data type	External identifier
Allowed values	\d+
Example	Michael Leitch (Q6832188) → 252737 281792 346604 381479 411357 416649 Ayaka Suzuki (Q11648832) → 200386 248754 383497 Chiharu Nakamura (Q26236482) → 187362 200383 261288 422368 Lote Tuqiri (Q6684640) → 252597
Source	https://www.rugby-japan.jp/japan/member/ http://en.rugby-japan.jp/japan-womens/member/ https://www.rugby-japan.jp/japan-womens/member/ http://en.rugby-japan.jp/sevens-womens/member/ https://www.rugby-japan.jp/sevens-womens/member/ http://en.rugby-japan.jp/sevens/member/ https://www.rugby-japan.jp/sevens/member/
Formatter URL	https://www.rugby-japan.jp/player/$1 http://en.rugby-japan.jp/japan/member/detail/$1 http://en.rugby-japan.jp/japan-womens/member/detail/$1 http://en.rugby-japan.jp/schedule/player/$1/ http://en.rugby-japan.jp/sevens-womens/member/detail/$1 http://en.rugby-japan.jp/sevens/member/detail/$1
Tracking: usage	Category:Pages using Wikidata property P4937 (Q50410948)
Related to country	Japan (Q17) (See 145 others)
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) 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/P4937 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 29 Main statement 15 51.7% of uses Qualifier 14 48.3% 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/P4937#Item P31, hourly updated report, search, 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/P4937#Unique value, SPARQL (every item), SPARQL (by value)

Item “occupation (P106): rugby union player (Q14089670), rugby sevens player (Q26237722)”: Items with this property should also have “occupation (P106): rugby union player (Q14089670), rugby sevens player (Q26237722)”. (Help)

List of violations of this constraint: Database reports/Constraint violations/P4937#Item P106, hourly updated report, search

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/P4937#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/P4937#Scope, SPARQL

Item “sport (P641): rugby union (Q5849), rugby sevens (Q270102)”: Items with this property should also have “sport (P641): rugby union (Q5849), rugby sevens (Q270102)”. (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/P4937#Item P641, search

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/P4937#Format, SPARQL

Note about this property

This property links a Rugby Union player item to player articles in Japan Rugby Football Union website. The values are not identifying players, but identifying pages describing a player at some time. A player can have multiple such pages time to time, so we cannot assume single-value constraint. Mzaki (talk) 05:47, 22 January 2024 (UTC)

There are 4 player properties related to Japan Rugby Football Union: Japan Rugby Football Union player ID (P4937), P4938 (P4938), P4940 (P4940), and P4941 (P4941). All these properties share the ID namespace, and accessible with the same URL, formatter URL (P1630)https://www.rugby-japan.jp/player/$1. The difference among them comes from the fact that the player will be listed in 4 different categories and accessible with the specific URL, formatter URL (P1630)https://www.rugby-japan.jp/****/member/detail/$1 during he/she is selected as a national team member of 4 categories: men's, women's, men's sevens, and women's sevens. I think this distinction is needless and these 4 properties should be unified. Mzaki (talk) 07:09, 22 January 2024 (UTC)

Hello @Mzaki. When I proposed these 4 Properties for creation, I think that the URL structure was not shared between the 4 categories and the website has since evolved... or I was not aware of it ! In any case, if a shared URL structure exists, I am in favour of merging the 4 properties ID. - Daxipedia - 達克斯百科 (talk) 21:43, 22 January 2024 (UTC)

Thanks for your comment, @Daxipedia. Since P4938, P4940, and P4941 have single use for each, actually nobody uses after its creation based on the proposal, we can proceed for requesting deletion of these 3 properties in order to unify them into P4937. Mzaki (talk) 09:45, 23 January 2024 (UTC)

Since there was no objection against my proposal for almost a month, I have changed the English label and description to accommodate statements of 3 properties, and flushed the translations in other languages, keeping old labels as aliases. Mzaki (talk) 14:25, 20 February 2024 (UTC)