Versions Compared

Key

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

...

Page Properties

Status

Status
colourYellow
titleIN PROGRESS

Description

Extend Alma Resource Sharing using UC P2P partners in addition to current UC AFN partners

Decision summary

Implementation plan to add UC P2P partners in Alma Resource Sharing for digitization requests (articles, book chapters, and ebooks); keeping physical requests as UC AFN partners.

Work Plan Deliverable

Get P2P for digitization requests

Owning group

SILS RS OST

Approver

SILS RS OST

Consulted

SILS OT, SILS F OST, ILL CKG

Informed

SILS D OST, SIlS Cohort

Decision-making process

After consulting & discussion, RS OST voted fist of five:

UC Berkeley

UC Davis

UC Irvine

UC Los Angeles

UC Merced

UC Riverside

UC Santa Barbara

UC Santa Cruz

UC San Diego

UC San Francisco

California Digital Library

Priority

Medium

Target decision date

Date decided

[type // to add Date]

Table of Contents
minLevel2
maxLevel3
outlinefalse
stylenone
typelist
printabletrue

Recommendation

RS OST recommends to (move forward/not move forward/reconsider) the implementation plan of extending UC’s Alma Resource Sharing with UC P2P partners for digitization requests.

...

Stakeholder group

Impact

SILS OT

Given high level permission required for some Alma configuration, campus SILS system administrator(s) may need to be tapped for work.

SILS F OST

little to no changes expected

ILL CKG + UC ILL Staff

Changes in workflow for digitization requests (articles, book chapters, and ebooks).

SILS Cohort

little to no changes expected

Reasoning

Background

...

& charge

With the implementation of the Automated Fulfillment Network (AFN), RS OST were informed that alternative options were available to replace or use in conjunction with AFN. One of those options was Peer-to-Peer (P2P), but the group was not ready to move forward on any additional changes. As limitations with the use of AFN became apparent, further discussions of implementing P2P were discussed.

...

  • 3 weeks (Sample dates: Sep 2-20): Make configurations in all UC PSBs, P2P configuration instructions (UC only; note ‘rota automation recommendation’ above)

  • 6 weeks (Sample dates: Sep 23-Nov 8): Testing in pairs, option to review/discuss testings in RS OST meetings

  • 2 weeks (Sample Dates: Nov 11-Nov 22): Discuss and evaluate tests

  • 1 day (RS OST meeting, Sample date: Dec 4): yes/no move forward with P2P in production

If yes, implement in production:

  • 1-2 days, coordinated (Sample date: late Jan 2025 or early Feb 2025): Make configurations in all UC production Almas

  • 2-6 months (Sample date: Feb 2025 - July 1 2025 - note: might be concurrent with other large project): go wild

  • After 1 month (sample date: August 2025): check analytic reports for these requests

  • After 6 months (Sample date: Dec 2025): check in, continue? Undo? expand?

If no:

  • 1-2 weeks: think about why not? Use answers to consider next steps, if any.

...