Versions Compared

Old Version 2

changes.mady.by.user Jennifer Eustis

Saved on

compared with

New Version 3

changes.mady.by.user Jennifer Eustis

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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.

...