Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 48 Next »

Deliverable

Effort/

Dependency

Priority

Due Date

Status

Related Links

Notes

930/973 fields
[Phase 4 delegated]

DONE

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

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

DONE

(check in with various parties on listservs)

Sharing of E-resource Licensing Information across UC

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.

Licensing - AEFG Handoff Document

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

DONE

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

HIGH

IN PROGRESS

  • current functions in CZ/CDI/Primo

  • local practices/workflows

  • changes in provider and ecollection

Perpetual rights and entitlement tracking in Alma

joint w/ ACQ, both local and CDL materials.

CRKN consortia perpetual access tracking project - tool forthcoming

NASIG Digital Preservation Webinar: Integrating Preservation into Librarian Workflows

  • document how IZ coverage trumps NZ coverage in some cases

  • separate from a comprehensive tracking project at each campus or for consortial e-resources

Local E-resources practices chat/clearing house

Regular check in between campus representatives

HIGH

IN PROGRESS

  • CKG?

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

Post-go-live CRL records in Primo

ExLibris/CRL support

HIGH

IN PROGRESS

CRL records in Alma/Primo (DRAFT)

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.

Multi-series electronic collection level records [CDL request]

RM

DISC

[SOT-CDL Capacity]

IN PROGRESS

Multi-Part E-Collections

Contact: Paula Pascual - consulting with Liz Miraglia and Caitlin Nelson about next steps

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.

Authentication/authorization protocols

MEDIUM

IN PROGRESS

Authentication methods (DRAFT)

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

Reporting/Analytics - “How much does UC spend with VendorX?”
[Phase 4 re-delegated from ACQ]

Tamara will review if this belongs with ACQ or outside SILS

NZ

LOW

IN PROGRESS

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

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

NOT STARTED

status gathering?/ local practices/delegate to discovery?

settings that can be configured during Acq process, but largely e-res/Discovery

E-resources troubleshooting communication

HIGH

NOT STARTED

  • Slack

  • more baseline communication rules?

E-resources troubleshooting communication

Steering Committee Contact: Michelle Polchow

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

HIGH

[SOT-CDL Capacity]

ON HOLD

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

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

SC will review/revise (split?)

NZ

CZ harmonization

ON HOLD

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.

Title Transfers

MEDIUM

[SOT-CDL Capacity]

NOT STARTED

Journal title 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.

Need to clarify goal - is this compiling feedback for CDL page or documenting local practice or other?

Review previous Phase decision pages

LOW

NOT STARTED

AEFG Decisions

https://uc-sils.atlassian.net/wiki/spaces/P4D/overview

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”)

Status

Definition

ON HOLD

Being investigated

IN PROGRESS

Actively worked on

DONE

Completed

NOT STARTED

Waiting to work on

DELEGATED

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

STALLED

Do not use, prefer on hold or delegated

Priority

Indicated the order of execution of deliverables

HIGH MEDIUM LOW

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)?

  • No labels