CDI Limit by Availability [Phase 4 delegated]

Legend: NOT STARTED IN PROGRESS STALLED DECIDED

Status	IN PROGRESS
Description	Investigate how limit by availability is impacting UX; also assess/consider ILL impact
Decision summary
Owning group	DISC
Approver	Final decider; group with the authority to approve the decision. Unless multiple groups are affected or additional staffing or finances are required, your group can approve its own decisions.
Consulted	eResources, Fulfillment
Informed	Groups/individuals who need to know about this decision. For broad-reaching decisions, SILS has a cohort-wide email list (SILS-Cohort-L@ucop.edu) and slack channel for all SILS members #all-cohort. SILS News email list reaches ~500 self-subscribed UC staff (SILS-News-L@ucop.edu)
Decision-making process	Describe the process your group will use to make the decision.
Priority	High
Target decision date	[type // to add Date] The date your group aims to make the decision. Allow time for consulting.
Date decided	[type // to add Date] You must add a date field for it to sort properly. It will not sort if you simply type the date. The date the Approver approves the decision.

Recommendation

(Harmonization undesirable. Each campus should make the decision based upon their collection and user needs).

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?
ILL
eResources

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.

What is Filter by Availability?

CDI has tens of millions of records. By default, a search will surface all CDI results regardless of availability to the library.
When configuring a search profile that includes the Central Index search scope, libraries can opt to “Filter by Availability” so that the search profile will not surface results that do not have full text availability. So, the only CDI records that would display would be those with full text availability.
This setting causes the “Expand My Results” toggle to display. Then, if a user wants to include results for CDI records that do not contain full text, they can select the Expand My Results check box.

Options Considered

	Default	Filter by Availability
Description	A search will return all relevant CDI results regardless of availability. Users will see electronic article and ebook results that are available online as well as those they must submit a request for.	A search will only return CDI results with full text availability. Articles and ebooks that must be requested are filtered out.
Pros
Cons

Dependencies

Questions to consider

How exactly does this impact ILL?
- How would they test this?
Why in the world did I approach this decision page and testing backwards?
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.
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?

Action Log

Action/Point Person	Expected Completion Date	Notes	Status