...
How exactly does this impact ILL?
How would they even test this?
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, but it creates extra work for the Fulfillment 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?
Things like bad/inaccurate metadata and broken access links are outside of Discovery’s control. CDI record displays are not affected by configuration or normalization rules set up in Alma.
Action Log
Action/Point Person | Expected Completion Date | Notes | Status |
|---|---|---|---|
Discovery Reviews Initial Recommendation |
| ||
Send to Eresource and Fulfillment for feedback. |
| ||
Final Decision |
|