Attendees:

• Debra Howell
• Laura Daniels
• Ann Crowley
• Vandana Shah
• Emily Zinger
• Cammie Wyckoff for Andy Horbal
• Jesse Koennecke
• Phil Robinson
• Simeon Warner
• Jacob Sayward
• Tom Trutt

Regrets:

• Andy Horbal

Agenda:

• Welcome Tom Trutt
• Review enhancement requests - None
• Security Team Updates - Phil
• Anything from CC/PC - Simeon/Jesse
  • PC - draft roadmap has been created; a few more weeks of review before finalization
  • CC - current focus is on membership drive; onboarding to the FOLIO community
• 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?"
  • Priorities review: https://cornell.app.box.com/file/892802124979

  • Holly created a filter (https://issues.folio.org/issues/?filter=14109) to display all of the Access Services issues from her assessment. She also added the JIRA issue keys to the original document at https://docs.google.com/document/d/1lwnZpkiw7G0c3EyObRRnjuV6XVMcFNK1lWUG952sFgI/edit?usp=sharing

  • 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
  • Andy's notes on prioritization:
    • Of these five issues, the one on line 35 of the “Cornell Current Priorities” spreadsheet you created (“Wrong slips are being inserted . . . ”) is our #1 top priority, and we humbly submit that it should be pretty high up on CUL’s list as well.
    • We think that the ones on lines 32 (“Part of the extended time . . . “), 33 (“The ‘print by default’ settings . . .”), and 34 (“Showing the print preview . . . “) would ideally be grouped as a single priority called something like “improve printing,” and it’s also pretty important to us. If we HAVE to treat them separately, the one on line 34 is the biggest problem, but it might also be the toughest one to solve.
    • The one on line 31 (“Pick slips need to include . . . “) has gotten quite a bit of attention on JIRA lately and appears to be headed to the RA SIG for further discussion. We will continue to advocate for this in the FOLIO community, but don’t necessarily think it needs to be super high up on CUL’s list of priorities.
• 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!

Tracking

• 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