Date
...
Issue was raised as to how to have FOLIO handle the situation where a recalled item is not returned when it should be – need a way to prevent the recall from getting 'stuck' and never be fulfilled if the item that is recalled never gets returned. Proposal was that there be an automated way in which if the recalled item is not returned by its recall due date, then the item with the next earliest due date has a recall placed on it. It was recommended that having this be an automatic feature or not should be customizable in the settings, as some institutions may prefer to re-order things manually.
...
It was previously determined not to have a 'recall status' because this should wait until the tripartite item status system is implemented (see Updates from item status group and Item State in FOLIO. Development of the three-part item state is not currently being doneunderway, but sentiment was expressed that developing it should be made a high priority. A three-part item state would make handling title-level requests/recalls easier.
...
Functional Area | Product Owner | Planned Release (if known) | Decision Reached | Reasoning | Link to supporting materials | Comments |
|---|---|---|---|---|---|---|
| e.g. loans, fees/fines | Name | e.g. Q4 2018, Q1 2019 | Clearly stated decision |
| e.g. mock-up, JIRA issue | |