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

Clean Scopus Journals JobClean Scopus Journals Job

What

You would like to unmerge some Journals, which were erroneously merged.

How

  • There is a job called Clean Scopus Journals.
  • This job cleans Journals that have been incorrectly merged.

When can it be used?

  • The Journals that the job is intended to clean up are the ones that have been merged incorrectly by the Merge Duplicate Journals job (AuthorProfileJournalDeduplicationJob).
    • When Journals are merged by the Merge Duplicate Journals job the merge details are added as a comment on the Journal with ReflectionMergeConverter as the username.
      • You can check, whether your Journals have this comment by opening the Journal editor window > History and comments:
         
      • If you have never run the Merge Duplicate Journals job (either as part of the sequential cron job "QABO data import & cleanup" or running it separately), then you will not be able to use this job, since you will not have the above comment on your Journals.

How does the job work?

  • It will process all Journals that have a Scopus primary or secondary source ID and a comment from the user "ReflectionMergeConverter".
  • It will split up a merged Journal by sending the ISSNs on the Journal to Scopus and then use the data received to create separate Journals (one Journal for each ISSN).
  • If two Journals merged by the content merge job, has also been merged manually with a third Journal, then it is also split up.
  • All the Research output relations from the merged Journal are transferred to the new Journals matching the same ISSN number that they were also related to on the merged Journal.
    • Journals which has been merged manually and does not have an ISSN, but has relations from its title to a Research output
      • This is logged and not moved
    • Merged Journals are deleted afterwards
      • If a Journals still has a relation, then it will not be deleted.

Job configuration

  • It is possible to run the job in dry run mode. If enabled, the job will log information about the content it processes but it will not make any change:
  • The job will log a warning if the merged Journal can't be deleted after it has been split up. This can happen if the merged Journal has a title with a relation to a Research output, as it can only move relations to the new Journals, if there also is a relation to an ISSN.

More information

KB-511 Merge Duplicate Journals job
5.18.0 Release notes
Note: Some of this information is for internal use only and might not be accessible.

Published at May 22, 2024

Download
Table of Contents
  1. What
  2. How
Related Articles
  • Merge Duplicate Journals Job
Keywords
  • cron job
  • splitincorrectlymergedscopusjournalscronjob
  • 5.18.0-2
  • manage duplicate

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