2018-03-16 Meeting notes
Date
Attendees
- Sebastian Hammer
- Kristen Wilson
- Tim Whisenant
- Charlotte Whitt
- Bethany Greene (Deactivated)
- Ann Crowley
- Ann-Marie Breaux (Deactivated)
- Nicole Trujillo
- Dennis Bridges
- Peter McCracken
- Kristin Kemner-Heek
Discussion items
Item | Who | Notes |
---|---|---|
Minute taker? | Bethany Greene (Deactivated) | |
Announcements/updates | Product Council is having a conversation about gap analysis, looking at functionality required for V1 and how much time it’s going to take to get it. July deadline for beta version isn’t going to happen at current level of resources. PC is re-prioritizing and changing deadline to September. The plan is to have a series of beta releases rather than just the one. | |
Acquisitions <> Inventory The following is a brief summary of the conclusions drawn in our Acquisitions <> Inventory discussion. Please comment on any discrepancies.
The details of this integration will remain in the following working document until we are ready to begin implementation. https://docs.google.com/spreadsheets/d/1gmRHCDhcdPgzsT1-CSrGDW0Jekpw2iuSV7FWa-izq5I/edit#gid=1798336802 | Dennis Bridges/Acquisitions Small group/all | Small group got together to look at Acq and Inventory inter-relationships, especially surrounding item status Discussion about how order status will interact with Inventory; short term for V1, any order will have corresponding instance in inventory (whether physical or electronic or both); all physical items will have corresponding item record in Inventory, for electronic items you have the ability to create item record in Inventory (in addition to holding record). Are there situations where it would be valuable to have item record for electronic resources? An order has to be associated with some "thing" that exists in Inventory. Right now, electronic resources data model in Inventory Can we have a configuration where we can block updates to KB records in holdings/Inventory so you don't have to worry about them being deleted and lose associated information? The strength of the Inventory app is that it has an internal format; if you don't want to store MARC records you can use another format. The group needs to think about when we need to pull KB data into Inventory and when we need to rely on it as an external service. Does eHoldings have to be its own app or can e-resources live in Inventory? Or at least look like they live there for FOLIO staff user? Inventory wasn't intended to represent just physical material. Circling back to the initial discussion: For the short-term, we don't have a mechanism to represent a package with relation to Acquisitions, but that is something the ERM subgroup is going to work on. This is fine at the title-level but package-level will need to be revisited. The Acquisitions small group is going to have a discussion at their next meeting about item status and interaction between other apps. |