Property talk:P11127

Documentation

Associated itemMinistry of Education, Culture, Sports, Science and Technology (Q1054379)
Has qualitycheck digit (Q1337960)
Data typeExternal identifier
Domainschool (Q3914) or higher education institution (Q38723)
Allowed values([ACDFH][12]|[BEG]1)(0[1-9]|[123][0-9]|4[0-7])[123][1-9][0-9]{7}
ExampleUniversity of Tokyo (Q7842) → F113110102700
Keio Senior High School (Q11495160) → D114310000222
Takarazuka Music School (Q10956082) → H228310000663
Sourcehttps://www.mext.go.jp/b_menu/toukei/mext_01087.html
Related to country  Japan (Q17) (See 148 others)
See alsoidentification code for Japanese universities and colleges (P7251), Japanese High School Code (P1386)
Lists
Proposal discussionProposal discussion
Current uses
Total36,491
Main statement36,488 out of 58,645 (62% complete)>99.9% of uses
Qualifier3<0.1% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Allowed entity types are Wikibase item (Q29934200): the property may only be used on a certain entity type (Help)
List of violations of this constraint: Database reports/Constraint violations/P11127#Entity types, hourly updated report
Scope is as main value (Q54828448): 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/P11127#Scope, SPARQL
Label required in languages: ja: Entities using this property should have labels in one of the following languages: ja (Help)
List of violations of this constraint: Database reports/Constraint violations/P11127#Label in 'ja' language, hourly updated report, search, SPARQL
Format “([ACDFH][12]|[BEG]1)(0[1-9]|[123][0-9]|4[0-7])[123][1-9][0-9]{7}: value must be formatted using this pattern (PCRE syntax). (Help)
List of violations of this constraint: Database reports/Constraint violations/P11127#Format, hourly updated report, 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/P11127#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/P11127#Single value, SPARQL
Single best value: this property generally contains a single value. If there are several, one would have preferred rank (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/P11127#single best value, SPARQL
Type “school (Q3914), higher education institution (Q38723): item must contain property “instance of (P31)” with classes “school (Q3914), higher education institution (Q38723)” or their subclasses (defined using subclass of (P279)). (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/P11127#Type Q3914, Q38723, SPARQL
Item “country (P17): Japan (Q17): Items with this property should also have “country (P17): Japan (Q17)”. (Help)
List of violations of this constraint: Database reports/Constraint violations/P11127#Item P17, hourly updated report, search, SPARQL
Item “instance of (P31): Items with this property should also have “instance of (P31)”. (Help)
List of violations of this constraint: Database reports/Constraint violations/P11127#Item P31, hourly updated report, search, SPARQL
 
MEXT School Code
MEXT School Code that have wrong checksum. NOTE: The IDs assigned in 2020-2022 have checksum digits calculated slightly differently from the document. The SPARQL query below is designed to verify assigned codes on a de facto basis. The IDs newly assigned in 2023 seem to have checksum digits calculated exactly as the document says, but this is yet to be clarified. (Help)
Violations query: SELECT ?item ?value { { ?item wdt:P11127 ?value } UNION { ?statement pq:P11127 ?value . ?item ?p ?statement . ?prop wikibase:claim ?p } UNION { ?ref pr:P11127 ?value . ?statement prov:wasDerivedFrom ?ref . ?item ?p ?statement . ?prop wikibase:claim ?p } . FILTER( STRLEN(?value) = 13 ) . BIND(xsd:string(STRLEN(STRBEFORE("@ABCDEFGHIJKLMNOPQRSTUVWXYZ", SUBSTR(?value, 1 , 1 )))) AS ?digit1) . BIND( STRLEN(STRBEFORE("0516273849", SUBSTR(?digit1, STRLEN(?digit1), 1))) + xsd:integer(SUBSTR(?value, 2, 1)) + STRLEN(STRBEFORE("0516273849", SUBSTR(?value, 3, 1 ))) + xsd:integer(SUBSTR(?value, 4, 1)) + STRLEN(STRBEFORE("0516273849", SUBSTR(?value, 5, 1 ))) + xsd:integer(SUBSTR(?value, 6, 1)) + STRLEN(STRBEFORE("0516273849", SUBSTR(?value, 7, 1 ))) + xsd:integer(SUBSTR(?value, 8, 1)) + STRLEN(STRBEFORE("0516273849", SUBSTR(?value, 9, 1 ))) + xsd:integer(SUBSTR(?value, 10, 1)) + STRLEN(STRBEFORE("0516273849", SUBSTR(?value, 11, 1 ))) + xsd:integer(SUBSTR(?value, 12, 1)) + xsd:integer(SUBSTR(?value, 13, 1)) AS ?checksum) . FILTER( FLOOR(?checksum / 10) != (?checksum / 10) ) } ORDER BY ?value
List of this constraint violations: Database reports/Complex constraint violations/P11127#MEXT School Code
 
This property is being used by:

Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Return to "P11127" page.