2017-06-23 Meeting notes
Date
Attendees
- Former user (Deleted)
- Michael Winkler
- Kristen Delwo
- Peter McCracken
- Kristen Wilson
- Leah Elzinga
- Ann Crowley
- Marc Johnson
- Charlotte Whitt
- Kathryn Harnish
- Steven Brown
- Scott Vieira
- Bill Verner
- Maria Grzeschniok
- Chad Smith
- Bethany Greene (Deactivated)
- VBar
- Cate Boerema (Deactivated)
- Former user (Deleted)
- Peter Murray
Goals
Discussion items
Item | Who | Notes |
---|---|---|
Minute Taker | Virginia Martin |
|
Introduction of Stacks Team and Background
| 1. Background and history i. Kristen Delwo – Co-Founder & CEO of Stacks ii. Chad Smith – Co-Founder & CTO of Stacks iii. Kevin Horek – Chief Design Officer iv. Leah Elzinga – Project Manager & Analyst v. Additional team members will be introduced as they join on 2. Background and history i. Kristen and Chad developed and implemented an integrated and automated acquisitions tool for a large consortium, supporting hundreds of selectors – they have previous experience in this area. ii. Why is Stacks interested in FOLIO? Stacks has a lot of experience reverse-engineering ILSs that don’t meet libraries’ needs. They’d like to see an ILS that doesn’t require reverse engineering. iii. FOLIO Acquisitions (FOLIO ACQ v.1)
| |
Prototype Demo:
| Stacks Team |
|
Timeline and plans for future development work | All |
i. For Stacks: figure out how to manage working with the group (?) ii. For RM SIG: Get examples of reports frequently run – fiscal management and just general acquisitions stuff iii. For RM SIG: Think about where we need triggers for alerts, notifications, etc. (e.g. fund not matching when a fund doesn’t exist; throwing out errors when batch loads are added) iv. For RM SIG: play around with prototype and come back with questions, comments next week 2. Next week: continue to work through prototype |
Action items
- Identify examples of reports run at your institution in support of acquisitions work
- Think about where/when the system needs to trigger alerts, notifications, etc.
- Play around with the prototype and bring feedback to next meeting on Friday, June 30