...
Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | UXPROD-4559 |
---|
|
Title-level request scenarios
A title-level request is placed. An item is available. A page request is created for that item. The item is located and the request is fulfilled.
A title-level request is placed. An item is available. A page request is created for that item. The item cannot be located. The request status remains Open until the item is located, or, in perpetuity.
A title-level request is placed. There is no item available to be paged. A hold request is placed. The staff looks for an un-inventoried item. An item is located and the request is fulfilled.
A title-level request is placed. There is no item available to be paged. A hold request is placed. The staff looks for an un-inventoried item. An item cannot be found. The request status remains Open until the item is located, or, in perpetuity.
...
Module mod-search in the Central tenant has the merged information about all instances (as well holdings and items), and in which tenants those instances are available
In the diagram, the “Some other FOLIO module” module called mod-tlr is located in the Congressional Tenant, but in general, it can be located in any tenant in the consortium
The case when ECS TLR starts from the
...
Central Tenant
Drawio |
---|
mVer | 2 |
---|
zoom | 1 |
---|
simple | 0 |
---|
zoominComment | 10 |
---|
inCommentcustContentId | 0644939898 |
---|
pageId | 644972610 |
---|
custContentIdlbox | 6458245311 |
---|
diagramDisplayName | Untitled Diagram-17331363508601733136789907.drawio | lbox | 1 |
---|
contentVer | 12 |
---|
revision | 12 |
---|
baseUrl | https://folio-org.atlassian.net/wiki |
---|
diagramName | Untitled Diagram-17331363508601733136789907.drawio |
---|
pCenter | 0 |
---|
width | 22822283 |
---|
links | |
---|
tbstyle | |
---|
height | 921.9999999999999923 |
---|
|
The case when ECS TLR starts from the
...
Data Tenant
Drawio |
---|
mVer | 2 |
---|
zoom | 1 |
---|
simple | 0 |
---|
zoominComment | 10 |
---|
inCommentcustContentId | 0645824531 |
---|
pageId | 644972610 |
---|
custContentIdlbox | 6449398981 |
---|
diagramDisplayName | Untitled Diagram-17331367899071733136350860.drawio | lbox |
---|
1 | contentVer | 13 |
---|
revision | 13 |
---|
baseUrl | https://folio-org.atlassian.net/wiki |
---|
diagramName | Untitled Diagram-17331367899071733136350860.drawio |
---|
pCenter | 0 |
---|
width | 2283.00000000000052282 |
---|
links | |
---|
tbstyle | |
---|
height | 923.0000000000002 |
---|
|
Sequencing
...
Sequencing
The diagram below illustrates the interaction process between modules for a scenario with three tenants. Important: the diagram lacks a section showing the interaction with mod-dcb/mod-circulation in the Central Tenant.
...
Work Breakdown Struc ture (draft, in man-days)
Task | Details | Estimates, workdays |
---|
Accept ECS TLR, store it, search for Data tenants available, search for an item available for fulfillment (Сrawl phase) |
Create a new backend Spring-based module mod-tlr | Create a new repo, and add it to building/deployment pipelines Note: this is the 1st Spring-based module for the team | 5 |
Create a database schema for storing ECS TLR requests | to store ECS TLRs (entity describing the initial information about the request - instanceId, date-time, info from mod-search, tenant IDs it works with, …) to be able to track statuses to track ECS TLR and one-to-many relations to single-tenant TLRs Need to design data schema(-s) - this will appear along with WBS Need to design a set of ECS TLR statuses Liquibase
| 5 |
Add API endpoints for TLR mgmt and CRUD support | | 5-10 (it depends on if this can be implemented in a Spring-based module) |
Implement a timer for triggering internal actions | | 3-5 |
Implement a call from mod-tlr to mod-search to retrieve a list of tenants by instanceId | | 3-5 |
Implement logic for analyzing data from the mod-search and choosing which tenant to place the Single tenant TLR request to | This is where we can start with the simplified logic first and postpone a more sophisticated approach to the Walk phase. E.g., the proposed option may look like this: get a list of tenants and information about how many items are in each of them. If there is only one tenant on the list, we work with him. If there are several tenants in the list, we select the one with the most items (this increases the likelihood of finding an item) and work with it Update ECS TLR with a chosen tenantId Need to design 1-to-many relation between ECS TLR and single-tenant TRL
| 3-5 |
Implement a call from the Central tenant’s mod-tlr to the Data tenant’s mod-circulation | Assumption: the TLR-support feature flag is enabled in the Data tenant’s mod-circulation We can use one of the two following API endpoints - the one used for the Front-end (exact TLR request type needs to be specified), or the other used for requests from discovery (TLR request type can be defined as a result of Page/Recall/Hold selection). The second one is more appropriate for the Crawl phase though we would need to implement something else in the Walk phase. The option with sequential selection Page/Recall/Hold is very good for the first phase. Subsequently, the following logic can be implemented: make a Page request to each tenant (one by one) and check whether the item can be taken right now. If it fails, try a Recall request to each tenant and wait until you succeed. If it fails, make a Hold without an expiration date and wait until the item appears somewhere. Since there is an explicit requirement that non-fulfilled Congressional Loan requests remain open in perpetuity, the expiration period must be set without restrictions or have some significant value (this will be clarified later, in the process of more detailed analysis). In a regular single-tenant installation, when creating a TLR request, you can specify its type. In this case, a list of possible types and associated service points is formed on the
|
back-end backend by searching through all known items and checking the circulation rules for them. In the case of ECS TLR, information about items and rules may not be available at the time the request is created. So the Page/Recall/Hold sequence seems justified in this case. What pick-up service point should be specified and used for TLR requests? (pre-defined? or one from the list of all available service points?) The requester should specify a pickup service point however the Data tenant
|
can about of it so it’s required to mock it somehow (note: mod-dcb does the same as a part of DCB transaction) How to specify circulation rules for such a request? Can we assume that the circulation rules are the same for the whole LoC? Using the Data tenants' circulation rules is the most straightforward option (this is how it will work if we do nothing)
| 3-5 to make an API call + 3-5 to address questions with service points and circulation rules |
Add Kafka integration | For Page/Recall types of TLR we will have the item ID immediately in the response, so won’t need to wait For Hold we would need to listen to a Kafka topic for events related to single-tenant TLR request status changes - it should change to OPEN In transit
| 5-10 ( need to implement event publishing in mod-circulation and consumers/listeners in mod-tlr) |
Transaction initialization in mod-dcb | | 3-5 |
Update mod-dcb | | 3 |
Update mod-circulation | when creating a request for an item, mod-circulation needs to learn to accept an optional parameter with a TLR ID, and if it is present, learn to find the corresponding TLR and use it instead of creating a new request review the process of communication between mod-dcb and mod-circulation
| ? |
mod-tlr - Orchestration phase | | 3-5 |
ui-requests | Since we need to be able to place an ECS TLR request directly through UI, ui-requests need to be able to support this | |
Other considerations and assumptions
Do we need a separate UI for ECS TLR? - No. A TLR request created in the Central Tenant will be available in the Requests App in exactly the same way as other requests. The TLR request created in the Data Tenant will also be visible. In this case, both will be maintained in a consistent state using mod-dcb. At the same time, the ECS TLR entity, which will be stored and processed in mod-tlr, is a service entity that helps organize the work of the platform, and end users do not need to work with it.
Can Central Tenant have its own collections/inventory? - Instance records
Can a Data Tenant cancel a TLR request? Do we want to avoid this? - No
Currently, when creating a TLR in mod-circulation through a discovery endpoint, settings are applied that regulate the creation of a Hold type TLR. This can be done through a policy, or some special flag, or you can add logic in the program code. We need to remember to pay attention to this later
mod-dcb and mod-circulation-item - assumption: no additional work will be required in this regard
...
In case when TenantA has 0 Available items, TLR Page placed in TenantA will fail even though TenanB TenantB might have Available items
mod-circulation in TenantA knows nothing about available items and location structure in TenantB => TLR Page placed in TenantA may be fulfilled with an item that is not the closest to the Pickup SP
...
In case when TenantA has 0 loans, TLR Recall placed in TenantA will fail even though TenantB might have open loans
mod-circulation in TenantA knows nothing about loans in TenantB => TLR Recall placed in TenantA may be fulfilled with an item that is not on the closest-due-date loan
Drawio |
---|
mVer | 2 |
---|
zoom | 1 |
---|
simple | 0 |
---|
inComment | 0 |
---|
custContentId | 645496917 |
---|
pageId | 644972610 |
---|
lbox | 1 |
---|
diagramDisplayName | Untitled Diagram-1733137262512.drawio |
---|
contentVer | 1 |
---|
revision | 1 |
---|
baseUrl | https://folio-org.atlassian.net/wiki |
---|
diagramName | Untitled Diagram-1733137262512.drawio |
---|
pCenter | 0 |
---|
width | 571 |
---|
links | |
---|
tbstyle | |
---|
height | 591 |
---|
|