Attendees:
- Phil Robinson
Regrets:
- Review enhancement requests
- Security Team Updates - Phil
- email address is ready, which will feed TDX; archive the FOLIO Permissions Slack channel
- At Monday's RA SIG meeting Stephanie Buck gave an update on Title-Level Requesting (TLR) and noted that institutions that wanted to implement it will likely be able to do so as early as Morning Glory. More details can be found on the FOLIO wiki here: https://wiki.folio.org/display/RA/Title+level+requests+-+features+and+info. Would CUL want to implement Title-Level Requesting - how do we make the decision as it spans functional areas? It definitely would impact both access services and LTS workflows, and might affect other areas as well, such as CUL-IT via Blacklight. - Andy
- 1 use case that we can think of: Long term loan laptops where the patron wants the next one that's available
- Could have potential for reserves stuff
- Next step: Andy will work with Access Services and Public Services to see if we want this and report back
- CONTINUED: Themes and Discuss how we might maintain this going forward: Continue conversation on "How do we understand and agree on CUL priorities for FOLIO?"
- Notes from last meeting:
- How do we get to a handful of top priorities?
- Could we code it like the Faculty Survey results?
- Could we build Epics around the themes for CUL?
- How many potential areas of the Library are impacted by an issue?
- Share the priority list in a place that people can see it
- What data do we already have?
- JIRA R1s
- Pointing exercise Excel spreadsheet: https://cornell.app.box.com/file/886530146018
- Holly's Access Services usability study: https://docs.google.com/document/d/1ab1rAhQYgHEbrreCsMhr0RW6uFJftMs1NwSBZ8gbSeY/edit?usp=sharing
- PRIORITIZED: https://cornell.app.box.com/file/896081201246
- List of LTS issues (Excel): analysis: https://cornell.app.box.com/file/891530533804
- CUL List of Enhancement Requests
- Priorities review: https://cornell.app.box.com/file/892802124979
- Notes from last meeting:
- Open discussion time
FYI
- Juniper Upgrade Hot Fix 4 Schedule:
- December 3 - Dry Run ready for testing - COMPLETE
- December 6-10 - testing dry run; approve or reject - APPROVED/COMPLETE
- December 13-17 - Upgrade Test and Training- COMPLETE
- December 17 - Upgrade Prod (after 6pm)