See Best Practices for Decision Pages and Tags for groups
Legend: NOT STARTED IN PROGRESS STALLED DECIDED
Recommendation
Describe the final recommendation/decision.
Impact
Stakeholder group | Impact |
---|---|
Who does this decision affect? [name of the group] | Explain the significance of the decision to EACH stakeholder group. How will this decision impact this particular group? What will change? Do they need to take any action? If so, when? |
Reasoning
Background
Prior to the migration to a consortium, campuses were able to curate their CDI collections. While this required them to turn on access to individual collections, it also allowed them to weed out collections with poor metadata.
The UC Library system is now on EasyActive. “Alma collections that you have active because you subscribe to their full text will become automatically searchable in CDI. For those collections no separate search activations are necessary.”
PPC (Go Live) CDI Models: FullyFlexible or EasyActive
“It is also important to note that while CDI collections in the EasyActive model cannot be “de-searchified” (ie. hidden from users even in expanded results sets), administrators can “override” the full-text activation, effectively hiding these collections behind the “Expand” option (for campuses limiting by availability).”
Campuses are allowed to decide for themselves if they would have their default search limit CDI results by availability or not.
We are revisiting this issue in order to provide guidance and examples of the pros and cons of limiting by availability or not.
Options Considered [remove if not needed]
Option 1: Limit CDI by Availability | Option 2: CDI displays all results, regardless of availability | |
---|---|---|
Description | ||
Pros | ||
Cons |
Dependencies
Questions to consider
How does the EasyActive Exception List work?