Work Plan: Acquisitions

(very much being developed, not finalized)

Deliverable

Priority

Due Date

Notes

Deliverable

Priority

Due Date

Notes

Re-testing of loading brief GOBI records into the NZ -see https://uc-sils.atlassian.net/wiki/spaces/P4D/pages/1845166629

DONE

4/25/2022

https://uc-sils.atlassian.net/wiki/spaces/AC/pages/1907884055 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

 

  • Laura started notes for a decision page about GOBI API CDI/standalone portfolio issues - still working through pending support ticket

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 - https://uc-sils.atlassian.net/wiki/spaces/P4D/pages/1845166601 and

 

N/A

E-Res offered to take ownership!
waiting on input from CDL for what they need campuses to adhere to (CDL cleanup is helping standardize how things are linked and what we need to do going forward)

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)

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.
Do we want to focus on shared reports? Sharing best practices? Shared meetings with Analytics focused people to discus Acq specific issues? System review/improvement processes - show and tell?

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

Taxes - Share campus practices / show and tell for individual campuses and determining how to handle line item tax.

Campus transitions to Oracle make it a changing landscape

presentation prep for a Fall sharing session?

Campus procedures shared in Google Drive

Reporting/Analytics - integrated data between campuses and NZ?

 

N/A

Initial one-button reporting idea found to be irrelevant/infeasible given how CDL is expected to share data

example question: “How much does UC spend with VendorX?”

Additional process work on NZ/IZ de-duplication/reconciliation.

No noticed Acq impact to date.

N/A

E-Res says several teams already doing this - can share techniques.
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)

No noticed Acq impact to date - essentially Discovery.

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?

The SILS mission is to transform library services and operations through innovation and collaboration. The future is shared!
Question? Contact AskSILS-L@ucop.edu