Revisit CDI Limit by Availability

See Best Practices for Decision Pages and Tags for groups

Legend: NOT STARTED STALLED DECIDED

Status	IN PROGRESS
Description	Investigate how limit by availability is impacting UX; also assess/consider ILL impact
Impact
Priority	High
Dependencies with other groups	lots of input needed from local groups
Optional: recommendations on which group(s) might be assigned the work
Notes and links to reference documents	Getting reports of problems with records that we have no services available, no recourse for users to pursue. LibGuides have been a common complaint.
Existing Salesforce tickets
Band-aid
Target decision date
Date decided
	Phase 4 Holdover

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

There was no good option with easy active vs fully flexible. There were pros and cons on both sides. Easy active was less work on the catalog side of things.
How does the EasyActive Exception List work? Is it theoretically possible to manually shut stuff off?
Consider that the whole point of this shared catalog thing was to get everything accessible by the UCs into one bucket for people to discover, even if it’s not currently on the shelf or subscribed to. An increased ILL Workload is definitely going to be a part of that.
- What options do we have on the Discovery side to reduce the number of “bad” requests coming from inaccurate metadata records?