Date
...
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 | |||||||||
| Requests | TBD | If you mark an item declared lost, claimed returned, missing, withdrawn and there are open requests on the item:
| JIRA feature has been created:
| |||||||||||
| Requests | Delivery requests side bar convo:
|
Notes
Holly Mistlebauer -
- Fine/Fees Refund Button - Discussion on whether or not to remove the "Refund" button on the Fines/Fees history page. Should the "Refund" button be treated the same as the "Error" button which is used selectively and only available in ellipses. Holly asked how many libraries do refunds on a regular basis. Some libraries do give refunds on a regular basis. Question asked if access to do refunds can be set in permissions to allow designated staff to handle refunds.
- Manual Charges for Fines/Fees - Discussed need to identify manual charge fee/fine type for actual cost for developers and the need to add "Default" for Fee/Fine types using default notice(s). Through lengthy discussion it was determined that Holly will develop a demo to show at the next meeting to show how the table works.
- Refunding fees/fines impact on Fee/Fine Details - Discussed refunding for two types of transactions, refund to the patron and a Bursar refund. Suggestion made to change wording of "refund" to "credit" to show amount credited to the patron or to Bursar. Concerns expressed on how the credit will show on the patrons account in the end. Holly will update for the MVP version and present changes at the next meeting.
Cate Boerema -
...
Reminder for everyone to look at Holly's video on using manual fee/fine charge table.
Holly Mistlebauer—Refunding fees/fines process
--Holly walked the group through a slide deck explaining how the refunding process will function for Round II implementers (Summer 2020), Round III (December 2020), and where we’d like it to be for Round IV implementers (Summer 2021) (Refunding fees/fines process)
--Holly will take the basic process forward to the Round II implementers to ask if this will meet their initial needs.
--Holly/Andrea are calling for volunteers for a sub-group for to determine needs related to the refunding process and institutional accounting going forward to Round IV. People may contact Holly or Andrea to sign up to be on this subgroup. Meetings on this sub-group most likely won’t start right away.
Cate Boerema—Request handling when item is marked declared lost, withdrawn, or missing
--Deck for discussion: https://docs.google.com/presentation/d/1T6D4W3tfswLnyrd61LWPHNcOFVL82-T5JA8CZBssPwk/edit?usp=sharing
--When marking an item declared lost, claimed returned, missing, withdrawn, but there are open requests on the item, the group suggested a pop-up that prompts staff for further action related to the request. Possibly with a link to the request (not MVP) so that the request could be canceled or moved to another item. Additionally, the in-app requests report would be another way to catch any requests on lost, claimed returned, missing or withdrawn items.
--When items are checked in with active delivery requests on them, FOLIO checks the item out to the requester to fulfill the delivery request, then the item is mailed out to the requester. A few group members were concerned that the item was checked out to the requester but may then need to be sent to the location that will mail it out for delivery. In transit is not used with delivery requests currently because there are no service points associated with delivery requests. This topic was flagged for future discussion by the RA SIG group.
Holly Mistlebauer—Discuss RA related MVP slippage PO MVP Feature Status
--Tabled until Monday