Property talk:P1153

Documentation

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

Scopus author ID
identifier for an author assigned in Scopus bibliographic database

Applicable "stated in" value	Scopus (Q371467)
Data type	External identifier
Allowed values	[1-9]\d{9,11}
Example	Jonathan A. Eisen (Q2000017) → 35247902700 Magnus Manske (Q13520818) → 25723615000 Frederic Y. Bois (Q5497170) → 7005487412 Richard Tol (Q823885) → 55765581600 Marc Greenberg (Q15217445) → 37083905900
Format and edit filter validation	Scopus assigns a unique identifier for each author, but sometimes the person has more than one author record.
Source	According to this template: w:Scopus, including Free Lookup Form. The ORCID database also includes scopus author ids.[1] Each university in Australia has its own database of Scopus Author ids for their academic staff, as the Australian government research data collections have required it since 2008, and research data repositories also record it[2]. According to statements in the property: https://www.scopus.com/freelookup/form/author.uri When possible, data should only be stored as statements
Formatter URL	https://www.scopus.com/authid/detail.uri?authorId=$1
Tracking: usage	Category:Pages using Wikidata property P1153 (Q50294849)
See also	Scopus affiliation ID (P1155), Scopus source ID (P1156), Scopus EID (P1154), ResearchGate contributions ID (P6023), Academia.edu profile URL (P5715), ResearchGate profile ID (P2038), ResearcherID (P1053), Google Scholar author ID (P1960), Loop ID (P2798), Semantic Scholar author ID (P4012), curriculum vitae URL (P8214)
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/Humans with missing claims/P1153 Database reports/Constraint violations/P1153 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 557,579 Main statement 555,890 99.7% of uses Qualifier 7 <0.1% of uses Reference 1,682 0.3% 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/P1153#Unique value, SPARQL (every item), SPARQL (by value)

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/P1153#single best value, SPARQL

Format “[1-9]\d{9,10}”: 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/P1153#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/P1153#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/P1153#Scope, 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/P1153#Entity types

Qualifiers “reason for deprecated rank (P2241), affiliation (P1416), subject named as (P1810), affiliation string (P6424), number of works (P3740)”: this property should be used only with the listed qualifiers. (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/P1153#allowed qualifiers, SPARQL

Label required in languages: en: Entities using this property should have labels in one of the following languages: en (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/P1153#Label in 'en' language, search, SPARQL

This property is being used by: s:ru:Шаблон:Внешние ссылки en:Template:Scopus, en:Template:Scopus id fa:الگو:Scopus fr:Modèle:Scopus ja:Template:Scopus sco:Template:Scopus ta:வார்ப்புரு:Scopus sq:Stampa:Scopus pt:Predefinição:Scopus id, pt:Predefinição:Scopus ar:قالب:سكوبس as:সাঁচ:Scopus ml:ഫലകം:Scopus id, ml:ഫലകം:Scopus sl:Predloga:Scopus uk:Шаблон:Scopus tr:Şablon:Scopus id, tr:Şablon:Scopus ko:틀:Scopus, ko:틀:위키데이터 속성 추적 zh:Template:Scopus hu:Sablon:Scopus bs:Šablon:Scopus, bs:Šablon:Scopus id ru:Шаблон:Scopus id kn:ಟೆಂಪ್ಲೇಟು:Scopus vi:Bản mẫu:Scopus sk:Šablóna:Autoritné údaje gv:Clowan:Scopus Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Handling duplicates

Following this discussion I would like to discuss together how to manage duplicate.

SCOPUS is a good service, I find very helpful when I have to quickly create an item with basic information, and it is improving, but there are still ID duplicates here and there. maybe one day they will ask for money and block the access but I think it is worth to cooperate somehow at the moment. We were thinking at the village pump for example to establish a rule where both duplicate IDs should be inserted, create a query to monitor them and maybe inform SCOPUS directly, establishing a communication line. in the end it is not difference than a request from a single author to merge, it is just from a wikidata volunteer.

Also it is interesting to know if their merge policy is based on redirects, uses to lowest number ID or sets priority for the profile with more entries.

Any advice?--Alexmar983 (talk) 05:55, 4 October 2017 (UTC)

Just a note - the "single value violations" list on the constraint violations page shows 279 right now, maybe a note to SCOPUS with that list right now would be a good idea? Or are some of those likely to be mistaken duplicates? ArthurPSmith (talk) 13:40, 4 October 2017 (UTC)

Thank you ArthurPSmith I have a work emergency today but I check the first item on the list, Michael Fritsch . One of his link is now dead, and not the other one but it is possible it was a duplicate.--Alexmar983 (talk) 04:58, 5 October 2017 (UTC)

Looking carefully we can maybe deduce the pattern of the workflow of SCOPUS. 7005829926 is lower than 55146703100, so it is possible they give priority to the older and lower profile during the merge.--Alexmar983 (talk) 05:01, 5 October 2017 (UTC)