CDI Feedback Form | Google FormERM Testing | |
EX Libris Known Issues | Issue | |
CDI for Consortia |
Reported issues | Status | Notes | What is the CDI impact on NZ collections? Will NZ collections be duplicated in the IZ? Or will NZ collections remain in the NZ and the NZ manager will have to create different groups in the NZ based on what institutions would like suppressed or not? How does Fully Flexible vs Easy Active factor into this? | Awaiting Ex Libris Response | Will Open Access collections be automatically enabled? | Awaiting Ex Libris Response | Is Hathitrust currently set for full-text search as opposed to metadata search? I've read that there are plans to update this to metadata search but is there a timeline? | Awaiting Ex Libris Response | It looks like the primo search scope will factor in this as well. I read some documentation that recommended that libraries set their search to filtered search. Could you expand on that? | Awaiting Ex Libris Response | This Fully Flexible documentation states, "There is no need to check which other collections to activate to achieve the best possible alternative coverage for such collections" However, in the webinar at 28.46, the presenter says we will need to take care of alternative coverage. Can we get clarification? | Awaiting Ex Libris Response | It's my understanding that "All collections that are set to full-text available will be automatically be searchable in unexpanded search regardless if the “Yes” checkbox for "Active for search in CDI" is checked or not." Is that correct? | Awaiting Ex Libris Response: |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Full text links were appearing when there was no full text “ebook says "full text" but no full text access for a collection we don't have CDI. This is one example of records appearing in our Primo with this particular collection - TN_cdi_askewsholts_vlebook. The record says "full text available" but the full record says "no full text available".” This collection was causing a lot of issues with the full text available displaying when it should not. Case #00855574 | Ex Libris remove the Vlebooks collection from CDI | |||||||||||||
Database content not discoverable in Primo. (Updated 7/06/2020) If the special “Full Text active in CDI only: Yes” does not exist in your IZ for Electronic Collection Type: database, then it must be inherited by individual libraries from the NZ or must be activated in the IZ by individual libraries to be discoverable. Complication: the bib record must be unsupressed which is against policy. Recommendation in progress. Case #852010, 851956. etc. | Reported to Ex Libris. Narrowed the issue down to Databases. Testing out possible solutions. Slowly developing instructions to check for discoverabilty of NZ collections here. | |||||||||||||
Proxied OA collections (Updated 7/06/2020) “16 out of 70 cases (23%) center around this issue. According to ex libris support, there is a "mismatch between the Alma collection being marked as Open Access and the CDI records not being marked as such in the metadata" We asked CDI_Info about how widespread the issue is.
| In progress… | |||||||||||||
Full Text Availability indication flag in brief record/No link in full record. (Updated 7/06/2020) About 26/70 (37%) were about this issue. We understand that this can be complicated to address however we thought we'd share some steps we've taken to do our part. First, we updated the " We subscribe to only some titles in this collection" for ProQuest and Gale Aggregator Packages Linkresolver type in the NZ to Yes instead of No….My question is: do you know if this will help and also are there other factors we should take into consideration? CDI_Info response: For aggregator collections which have some content without identifiers and which use the link resolver the match can be difficult and fail. So if such collections are set generally to all content as full text available, and some content cannot find a match you have the false positives. While the content team is working on improving this over time I doubt that this is something we can entirely fix. So for collections that have such content it is better to use the selective flag as you suggest in your email. That will definitely make it more accurate. It will lead to some content not being flagged as available so the downside is that you have false negatives. But you have no false positives anymore that can lead to linking problems. | Testing different solutions |
Q&A
Expand | ||
---|---|---|
| ||
Answer (2/1627/2020): We are adding the CDI fields to Alma Analytics so you will be able to select by type of collections and whether they are in CDI or not. The development is not yet done, this is planned to be added in May so will not be available immediately but soon after you are enabled with CDI. Documentation with more details on the fields etc. will become available upon release.
There is one customer and the other are the institutions that are part of the "California State University (System)", that is mean that the campuses are under the same client. |
Expand | ||
---|---|---|
| ||
Answer (2/11/2020): You mean when you are going live with CDI? Yes, if you are all registered under the same customer then you need to go live together. You can either agree on a date or you wait until the general switchover when we automatically switch all to production in July/August. About the EasyActive – currently all institutions in a consortium (connected to one Alma network) need to be on the same setting. We did have some requests to provide an option for individual institutions in a consortium to move to EasyActive but nothing definite. Do you already know which institutions would choose EasyActive as opposed to the Fully Flexible setting? |
Expand | ||
---|---|---|
| ||
Answer (1/30/2020): Records with different ISSNs are not merged. Were you thinking of a specific use case? It does not seem likely that there are records for articles that are exactly the same but have different ISSNs but I can check to make sure if you have an example or a specific use case. Follow-up question: If ExL will be merging records according to ISSN, what happens to records that shouldn’t be merged together? Like a bibliographic record for a print journal linking to a CZ e-portfolio Answer (1/31/2020)We are not merging CDI records with records from the CZ, or other records that you create locally. Also, CDI indexes articles rather than journal records. |
Expand | ||
---|---|---|
| ||
Answer (2/16/2020): We are adding the CDI fields to Alma Analytics so you will be able to select by type of collections and whether they are in CDI or not. The development is not yet done, this is planned to be added in May so will not be available immediately but soon after you are enabled with CDI. Documentation with more details on the fields etc. will become available upon release. |
Expand | ||
---|---|---|
| ||
Answer at 2:10. Webinar Link. Written transcript. |
Expand | ||
---|---|---|
| ||
Answer at 2:25. Webinar Link. Written transcript. |
Expand | ||
---|---|---|
| ||
Answer at 3:10. Webinar Link. Written transcript. |
Expand | ||
---|---|---|
| ||
Answer at 8:45. Webinar Link. Written transcript. |
Expand | ||
---|---|---|
| ||
Answer at 9:10. Webinar Link. Written transcript. |
Expand | ||
---|---|---|
| ||
Answer: 11:05. Webinar Link. Written transcript. |
Expand | ||
---|---|---|
| ||
Answer at 26:20. Webinar Link. Written transcript. |
Expand | ||
---|---|---|
| ||
Answer at 26:30. Webinar Link. Written transcript. |
Expand | ||
---|---|---|
| ||
Answer at 29.30. Webinar Link. Written transcript. |
Expand | ||
---|---|---|
| ||
Answer at 31.48. Webinar Link. Written transcript. |
Expand | ||
---|---|---|
| ||
Answer at 34.40. Webinar Link. Written transcript. The ERM group has proposed that Central Office/Consortia PCI activations for ECC and Opt-ins are moved to the Network Zone. Not in the initial migration but as a phased process. Currently all institutions in a consortium (connected to one Alma network) need to be on the same setting. So we will need to decide as a consortia if we want to remain Fully Flexible or Easy Active. If we move to Easy Active we will not not be able to revert back to Fully Flexible (source: [ALMA-L] CDI - Where is the Easy Active setting?) |
Expand | ||
---|---|---|
| ||
Yes, that’s correct, there is no need to set up the libraries in the CDI Group Settings in case a collection has full text availability for them in Alma.We won't be activating any other Web of Science databases in the NZ. Yes, anything not already activated in the NZ should be activated in the IZ for CDI purposes. |
Expand | ||
---|---|---|
| ||
The ‘showPnx’ bookmarklet can be used for CDI the same way as for PC records. For the interim period, between CDI enablement to CDI switchover, the &searchCDI=true parameter need to be added for it to work. After the switchover the &searchCDI=true parameter will not be needed any more. |
Expand | ||
---|---|---|
| ||
We won't be activating any other Web of Science databases in the NZ. Yes, anything not already activated in the NZ should be activated in the IZ for CDI purposes. |
Expand | ||
---|---|---|
| ||
EDIT: There is an actual “parameter ‘cdi_consortia_inheritance’. It can be set to ‘N’ (no inheritance) or ‘Y’ (inheritance)” in each library’s Alma instance. The ERM committee has not recommended that library’s turn this on since full text activation should take care discoverability. CAVEAT: we just learned from Ex Libris that the same does not apply to Databases with CDI Type: Full Text Collection. The contents of these databases are not discoverable in Primo even if it shared by libraries in the NZ. |
Expand | ||
---|---|---|
| ||
EDIT: The ERM group has set all NZ managed collections to In CDI:Yes. Since no libraries have set the actual “parameter ‘cdi_consortia_inheritance’ to yes, this does not actually do anything. As long as a collection is set as full-text active, then the resources should be discoverable within OneSearch/Primo. Please see below for a caveat. Now, if a library were to set their parameter to ‘cdi_consortia_inheritance’ to yes, then In CDI:yes does affect expanded search.This setting also has an effect if we ever want to suppress discoverability in the future. CAVEAT: we just learned from Ex Libris that the same does not apply to Databases with CDI Type: Full Text Collection. The contents of these databases are not discoverable in Primo even if it shared by libraries in the NZ. |