Product Council Reviews

• New FOLIO Apps

• New functionality that requires new back-end modules and makes significant changes to existing front-end user interface

Examples of new functionality recently reviewed by the PC

• LIsts App: originally this app was not part of FOLIO, but was proposed to fill a gap in functionality. The Lists App went through the full review process with the PC, and the modules that composed it were reviewed by the Technical Council. BELA (Bulk Edit and Lists App) continues as a subgroup under the Application Interaction SIG, and continues List App development.

• New Serials App that was part of the Quesnelia flower release. Before that release, the Product Owners worked with the Acquisitions to share development progress and garner feedback, then presented this new App’s features and how it interacted with other Apps.

• New backend modules and front end UI work, the mod-marc-migrations (This backend module supports more seamless updates of bib and authority records to reflect mapping rules change) and mod-record-specifications (aka Mr Specs) (This backend module supports tenant level MARC validation rules configuration. A library will be able to define MARC validation rules MARC bib and MARC authority records with this module. An error will either warn a cataloger or prevent the quickMARC from being saved). These were presented to the PC for review for the Ramsons flower release.

Examples of new functionality recently NOT reviewed by the PC

• Changes to property field names (both back and front end). For example, In Marc Source Record Storage, the inventoryHRID was renamed to externalHolderIDsInstanceHRID. This change was to accommodate other types of external identifiers for MARC holdings records and MARC authorities. This change can be seen in the API and in 3rd party systems such as LDP. This was a back end change to existing code.

• Updates to current functionality. For example, advanced search which was introduced in the Poppy flower release. This is new functionality built on existing code.

• New functionality to existing Apps. For example, the bindery functionality adds new features to the Receiving and Inventory App. This is new functionality built on existing code.

• New edge module for the API for ERM functionality. No UI features or functionality in FOLIO were impacted by the module, so the PC decided that the Technical Council modules review of edge-erm was sufficient.

What Should Not be Reviewed

• Any retroactive assessment of existing modules.

• Review of new code to be placed within existing modules. The Councils are always interested to learn about new functionality under development, especially as it relates to the roadmap or other planning, but changes to existing modules should follow existing processes and do not require a special review process. Product Owners with responsibilities for existing modules and areas of functionality should work through the respective SIG(s) as enhancements and updates are made.

• A review of code which will not be distributed as part of the FOLIO LSP under the FOLIO project and where the intellectual property rights will not be turned over to the OLF. As an open-source project, the FOLIO code is available for anyone to use, enhance, or modify outside of this process.

• A blueprint for long-term vision for FOLIO. This process has been designed to support the inclusion of new functionality and features under the current release framework.

When to Submit a Review

The Product Council aspires to review new functionality in its earlier stages of development. As a collaborator, the Product Council wants to understand how new functionality fits into FOLIO as a whole, consider ways to best integrate new functionality into the software, communicate it within the large FOLIO community, and ensure all stakeholders are aware of upcoming new functionality that will be developed. We recognize all new development is desired by at least one institution, and part of the goal of the review is to see how we can make it work even better for the broader community.

What is the role of the Product Council

The role of the Product Council is to:

• Support SIGs in understanding new functionality and its implications for FOLIO as a whole

• Collaborate with SIGs, POs, and other stakeholders on new functionality early on in the process

• Provide guidance and gather ideas on ways to best integrate the new functionality into FOLIO as a whole

• Envision how the new functionality fits into FOLIO as an international product

• Play a role in the decisions about what is included in the “Flower release” of FOLIO. This role doesn’t dictate what can or cannot be developed. This roles also doesn’t dictate what can or cannot be included in a FOLIO release supported by any particular service provider.

General Guidelines

Use your best judgement as to whether to seek review from the Product Council. In general, if you are seeking TC review, then also seek PC review. If you feel the functionality impacts current apps and functionality and has downstream impacts to front and/or back functionality, then submit a PCR. We also encourage you to reach out to the PC with questions.