Date
...
- Michael Winkler
- Nicole Trujillo
- Ian Ibbotson (Use this one)
- Owen Stephens
- Eric Hartnett
- Martina Tumulla
- Tim Whisenant
- Peter McCracken
- Bethany Greene (Deactivated)
- Kirstin Kemner-Heek
- Peter McCracken
- Marc Johnson
- Michael Arthur
- Kelsey Brett
- Ann-Marie Breaux (Deactivated)
- Charlotte Whitt
- John Ballestro
Discussion items
| Item | Who | Notes |
|---|---|---|
| Minute Taker? | Eric Hartnett | |
| Announcements/Items from PC | The recurring RM SIG appointment ends today. Everyone needs to add an appointment to their own calendars from this point forward. WOLF-Con is still being scheduled - maybe have it scheduled by next week. If you're attending ER&L and are interested in having dinner, sign up here: | |
E-holdings subgroup update: -- Please look at creation of high-level requirements document. This contains requirements for e-holdings integration with other areas of FOLIO, in particular ERM. What other requirements/integrations do does the group have to add? What other questions exist? --- We want RM SIG members to review this document and provide any additional requirements/comments/questions | Kristen Wilson/All | Have been doing user-testing of the app. Scope of Frontside's work is to be the open source app and ends with EBSCO integration. Integration work with other vendors will need to be done. Order integration - at point of placing order or paid for? Once access is confirmed. Integration with Ex Libris/Serials Solutions - Michael Winkler will follow-up with ProQuest. See what work needs to be done before approaching others. Who will do the work of integrating others. Creating a holdings record - Does this create duplicate work? Where do the linkages occur? Tied to some questions with the ERM app. View order info in eHoldings - Pull all together, Ex. current order, backfile purchase, from other publisher, etc. How would you want to represent history? What should be stored in eHoldings, what in Inventory? Need to be able to track access when moving from one publisher to another. Are aggregators and subscribed packages handled different? Keeping track of ebooks that are required reading (course reserves) - what happens when a title is removed from a package? Update holding based on order status - Need to retain order history even when an order is closed. Could be part of workflow app. Again, is this duplicate work - need to avoid over-tracking. Being able to see when a subscribed title is in aggregators would be helpful for cancellation decisions. Search KB, click button to generate an order for holding or package. Needs to work with renewals. View print/electronic orders via codex - Use codex as starting point as opposed to having eHoldings as a starting point. Are analytical tools, e.g. cost per use, a separate thing from eHoldings/ERM? Can create the integration now but would probably be separate. Discussion for ERM group? Public display of holdings - to help avoid duplication of work. Need to be able to crosswalk data. GoKB is the local source of truth (a library's local holdings). GoKB plus something gives you the source. Would you have an eholdings app for each provider or would they all be in the one app? You could have instances, one for each provider. This isn't fleshed out yet. Need API for eholdings so all apps can be connected to it. |
ERM Subgroup: ERM project setup is nearly finished Questions for group: 1. How will ERM/e-holdings work together to create a comprehensive ERM solution, both back-end management and access? How will the different development teams share the work? 2. What changes to the eHoldings app from Frontside might be needed to support the needed ERM features that the GBV will be working on (such as multi KB support and specific requirements for GOKb, which does not support local holdings within the knowledgebase)? 3. How will ERM align with work done with Inventory that right now is really focused on the monograph model? 4. How can we make sure the ERM and eholdings model can be sustainable for both migration and populating the data and for ongoing management? People are encouraged to bring their own questions to. Discussions will help inform the agenda of the in-person meeting. | Owen Stephens is the product owner. Agenda for meeting: What are the overlap points between ERM/eholdings? Come out of the meeting with answers. Full agenda is in the Google drive folder. ERM subgroup will be driven by backlog of priorities (maintained in JIRA). Does this accurately represent the spreadsheet the RM SIG worked on? Two sides - spreadsheet is the functionality, JIRA is the technical side. Goal is to provide more detail as to the scope of the work to be done. | |
| Fiscal year roll-over walk-through | Dennis Bridges | Will get to next week. |
Action items
Hi there,
OLE2 OLE2 is inviting you to a scheduled Zoom meeting.
...