2017-06-23 Meeting notes

Introduction of Stacks Team and Background

• Individual members, role in development
• Background and history

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)

•  Want to make sure they honor the work done to date
• Kevin will be leading a group engaging with functional prototypes with support from Leah

Prototype Demo:

• 1st time/one time purchase (monograph)
• renewal (serial)

1. Prototype at: http://FOLIO.StacksDiscovery.com (this prototype will keep being added to throughout development)
   1. Want to make sure this is being built for future scalability – especially responsive design for mobile and tablet environments.
2. We should look at the prototype with an overarching approach rather than a detailed one right now – do we like how it flows? This is very preliminary and not open source code at this time.
3. Areas for RM SIG to provide feedback on:
   1. Verbiage selected for filters – correct terminology, everything covered?
   2. Labels for high level view of orders – what should display?
   3. How should we sort / manage / organize lists of orders in the interface?
   4. V.1 will likely not have totally customizable workflows – we will need to decide which statuses, workflow levels are appropriate
4. Feedback from RM SIG during call:
   1. Make order view available in a compressed list view / in a table
   2. Must put title information on order record results list view
   3. Need to be able to have orders for 1 item/title as well as for multiple item/titles
   4. Suggestion – be able to view order lines to see multiple titles on a “batch” orders
   5. Ways to get orders into system: vendor APIs, batch loads from vendor or local batch loads, manual creation
   6. Primary agents / jobbers to work with on integration with Acquisitions part of FOLIO
      1. Monographs
         1. YBP
         2. Amazon
         3. Coutts (ProQuest)
         4. Harrassowitz
         5. Amalivre
         6. Casalini Libri
      2. Serials
         1. EBSCO
         2. Harrassowitz
         3. WT Cox
   7. Preferred method of batch loading records would be for them to be automatically added into FOLIO when the order is placed in the vendor system (as opposed to some sort of manual retrieval and uploading of batch files)
   8. Need the order statuses to be locally configurable – names and location in workflow / how many statuses required
   9. Licensing is a separate, but related, workflow for e-resources
   10. We discussed the importance of:
       1. Automation for high volume of orders and invoices
       2. Workflow configurability at the local level
       3. Fitting this all into a new data model that will be used across FOLIO, Especially for linking up electronic resources with larger aggregates, the orders, bib records

1. Homework:

  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