...
Context
In the (single tenant) FOLIO Requests app, the user can perform one of the actions available in the Actions menu: Cancel, Edit, Duplicate, Move, Reorder. We need to decide on the expected behavior for those actions for the ECS TLR Requests. Additionally, action menu priority:
Cancel
Edit
Reorder
Move (not available in Ramsons)
Duplicate (not available in Ramsons)
Logically, we have the following entities - actually, ECS TLR, primary circulation request, and secondary circulation request. At the same time, ECS TLR is an internal entity of the application, and there are no UI forms for it to be displayed to users. Users can only see and work with primary and secondary circulation requests.
| Drawio | ||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Circulation Request status and Circulation request type | Open - Not yet filled | Open - In transit | Open - Awaiting pickup | Open - Awaiting delivery |
|---|---|---|---|---|
Primary Circulation Request (Borrowing Tenant) |
|
|
|
|
Secondary Circulation Request (Lending Tenant) |
|
|
|
|
Challenge: At the current stage of the ECS TLR implementation, do we need the ability to close only the secondary request, leaving the ability to continue the search, or do we focus on canceling both requests at once?
...
The current DCB implementation assumes that related requests are canceled all at once (2 or 3). It is worth noting, however, that FOLIO mod-dcb does not know what OpenRS does on their side while canceling, so FOLIO mod-dcb simply performs a status update when receiving a message from OpenRS.
...
During the meeting, it was decided that cancellation of the Secondary Circulation Request for ECS TLR from the Lending tenant will not be available, see
Jira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIREQ-1090
...
Fields that can be changed when editing and Circulation request type | Expiration date | Fulfillment preference (Hold shelf / Delivery) | Pickup location |
|---|---|---|---|
Primary Circulation Request (Borrowing Tenant) |
|
|
|
Secondary Circulation Request (Lending Tenant) |
|
|
|
DCB / Open ReShare does not provide the ability to set or change the parameters mentioned (there are no fields for this in the Edge DCB FOLIO API - https://s3.amazonaws.com/foliodocs/api/edge-dcb/s/edge-dcb.html# tag/circulation). Additionally, these parameters are not set when creating requests from mod-dcb https://github.com/folio-org/mod-dcb/blob/master/src/main/java/org/folio/dcb/service/impl/RequestServiceImpl.java#L52
...
Reordering on the part of the Primary Circulation request is allowed; the changes should be synchronized to the Secondary Circulation request.
Reordering on the part of the Secondary Circulation request is not available (the same as for Cancel and Edit actions).
Duplicate
*Not available in Ramsons
Action scope:
Item level requests: You can duplicate open requests but you will need to change either the requester or the item to save the request, as there cannot be two requests on the same item by the same requester. Closed requests can be duplicated, but you will need to enter a requester barcode.
Title-level requests: You can duplicate any open title-level request. When you duplicate the request, you will need to change the instance or the requester, because a patron cannot have more than one open title-level request on the same instance.
...
This action item should be hidden and unavailable in the Requests App UI menu both on Borrowing and Lending tenants .(in Ramsons)
The workaround proposed is to create a new request from scratch.
Move
*Not available in Ramsons
Action scope: This action allows you to move a request from one item to another. For example, when a regular TLR exists, and some item is selected for request fulfillment, you can move the request to another available item. It is only applicable if the request status is Open - Not yet filled, later it’s not possible to move. 
I wonder if there are any other move scenarios other than the one described above?
If you move a Primary Circulation Request it means the existing Secondary Circulation Request must be canceled and a new one created.
...
This action item should be hidden and unavailable in the Requests App UI menu both on Borrowing and Lending tenants .(in Ramsons)
The workaround proposed is to cancel the initial request and create a new one from scratch.