Date
...
Andy said that implementation of FOLIO at Cornell on July 1 has generally gone well. On the performance side there were some issues with slow response times for check-in/out and requests. EBSCO was able to help with these issues on a case-by-case basis and resolved them fairly quickly after their being reported. Problems may have been due to local setup conditions. Slow check-ins when there were a lot of items was more of a browser problem than a FOLIO problem, and ending sessions more frequently fixed this.
...
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.
Darcy raised the issue of whether there needs to be an easier way to see what items have overdue recalls/requests on them, so library staff can check if they need to manually re-order the queue. Currently Request Search does not show due dates, Requests Results List does not have a column for due date. Request Detail does show due date, but due date not currently facet-able. It was suggested using either tags or item status to allow search for overdue recalls.
...
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 | |