Open main menu

Property talk:P1153

Documentation

Scopus Author ID
identifier for an author assigned in Scopus bibliographic database
RepresentsScopus (Q371467)
Data typeExternal identifier
Allowed values\d{10,11}
ExampleJonathan 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 validationScopus 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:
http://www.scopus.com/search/form/authorFreeLookup.url
When possible, data should only be stored as statements
Formatter URLhttps://www.scopus.com/authid/detail.uri?authorId=$1
Tracking: usageCategory:Pages using Wikidata property P1153 (Q50294849)
See alsoScopus Affiliation ID (P1155), Scopus Source ID (P1156), Scopus EID (P1154), ResearchGate contributor 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)
Lists
Proposal discussionProposal discussion
Current uses247,591
Search for values
  Distinct values: this property likely contains a value that is different from all other items. (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P1153#Unique value, SPARQL (every item), SPARQL (by value), SPARQL (new)
  Single value: this property generally contains a single value. (Help)
Exceptions are possible as rare values may exist. Known exceptions: Stephen H. Leppla (Q59127270)
List of this constraint violations: Database reports/Constraint violations/P1153#Single value, SPARQL, SPARQL (new)
  Format “[1-9]\d{9,10}: value must be formatted using this pattern (PCRE syntax). (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P1153#Format, SPARQL, SPARQL (new)
  Item “instance of (P31): human (Q5): Items with this property should also have “instance of (P31): human (Q5)”. (Help)
List of this constraint violations: Database reports/Constraint violations/P1153#Item P31, hourly updated report, search, SPARQL, SPARQL (new)

Handling duplicatesEdit

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)
Return to "P1153" page.