[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:
Defines
is defined by UXPROD-4325 DCB FOLIO circulation In Review
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.
Requirements/Scope:

  1. Identify what UI screens related to circulation use item API from inventory
  2. Prepare a list of affected UI-modules
  3. Determine approach what properties of DCB Items should be displayed at affected screens

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.

Check out - FOLIO - FOLIO

Check in - FOLIO - FOLIO

 

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 - Do not show umbrella inventory and holding on UI.

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 - Let the umbrella instance and holding just be there. BE implementation, fetches it or creates it if one doesn't exist already. 

 

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: Leverage tags for DCB records. - Disagreed by Amelia

Approach3: Add alias (DCB in suffix/prefix) for all those newly created DCB entities - Not a smart way. This will be the worst case approach.

 

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 -

  1. 'Fee/Fine'
  2. Item Block
  3. Loan
  4. Manual Block
  5. Notice
  6. Patron Block
  7. Request
  8. "N/A"

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),
noticePolicyId (for Notice policy menu item), templateId (for Live version of template menu item)), there can be 7 types of menu items -

  1. Item details
  2. User details
  3. Fee/fine details
  4. Loan details
  5. Request details
  6. Notice policy
  7. Live version of template

Assumptions:

 

  1. Menu Items 6 and 7 redirect to circulation notice policies and policy templates, there is nothing to be worried about from DCB transactions perspective.
  2. Patron Notifications and Fee Fines should not be sent to virtual patrons from lending and pickup libraries. These loan policies should be managed by library staff manually as part of configuration. This one need to be discussed.

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.


  1. 1. As per the discussions, menu items 1-5, will have to be disabled based on role that the Folio system plays in DCB life cycle. It is probably based on virtual item or virtual patron checks.
  2. The links to patron barcode and item barcode should be handled too.
  3. UI implementation will be based on BE implementations and API response values for barcodes.
  4. This is stated in the assumptions on DCB Qs wiki

 

Comment by Priyanka Terala [ 25/Sep/23 ]

ui-requests

Links to instance, item, user/requester needs to be handled.

  1. Should the item be displayed as normal text and not as a link in case of virtual items, which means borrowing library and pickup library Hold requests?
  2. Based on further BE implementation, there will be information on what item id would be received for these hold requests. This needs to be checked in future.
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

Generated at Fri Feb 09 00:40:06 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.