[MODDCB-33] [SPIKE] Investigate UI Changes Required by Implementation of CirculationItem. Part 2 Created: 11/Sep/23 Updated: 05/Oct/23 Resolved: 25/Sep/23 |
|
| Status: | Closed |
| Project: | mod-dcb |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Story | Priority: | P3 |
| Reporter: | Kalibek Turgumbayev | Assignee: | Priyanka Terala |
| Resolution: | Done | Votes: | 0 |
| Labels: | dcb, front-end, non-testable | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Sprint: | |||||||||
| Story Points: | 5 | ||||||||
| Development Team: | Volaris | ||||||||
| RCA Group: | TBD | ||||||||
| Description |
|
Purpose/Overview: DCB integration will introduce circulationItem entity. This entity for Borrowing and Pickup libraries represents Item from Lending library and should not provide any links or information from Inventory. The circulation item in different UI screens should only provide info that it is DCB-related item without links.
Acceptance criteria:
Additional info: Integration Design: https://folio-org.atlassian.net/wiki/display/FOLIJET/%5BDRAFT%5D+DCB+Integration ** |
| Comments |
| Comment by Priyanka Terala [ 21/Sep/23 ] |
|
list of affected UI-modules ui-users ui-requests ui-circulation-log ui-inventory ui-checkin ui-checkout ui-servicepoints (may be) - ATM Service points are hard coded in BE implantations - example use case - Page Request creation. The approach would be analyzed as part of spike https://folio-org.atlassian.net/browse/MODDCB-28 Then ui-servicepoints might need to be analyzed. Identify what UI screens related to circulation use item API from inventory Here snapshot deployment has been taken as reference.
Many UI implementation questions have been documented at DCB Questions - Folio Development Teams - FOLIO Wiki along with other questions and assumptions. |
| Comment by Priyanka Terala [ 21/Sep/23 ] |
|
ui-inventory Proposal1 - Challenge: How? Proposal2 - Let Umbrella Inventory and Holding display in UI, but all their actionable button be disabled. Challenge: Based on what check, the actionable be disabled? Proposal3 -
|
| Comment by Priyanka Terala [ 21/Sep/23 ] |
|
ui-users Decision: DCB users should not be searchable from within the FOLIO application. The technical approach on how to exclude DCB users from search needs to be discussed. Approach1 : Introduce User_Type = DCB - Agreed by Kalibek and Amelia. Suggestion from Amelia, on ui-users app (user detail, user detail full screen), DCB user detail action menu items and other actionable buttons are to be preferably disabled. There can be some Consortium related action buttons as well. Needs to be checked on consortium enabled environment. Approach2: Approach3:
ATM, there is no clarity if Users - FOLIO and Users - FOLIO screens would be reached through ui-circulation. These screens have links to items. In case of virtual items, and if these screens are reachable, how are the links be rendered? |
| Comment by Priyanka Terala [ 21/Sep/23 ] |
|
ui-circulation-log Circulation Log list consists of objects of 8 types -
Based on the type of object and availability of ids (like userId (for User Details menu item), feeIf and userId (for Fee Details menu item), requestId (for Request Details menu item),
Assumptions:
As per the discussion with BE team, mod-circulation talks to mod-pub-sub which writes to audit data, this is what is available through circulation log list. This flow is not being controlled by mod-dcb.
|
| Comment by Priyanka Terala [ 25/Sep/23 ] |
|
ui-requests Links to
|
| Comment by Priyanka Terala [ 25/Sep/23 ] |
|
ui-checkout ui-checkin After scanning items, the table that list the details of scanned item has actions menu items. These items needs to be handled |