...
Topic / Desired Outcome | Time | Who | Notes | Decisions | Actions | ||
---|---|---|---|---|---|---|---|
1 | make sure Jason records meeting / any announcements? | 1 | Jason | ||||
2 | Feedback for Alternative Access team (email to RS OST list 2/2/2024 from Sarah Houghton) | 20 | Jason/Alison | questions raised: have some campuses suppressed ill link on held ejournals or journals? how/when does it appear in articles (CDI or OURL)? does/can message show up for all users or only those eligible for ill? - not in RS OST purview; answers to these questions influence RS OST's feedback; RS OST has concerns about ‘rush requests’ negatively impacting regular/typical service | pause discussion until qs answered |
| |
3 | Review Tipasa decision page feedback | 10 | Alison | reviewed feedback, no changes/edits needed on page | page decided ‘yes’ next step: slot in voted projects into RS OST work plan | ||
4 | Suppressing primo request links for material on loan or missing?? - who has done this? how was this done? | 10 | Judea | why not suppress? avoid recalling items checked out; UCR: settings that only some users can create holds/recalls on checked out items (will send info to lists) | |||
5 | Wrap up / Review actions and decisions | 5 | NEXT TIME: slot in projects from Tipasa Testers 2023 decision page to Work Plan: Resource Sharing | ||||
6 | |||||||
7 | Capture important topics for future discussion | Revisit tipasa tester’s feedback 2/7 jcn RS Analytics ticket (06398481) & Analytics Future proofing group – revisit in January 24 items being kicked out to WorldshareILL at end of ROTA even though we have those items in our catalog (Demitra) [RS OST SC notes 5/1/23: hold for consideration post Tipasa implementation]: ‘pick up anywhere exceptions’: review shared messages, what would be next steps | |||||
8 | Total | x/x |
...