FOLIO Project Update – Week of July 15, 2019
Project Updates / 22 Jul 2019
Accessibility concerns, feature requests, use case reviews and security testing in this week’s project report.
The FOLIO Product Council approved a strategy statement resulting from discussions at the Face-to-Face meetings in DC. This document will be used to help guide the work of the PC over the coming year. PC discussed how to communicate the statement and related work and timelines with the stakeholders during their July 23rd – 24th meetings, and reviewed a presentation that Harry Kaplanian will make to the stakeholders.
The FOLIO Technical Council met and discussed the status, expectations, and next steps for any of the items on the list. TC also discussed an ongoing process for tracking and reporting Tech Debt, which will include cadence for review and update, as well as the channels to get recommendations reviewed and acted upon. This discussion will continue at the TC’s next meeting on July 31st, 2019.
The FOLIO Implementation Group conducted a Round Robin on local planning and reviewed the “Planning” section on the implementers toolkit brainstorming board, adding types of planning that need to happen with an implementation. IG also discussed having a vision statement for an institution’s implementation.
Debbie Hamrick, Khalilah Gambrell, and John Coburn met with Mike Williamson, an accessibility expert from CU-Boulder, to discuss accessibility concerns from the perspective of FOLIO UI module developers and the Accessibility SIG .This discussion included a review of FOLIO’s Accessibility documentation for POs and will feed further documentation efforts focused on general accessibility for web-based projects, as well as recipes for accomplishing those with FOLIO’s front-end framework, “Stripes.” Khalilah has created a resource for product owners, Product Owner Accessibility Testing & Requirements.
The Consortia SIG continued its review of Cross-tenant Unmediated requesting stories, focusing on the staff perspective at the owning library. There are a number of conditional “edge cases” in the requesting workflows. The SIG will also be reviewing what has been worked out in the single-tenant Requests feature in order to try to solve some of these scenarios in a similar manner. The SIG encourages continued entries to the Consortia Profiles page.
The Metadata Management SIG had a conversation around continuing to clarify the scope of Inventory. The SIG outlined use cases for several outstanding data elements, with an eye for what was critical (e.g., ability to see the data) vs. what could be implemented at a later date (e.g. linking functionality).
The Reporting SIG reviewed LDP (Library Data Platform) feature requests and ranked their priority by institution for capacity planning. The Reporting Data Privacy Group has identified reports that use personal information, which will be updated with a “personal info” label in JIRA. The Report Prototype Working Group is evaluating options for test datasets for the LDP from various institutions.
Mike Gorrell spoke to the Resource Access SIG about the short and long term plans for the workflow engine. A sub-group to develop related user stories and use cases is being formed. There was also discussion around the timing of anonymization of closed loans (at point of check-in or session based), and a review/re-ranking of outstanding request issues. The SIG also explored finding a thin thread for handling item states.
The Sys Ops & Mgt SIG had a discussion about deployment security items in a small group. Jo Drexl put a Debian package of Okapi to GitLab (a local GitHub solution), which Chris Creswell and Florian Ruckelshausen will test. Wayne Schneider will create JIRA tickets about Okapi security.
Integrations prerequisites will need to be addressed now in order to influence development priorities. The group has compiled a comprehensive spreadsheet about institutional integrations, including listing related JIRA tickets. There is also a wiki space under the SysOps wiki page which lists required integrations. SysOps SIG will pass on this work to the Implementations Group. Implementing Institutions will be asked to identify gaps.