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
  • Community Module

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

Deduplication of external organizationsDeduplication of external organizations

This article details the deduplication of external organizations according to the automatic process.

Identification and validation

The following chart shows how the system identifies and validates merge candidates:

Identification and validation process of merge candidates from external organization records

Merge target identification

If one of the items has a SciVal ID, then that item is the target of the merge. If the items were identified based on a classified ID other than SciVal, or if none of the items has a classified ID, then the oldest item by date created is the target of the merge.

Note: Items with a SciVal ID will never be merged into another item.

 

 

Merge

The system merges values in the following fields according to the default merge logic:

  • TYPE_CLASSIFICATION
  • NATURE_TYPES
  • NAME
  • ACRONYM
  • ALTERNATIVE_NAMES
  • IDS
  • ADDRESS1
  • ADDRESS2
  • ADDRESS3
  • ADDRESS4
  • ADDRESS5
  • POSTALCODE
  • CITY
  • STATE
  • COUNTRY
  • SUBDIVISION
  • PHONE
  • MOBILEPHONE
  • FAX
  • EMAIL
  • BANKACCOUNT
  • VAT
  • LINKS
  • KEYWORD_GROUPS
  • NOTES
  • WORKFLOW

The system applies specific logic for values in the following fields:

  • Hierarchy: In addition to the default logic, the following additional logic applies: If there is a parent organization on the source but not on the target, and that parent is not the same organization as the target organization itself, then the system adds the parent to the target. If the source is the same as the parent on the target, then the system removes the parent. If there is a parent on the target but not on the source, then the system keeps the parent on the target.
  • Taken over by: The system does not apply the default logic. Instead, the the system cleans up the values as follows: If the field is defined on the target then the system iterates over the values. If the items evaluated do not exist on the source, or are equal to the source, then the system discards them.
  • Visibility: If the visibility of the target is less restrictive than the visibility of the source, then the system sets the visibility of the target to the visibility of the source. If the source is marked as confidential and the target is not, then the system sets the visibility of the target to confidential.

Published at February 06, 2025

Download
Table of Contents
  1. Identification and validation
  2. Merge target identification
  3. Merge
Related Articles
  • Bulk Change Keywords on Content Job
  • Deduplication of persons
Keywords
  • community deduplication
  • organization merge

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