(very much being developed, not finalized)
Deliverable | Priority | Due Date | Notes |
|---|---|---|---|
Re-testing of loading brief GOBI records into the NZ -see AEFG (Go-Live) Vendor bib records/overlay rules and Import Profiles - AEFG w/ RMFG (MVP 003) | 4/25/2022 | Procedural as well as configuration - new Decision Page to advise on best practices. Include collab w/RM, etc. | |
Have session about GOBI Ordering APIs to share campus practices, explore consortial possibilities | |||
Potential to add or share configuration views. | |||
CDL/Campus E-Resources Workflow/Record Structure - AEFG (Go-Live) Electronic Resources Practices - Linking IZ orders to relevant CDL e-collections (MVP 001) and AEFG (Go-Live) Campus Purchase Order Practices for CDL and Related Local E-Resources (AEFG-MVP-002) | waiting on input from CDL for what they need campuses to adhere to | ||
Licensing - terms visibility for ILL, etc. | starts at CDL for standards on consortial purchases, then flows to campuses for harmonization of local practices | ||
Perpetual rights and entitlement tracking in Alma (generally) | joint w/ e-res, both local and CD materials. Potential to move up in combination with licensing deliverable (above | ||
Reporting/analytics - define desired statewide reports | 9/12/2022 | Stakeholders: selectors , AULs/ULs, others? SCLG for input on local vs UC, campus reports into Shared space in Analytics (esp already-Alma campuses). Reports NOT in analytics? need input from stakeholders (Operations Team?) on what kinds of reports are needed so we can see if current data entry is providing needed connections for effective reports | |
Reporting/analytics - System review/improvement processes - show and tell? | |||
Reporting/Analytics - Shared Vendors vs harmonized vendor codes for consortia-level spending reporting | “How much does UC spend with VendorX?” | ||
Additional process work on NZ/IZ de-duplication/reconciliation. | need clarification on who is responsible/can work in NZ - only CDL? Largely e-res management | ||
Confirm approach to scoping of IP ranges for discovery outcomes (more Discovery but affects e-resources troubleshooting) | settings that can be configured during Acq process, but largely e-res/Discovery | ||
Use Taxes - Share campus practices / show and tell for individual campuses and determining how to handle line item tax. |
Note: how to indicate dependencies/waiting-for statuses? Separate column?