Page Comparison

Concern about only allowing orders with EBSCO, which is not what we meant for FOLIO. EBSCO may be one of the first vendors to integrate, but encourage other vendors to integrate as well. So what does it mean to become an integrated vendor?

Is there a FOLIO-compliant vendor for vendors to follow requirements to become integrated?

• opportunity to design APIs to get away from old-fashioned file transfer
• What is motivation for vendors to become "FOLIO-compliant"?
• How can we support vendors with different levels of technical sophistication?: Large vendors interested in API connections, but can small vendors manage this?
• Can APIs be made a NISO standard? This would be a longer-term issue.
• Still deciding who the appropriate team is for developing the APIs
• Even if we don't do the APIs initially, our current work will lay the groundwork for more sophisticated coding
  • e.g., we begin with MARC 9xx and EDI, and move toward APIs
• Get the API open-source. Then vendors can grab it, and it can be used both with FOLIO and outside of FOLIO, to make it more of a  standard.

Workflow Demo conversation and Comments

• • • See Discuss Post: https://discuss.folio.org/t/zap-workflows-ux-iteration-3-english/1041

Stacks Work Package Acquisitions workflow

• Version two is here: https://docs.google.com/document/d/1TvAAf4TOhF5TIEVRQye8ngOoC5ftQQKaGcmEihKaEMg/edit
• Check-in with group: how's the process going? Do we feel like this is getting us where we want in the timeframe needed?
• list of the workflows, timeframe and scope that will be covered during development / SIG Meetings (Discussion outcome from last week)