CDI Basics

A look under the hood

Alma Review & CDI Activation

• Alma E-collection Activation -Review of Alma before CDI
• Alma full text collection activation (has portfolios, full text e-collection)
• Alma database-only activation (no portfolios)
• CDI: Very simple breakdown of what should appear where.
• Alma will publish to CDI several sets of data (Institutional holding files) that include the following information(from Ex Libris):
• Full text availability (All your active full text in Alma) This will affect records returned in CDI for the filtered search (flag them as available and make them discoverable in the filtered search)
• Search availability (All collections that you activated for search): This will affect records returned in CDI for the expand search (for those items that are not also available in full text and do not fall under the item above.)

​

Primo Search results

Filtered and Expanded: Basic description of what data is where

• Filtered Search: Library’s holdings
• Expanded Search: Outside library’s holdings

Search activation has an impact on filtered and expanded searches.

• The “easy” activation: full text e-collections
• By default, all active e-collections will be searchable in CDI and will display as “full text available” in both Filtered and Expanded searches.
• But it gets tricky, full text may not be available from Alma but there is full text content from CDI. Those records appear in the Expanded search in Primo with “full text available” link resulting in a “false positive”
• The user thinks there is full text when there isn’t.

​

CDI: We Subscribe to only some titles in this collection

• Workaround the “full text available” in expanded search results
• All content from CDI is marked as full text available when set to “No” in expanded search
• In NZ, I changed all of the aggregator collections to Yes, instead of No, to remove the “false positives” in the brief results in OneSearch.
• Full text available messages were appearing in expanded search results when they shouldn’t have
• Highly recommend libraries set to this “yes” in aggregator e-collections.

�

CDI: Types of Activation-Link Resolver & Link in Record

Now the hard part...Two types of CDI Linking: Link Resolver (Alma) and Link in Record (CDI)

• CDI Search Activation: Link Resolver
• Activation is on the collection level
• Go to the CDI tab after going to the Edit Collection page
• In CDI tab - Full Text Linking in CDI: Linkresolver
• Uses active Alma portfolios to link to full text article

​

CDI Activation: Link Resolver

Link Resolver Activation in CDI

Example: SAGE Complete Deep Backfile Purchase 2010

​

• Full text link in OneSearch full record is from Alma
• Full text type collection in CDI, see records in expanded search with “Full Text Available”

Note: You may see two collections in Alma for the same resource. One has full text portfolio and order/license information but no CDI services. The second collection has CDI services activated but no portfolios or order information. This was done during PCI -> CDI migration.

• Keep as-is
• Move administrative information, orders, notes, license link, to new CDI resource

CDI Activation: Link in Record

Example Data-Planet Statistical Datasets:

• Active for CDI search
• Full Text CDI collection
• No full text from Alma
• Linking Type: Link in Record
• “View Record” in OneSearch
• Does not use Link Resolver (Alma) to link to full text

CDI Activation: Alma Database-only

Resource is only activated in CDI. Alma database-only e-collections do not have portfolios and do not use the link resolver (Alma) to link to the full text article.

• Full text portfolios are not activated or not available in Alma e-collection.
• The bib record for Alma e-collections is suppressed so the record for the database is not in Primo
• Example: Data-Planet Statistical Datasets, the link the database does not appear in OneSearch
• Bib records for all NZ collections are suppressed
• ERM/Resource Management Policy
• CDI full text only
• No full text portfolios in Alma
• Link to full text is coming from CDI

​

​

CDI - Take a breath

OK, so far that was a lot of information. More to come...

What we covered so far:

• Filtered search (library’s holdings)
• Expanded search (outside library’s holdings)
• Link to full text:
• Link Resolver (Alma)
• Link in Record (CDI)
• CDI had full text and A&I collections, similar to Alma but separate from Alma.
• Work around for false “Full Text Available” records in OneSearch results
• We subscribed to only some of these titles in the collection -change to “Yes” for aggregators.

​

CDI Search Activation - Back to Aggregators

Aggregator e-collections automatically have CDI searching activated.

It doesn’t matter if you change the CDI search activation from “No” to “Yes” or the other way around. CDI is already being searched.

​

CDI Search - Here’s where it gets tricky

The “In CDI” is set to yes for Alma full text e-collections. The e-collections are published to CDI and will appear in OneSearch filtered search results, whether it is set to “yes” or “no”

*Exception: Do not show as Full Text available in CDI even if active in Alma

• Check this box to remove the full text availability label from the filtered search for the CDI records.
• Ex Libris suggests this could be applied to Open Access e-collections. Can also be used with e-books.
• The full text link from the link resolver (Alma) will still appear in the OneSearch record.
• The link resolver links will appear when coming in from another source, other than OneSearch like Google Scholar, EBSCO, ProQuest, etc.
• Records appear in expanded search but will not have the full text available label. User will have to go to the full record to see the link resolver full text link.

More: Do Not Show Full Text Available

To remove the “full text available” links from Expanded search results in Primo where there is full text available from Alma, check the “Do not show as Full Text available in CDI even if active in Alma.”

Why use it:

• Declutter results
• Remove duplicate ebook records (coming from IZ/NZ and CDI)
• Remove book chapters from search results

​

​

CDI: “No Full Text Active” Review

When the box is checked:

• CDI records from this collection will not appear in the filtered search results
• CDI records will only appear in the expanded search results if activated for search in CDI but they will not have the “Available Online” link.
• The full text link from the Alma collection will still appear link resolver section of the full record.
• The impact is on CDI, the full text records are removed from the Primo search results but the full text links will appear in the full record.
• Results in a “false negative” The user doesn’t know there is full text available unless they go to the full record.
• If used on e-book collections, the CDI record could be coming from another collection where CDI has the e-book available so the library may need to check this box for all e-book collections.
• Decision: Which e-collections should have the box checked?

​

CDI E-books: Configuration Decisions

In CDI, full text Alma e-collections are automatically published to CDI. Previously in PCI, if the library did not want e-books from PCI, the resource would be deactivated in PCI. That is not the case in CDI.

Three options:

1. Check the “Do not show as full text available in CDI” box
2. Suppress the bib record from Primo index
3. Use both unsuppressed indexed bib records and CDI

There will be more information about e-books later in the presentation.

From Ex Libris: Why do I see duplicate ebooks?

CDI E-books: Configuration Decisions Results

Outcome option 1:

• No book chapters published in Primo search results.

Outcome option 2:

• Users will see records from CDI but not from Primo index.
• Book chapters will be included in Primo search results and marked as available.

Outcome option 3:

• Duplicate records for ebooks will appear in the Primo search results.

Linking and Merged Record - Update from Ex Libris

Ex Libris has updated how the full text links appear in the Primo record.

• All records in a merged group are coming from collections using the link resolver – The merged record will use the link resolver (Alma), where the number of links displayed, the order of the links, and other priority settings are managed by the library.
• All records in a merged group are coming from a collection using the link in the record – Typically, an institution has access rights only to one of the available platforms, and therefore links to those platforms will be displayed and used. If an institution has access to several platforms, the system will give priority to collections with the most reliable link, which is the direct link (using a document ID from the provider platform) if available.
• Mix of records: One or more of the records in a merged group is coming from a collection using the link resolver, and others come from collections using the link in the record –
• If the library has no access to any of the collections using the link in the record, the merged record will use the link resolver.
• If the library has access to at least one of the collections that use the link in the record and that link is not for an open access item, those collections will be given precedence over the collections that use OpenURL. Links that use a document ID will be given priority over metadata links. If the "link in the record" collection is open access, then the OpenURL link will be given precedence.

​

CDI: Linking and the merged record

Linking in CDI works very similar to how it works today in Primo Central, and collections will continue to use the same linking methods with CDI. Primo supports the following linking methods, which are set at the collection level:

• OpenURL linking (Link Resolver) – Full text linking is handled by the link resolver (Alma/SFX), which allows the library to decide which links to display and their order. Where possible, Primo will add a platform-specific document ID to the OpenURL to allow the link resolver to use that ID to link to the full text instead of using metadata to create the link. This ensures a higher reliability of the links. OpenURL linking is used for approximately 60 percent of the collections indexed in CDI. Collections that use this method include primary publishers and, in general, collections that contain mainstream material such as articles and books that may be available from more than one platform.
• Link in Record – In cases where the record is uniquely available from a single platform and/or the link is difficult or impossible to create using the link resolver, Primo will use the link stored in the record, which has been provided by the information provider, in CDI. This method is used for approximately 40 percent of the collections. Collections that use this method include for example video collections (such as Alexander Street Press), some reference collections, or collections that contain special and unique material.
• Primo LinkTemplate CDI collections – This method is used rarely and is used for collections (for example, Naxos and Kanopy collections) where the linking method is the link in the record, but the provider requires Primo to add customer-specific parameters (which are stored in Primo’s linking templates) to the URL.

​

CDI Special Links

*Special links for CDI need to set up in Primo/Primo VE

Some resources require special links to be set up Primo for CDI linking to work.

Very important to set this up to fix links for those listed resources, such as Gale, Films on Demand, or Naxos.

CDI: Full Text Access Rights Update

There have been issues with Open Access resources with mixed content with some content being OA and some content not being open in the CDI collection so Ex Libris has added new labels to help libraries make decisions on whether or not to use the OA content. From Ex LIbris: Alma and SFX collections also have an indication regarding Full text rights on the Collection level. This indication is descriptive and not functional, as the Open Access indication is handled at the record level. The purpose it is to assist librarians in selecting collection activations and subscriptions.

For each collection, we currently specify the following indications for Access Rights for Full text:

• Open Access – Indicates that the majority of the content is Open Access, but a small portion (less than 5%) may or may not be restricted.
• NEW: Partially Open Access – This is a new option that is used when CDI has mixed collections where some of the records are available as Open Access while other records are restricted or have no access to full text.
• Subscription (Collection Level) – Requires a subscription to access to full text.
• Subscription (Link Resolver) – Requires a subscription and full text linking is provided by the link resolver.

*For cases in which provider content is partially restricted for subscribers and partially Open Access, we will check the option to create a separate Open Access collection, so institutions will have the option to select only the Open Access content and not receive restricted content results marked as Available.

​

Access Rights Examples

DOAJ:

​

​

​

JSTOR:

​

CDI Open Access: Proxy

Parameter in Primo for CDI Open Access Proxy

“A new parameter was added to the Views Wizard, to determine whether an EZProxy prefix should be added for records of open access collections, in order to optimize delivery.

Primo Home > Ongoing Configuration Wizards > Institution Wizard > Delivery Base URLs

Do not proxy Open Access records - Choose whether to check / uncheck this box.”

The removal of the EZProxy will occur at the record level, based on the indication on the record.

Now to really confuse you: NZ CDI Activation

• Libraries automatically inherit CDI for full-text collections in the NZ.
• New: Libraries not subscribed to full-text collections should be set to NO in the CDI Group Settings.
• Recommended by Ex Libris CDI Team.
• This will take time to set up for libraries in NZ. Default setting is libraries inherit CDI full-text for all e-collections. Will take some planning, need to know the impact of these changes.
• By default, libraries are not inheriting CDI for database-only e-collections in the NZ.
• Configuration needs to be changed to “Yes” to inherit CDI for database-only collections.
• cdi_consortia_inheritance parameter is set to N, the member institution will inherit only full text activations from the Network Zone (default setting). Libraries will need to change this to Y to inherit database-only CDI collections.
• Can continue to use these database-only e-collections in the IZ or switch the configuration from N to Y if that helps with troubleshooting.

​

CDI Known Gaps and Issues

Ex Libris has listed the known gaps and issues for CDI and when they will be fixed.

They are indicated when an issue has been fixed.

If there is a known issue that is not listed here, open a SalesForce case.

​

​

More CDI

SUNY did a great presentation with more details about CDI. Will share those slides. There is no recording of their presentation.

Stacey von Groll worked with Ex Libris on creating these knowledge base pages:

• E-collection Matrix
• CDI cheat sheet (very helpful for deciding what to activate and how to activate certain configurations)
• Troubleshooting tips

​

​

CDI: Time to close the hood

• This is a very basic overview of CDI, there are a lot of other configurations to suppress records, include CDI records, or fix incorrect full text available labels.
• There are changes to CDI all of the time and presentations from ExL seem to change monthly. ExL Known Issues and Gaps is updated as issues are fixed.
• I include any of the monthly CDI updates ExL publishes in the ERM Weekly Update.
• Highly recommend the documentation from Stacey von Groll, very detailed and helpful.
• Now a look at configurations from our own libraries.