Property talk:P5029
Latest comment: 1 year ago by Mzaki in topic Uniqueness
Researchmap ID
іdentifier for a researcher on researchmap.jp
іdentifier for a researcher on researchmap.jp
[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/P5029#Item P31, hourly updated report, search, SPARQLSingle 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). Known exceptions: Shun'ichi Amari (Q7505004), Takumi Satō (Q11383775), Etsuko Akiba (Q11595089), Yoshio Izumiya (Q104903586), Yoshihiro Ito (Q116938005)List of violations of this constraint: Database reports/Constraint violations/P5029#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/P5029#Unique value, SPARQL (every item), SPARQL (by value)
Format “
List of violations of this constraint: Database reports/Constraint violations/P5029#Format, hourly updated report, SPARQL[0-9a-zA-Z\-\._`\{\}]{3,20}”: value must be formatted using this pattern (PCRE syntax). (Help)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/P5029#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/P5029#Scope, SPARQL
Conflicts with “instance of (P31): Wikimedia disambiguation page (Q4167410), Wikimedia category (Q4167836), Wikimedia list article (Q13406463), Wikimedia template (Q11266439), Wikimedia module (Q15184295), Wikimedia human name disambiguation page (Q22808320), Wikimedia administration category (Q15647814)”: this property must not be used with the listed properties and values. (Help)
List of violations of this constraint: Database reports/Constraint violations/P5029#Conflicts with P31, hourly updated report, SPARQL|
This property is being used by: Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
| ||||||||||||||||||||||||||||||||||||||||||||||
Uniqueness
editHow unique are the database items? For Shun'ichi Amari (Q7505004) there seems to be two: https://researchmap.jp/amari and https://researchmap.jp/read0080427 — Finn Årup Nielsen (fnielsen) (talk) 12:31, 9 April 2018 (UTC)
- @99of9, Fnielsen: https://researchmap.jp/amari now redirects to https://researchmap.jp/read0080427 and this page displays researchmap Member ID: 5000003544 which is a red herring. Shall we adapt this property or add a new one (alphanumeric)?--U. M. Owen (talk) 16:05, 29 September 2023 (UTC)
- The uniqueness of registration for a person is not guaranteed. Although registration to researchmap is chiefly on voluntary basis, there could be an institution-wide registration, leading to duplicated items. In addition, researchmap is made after a merger of 2 similar projects (ReaD & Researchmap), so there could be two items for the same person, though not frequently. Even in such cases, researchers maintain only one item among them. So I have changed single-value constraint (Q19474404) to single-best-value constraint (Q52060874). The abondoned item should be marked with deprecated rank (Q73737357) and reason for deprecated rank (P2241)abandoned account (Q66107668). Sometimes items would be removed; mark it with deprecated rank (Q73737357) and reason for deprecated rank (P2241)withdrawn identifier value (Q21441764). As for researchmap Member ID, it is the identifier for item within the database, but is not directly linkable (although we can use search UI like https://researchmap.jp/researchers?user_id=5000003544), and not useful as an external identifier in wikidata. If someone incorrectly add researchmap Member ID with Researchmap ID (P5029), it should be marked with deprecated rank (Q73737357) and reason for deprecated rank (P2241)unrecognized identifier value (Q54976355). --Mzaki (talk) 01:08, 24 October 2023 (UTC)