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 20 Current »

See Best Practices for Decision Pages and Tags for groups
Legend: NOT STARTED IN PROGRESS STALLED DECIDED

Status

DECIDED

Description

Timing of the replace VDX with Tipasa: target for summer 2023

Decision summary

Change timeline for replacing VDX with Tipasa from summer 2022 to summer 2023

Work Plan Deliverable

Replace VDX with Tipasa

Owning group

Resource Sharing OST (SILS-RS-L@listserv.ucop.edu)

Approver

Resource Sharing OST

Consulted

ILL CKG, CDL Resource Sharing Team, SILS Operations Center, Fulfillment OST, SILS All Chairs

Informed

SILS-Cohort; SILS OT

Decision-making process

fist of five

passed, unanimous fives

Priority

high

Target decision date

Date decided

Recommendation

  • Target summer 2023 for replacing VDX with Tipasa

Impact

Stakeholder group

Impact

Resource Sharing OST

Major impact in terms of project planning, investigation, testing, configuration, and integration related to Alma and all resource sharing aspects.

All UC Libraries resource sharing staff

Major impact to workflows related to Alma and all resource sharing aspects.

SILS Operations Center

Medium impact to system maintenance, configurations, and data tables.

CoUL

Strategic prioritization of major systemwide projects.

Reasoning

The replacement of VDX with Tipasa is better positioned for summer 2023 rather than August 2022 because:

  • UC ILL staff are still working to optimize configuration and workflows needed for Alma resource sharing;

  • The replacement involves high impact for all UC ILL staff and potentially other UC library staff;

  • The replacement requires complex decisions related to workflow and integration that need to be done prior to being ready for the actual replacement.

Background

The Intercampus Resource Sharing Operations Subteam (RS OST) received this project in the “Phase 4 hand off”, as reviewed by the SILS Operations Team (OT) and SILS Leadership Group (SLG). The project fits squarely within RS OST’s area of responsibility pertaining to the workflow, data, policies, and integration of external resource sharing management applications (page 19 of Ongoing SILS structure, work practices, and charges).

The external (ext.) resource sharing (RS) management application, VDX, should be replaced with Tipasa because:

  • According to OCLC (December 2021) the current planned sunset of VDX application is in 2024

  • OCLC halted active development on VDX several years ago

  • Tipasa is considered by OCLC to be their best, most future forward resource sharing product

  • Replacing VDX with Tipasa could offer further integration options with Alma and other external resource sharing management applications

  • An RFP for a new ext. RS management application would likely take at least 24 months, exceeding any timeline OCLC has given for VDX’s sunset

Options Considered

Option 1

Option 2

Description

Replace in August 2022

Replace in summer 2023

Pros

Strike the project as complete sooner

Take sooner advantage of possible integration offerings not available on Alma [or VDX]

Time to understand UC’s ext. RS management application needs

Time to evaluate Tipasa’s integration capabilities with Alma & identify any missing necessary components

Time to evaluate Tipasa’s integration capabilities with other potential ext. RS management applications & identify any missing necessary components

Time for OCLC to build out any missing features or integration options

More integration offerings will be available on Tipasa

Opportunity to learn from the first VDX upgrade clients

Cons

The Alma AFN configuration needs further optimization (the AFN Task Force project); replacing VDX at the same time pulls resources from the AFN TF;

UCs may miss needed requirements in Tipasa due to short time table;

Tipasa may not be ready to meet UC’s needs;

First VDX clients scheduled to go live in summer 2022; No VDX clients have yet done this migration; we don’t want to be first.

There are no significant cons to waiting: VDX is stable and we see no risks in staying on it for now.

Dependencies

Questions to consider

Action Log

point person/action/due date

Completion Date

Notes

Status

on 3/9/22 agenda

DONE

  • Alison Ray (CDL) send request for feedback to ‘consulted’ groups

requests sent via email; due date of march 21, 2022

DONE

3/9/22: request to be on 3/16/22 agenda sent

took questions during 3/16/22 meeting

DONE

DONE

  • Alison Ray (CDL) inform OT of decision, recommend communication to DOC / CoUL

DONE

  • No labels