Deliverable | Effort/ Dependency | Priority | Due Date | Status | Related Links | Notes |
|---|
930/973 fields |
delegated |
] |
SC will review/revise (split?)
NZ
CZ harmonization
| Status | ||
|---|---|---|
|
workflow/policy/practice page
need clarification on who is responsible/can work in NZ - only CDL? Largely e-res management
Feb 2023 Survey comment:
(RE: Additional process work on NZ/IZ deduplication) I think the best course of action is to create a policy/practice page that documents how activating a resource in both the NZ and IZ interacts - specifically that IZ coverage trumps NZ coverage in Primo display if it is the same portfolio in the same CZ collection. Document awareness around this issue more than performing any deduplication work at this time. ALSO, a page about how to use Analytics to reduce any local eDDA records in the IZ that are already owned in the NZ - ask Lisa Wong for this report (RE: Confirm approach to scoping of IP ranges for discovery outcomes) I think this can be safely delegated to Discovery.
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)
[Phase 4 re-delegated from ACQ]
SC will review/revise based on work from CDLNZ-PT and Shared Collections
NZ
| Status | ||||
|---|---|---|---|---|
|
[SOT-CDL Capacity]
| Status | ||
|---|---|---|
|
waiting on input from CDL for what they need campuses to adhere to
CDL/Campus E-Resources Workflow/Record Structure - AEFG Handoff Document
CSU ACQ ERM Workflow (local) visual model
|
|
| These fields are used by CDL and campuses to pull together e-resource packages. There is a need to evaluate how effective these are and whether Alma has a better alternative, including relying on on e-resource Collection Names instead | |||||||||||||
Sharing of E-resource Licensing Information across UC [Phase 4 delegated] |
|
|
| Create a shared storage space where the entire license documents for UC Tier 1-3 e-resource licenses can reside, so that we can compare terms obtained previously within the system. It would be of additional benefit to be sharing information about license negotiations that have failed and reasons why. | ||||||||||||
Licensing - terms visibility for ILL, etc. |
|
|
status gathering?/ local practices/delegate to discovery?
settings that can be configured during Acq process, but largely e-res/Discovery
E-resources troubleshooting communication
| Status | ||||
|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
Slack
more baseline communication rules?
Steering Committee Contact: Michelle Polchow
Authentication/authorization protocols
| Status | ||||
|---|---|---|---|---|
|
|
|
|
|
Document current authentication practices at UC campuses. Track discussion around this topic
NZ
| starts at CDL for standards on consortial purchases, then flows to campuses for harmonization of local practices | |||
Perpetual rights and entitlement tracking in Alma (campus/IZ) |
Tamara will review if this belongs with ACQ or outside SILS
|
|
|
|
Reporting/Analytics - AEFG Handoff Document (applies to all Analytics topics from Phase 4)
Multi-series electronic collection level records [CDL request]
RM
DISC
[SOT-CDL Capacity]
| Status | ||||
|---|---|---|---|---|
|
CSU - Descriptive and Collection Level Records in NZ
NZ e-collection level record/ workflow to be worked out/ SCP advisory committee – Decision Page draft by Kevin 3/17/2022 start.
Reporting/analytics - System review/improvement processes - show and tell?
[Phase 4 re-delegated from ACQ]
NZ
[SOT-CDL Capacity]
| Status | ||||
|---|---|---|---|---|
|
Reporting/Analytics - AEFG Handoff Document (applies to all Analytics topics from Phase 4)
| Perpetual rights and entitlement tracking in Alma DRAFT Best Practice for activating a CZ portfolio in both NZ and IZ | Contact: Michelle Polchow and Tamara Pilko
NASIG Digital Preservation Webinar: Integrating Preservation into Librarian Workflows | ||
Perpetual rights and entitlement tracking in Alma ( |
CDL/NZ) |
|
|
|
|
current functions in CZ/CDI/Primo
local practices/workflows
changes in provider and ecollection
Steering Committee Contact: Sherry Lochhaas
joint w/ e-res, both local and CDL materials.
|
CRKN consortia perpetual access tracking project - tool forthcoming |
NASIG Digital Preservation Webinar: Integrating Preservation into Librarian Workflows
Local E-resources practices chat/clearing house |
campus |
interest |
|
|
|
|
|
CKG?
Contact: Jeremy Whitt SILS Community Slack - #acquisitions-and-e-resources | |||||||||||||||||
ExLibris/CRL support |
|
| CRL records in Alma/Primo (DRAFT) RMFG had a recommendation from phase 4 |
Contact: Tamara Pilko UCLA troubleshooting identified CRL content missing June 2023. |
930/973 fields
[Phase 4 delegated]
N/A
Multi-series electronic collection level records [CDL request] | RM DISC |
| [SOT-CDL Capacity] |
| Contact: Paula Pascual | |||||||||||||
Authentication/authorization protocols |
|
|
|
These fields are used by CDL and campuses to pull together e-resource packages. There is a need to evaluate how effective these are and whether Alma has a better alternative, including relying on on e-resource Collection Names instead
| Contact: Tamara Pilko Document current authentication practices at UC campuses. Track discussion around this topic | |||||||||||||||||
E-resources troubleshooting communication |
|
|
| Contact: Jeremy Whitt | ||||||||||||||
Confirm approach to scoping of IP ranges for discovery outcomes (more Discovery but affects e-resources troubleshooting) |
|
(check in with various parties on listservs)
Steering Committee: Sherry Lochhaas
Create a shared storage space where the entire license documents for UC Tier 1-3 e-resource licenses can reside, so that we can compare terms obtained previously within the system. It would be of additional benefit to be sharing information about license negotiations that have failed and reasons why.
[Phase 4 re-delegated from ACQ]
|
| Contact: Carla Arbagey Need to clarify what the task is for us. Previous ERES convos suggested that it is ambiguous whether this setting is needed and where the decision lies (ERES v DISC) settings that can be configured during Acq process, but largely e-res/Discovery | ||||||||||
Review previous Phase decision pages |
|
|
| Contact: Paula Pascual Review previous Phase decision pages to determine what is still relevant and needs to be included in SILS Documentation Center (copy over to ER space and label as “current” “pnp”) | ||||||||||
Title Transfers |
|
|
|
[SOT-CDL Capacity]
| Reinstate journal title transfer support that CDL offered a few years ago, so campuses know when a title moves from one publisher to another and if new access is included in Tier 1, 2 or 3 licensing agreements. Record keeping and confirmed access for backfile - IZ vs NZ. Need to clarify goal - is this compiling feedback for CDL page or documenting local practice or other? 2024-05-09 Meeting notes -UCD process demo | |||||||||||||||||
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) SC will review/revise based on work from CDLNZ-PT and Shared Collections | NZ |
| [SOT-CDL Capacity] |
| Contact: Sherry Lochhaas , Judy Keys Paused pending results of CDLNZ-PT and CDL Shared Collections work with ExLibris consultant CDL/Campus E-Resources Workflow/Record Structure - AEFG Handoff Document CSU ERM Best Practices and Procedures → Shared e-Resources - Consortial Acquisitions CDLNZ-PT Testing Documents and Results on SILS GDrive | |||||||||||||
Additional process work on NZ/IZ de-duplication/reconciliation. |
|
|
| Identifying eBooks and eJournals in an IZ that are also activated in NZ | Contact: Tamara Pilko |
Status | Definition | ||||||
|---|---|---|---|---|---|---|---|
| Being investigated | ||||||
| Actively worked on | ||||||
| Completed | ||||||
| Waiting to work on | ||||||
| Only use for joint deliverable that is with another OST for evaluation | ||||||
| Do not use, prefer on hold or delegated |
Priority
Indicated the order of execution of deliverables
...