(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) | DONE | 4/25/2022 | Use of (Brief) Order Records in NZ/IZ Procedural as well as configuration - new Decision Page to advise on best practices. Include collab w/RM, etc. Not sure where statewide training/procedural stuff will live - create just in our space to move later. Subgroup to discuss. |
Have session about GOBI Ordering APIs to share campus practices, explore consortial possibilities | DONE - left to local preferences |
| |
Have session about Rialto, various ordering options to share campus practices, explore consortial possibilities | Option for 23-24 session | ||
Share acquisitions configuration views - show and tell cases. | (essentially on hold for CDLNZ-PT, E-Res has similar line item, CDLNZ-PT hasn’t yet run into many cases) | ||
Review/follow up with E-Res team on 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) | N/A | E-Res offered to take ownership! | |
Licensing - terms visibility for ILL, etc. | (1) 4/6/2022 (2) 5/1/2022 (3) CDLNZPT working on planning/scheduling for CDL licenses workflow development (4) | Licensing Terms for Display in Primo starts at CDL for standards on consortial purchases, then flows to campuses for harmonization of local practices - (1) UCD presentation on how to use licensing terms, (2) which terms to display? w/ILL, E-Res then ask Discovery to implement (3) vocab for various terms, (4) data entry (automated?!) for licenses not yet in system 360 access through 6/30/2022 | |
Financial data management/retention for auditing/legal reasons | There is a UC level policy/system to comply with. Focus: Ex Libris functionality for batch management, UC-wide best practices options | ||
Perpetual rights and entitlement tracking in Alma (generally) - licenses, payment info, annual title lists, etc. | joint w/ e-res, both local and CDL materials. (Can be developed solo, but preferable to develop in conjunction/parallel with CDL practices) Potential to move up in combination with licensing deliverable (above) | ||
Reporting/analytics - define desired statewide reports | 9/12/2022 | Analytics team focusing on UCoP statistics for now. Probably need another session of task force to look at uses. Work Plan 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 | |
Use Taxes - Share campus practices / show and tell for individual campuses and determining how to handle line item tax. | (not yet reviewed) | Campus procedures shared in Google Drive | |
Reporting/Analytics - Shared Vendors vs harmonized vendor codes for consortia-level spending reporting | (not yet reviewed) | N/A | found to be irrelevant given how CDL is expected to share data “How much does UC spend with VendorX?” |
Additional process work on NZ/IZ de-duplication/reconciliation. | (not yet reviewed) | N/A | E-Res says several teams already doing this - can share techniques. |
Confirm approach to scoping of IP ranges for discovery outcomes (more Discovery but affects e-resources troubleshooting) | (not yet reviewed) | N/A | E-res offered to take ownership! settings that can be configured during Acq process, but largely e-res/Discovery |
Note: how to indicate dependencies/waiting-for statuses? Separate column?