Bulk Edit (UXPROD-868)

[UXPROD-3806] Bulk edit - request hold shelf expiration date Created: 19/Sep/22  Updated: 30/Nov/23

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: Sunflower (R3 2024)
Parent: Bulk Edit

Type: New Feature Priority: P3
Reporter: Magda Zacharska Assignee: Magda Zacharska
Resolution: Unresolved Votes: 0
Labels: LC1, consortia-ebsco, firebird-po-share, loc, volaris-candidate
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
clones UXPROD-3805 Bulk edit - loan due dates Draft
Relates
relates to UXPROD-1636 Make Hold Shelf Expiration Date Respe... Closed
Release: Sunflower (R3 2024)
Epic Link: Bulk Edit
Front End Estimate: XL < 15 days
Front End Estimator: Magda Zacharska
Front-End Confidence factor: 20%
Back End Estimate: XXL < 30 days
Back End Estimator: Magda Zacharska
Back-End Confidence factor: 20%
Development Team: Volaris
PO Rank: 0
Rank: Cornell (Full Sum 2021): R4

 Description   

Current situation or problem
When the access to the library is restricted due to some unexpected events as sudden building repairs, inclement weather or pandemic, the the request hold shelf expiration dates need to be adjusted accordingly so that the material is still available for the pickup or delivery when the library resumes normal operations. a Currently in FOLIO, adjustments to the hold shelf expiration dates need to happen one by one.

In scope

  • Bulk edit of hold shelf expiration date
  • Records identified for bul bulk edit by submitting a list of request UUIDs
  • Preview of matching records includes top five column from the request record
  • User can select and unselect columns and the selection persists throughout all bulk edit screens

The flow should be the same as already implemented for users and item records ([in app approach|https://drive.google.com/file/d/1lw3W4PUgcoUUBsCBbgmpPr2-nW8GGN_T/view?usp=sharing).

Out of scope

  • bulk editing other fields from the request record
  • building query - to be covered in UXPROD-3785 Closed
  • preview of matching records containing columns from other record types

Use case(s)

  • Library closes for inclement weather and patrons cannot return their loaned material on time.
  • Library closes a part of the building for necessary repairs
  • Library closes a part of the building due to mold outbreaks or flooding
  • Delivery van is broken down and the library cannot make deliveries

Additional use cases: https://folio-org.atlassian.net/wiki/display/BULKEDIT/Bulk+Edit+Use+Cases

Questions

  1. Should the change in the hold shelf expiration date impact the request expiration date?
  2. Which request statuses should be impacted?
  3. Should the hold shelf expiration date be updated for holds, pages and recalls?
  4. Should the hold shelf expiration date be updated for other requests statuses than:
    a. Open – Awaiting delivery
    b. Open – Awaiting pickup?


 Comments   
Comment by Erin Nettifee [ 23/Sep/22 ]

Hi Magda:

1. List of supported identifiers:
Request uuid
Pickup service point
User id
Patron group

We'll want user UUIDs and user barcodes (not sure what User ID means in this list.) Both user UUID and user barcode are on the request schema.

In terms of columns, you could definitely eliminate proxy from showing automatically. I think you would want to add pickup service point as a column (that doesn't show currently in the Requests app, but we have been talking about adding it.)

Should the change in the hold shelf expiration date impact the request expiration date?
Which request statuses should be impacted?
Should the hold shelf expiration date be updated for holds, pages and recalls?
Should the hold shelf expiration date be updated for other requests statuses than:
a. Open – Awaiting delivery?
b. Open – Awaiting pickup?

To be clear on functionality - the hold shelf expiration date is empty when a request is created. It's populate when a request moves to Open - Awaiting Pickup, based on the value in the associated service point configuration.

The hold shelf expiration date is not populated when a request goes to Open - Awaiting Delivery, because the request is not going on the hold shelf, it's getting delivered.

Once a request is in Open - Awaiting Pickup, the request expiration date doesn't serve any workflow function anymore, so it can be ignored.

The only request status that this particular feature applies to is Open - Awaiting Pickup.

All three types of requests (pages, holds, recalls) can move to Open - Awaiting Pickup, so all of them need to be included in this feature.

Comment by Magda Zacharska [ 08/May/23 ]

Moving LC1 label from epic to defining features with Caitlin Stewart permission.

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