Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Deliverable

Effort/

Dependency

Priority

Due Date

Status

Related Links

Notes

Implement the E-Resources/Acquisitions/Centrally Managed Licenses for Network Zone architecture
Resource: Alma Collaborative Networks

CDL initiative

Status
colourRed
titleHIGH

[SOT-CDL Capacity]

Status
colourPurple
titleDELEGATED

https://uc-sils.atlassian.net/wiki/spaces/CDLNZPT

CSU Model - Shared Electronic Resources Procedures and Best Practices

930/973 fields
[Phase 4 delegated]

N/A

N/A

Status
titlena

Status
colourGreen
titleDONE

930/973 fields - practice for continued use

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

Multi-series electronic collection level records [CDL request]

[SOT-CDL Capacity]

Status
colourRed
titleSTALLED

Multi-Part E-Collections

Steering Committee: Sherry Lochhaas
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.

Sharing of E-resource Licensing Information across UC [Phase 4 delegated]

[SOT-CDL Capacity]

Status
titlena

Status
colour

Red

Green
title

STALLED(check in with various parties on listservs)

DONE

Sharing of E-resource Licensing Information across UC

Steering Committee: Sherry Lochhaas Additional process work on NZ/IZ de-duplication/reconciliation.

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 - AEFG Handoff Document

Licensing - terms visibility for ILL, etc.
[Phase 4 re-delegated from ACQ]

Status
titlena

Status
colourGreen
titleDONE

NZ License Practice

starts at CDL for standards on consortial purchases, then flows to campuses for harmonization of local practices

Shared decisions around the CZ
[Phase 4 delegated]

NZ

N/A

Determine when we can make shared decisions for specific collections and/or use cases with regard to the CZ

Example from another consortia:

Closely tied to NZ/IZ de-duplication/reconciliation work. A wide range of local practices would lead to duplication of records (for any given title, some campuses might accept a CZ records while other would choose to import from OCLC, or a vendor, etc.). What level of duplication would be allowed?

Also, often not clear ahead of time whether CZ metadata is acceptable, so has impact on Acq-to-Cat workflow. If Acq chooses CZ record and Cat decides to use NZ record, it leaves a “ghost” CZ bib in the NZ (example - MMS ID: 9917241870306531)

Perpetual rights and entitlement tracking in Alma (campus/IZ)
[Phase 4 re-delegated from ACQ]

NZ

CZ harmonization

Status
colourRed
titleHIGH

Status

STALLED

workflow/policy/practice page

Steering Committee Contact: Sarah Sheets
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

colourYellow
titlein progess

Perpetual rights and entitlement tracking in Alma DRAFT

Best Practice for activating a CZ portfolio in both NZ and IZ

Best Practices: Recording Perpetual Access in Alma

Contact: Michelle Polchow and Tamara Pilko

  • separate from a comprehensive tracking project for consortial e-resources

  • document how IZ coverage trumps NZ coverage in some cases

  • local practices/workflows

  • tracking changes in provider and ecollection

NASIG Digital Preservation Webinar: Integrating Preservation into Librarian Workflows

Perpetual rights and entitlement tracking in Alma (CDL/NZ)
[Phase 4 re-delegated from ACQ]

NZ[SOT-CDL Capacity]

Status
colourRed
title

HIGH

high

Status
colour

Purple[SOT-CDL Capacity]

Red
title

DELEGATED

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

CSU ERM Best Practices and Procedures

Reporting/analytics - define desired statewide reports
[Phase 4 re-delegated from ACQ]

UCOP Statistics Task Force

not started

  • separate from a comprehensive tracking project at each campus

  • Track in Alma? or point of need service?

CRKN consortia perpetual access tracking project - tool forthcoming

Local E-resources practices chat/clearing house

campus interest

Status
colourRed
titleHIGH

Status
colour

Purple

Green
title

DELEGATED

done

Stakeholders

https:

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 - AEFG Handoff Document (applies to all Analytics topics from Phase 4)

CSU Helpful Alma Repository Searche Queries

Reporting/analytics - System review/improvement processes - show and tell?
[Phase 4 re-delegated from ACQ]

NZ

[SOT-CDL Capacity]Low

//uc-sils.atlassian.net/l/cp/EDXa1bRs

Contact: Jeremy Whitt

SILS Community Slack - #acquisitions-and-e-resources

Post-go-live CRL records in Primo

ExLibris/CRL support

Status
colourRed
titleHIGH

Status
colourYellow
titleIN PROGRESS

Reporting/Analytics - AEFG Handoff Document (applies to all Analytics topics from Phase 4)

Reporting/Analytics - Shared Vendors vs harmonized vendor codes for consortia-level spending reporting
[Phase 4 re-delegated from ACQ]

NZ

CRL records in Alma/Primo (DRAFT)

RMFG had a recommendation from phase 4

Contact: Tamara Pilko

UCLA troubleshooting identified CRL content missing June 2023.

Multi-series electronic collection level records [CDL request]

RM

DISC

Status
colourYellow
titlemedium

[SOT-CDL Capacity]

Status
colour

PurpletitleDELEGATED

“How much does UC spend with VendorX?”

Reporting/Analytics - AEFG Handoff Document (applies to all Analytics topics from Phase 4)

Green
titledone

Multi-Part E-Collections

Contact: Paula Pascual

Authentication/authorization protocols

Status
colourYellow
titlemedium

Status
colourGreen
titledone

Authentication methods

Contact: Tamara Pilko

Document current authentication practices at UC campuses. Track discussion around this topic

E-resources troubleshooting communication

Status
colourRed
titleHIGH

Status
colourGreen
titledone

E-resources troubleshooting communication

Best Practices: Writing Tickets & Troubleshooting

Contact: Jeremy Whitt

Confirm approach to scoping of IP ranges for discovery outcomes (more Discovery but affects e-resources troubleshooting)
[Phase 4 re-delegated from ACQ]

Status
colour

Red

Green
title

NOT STARTEDstatus gathering?/ local practices/delegate to discovery?

low

Status
colourYellow
titleIN PROGRESS

Scoping of IP Ranges DRAFT

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

Perpetual rights and entitlement tracking in Alma (generally)
[Phase 4 re-delegated from ACQ]

Review previous Phase decision pages

Status
colour

Red

Green
title

HIGH

Local E-resources practices chat/clearing house

Regular check in between campus representatives

Statuscolour

low

Status
colour

YellowtitleIN PROGRESS
  • current functions in CZ/CDI/Primo

  • local practices/workflows

  • changes in provider and ecollection

Perpetual rights and entitlement tracking in Alma

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

Red
title

HIGH

Status
colourYellow
titleIN PROGRESS

  • CKG?

not started

AEFG Decisions

https://uc-sils.atlassian.net/

l

wiki/

cp

spaces/

EDXa1bRs

E-resources troubleshooting communication

Status
colourRed
titleHIGH

P4D

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

Status
colour

Red

Authentication/authorization protocols

Yellow
title

NOT STARTED
  • Slack

  • more baseline communication rules?

E-resources troubleshooting communication

Steering Committee Contact: Michelle Polchow

medium

Status
colour

Red

Yellow
title

NOT STARTED

Authentication/authorization protocols

Steering Committee Contact: Michelle Polchow

Title Transfers

Status
colourRed
titleHIGH

[SOT-CDL Capacity]

Journal title transfers

IN PROGRESS

Best Practices: Title Platform Transfers

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.

Post-go-live CRL records in Primo

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)
[Phase 4 re-delegated from ACQ]

SC will review/revise based on work from CDLNZ-PT and Shared Collections

NZ

Status
colourRed
titleHIGH

[SOT-CDL Capacity]

Status
titleOn hold

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 ACQ ERM Workflow (local) visual model

CSU ERM Best Practices and ProceduresShared e-Resources - Consortial Acquisitions

CDLNZ-PT Testing Documents and Results on SILS GDrive

Additional process work on NZ/IZ de-duplication/reconciliation.
[Phase 4 re-delegated from ACQ]

Status
colourYellow
titlemedium

Status
colourGreen
titledone

Identifying eBooks and eJournals in an IZ that are also activated in NZ

Contact: Tamara Pilko

Status

Definition

Status
titleon hold

Being investigated

Status
colourYellow
titleIN PROGRESS

RMFG had a recommendation from phase 4

Post-go-live migration handoff misplaced assigning this deliverable to SILS. UCLA troubleshooting identified CRL content missing June 2023.

Actively worked on

Status
colourGreen
titleDone

Completed

Status
colourRed
titleNOT STARTED

Waiting to work on

Status
colourPurple
titleDelegated

Only use for joint deliverable that is with another OST for evaluation

Status
titlestalled

Do not use, prefer on hold or delegated

Priority

Indicated the order of execution of deliverables

Status
colourRed
titlehigh
Status
colourYellow
titlemedium
Status
colourGreen
titlelow

Questions to ask when assigning priority:

  • What is the frequency at which members experience the issue?

  • If it is not addressed, will it impede local workflows?

  • Does it affect other areas of members' work?

  • Do we have some/most of the information we need?

  • Is it contingent on other groups (SILS or other)?