Work Plan: Resource Sharing
Deliverable | Priority | Due Date | Status | Effort | Related links | Notes | |
|---|---|---|---|---|---|---|---|
| 1 | CNR (article) requests: Update original Alma CNR request with status | high |
| in progress subgroup UCB, UCR, UCI | UC effort low; testing, but urgent |
| working with OCLC & ExL to assist their development & testing |
| 2 | UC and CSU Resource Sharing Partnership (in Alma) - as a whole UC (can act independently or subgroup) UCI; UCSD; UCM; UCR; UCD campuses experiment/keep in touch with RS OST; watch out for conflicts; keep eye out for interactions with SLFs | high |
| In progress next step: discuss impact of CSU ill-ing practice changes | partnership with CSUs large size effort on UCs (also on CSUs) | first step would be to think about what sort of options/scenario to explore | |
| 3 | Tipasa outstanding issues
| high |
| in progress |
| from testing & development with OCLC: Tipasa outstanding issues | identify priorities of known gaps in Tipasa/Alma integration |
| 4 | Get P2P for digitization requests (uc to uc) (long term: P2P in addition to AFN; or P2P replacing AFN) | high | no explicit dependencies | paused | ExL willing to assist in config; lots of effort - config & testing, figuring out workflow implications |
| |
| 5 | Prioritized list/”specifications” of reports needed for AFN (including schedule c ExL case) | Medium |
| paused | medium effort (avoid delving into Alma guts) | potential overlap with chunk out & prioritize most important reports (include ccc report within priority)
| |
| 6 | pick up anywhere issues | medium | no external due date | not started | high |
| potential ideas: Questions: |
| 7 | Vendor environment scan | medium |
| not started | medium 12-18 months once begun | Tipasa Testers 2023 decision page | Vendor Environmental scan | next step: develop general criteria & questions (methodology) |
| 8 | RapidILL/Rapido for UCs (in Alma) - possible proposal for purchase | medium | may be influenced by walkaways of content negotiations | not started | Large effort Substantial new workflows at many locations, starting: Substantial set up in Alma, Ongoing: commitment to RapidILL standards for reciprocation. |
| |
| 9 | Environmental scan of peers
| low |
| not started | medium 12-18 months once begun | Tipasa Testers 2023 decision page | Environmental scan of peers | next step: develop general criteria & questions (methodology) |
| 10 | Harmonization of notices | low | no dependency dates, FOST targeting 2026 | not started (on hold in F OST; target date 2026) | F OST has taken up; RS OST may participate |
| Harmonization of notices such as overdue and “courtesy reminder time to renew” sent out by Lenders across the AFN so Network Borrowers are not told to go to Lending Institution’s portals to access renewals. |
| 11 | ExL’s solicitation to “contribute to the Resource Sharing Directory”. | low | after P2P investigation / (?)after CSU partnership | not started | tbd / pending P2P investigation |
| |
| 12 | potential AFN mismatches out of auto-flow to external broker (requests with bad/incomplete metadata) | low | no dependency dates (after P2P investigation & after Tipasa implementation) | not started | ExL willing to work with UCs on config; low-ish effort | use ‘sending borrowing request rules’ to catch requests in ‘ready to be sent queue’; option: if no identifiers, don’t sent to broker (aka VDX/Tipasa) and/or don't send through any partners | |
| 13 | Would like to see 3 option in the Blank ILL Form, specifically separate the Article or Chapter into two, one for "Chapter" and one for "Article"; impacts all resource sharing forms (investigate options, write up options & ramifications, ask D OST for feedback) possibly ask ExL for third form… | low | no due date | not started | large effort | page with the harmonized decisions for the resource sharing forms from SILs phase 4: FFILL (Go-Live) Policies for Resource Sharing Forms | possible dependencies on other forms (from Sandra FG: The UCLA Discovery team recommend this enhancement, they believe current options are confusing to patrons) |
| 14 | expired holds not found on the hold shelf or still stuck in transit | low |
| not started in progress in F OST (“item should be on hold shelf & is not”) | coord. with F OST |
| Create decision and documentation on what to do with expired holds not found on the hold shelf or still stuck in transit |
| 15 | procedures for handling Lost UC ILL Items ('scenarios' table of phase 4 decision page) have contacts, but not procedures/best practices F OST created directory for circ contacts;Library Fulfillment Directory (working on lost item practice recommendations) ; For ILL contacts, use OCLC policy directory | low | no external dependency dates | not started (in progress in F OST) |
| FFILL Post-Go-Live- Decisions on How to Handle Lost UC ILL Items | A decision page has been started to capture how the UCs want to handle Lost UC ILL Items. The Resource Sharing Group should discuss/add to this page and decide on the best way forward for each scenario presented, then communicate the information broadly. |
| 16 |
|
|
|
|
|
|
|
| 17 |
|
|
|
|
|
|
|
| 18 | Replace VDX with Tipasa - Tipasa implementation 2025 | high | Jul 1, 2025 | done | large effort | Tipasa Implementation Project Team charge Tipasa Implementation (2025) - SILS cohort only |
|
| 19 | Replace VDX with Tipasa | high | Aug 6, 2024 TDRII ‘tipasa development review, part II’ small team March 2024-August 2024
| done | large effort | from phase four hand off: | |
| 20 | UC request of RLF Building Use Only Items (similar to “library use only” deliverable?) Decision on how library identifies library use (non RLF) only material borrowed via AFN (similar to UC Req RLF Building Use deliverable?) | high | recommendation around mid 2025 - new bookband; working well Fulfillment completed August 1st, 2024 | done | coord. with F OST (F OST may lead) |
| This is a continuation of a service already provided by the RLFs for UC patrons. UCR and UCB are currently exploring how to enable BUO requesting from the RLFs, and will inform the campuses once they find a workable solution that can be implemented (may also be related to AFN reading room issues) This will affect local Fulfillment and ILL teams workflows in a positive manner (may also be related to AFN reading room issues) |
| 21 | Analytics ‘sub’project, schedule c for 2024 due date | high | Completed April 2024 | Done | large, in conjunction with ExL |
| gathering afn digization requests |
| 22 | UC + Ex Libris AFN Task Force (label: afntf) | high | completed on May 12, 2022 | DONE | approx. 3 months elapsed | https://uc-sils.atlassian.net/wiki/spaces/RS/pages/1879343105 | from Phase 4 hand off, “Identify root cause of resource sharing effectiveness discrepancies” |
| 23 | Evaluate initial resource sharing strategy and compare with alternatives. | high | completed Jun 1, 2022 | DONE |
| Evaluate the current resource sharing strategy (AFN plus VDX integration). Is it working well? What are the alternatives (eg. Alma P2P, Alma brokering) and should they be considered? | |
| 24 | Enable sandbox environment for system-wide resource sharing testing for SILS Ops Center | high | target Aug 19, 2022 (after next sandbox refresh) | DONE | approx. 10-20 hrs per campus (likely 2 people per campus) | https://uc-sils.atlassian.net/wiki/spaces/RS/pages/1877934227 | Create and document test patron accounts; create resource sharing analyst accounts; document and implement sandbox refresh procedure. |
| 25 | Phase 1: Set up recurring statistics for resource sharing in Alma Analytics borrowing/lending counts; schedule C | high | Nov 1, 2022 | DONE | phase 1: 5 months elapsed |
| |
| 26 | which hybrid model should RS OST investigate - direct FN and/or P2P | high | Nov 2, 2022 https://uc-sils.atlassian.net/wiki/spaces/RS/pages/2018574347 | DONE | “phase 1” three person team to look into config options & begin test planning ExL willing to work with UCs on config; low-ish effort | google drive folder for project RS Retrospective: Fulfillment Network https://uc-sils.atlassian.net/wiki/spaces/RS/pages/1919221761 (discussion) | informs ‘ILL-ing ER in UC’ deliverable |
| 27 | Consortial block | high | decision page delivered to OSTs for voting: anticipated (no dependency dates) | DONE | Co-lead F & RS involvement | block blocked users at point of requesting (rather than surprising them with a block they attempt to check out) | |
| 28 | Documentation Review (with ExL; WorkStream Improvement Plan, SILS cohort only) |
| November 2025 | DONE |
| WIPT - doc (SILS Cohort) |
|
| 29 | VDX clean up account for all active requests in VDX | high | mid December | DONE | high | VDX Cleanup (SILS Cohort) |
|
| 30 | AFN protocols and procedures (consulting for F OST) | low (RS OST priority) | TBD (driven by F OST) | DONE (in progress on F OST side) | consult/provide feedback in creating document; F OST feels need for at least on RS person Meet 2-3 times per month [could frequency be less?] or as needed and consult with the larger RS OST & F OST cohorts | https://docs.google.com/spreadsheets/d/1gNy67PbyVvSw7wPY177mGOkriv4i7w_h/edit#gid=915265881 | Streamline policies, procedures, and best practices for AFN lending & borrowing institutions to expeditiously address, communicate, and resolve fulfillment questions, issues, and discrepancies |