Issue | Status |
|---|
We were expecting since full text is activated that meant our NZ collections should be discoverable in Primo. I understand that analysts will need to look at specific examples, but it seems this is not working as expected - at least not for all the collections. This means we will need to report issues as we find them. My assumption is that we have to check that NZ collections are discoverable. Does Ex Libris have any instructions we can use to do this? With merged records and the use of metadata from different sources, I can see how this would be difficult to verify that a specific collection is discoverable or not. | Adding instructions here. |
Q&A
Are all of our campuses registered under the same customer?
Answer (2/27/2020): 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.
Our consortia will need to move at the same time. Is that correct? Also, does this mean " all campuses must go-live and stay live on same system (EasyActive vs. Fully Flexible)"? Does that mean individual campuses cannot choose to change to EasyActive after the migration?
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?
What happens to ejournals that have different ISSN's?
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.
CDI in Alma and analytics impact?
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.
Will Open Access collections be automatically enabled?
Answer at 2:10. Webinar Link
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?
Answer at 2:25. Webinar Link
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?
Answer at 3:10. Webinar Link
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?
Answer at 8:45. Webinar Link
Can you walk us through what the differences are between full-text availability and active search in CDI and how these affect expanded search versus filtered search in Primo? Specifically, does this mean we only control search for the expanded search?
Answer at 9:10. Webinar Link
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?
Answer: 11:05. Webinar Link
What would the migration process look like if an individual member library DID NOT have the “Inherit Consortium Central Office resource checked in their PCI instance?
Answer at 26:20. Webinar Link
What would the migration process look like if an individual member library DID have the “Inherit Consortium Central Office resource checked in their PCI instance?
Answer at 26:30. Webinar Link
I've heard that the default setting for CDI is full flexible for a consortia. I'm curious about this because if a consortia is set up so each institution is maintaining its own CDI in its IZ, then, shouldn't the institution be able to decide which setting it wants?
Answer at 29.30. Webinar Link
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? What would the development process and timeline look like if we’d want to member libraries to choose between Fully-Flexible and EasyActive in a Network Zone?
Answer at 31.48. Webinar Link
I would like clarification that that we will continue to have the option of each institution activating their own resources AND choosing whether to go with Fully Flexible or Easy Activation. If that is the case, it seems we would want a conversation about whether we want
Answer at 34.40. Webinar Link. 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?)
For consortia, since the following collection has full text availability for the six libraries, we do not need to set up these same six libraries in the CDI Group Settings as well. Those should already be discoverable in Primo for only those six libraries, correct?
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.
We extensively use the primo bookmarklet/show PNX to troubleshoot records/linking issues in Primo. WIth match and merge, I see troubleshooting may become an issue. Is there an equivalent tool we can use in the CDI?
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.
So, Web of Science has many entries in CZ by years and index. We only have one Web of Science in the NZ. Will you be adding all the Web of Science entries from the CZ and activating the CDI status?
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.
Did we, as a consortium, decide to inherit CDI activation from the NZ, or not?
Yes, we are inhering the CDI activation from the NZ. If full-text access is set up in the NZ, resources from those collections should be found within libraries Primo instance if they are sharing the collection. Instructions on checking NZ discoverability can be found here.