Legend:
Status | ||
---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Page Properties | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||
|
Recommendation
Reasoning
Background
The Discovery Functional Group is charged with the delivery of, “A Primo VE instance for the UC Libraries Network Zone (NZ) will also be developed to provide centralized indexing, shared customization of views via a Central Package, and centralized configuration of mapping and code tables, allowing for the discovery of records and holdings across the NZ, and services such as fulfillment and resource sharing.”
...
Each campus Primo VE will include a DiscoveryNetwork search profile
Consortia union views do not include features or functionality not available via DiscoveryNetwork search profiles (confirmed by ExLibris)
Dependencies
Understand dependencies – are there any? Or can this decision be made anytime before go-live?
Questions to consider
What is the experience/process for end-users for the discovery and request of network holdings via the Discovery Network scope?
Would a consortia union view improve user experience for the discovery and request of network holdings?
Action Log
Action/Point Person | Expected Completion Date | Notes | Status |
---|---|---|---|
Create document summarizing Discovery Network Scope functionality and appearance and Consortia Union View functionality and appearance / Jess Waggoner | 6/23/2020 | Discovery Network Scope and Consortia Union View Summary document in Google Drive | Complete |
Deliver summary document to campus stakeholders and discuss end user needs for discovery and request of network holdings / All Discovery FG members | In Progress |