[UXPROD-868] Bulk Edit Created: 08/Jun/18  Updated: 24/Jan/24

Status: In Progress
Project: UX Product
Components: None
Affects versions: None
Fix versions: None

Type: Epic Priority: P3
Reporter: Cate Boerema (Inactive) Assignee: Magda Zacharska
Resolution: Unresolved Votes: 0
Labels: crossplatform, loc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by UXPROD-3543 Bulk Edit performance Closed
is defined by UXPROD-3842 Bulk edit - architectural improvements Closed
Relates
relates to UXPROD-600 Workflow App with To-Do App Integration In Review
relates to UXPROD-120 Bulk edit Inventory records In Progress
relates to UXPROD-949 Rewrite Cornell's Web based LS-Tools Closed
relates to UXPROD-3651 Ability to batch renew loans across m... Draft
relates to UXPROD-47 Batch Importer (Bib/Acq) Analysis Complete
Epic Name: Bulk Edit - batch changes to lists of records (inventory, users, requests, budgets, etc)
Development Team: Firebird
Score: 37.13
Start date (migrated):
End date:
Epic Color: ghx-label-9

 Description   

User should be able to identify records for bulk edit based on a list of submitted identifiers or a query and have ability to change one or more properties for each record in a list of records to a given value (add new data, remove existing data, change existing data)

Before the changes are committed, user should be able to review them, confirm them and commit them. If an error occurs during the bulk edit, user is notified about it and the logs are available for the user so that the errors can be addressed in the future

The bulk edit functionality should support expert users who are familiar with FOLIO data structure and are aware of the impact of the bulk edit operation (CSV approach) but also need to provide a way to a limited impact bulk edit that could be done by less technically savy users (in-app approach)

The planned functional areas for bulk edit include:

  • Circulation (requests, loans)
  • Users (permissions, user records)
  • Acquisition (orders, finances)
  • ERM (agreements, licenses)
  • SRS (bib records, holdings, authority)
  • Courses
  • Tags (can be a part of each functional area)

Out of scope
Bulk adding of new records

Additional information:

  1. Use cases at https://folio-org.atlassian.net/wiki/display/BULKEDIT/Bulk+Edit+Use+Cases
  2. High level roadmap: https://folio-org.atlassian.net/wiki/display/BULKEDIT/High+Level+Roadmap+for+Bulk+Edit+App
  3. Mockups:


 Comments   
Comment by Ann-Marie Breaux (Inactive) [ 04/Aug/20 ]

Hi Cate Boerema This has a Q3 2019 fix version on it. Should we wipe that out?

Comment by Cate Boerema (Inactive) [ 05/Aug/20 ]

Yes, that's odd - I removed it. BTW, it's usually Hkaplanian who puts fix versions on epics.

Comment by Ann-Marie Breaux (Inactive) [ 05/Aug/20 ]

Good to know Cate Boerema Thank you!

Comment by Jennifer Eustis [ 20/Nov/20 ]

The work of batch edits relies on being able to effectively find and identify the records you need to edit. Having a strong, effective, and accurate search is a must. Also, the ability to work on sets not just in terms of doing bulk edits on records in those sets but also working with sets from saved searches to filter down to records you need to work with. In Aleph, you can save search results and then manipulate those further with boolean commands like and, or, first set but not second, second set but not first. In Alma, there was the possibility of having dynamic sets where if any new records or update records in Alma fit the search parameters then that record was added to your set. This was fantastic.

Comment by Charlotte Whitt [ 20/Nov/20 ]

Thanks Jennifer Eustis - Thanks for adding these comments above. I fully agree.

CC: Magda Zacharska (PO for implementation of Elastic Search), and Kyle Felker (as lead developer for Elastic Search)

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