...
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?