See Best Practices for Decision Pages and Tags for groups
Legend:
| Status | ||
|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
| Page Properties | ||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Recommendation
[RS OST will create a small group to check in & test after each deliverables - (currently slated for May & June/July 2024]
[delay a ‘firm’ decision about summer 2025 target until … Dec? Nov? 2024]
[2024); report back to RS OST by August 2024.
RS OST will determine a target implementation date after the successful full test of the integration possibly in summer/fall 2025.
RS OST to re prioritize in work plan projects https://uc-sils.atlassian.net/wiki/spaces/RS/pages/2271739914/Tipasa+Testers+2023+decision+page#RS-OST-approves-these- projects-for-RS-OST%E2%80%99s-work-plan based on new & relevant information (copy them in???)].
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
As of March 8, 2024 the integration between Tipasa and Alma does not meet the minimum requirements of the University of California, thus Tipasa cannot be implemented in summer 2024.
March 8 2024 snapshot Gaps in Alma/Tipasa integration, [UC only, request access if prompted]
Background
Tipasa Development Review period
Timeframe: November 8, 2023 to March 8, 2024
After two failed integration projects (detailed below) OCLC reached out to Ex Libris in September 2024 2023 to address the remaining gaps in the integration between the two products. OCLC presented their summary report to UC [UC only, request access if prompted] to UC in early October 2023. Based on OCLC’s work plan, RS OST created the small group “Tipasa Developer Review” to work with OCLC and Ex Libris on the remaining gaps.
...
Based on the necessary work to test the full integration, kick off an implementation project, implementation itself, and any pre term training for student staff, March 8, 2024 was the last possible viable date for a full integration delivery that could possibly result in a Summer 2024 implementation of Tipasa.
Tipasa Pilot
Timeframe: September 2022 to January 2023.
...
OCLC provided a multi-month implementation plan that included demonstrations for Tipasa configuration and use, that did not take into account our requirements of our Alma integration needs and expectations.
“The findings of the UC RS OST is that the Tipasa product in its current state is not ready for implementation at the UC.” from Tipasa project plan outline 2023/2024 (decision page)
RS OST created a gaps document [UC only, request access if prompted] to identify shortcomings with the Tipasa program and integration with Alma as of the time of testing.
“The gaps are to a number and degree such that manual remediation on UCs part would effectively halt any non-consortia interlibrary loan traffic in or out of the UCs. This would negatively impact UC patrons, as roughly 47% of materials supplied to UC patrons are filled from outside the consortium (from UC Library Annual Statistics, 2021-2022, table 5, pages 5-6)” from Tipasa project plan outline 2023/2024 (decision page)
Tipasa Testing period
Timeframe: March to October 2023
...
Tipasa Testers group found that Tipasa is not ready for UC to use as a VDX replacement as of Oct 6, 2023.
Dependencies
Questions to consider
Action Log
point person/action/due date | Completion Date | Notes | Status |
|---|---|---|---|