| Requests | | TBD | If you mark an item declared lost, claimed returned, missing, withdrawn and there are open requests on the item: - There should be a popup letting you know
- There should be a link to the requests app (pre-filtered to show the relevant request(s))
- You can then move the request to another item or cancel it
- 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
|
|
|
|