Sign up now for Client Certification Foundation Course - June cohort!
Pure's logos
Pure Help Center for Pure Administrators

If you are a researcher, or other non-admin at your institution, click here.

  • Home
  • Announcements
  • Release Notes
  • Technical user guides
  • Training
  • Events
  • Support
  • Contact Us
  • Home
  • Knowledge base articles
  • Data Sources and Integrations

How Can We Help?

Search Results

Filter By Category

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Contact us

Match Scopus IDs for PublicationsMatch Scopus IDs for Publications

This job is designed to ensure accurate matching of publications to their respective Scopus IDs. This article will provde an overview of purpose, functionality, and configurations related to the job. The job is by default enabled on all servers and is free of charge. 

 

Purpose of Running the Job 

  • Identify Scopus-Indexed Articles: Determine whether a publication is indexed in Scopus. 

When a Scopus ID is identified and added it will used by these jobs:

  • Access Scopus Citations and FWCI: Essential for retrieving Scopus citations and Field-Weighted Citation Impact (FWCI). See more about Field Weighted Citation Index (FWCI) 
  • Updates from Scopus Import/Update Job: Records with a Scopus ID will not be imported but will be updated through this job.
  • Available updates accuracy: Improves the accuracy of the update job when querying Scopus 
  • Export to SciVal: Facilitates the export of publications to SciVal. See Export to SciVal 

 

How the Matching Job Works 

The matching process consists of two steps: 

Step 1: Initial Matching Strategies Used by the API 

  • PMID (PubMed ID): Matches publications using their unique PubMed identifier. 
  • DOI (Digital Object Identifier): Matches publications based on their DOI, a unique alphanumeric string assigned to documents. 
  • ISSN, Volume, and Page: Matches using the International Standard Serial Number of the journal, along with volume and page numbers. 
  • Title (100% Match) and Year: Matches publications by title and year of publication. 
  • Author, Year, and Page: Matches based on the author's name, publication year, and page numbers. 

Note: Only one criteria is needed for initial matching. 

 

Step 2: Additional Criteria for Verification 

Once potential matches are identified, Pure conducts further verification using the following criteria: 

  • PMID 
  • Article Number 
  • Volume and Issue Number 
  • Journal ISSN 
  • Pages 
  • Host Publication Title/Journal Title/Series Title 
  • Author + Year + Pages 
  • Title (concatenated title and subtitle) (80% match) + Year 
  • ISSN + Volume + Pages 
  • DOI 

Matching Acceptance Rules: 

  • As default at least two verification criteria must be fulfilled for a match to be accepted. This can be configured in the job settings. 
  • Some criteria carry more weight in the matching process; for example, a match on DOI or ISSN is considered more significant. 
  • If an exact Scopus ID match cannot be determined, an entry will be logged in the job log, and the record will need to be manually adjusted with the correct Scopus ID.  

Duplicate Scopus ID Prevention 

To maintain data integrity, Pure will not assign a Scopus ID to a publication if that ID is already associated with another publication. This ensures that each Scopus ID is unique to a single publication within Pure. 

 

Job configurations 

Go to Administrator > Jobs > Cron Job scheduling. Locate the job and click on the job title to get to the configurations.

Excluded Publication Types:  

You can configure the job to check only specific publication types that are covered by Scopus, excluding types such as non-textual publications. 

Limit Job to Specific IDs:  

This allows you to specify a list of Pure IDs to check, which can expedite the process without waiting for automatic revisits. 

Verification of Existing Scopus IDs 

The "Match Scopus IDs for Publications" job can also be configured to verify existing publications with Scopus IDs: 

Check existing publications for invalid/incorrect Scopus IDs: 

The job can verify whether the existing Scopus ID is valid and currently exists in the Scopus database. 

Removal of Non-Existent IDs: 

If a Scopus ID is found to be invalid, it will be automatically removed from the corresponding publication in Pure. 

 

Publication Update Schedule 

  • Initial Run: All publications will be checked, and progress can be monitored in the job log. 
  • Ongoing Checks: New publications will be checked during the next scheduled job run (default is Daily). 
  • Revisiting Existing Publications: Existing publications without a Scopus ID will be revisited every 90 days. 

This comprehensive approach to matching and verifying Scopus IDs ensures accurate representation of publications within Pure, enhancing research visibility and supporting effective citation practices. 

  

 

 

 

Published at April 11, 2025

Download
Table of Contents
  1. Purpose of Running the Job
  2. How the Matching Job Works
  3. Step 1: Initial Matching Strategies Used by the API
  4. Step 2: Additional Criteria for Verification
  5. Matching Acceptance Rules:
  6. Duplicate Scopus ID Prevention
  7. Job configurations
  8. Excluded Publication Types: 
  9. Limit Job to Specific IDs: 
  10. Verification of Existing Scopus IDs
  11. Check existing publications for invalid/incorrect Scopus IDs:
  12. Removal of Non-Existent IDs:
  13. Publication Update Schedule
Related Articles
  • Export to SciVal
  • Field Weighted Citation Index (FWCI)
Keywords
  • synchronisation - configuration
  • 5.13.4-3
  • match scopus ids for publications
  • scopus match

Was this article helpful?

Yes
No
Give feedback about this article

    About Pure

  • Announcements

    Additional Support

  • Events
  • Client Community
  • Training

    Need Help?

  • Contact Us
  • Submit a Support Case
  • My Cases
  • Linkedin
  • Twitter
  • Facebook
  • Youtube
Elsevier logo Relx logo

Copyright © 2025 Elsevier, except certain content provided by third parties.

  • Terms & Conditions Terms & Conditions
  • Privacy policyPrivacy policy
  • AccesibilityAccesibility
  • Cookie SettingsCookie Settings
  • Log in to Pure Help CenterLog in to Helpjuice Center

Knowledge Base Software powered by Helpjuice

Expand