Primo VE Dedup and FRBR
Related product I-Share

Primo VE Dedup and FRBR

Revised: April 28, 2026

By default, Primo VE performs record deduplication and record FRBR-ization when displaying search results. FRBR is the Functional Requirements for Bibliographic Records published by the IFLA Study Group on the Functional Requirements for Bibliographic Records.

It is HIGHLY recommended you first review the "Best Practices for Testing Configuration Changes" section at the end of this page before you make any changes to configuration.

Configuring Dedup and FRBR Display Options

Records are evaluated for duplicates and FRBR and grouped together for display in results. Records that have been deduplicated and grouped will not be obvious in search results, but you can use the Dedup and FRBR Test Utility to reveal them. Records that have been grouped according to FRBR will appear with the indication "N versions found. See all versions >" as a single entry in the initial search results, and then the user can click into this entry to see all of the versions.

Primo VE search result showing a FRBR result "2 versions found" with a link to "See all versions"

Role Needed: Discovery Admin

The Dedup and FRBR settings are configured per View in:

Alma Configuration > Discovery > Display Configuration > Configure Views > Edit the View > Brief Results tab

Alma configuration screen of the Primo VE View Brief Results tab showing the FRBR and Dedup settings.

I-Share libraries can influence which bibliographic record is chosen to display as the representative record when FRBR Groups or Dedup Groups exist in a search result.

Note: Some I-Share libraries have chosen to UNcheck "Enable FRBR" and/or "Enable Dedup" to turn OFF either FRBR or Dedup in their Primo VE results.

For a comprehensive explanation of all of the options and settings associated with FRBR and Dedup, please see the Ex Libris documentation on Configuring FRBR/Dedup Display Options.

Important Notes

  • These settings are within an individual Primo VE View, so these can be tested using a TEST VIEW. This is HIGHLY RECOMMENDED. For more about Primo VE Views and how to create Test Views, see CARLI's Primo VE Views page.
  • Changes to Dedup and FRBR settings will take effect immediately.

Additional Resources

Best Practices for Testing Configuration Changes

Before you make any changes to Primo VE configurations:

  • Identify several example searches in Primo VE to serve as your baseline of how things work now.  
    • If possible, use known searches that you are already familiar with.
    • Document the behavior of the example searches.
      • Copy the URLs of the search results page
      • Take screenshots of Alma settings screens or Primo VE results
      • Record a short video of yourself doing the search
  • Reach out at your institution to stakeholders who may have encountered issues with search results, may have suggestions about these behaviors, or will be affected if changes are made.

When testing:

  • Test one small change at a time.
  • After you make a change, use a new Private browser window to perform the search again in order to avoid caching. 
  • Document what you change or try as you go, noting the effects on the search results of the example searches you identified beforehand.
  • Consider small group testing with other stakeholders at your institution.

Once you’ve decided to implement a change in production:

  • Document the change, the date, and the rationale for the change. Future You will thank Past You!
  • Share information on the change(s) with other stakeholders at your institution as appropriate.