FOLIO Project Update – Week of June 11, 2018

The FOLIO Product Council is creating a gap analysis/feature prioritization document will be sent soon to the FOLIO Early Implementers institutions for completion by June 25th. This will help form a consensus of which features are needed by these institutions in order to implement FOLIO. All FOLIO institutions will be asked to rank 60 Epics by June 25th so as to be able to identify needs and deploy resources effectively. The SysOps SIG presented their development priorities needed for successful migrations to the Product Council. This was informational for the PC and outside of the prioritization exercises above. The Community Outreach SIG shared a budget proposal they are taking to the Open Library Foundation Board for funding.

The Consortia SIG modified their plan to form a single-tenant/shared model subgroup after receiving further insight on the current thinking about consortia implementations. Instead, they are forming a Consortia Implementation Models subgroup that will define various ways in which a consortium might implement FOLIO.

The Metadata Management SIG considered responses to the working definition of Inventory, particularly in light of possible overlap with ERM. Future discussions of this will need to include members of other SIGs and their respective Product Owners (POs).

The Reporting SIG still does not have a Reporting Product Owner assigned. An overview of work will be created with other PO’s to document in app report requirements as JIRA tickets. More discussion on in app reports and data warehouse development is scheduled for their 6/18/18 meeting.

The Sys Ops & Mgt SIG has rescheduled its meeting time and day to Friday’s at 10 AM (Eastern time). They prioritized and discussed the Action Items.