Skip to end of banner
Go to start of banner

2020-04-27 Resource Access Meeting Notes

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Date

Attendees


Discussion Items

TimeItemWhoDescriptionGoals/Info
2minAdministrivia Andrea Loigman
20minfines/feesHolly MistlebauerRefunding fees/fines process

Understanding of how the amounts should be handled for round 2 implementers.

Create sub-group for accounting going forward.

20minRequestsCate Boerema (Deactivated)Request handling when item is marked Declared lost, Withdrawn or Missing
- What should happen when an item that has one or more open requests on it is Declared lost, Withdrawn or Missing?
- Current behavior is that the Request status becomes "Open - Not yet filled"
- But what then happens to those requests? How does the staff know to cancel them or move them?
- Deck for discussion: https://docs.google.com/presentation/d/1T6D4W3tfswLnyrd61LWPHNcOFVL82-T5JA8CZBssPwk/edit?usp=sharing
- Goal is to answer questions in deck
20minMVPHolly MistlebauerDiscuss RA related MVP slippage

  PO MVP Feature Status


Meeting Outcomes

Functional Area

Product Owner

Planned Release (if known)

Decision Reached

Reasoning

Link to supporting materials

Comments

e.g. loans, fees/finesNamee.g. Q4 2018, Q1 2019Clearly stated decision
  • Because...
  • Because...
e.g. mock-up, JIRA issue
RequestsTBD

If you mark an item declared lost, claimed returned, missing, withdrawn and there are open requests on the item:

  1. There should be a popup letting you know
  2. There should be a link to the requests app (pre-filtered to show the relevant request(s))
  3. You can then move the request to another item or cancel it
  4. You can also use the requests csv report periodically to check for items with status declared lost, missing etc with open requests to catch any that might have been missed in this process



Requests

Delivery requests side bar convo:

  • Delivery requests have no service points (they have requester addresses)
  • When you check in a delivery request at any service point:
    • The system prompts you to check the item out to the requester
    • If you decline to do that, the request will stay in "Open - Awaiting delivery"
  • There is no notion of In transit for a delivery request
  • There is no notion of a delivery request fulfillment service point -
  • It sounds like folks would like to have the request status In transit until it gets to a fulfilling service point and, only when it gets there, to have the check in trigger check out to the requester
  • This would likely require flagging service points that can do delivery and some way of knowing which items should go to which delivery service points for fulfillment?
  • Cate will put this topic on the RA SIG agenda document for future discussion



Notes 

Holly Mistlebauer - 

  1. 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.  
  2. 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.
  3.  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 - 

  1. Request handling when item is marked Declared lost, Withdrawn or Missing - Discussed impact of these statuses on requests. Cate listed a set of questions that she would like the group to answer.  Andrea asked everyone to review set of questions and be ready to discuss at the next meeting.  
  • No labels