Bulk Edit (UXPROD-868)

[UXPROD-4011] Bulk edit - ERM - tags, access status types, eHoldings assign/unassign, add to agreement Created: 03/Feb/23  Updated: 30/Nov/23

Status: Open
Project: UX Product
Components: None
Affects versions: None
Fix versions: Umbrellaleaf (R2 2025)
Parent: Bulk Edit

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

Issue links:
Cloners
clones UXPROD-4007 Bulk edit - items electronic access Draft
is cloned by UXPROD-4012 Bulk edit - Patron blocks Open
Epic Link: Bulk Edit
Front End Estimate: XXL < 30 days
Front End Estimator: Magda Zacharska
Front-End Confidence factor: 20%
Back End Estimate: XXXL: 30-45 days
Back End Estimator: Magda Zacharska
Back-End Confidence factor: 20%
Development Team: Firebird
PO Rank: 0

 Description   

Current situation or problem:
Any changes ERM records have to be done manually, one record at the time.

In scope

  • Identify records for bulk update based on the submitted list of identifiers or based on a query
  • In app support In app edits for:
    • adding/removing tags
    • editing access status types
    • adding to agreement
    • selecting/deselecting eHoldings
  • Preview changes before they are committed
  • Notify user about:
    • successfully updated records
    • errors that occurred during the update

Links to additional info
Mockups: TBD

Use case:
Keep track of ebooks purchased or on evaluation in EBA (evidence based acquisition) by adding tags, access status types, add to agreement and/or select/deselect in bulk in eHoldings. Usually in the hundreds, the titles are too many to work with one-by-one.

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



 Comments   
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:36:34 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.