2022-04-25 Meeting notes: Planning Wolfcon sessions

2022-04-25 Meeting notes: Planning Wolfcon sessions

Date

Apr 25, 2022

Housekeeping

  • New page to collect cross-app implementers topics: Implementers topics | Cross-app

    • SIG conveners: please make SIG members aware

    • everyone can add topics; will be invited to the relevant meeting for discussion

  • Next topics

    1. Permissions

      1. field based → walk through where needed?

      2. SIG reps and PO

        1. example: specific perms to edit the barcode field

        2. view and edit vs. only view e.g. source record (quickmarc) - there seems to be a JIRA

        3. would be UI-based permissions

        4. Brooks: better-focused on managed customized UIs?

        5. Owen: would be good to undertsand the use cases

    2. searching in FOLIO

      1. ERM SIG started to collect areas of improvement - of Interest for all apps? - consistency when filtering ...

      2. save searches/filters and apply them in one click

      3. look-up for users: add filter for tags

      4. in Organizations: keep search/filter after editing a record

        1. users applies filters and has 5 results that all need to be edited

        2. when one record is edited, the search/filter is deleted and the user needs t start searching/filtering again

    3. ACQ units in ERM

Discussion items

  • Potential topic: Planning for Wolfcon sessions

Minutes

Workflow sessions

  • Libraries walk through workflows from beginning to end, e.g. Purchase a resource for a patron (incl. Orders, Receiving, Requests, Invoices, Check-in, Check-out, Inventory)

    Incl. gap analysis

  • pain points related to record interactions

    • when migrating 

    • moving items, holdings 

    • right use cases and right library person needs to be there

  • Managing upgrades so that implemented libraries to take advantage of new functionality

    • Example: new connection between order lines and holdings records with Kiwi, but existing orders migrating over will not have this information populated. There should be a way to support existing data in FOLIO to take advantage of the new feature.

    • May be related to earlier issue of reference data getting overwritten when upgrading. Tech Council recommended a series of test scripts as part of definition of done. Maybe we need to also address assisting libraries who are upgrading.

    • There will be a conversation with the Acquisitions SIG - can also go to Implementer's SIG.

  • talking through use cases

  • Inventory is a central app; how can we make interactions easier

  • define business processes involved

  • thinking about process rather than data points

  • SWOT related to design decisions: showing advantages of FOLIOs approach vs. disadvantages (we do not want to build a monolithic system)

    • devs needed

Chat

00:07:20 Martina Schildt | VZG: https://folio-org.atlassian.net/wiki/display/AppInt/Implementers+topics+%7C+Cross-app 00:08:49 Brooks Travis: Apologies for missing context on my part, but what do you mean by field-based permissions? 00:09:03 Brooks Travis: Is this crossover with UI-customization? 00:09:46 Kristin Martin: BRB 00:10:42 Brooks Travis: So, ui-only permissions, because we don’t presently have the ability to limit that at the API level 00:11:30 Brooks Travis: I think there’s a Jira for that 00:12:35 Kristin Martin: back 00:14:59 Brooks Travis: I just wonder if the lift would be better-focused on managed customized UIs 00:15:32 Maura Byrne: So to configure things in Settings? 00:19:18 Brooks Travis: My audio dropped out there… :/ 00:19:47 Jana Freytag: It's Monday! 00:20:17 Maura Byrne: And I'd like to ask UM. 00:20:36 Jana Freytag: And I RA 00:28:52 Brooks Travis: I say this as someone who isn’t going to be at WOLFCon in-person, but I think that cross-app data sync should be on the agenda for discussion, because even if our group has something actually out by then, it will only be a sub-set of the desired functionality. 00:32:43 Brooks Travis: It’s potentially a fundamental shift in the data architecture of FOLIO… 00:33:30 Kristin Martin: What's our desired outcome from the discussion? 00:33:42 Maura Byrne: I would think that for this topic, we’d want a developer there to see the problem, and be able to say if the problem can be solved, or if we have to find a workaround. 00:36:52 Maura Byrne: BRB 00:39:04 Maura Byrne: Back. 00:39:25 Laura (she/they): I really appreciate you bringing this up, Brooks 00:40:41 Owen Stephens: Perhaps something like a session to do a SWOT of current state of Folio to understand where we are might be a start? 00:44:52 Brooks Travis: Download glitches, upload fixes, Owen 🙂

 

 

Attendees

Present

Name

Home Organization

Present

Name

Home Organization

 

Ann-Marie Breaux

EBSCO

x

Brooks Travis

EBSCO

 

Charlotte Whitt

Index Data

regrets

Dennis Bridges

EBSCO

x

Dung-Lan Chen

Skidmore College

 

Gill Osguthorpe

UX/UI Designer - K-Int

x

Heather McMillan Thoele

TAMU

 

Ian Ibbotson

Developer Lead - K-Int

x

Jana Freytag

VZG, Göttingen

 

Khalilah Gambrell

EBSCO

 

Kirstin Kemner-Heek  

VZG, Göttingen

 

Kristin Martin

Chicago

x

Laura Daniels

Cornell

x

Lloyd Chittenden

Marmot Library Network

x

Martina Schildt

VZG, Göttingen

x

Martina Tumulla

hbz, Cologne

x

Maura Byrne

Chicago

 

Mike Gorrell

Index Data

x

Owen Stephens

Product Owner -  Owen Stephens Consulting

 

Patty Wanninger

EBSCO

Action items