Date
Attendees
Discussion tems
| Time | Item | Who | Description | Goals |
|---|---|---|---|---|
| 5min | Housekeeping |
| Call number review document | |
| 55min | Confirmation of request behavior by type | Cate Boerema (Deactivated) | Review documents: -https://docs.google.com/document/d/1lmr5UuXtYyH8vW-uXTwWA5rH7IDBbtW_IH69xhwHUh4/edit# - https://docs.google.com/spreadsheets/d/1jaID-HGft3q4YzJq6Ycy2ejWByAIvou3Zyyw4ko87YI/edit#gid=0 | - Confirm understanding of various types of requests and what statuses they should be allowed on (this is just needed until we have the ability to configure the request to status mappings - UXPROD-1320) - I'd like to confirm that paging requests should only apply to items that are Available AND that we should prevent paging requests on items that already have a paging request (I think this would be simplifying) - I'd like to discuss what should happen if you try to place a disallowed request - Wireframes: https://drive.google.com/drive/folders/1qMLWk7RThsy9xUDYQpTHMrw95E-qydYz |
Meeting Outcomes
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 | |
Notes
The Spring FOLIO meeting will be held at EBSCO headquarters in Ipswich, MA and will primarily be a developers meeting. Attendance is limited to around 100 people. Unless we have a need to have an RA representative to discuss high-priority issues in person with developers, we can probably forego the meeting and discuss issues with other SIGs, such as User Management, through usual channels. Deb suggested that we meet with UM members on the topic of permission sets. Andrea will ask Maura to share the presentation she prepared for UM on this topic with us.
We spent the rest of the meeting reviewing Cate’s Request Type/Item Status matrix, which will be used to hard-code the types of requests that may be placed on materials with the given item statuses. The request types included in the discussion were: Hold, Recall, Page (Rush Recall put on hold for now). Some issues that arose include:
- There are other common items statuses that will have to be included in the matrix (such as Lost/Billed, Claims returned)
- Request types “Delivery” and “Remote Storage Request” need to be included
- In Transit will probably have to be further broken out into ‘In Transit for Hold’ and ‘In Transit for Shelving’; allowable request types will differ
- Is “Recall” an allowable request type for items In Transit? Yes, if the item is in transit for hold, but not for in transit for shelving. If only request type Hold is permitted, the borrower for whom the item is in transit will be given a standard loan instead of a shortened loan upon checkout. The system will have to check for the existence of requests upon checkout.
- Page requests should update the item status from “available” to something else (terminology needs to be resolved)
- When a Hold request is placed on an item that is checked out, even though it won’t shorten the due date, the borrower should be notified of the existence of another request
- In the situation where more than one Hold exists on an item, we need to be able to configure how long the first borrower will get (= alternative loan period for Hold)
- If allowable request types are hard-coded against item statuses, we need to be able to override through the loan rules (that account for patron group, location, material type)
- If a request type is not allowed in a given situation, a modal will be displayed; but it’s preferable that the operator be allowed to choose a different request type without having to start the request process from the beginning. Ideally, the system should first check the loan rule to determine which request types are permitted for a given patron/material/location, and only present those request choices.
Next meeting: discussion about call number displays on functional screens. Andrea has started a Google doc to get us thinking (see link above).