Description

This epic is a starting point for the addition and expansion of a new item field called Process, the creation of custom item status, and the modification of circulation rules. Because a lot of these parts need to be completed at the same time or close to each other this Epic is in place to give an overarching idea of how the pieces fit together and the respective timelines.

Background

The 3-part item status was conceived as a way for library staff to mark what library processes an item may have to undergo. The 3 parts consisted of customizable Item status, Process, and Needed For. Process and Needed for would be used to indicate what workflows an item would need to enter and the steps within that workflow. Item status would be used to communicate this to the patron but also limit if an item could be requested or circulation. Since there was not enough time to complete this work a thin thread solution was created where item statuses and their logic were hard-coded into the backend. This Epic will split out and rework parts 2 and 3 of the 3-part item status into a single new Process field.

The purpose of the Epics linked issues is to complete the work originally conserved as well as refine it to meet the current FOLIO architecture and needs of library staff.

Considerations

• Where possible the lines between apps should be maintained.

• Process data will belong to and be contained within the Inventory app.

• Item status data will belong to and be contained within the inventory app.

• Hardcode rules in circulation will be replaced with entries in the Circulation Rules where possible.

• All aspects of this work need to take into consideration an ECS environment.

Phase 1

Phase 2

Phase 3

Resources

Historical documents

Questions