Legend:
| Status | ||
|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
...
All institutions in a consortium must use the same CDI activation model, either EasyActive or FullyFlexible.
EasyActive was implemented for the Test Load.
With EasyActive, all collections in CDI (except a small subset) are now searchable in Primo and you cannot turn them off. Ex Libris assumes that campuses will limit what is searchable by availability (clicking a box to expand the search to items available in print and via ILL). Cons: research indicates that users ignore the “Expand my results” filter and this model may get more support tickets and ILL requests.
“The FullyFlexible setting does require the library to manage all their activations themselves, on an ongoing basis, including for collections used for alternative coverage of providers that are not directly indexed in CDI. The EasyActive setting activates the majority of collections automatically without library intervention.”(from“What is the EasyActive Setting?” in Ex Libris Knowledge Center). Cons: more staff time needed to activate and deactivate collections.
The roadmap of CDI product development is all new ALMA customers should be on EasyActive model. The Fullyflexible model is a transitional model for PCI customers to move CDI, and eventually they will move to EasyActive model in the future.
No UC Alma campus is using CDI yet or planning to move to CDI in production before go-live.
Ex Libris is not saying that they couldn’t switch us from our current EasyActive to FullyFlexible, however, switching from the EasyActive model to the FullyFlexible model has never been done/tested.
If we switch to FullyFlexible for cutover, we could lose any configurations we have currently set in EasyActive during test load.
...
Do we have a choice of which CDI model to use (FullyFlexible or EasyActive)? Answer: Communication with Ex Libris leads us to infer that we do.
Will EasyActive settings be saved from Test Load to Go-Live? (i.e., if we turn off CDI collections in Test, will that “stick” through Go-Live). Answer: Yes they will be saved.
The changes the campuses make now in CDI collections (i.e. CDI related attributes in collections or manually activate collections from exception list) in Testload will be retained at Cutover.
EXL will run export report before cutover data frozen in TestLoad/Pre-production environment.
At cutover, EXL will import the report and apply the changes to cutover data.Is there a difference for the already-Alma campuses? Answer: There is no difference for the already-Alma campuses from the process listed above. Just a reminder however they must switch to EasyActive model in their live production environment before cutover.
How much work will need to be done right after go-live?Answer: The export & import should take care of the task with no additional work after go-live.
Link to Basecamp post with other questions & answers on CDI EasyActive model for UCs:https://3.basecamp.com/3765443/buckets/15553579/messages/3398528891 (access is restricted to the SILS cohort).
What are the concerns of each campus? Answer: Neither model is perfect, but FF will be more time consuming overall and require more staff to support the work.
...