Which CDI Collection a record is coming from?

Identifying which CDI Collection a record is from

Several of you have asked similar questions to "How do I find out which collection a CDI record came from?" So, here are some ways to find this information.

CDI Record "Source" Collections 

The source field lists your activated collections (or local standalone portfolios), causing a CDI record to appear.

Drawback: The PNX data or Primo VE record display does not always list all activated CZ collections or local-IZ collections related to the title. The CDI and Primo note local collections or standalone portfolios as Source = Alma/SFX Local Collection in the Primo VE record display and the PNX data. When troubleshooting the source causing a record to display, I use data from the display, the background PNX data, Alma electronic collection searches, Alma electronic portfolio searches, and other data to discover the source. 
We can explain some of this as follows:

The CDI merged record approach 

The CDI merges content records from numerous providers into one record displayed in Primo VE. You usually see your activated collections in  the full record view's source field. It does not typically display a long list if you have more than two or three collections activated. It picks a few. Or,  you can open up the PNX data to see the additional collection names and provider package codes that appear there.  To open the PNX data, add &showPnx=true to the URL's end and have your browser go to that page. All collections associated with that record show in the <source> fields. The provider package codes show in the <scope> fields. 

The Primo VE permalink also contains information about the record's source provider. Remember, the permalink might contain information about another provider as the CDI only picks one provider record ID to use there – and it doesn't always match your activated collection(s). It usually doesn't give a specific collection name. If the record uses a link in record to provide access, you can look at the destination site. The link resolver links can also provide collection information.

If the collection name does not show up in the full record view or the PNX data, you will need to dig into the data from other sources. 

A few notes: 

  1. The background PNX might not list all individual records' (physical records) source collection of the logical record (a.k.a. the merged record).
  2. The collections listed in the PNX include collections that you have not activated. So, you need to review the list. 
  3. Also, the <scope> fields might list an extra collection or two from the <source> field. Create a report in Analytics with the provider package code displaying for your collections or use an advanced Electronic Collection > Electronic Collection: CDI Collection ID (DB ID) search. It is the quickest way to figure out the collection for a code. 
  4. The <scope> field codes might be easier to work with than the collection names. The CDI collection names are not always the same as the Alma electronic collection name.
  5. You can search the CZ for the publication. Look for collections where the portfolio is not localized, but you did activate other titles in the collection. Your settings could cause additional records to appear. 
  6. If there is a problem, check the CDI settings for all the collections you identified. 
  7. You can also try searching for a few articles from the publication. Look for duplicated CDI records. The other record may provide different collection information. The collection activation and settings that caused the second record to appear also caused the first record to appear. The triggering holdings or CDI settings would be the same. 
  8. Ex Libris released a CDI Activation Analysis tool that also does all of this, which some of you may find easier or harder than these other steps. The instructions are at https://cdi-rights-analysis.hosted.exlibrisgroup.com/client/help. (Note: the CDI record ID is the part of the permalink beginning "cdi" and continuing to the end.)
  9. If you still cannot identify the problematic collection, ask PALS for assistance.
    • Related Articles

    • Recommendations for Open Access Electronic Collections

      In the Fall of 2020 a MNPALS Open Access Workgroup convened to analyze a list of Open Access electronic collections and make recommendations in favor of activation or deactivation based on the quality of the collection and links. The findings of the ...
    • CDI Record Linking Behavior webinar

      CDI Record Linking Behavior webinar (from the OA Recommendation TF Meeting - October 9, 2020 meeting)  The OA Recommended Task Force requested Carrie Curie from PALS to present a session covering the basics of CDI Record Linking Behavior. This ...
    • CDI Basics: From A Systems Perspective webinar

      CDI Basics: From A Systems Perspective webinar (from the Systems UG Discussion Meeting - October 23, 2020 meeting)  The Systems User Group requested Carrie Curie from PALS provide an overview session on the CDI. This session included information ...
    • The NZ: Vendor Records and Electronic Collections

      The NZ: Vendor Records and Electronic Collections (including CDI) (January 19th, 2021 webinar) Carrie conducted an Alma training on The NZ: Vendor Records and Electronic Collections (including CDI) Recording Link Topics covered included (recording ...
    • Where to update CDI settings in Alma

      Setting Electronic Collection Search Results Electronic Collection Editor > CDI Tab For collections where you want to activate or deactivate a collections’ CDI records – remember CDI records automatically activate for aggregator or selective packages ...