How Can We Help?
Match Scopus IDs for Persons Job: TroubleshootingMatch Scopus IDs for Persons Job: Troubleshooting
What
With 5.21 a new job, called 'Match Scopus IDs for Persons job' was added to help cleanup author IDs. The purpose of this job is to help improve the accuracy and completeness of Scopus Author IDs by using Scopus to check author IDs in Pure and provide options to add or remove IDs if necessary. Full details on this new job are outlined in the 5.21 release notes under Match Scopus IDs for Persons: a cleanup job for author IDs.
When running this job, you may encounter scenarios where content is not touched or you may receive warnings and/ or errors that are not readily understood. Below reviews these scenarios and how to troubleshoot them.
Why
Content Skipped:
The 'Match Scopus IDs for Persons job' has a list of requirements that it runs through and persons that match one (or more) of the following will be reviewed by the job:
- Has a Scopus Author ID
- Has an ORCID
- Is an active (including future) academic staff
- This can be confirmed by going to the Person overview and adding the filters 'Academic staff' and 'Affiliation period'
Warnings and Errors:
WARN: Could not check Author ID in Scopus - please perform this check manually
- This error indicates problematic Scopus IDs and usually occurs when Scopus is called with an ID that they say has been taken over by multiple other IDs.
- Examples of problems the job encounters to trigger this warning:
- Person has added a non-standard ID as a Scopus ID; common examples include a URL instead of an ID.
- For a standard ID, Scopus returns multiple taken over IDs. For example, when you try to navigate to an Scopus Author ID you sometimes are re-directed to another url with a new ID which indicates that ID was taken over by another ID.
- We are in communication with Scopus on how to best handle this, but for now we log this as a WARNING so you can handle these cases manually.
WARN: Returned an unexpected result: HTTP/1.1 500 Internal Server Error ERROR: Could not retrieve Scopus EIDs for author with ID: 23989076100 Exception details dk.atira.pure.api.shared.contentimport.sciverse.SciVerseServiceException: resourceKey: contentimport.error.fetch, resourceArgs: {exception=GENERAL_SYSTEM_ERROR : Error calling Solr Search Service}
- This error occurs when we try and look up related research output for a given Scopus Author ID. This error is more rare and upon further runs, the error should no longer occur and is likely caused by Scopus being overloaded.
More information
Updated at September 10, 2024