...
Page Properties | ||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
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
Option 1 | Option 2Default | Filter by Availability | |
---|---|---|---|
Description | Limit CDI by Availability | CDI displays all results, regardless of availabilityA 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
...
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?
...