...
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
- gaps = functionality that is missing vs. functionality that is not working well
Status colour Green title submitted 
how many sessions (50 min. each) - multiple- list of workflows
- orders, receiving, cataloguing (different from library to library whether cataloguing is part of that)
- request, pre-acquisition in Inventory (searching), ordering
- acquisition of e-package (journals, ebooks), check in Inventory for print version, then ordering in orders (maybe as a package), renewing that, invoices, inventory (to create item)
- would be good to have tangible action items as an outcome
- Laura: I like the idea of starting with a request then proceeding through ordering, receiving, paying, cataloging, and circulating would be great -- that might take more than 50 minutes?
- rather face2face or hybrid - hybrid option would be good
- pre-recorded presentations may be helpful - have then a hybrid discussion
- if we need more time, we could wathch pre-recorded presentation in advance
- Laura in chat: would it be acceptable to make it hybrid but not account for the time difference (so that participants in the US would just have to get up early or stay up late)?
- jana in chat: With something like this we had a lot of trouble at work in Germany. Maybe we can schedule these hybrid sessions accordingly?
- knowledge sharing will work well when hybrid
- intended audience:
- pain
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) with focus on pain points related to record interactions
- when migrating
- moving items, holdings
- right use cases and right library person needs to be there
Status colour Green title submitted - how many sessions (50 min. each)
- rather face2face or hybrid → face2face
- 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.
- talking through use cases - see above
- 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
- not sure about the outcome; hard to have a useful discussion; different expectations
- on the other hand good opportunity, because it is easier to discuss in person
- Martina will ask for a separate open slot
...