Date
Housekeeping
- Next topics
- Permissions
- field based → walk through where needed?
- SIG reps and PO
- example: specific perms to edit the barcode field
- view and edit vs. only view e.g. source record (quickmarc) - there seems to be a JIRA
- would be UI-based permissions
- Brooks: better-focused on managed customized UIs?
- Owen: would be good to undertsand the use cases
- searching in FOLIO
- ERM SIG started to collect areas of improvement - of Interest for all apps? - consistency when filtering ...
- save searches/filters and apply them in one click
- look-up for users: add filter for tags
- in Organizations: keep search/filter after editing a record
- users applies filters and has 5 results that all need to be edited
- when one record is edited, the search/filter is deleted and the user needs t start searching/filtering again
- ACQ units in ERM
- Permissions
Discussion items
- 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
- SUBMITTED
- pain points related to record interactions
- when migrating
- moving items, holdings
- right use cases and right library person needs to be there
- SUBMITTED
- 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
Attendees
Present | Name | Home Organization |
---|---|---|
Ann-Marie Breaux | EBSCO | |
Brooks Travis | EBSCO | |
Charlotte Whitt | Index Data | |
Dennis Bridges | EBSCO | |
Dung-Lan Chen | Skidmore College | |
Gill Osguthorpe | UX/UI Designer - K-Int | |
Heather McMillan Thoele | TAMU | |
Ian Ibbotson | Developer Lead - K-Int | |
Jana Freytag | VZG, Göttingen | |
Khalilah Gambrell | EBSCO | |
Kirstin Kemner-Heek | VZG, Göttingen | |
Kristin Martin | Chicago | |
Laura Daniels | Cornell | |
Lloyd Chittenden | Marmot Library Network | |
Martina Schildt | VZG, Göttingen | |
Martina Tumulla | hbz, Cologne | |
Maura Byrne | Chicago | |
Mike Gorrell | Index Data | |
Owen Stephens | Product Owner - Owen Stephens Consulting | |
Patty Wanninger | EBSCO |