Attendees:
- Phil Robinson
Regrets:
- Review enhancement requests - NO NEW
- Security Team Updates - Phil
- Disabled Student workers access before break manually; will re-enable them for the Spring semester - team will look for a way to automate this
- Getting ready to archive FOLIO Permissions Slack channel and stand-up email/TDX
- Functional Support Team is approved with Tom Trutt as lead
- Should Tom be added to this committee?
- If Tom is interested, yes
- Do we want to charge the Support team with updating Procedures?
- Yes, for FOLIO administrative procedures
- Should Tom be added to this committee?
- UPDATE - Andy
- 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
- Andy talked with Bonna and her recommendation is to ask the ASST to consult with other groups and come up with a recommendation for CUL
- 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
- 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
- NEXT STEPS:
- What are our criteria for prioritization?
- Most painful/impactful on work
- Items that would benefit multiple areas
- How quickly can it be done?
- Prioritize list of top priorities
- What are our criteria for prioritization?
- Notes from last meeting:
- Open discussion time
FYI
- Kiwi proposed upgrade:
- Dry Run 4/4 - I have told EBSCO this doesn't work for us and we need the dry run sooner
- Upgrades of all 3 tenants by 4/18
- Andy - Spring break begins on 4/2--this might be a good time to upgrade!