Skip to main content
ExLibris

Knowledge Assistant

BETA
 
Back
Primo

 

Ex Libris Knowledge Center
  1. Search site
    Go back to previous article
    1. Sign in
      • Sign in
      • Forgot password
  1. Home
  2. Primo
  3. Knowledge Articles
  4. How to fix FRBR/DEDUP grouping issues in PrimoVE?

How to fix FRBR/DEDUP grouping issues in PrimoVE?

  1. Last updated
  2. Save as PDF
  3. Share
    1. Share
    2. Tweet
    3. Share
No headers
  • Product: PrimoVE

Please see: Dedup and FRBR Analysis Tool for Primo VE

With this tool you can perform the following tests to analyze how the system determines whether records belong to Dedup/FRBR groups, which are used to reduce redundant records in the brief results:

  • Find matching records – This test enables you to find a record's matching FRBR or Dedup records.
  • Recalculate Dedup and FRBR Groups – This option enables you to recalculate Dedup and FRBR groups after updating a record's metadata.
  • Compare records – This test enables you to compare two records to determine whether they belong to the same FRBR or Dedup group.


Open the Dedup and FRBR Test Utility page (Configuration Menu > Discovery > Other > Dedup and FRBR Test Utility)
When you try to compare the records and if you see any issue with the Dedup/FRBR grouping, it could be because of some indexing issue with the records.

Steps to follow when you see an issue FRBR/DEDUP grouping:

  1. Click on Recalculate FRBR/Dedup groups button for all the records individually.
    Maybe some records are connected and some records may not be connected due to some indexing issues.
    For example, there are 4 records in a FRBR group. A, B, C and D records.
    A is connected to B, B is connected to C, C is connected to D.
    This indirectly means that (A and D), (B and D) have matching keys, but they are not yet directly connected.
    So, clicking recalculate FRBR/Dedup groups button for all the individual records, A, B, C and D individually can establish the connection.
     
  2. Run the Recalculate resource type on all the records.
    In this example, i have run this job because clicking on the Recalcutate FRBR/Dedup group did not work out.
     
  3. If you still see the records are not FRBR/Deduped as expected, then you can run 'Prevent FRBR and/or Dedup in Discovery' job.
    Please see: How to use 'Prevent FRBR and/or Dedup in Discovery' job'
    'Prevent FRBR/Dedup in Dicsovery'job will help you to either manually group or ungroup a few records.

If the FRBR/Dedup grouping records are still not as expected, please open a case via the support portal with all the information needed.

PS: In any case, it may take 15-30mins to see the changes visible from the Primo front end, after any indexing job is completed.
Please wait for atleast 30mins after running any job to see the changes that are made to the record or the dedup/frbr groups.

 


  • Article last edited: 18-Feb-2025
View article in the Exlibris Knowledge Center
  1. Back to top
    • How to filter reports by date in Primo Analytics
    • How to fix issue with databases resource type facet translation
  • Was this article helpful?

Recommended articles

  1. Article type
    How-To
    Community Content Type
    How To
    Content Type
    Knowledge Article
    Language
    English
    Product
    Primo
  2. Tags
    This page has no tags.
  1. © Copyright 2025 Ex Libris Knowledge Center
  2. Powered by CXone Expert ®
  • Term of Use
  • Privacy Policy
  • Contact Us
2025 Ex Libris. All rights reserved