Bulk Edit (UXPROD-868)

[UXPROD-4149] Bulk edit - query tool - BE Created: 22/Mar/23  Updated: 05/Feb/24

Status: In Progress
Project: UX Product
Components: None
Affects versions: None
Fix versions: Quesnelia (R1 2024)
Parent: Bulk Edit

Type: New Feature Priority: P2
Reporter: Magda Zacharska Assignee: Magda Zacharska
Resolution: Unresolved Votes: 0
Labels: LC-priority2, bulk-edit-query, consortia-ebsco, loc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
clones UXPROD-3785 Bulk edit - query tool - FE Closed
Defines
is defined by UIBULKED-404 Render preview after query executed Open
is defined by FQTM-1 Setup folio-query-tool-metadata module Closed
is defined by MODBULKOPS-31 Removing data generated by test query Closed
is defined by MODBULKOPS-32 FQM Query Tool Metadata supporting Closed
is defined by MODBULKOPS-43 FQM Integration - FQM Results handling Closed
is defined by MODBULKOPS-44 FQM Integration - Deprecate Bulk Oper... Closed
is defined by UIBULKED-367 Logs - Provide a link to file with id... Closed
is defined by UIBULKED-392 Unhide Query tab Closed
is defined by UIBULKED-403 Integrate query-plugin with bulk-edit... Closed
is defined by MODBULKOPS-45 Results Preview API Closed
is defined by MODBULKOPS-46 Selection API Closed
is defined by MODBULKOPS-47 Start Export API Closed
is defined by MODBULKOPS-33 FQM Integration - EntityType API Draft
is defined by MODBULKOPS-34 FQM Integration - FQM Results preview Draft
Gantt End to Start
has to be done before UXPROD-4674 Bulk edit - Sorting and filtering res... Open
has to be done before UXPROD-4058 Bulk edit - Display entire record set... In Progress
Relates
relates to UIBULKED-351 Hide Query tab Closed
Epic Link: Bulk Edit
Front End Estimate: XXL < 30 days
Front End Estimator: Magda Zacharska
Front-End Confidence factor: 10%
Back End Estimate: XXL < 30 days
Back End Estimator: Viachaslau Khandramai (Inactive)
Back-End Confidence factor: 80%
Development Team: Firebird
PO Rank: 0
Rank: Cornell (Full Sum 2021): R1

 Description   

Current situation or problem:

Currently users can trigger bulk edit by submitting a list of records identifiers.  However, in many cases the list of identifiers is not available and users will need to have a way to identify records for bulk editing based on a query.  In many cases, the search will need to be performed across different record types (for example, searching for users with a specific permissions or users with outstanding fees)

In scope
1. Create a tool that will visually guide the user in building a query
2. Support selecting one or more record types that will be used to build the query
3. For multiple record types selection, maintain the supported relationship between those records so that it is not possible to select unrelated records
4. Support picking fields based on selected records
5. Support operation on the selected fields. For example:

  • "in" and "not in" for repeatable fields
  • "=" and "<>" for single value field
  • possible support for regular expressions

6. Supported operation should include: "starts with", "contains"

7. For the fields with predefined values (for example, patron groups or note types) the list should be prepopulated
8. Support Boolean operator (AND)
9. Query validation
10. Query execution (invocation of the appropriate back-end data provider)
11. Show the retrieved resultset to the user; the resultset is pageable so that the user can see all records matching the search
12. List of UUIDs of the records that match the query is saved so that it can be retrieved from the Logs tab

Existing bulk edit operations will remain unchanged
1. Users still can download matching results in .csv format.
2. Users can preview the list of selected records before the update is committed
3. Users can see and download the updated records
4. All files generated during bulk edit jobs can be accessed from the Log tab for 30 days

Use case(s)
https://folio-org.atlassian.net/wiki/display/BULKEDIT/Bulk+Edit+Use+Cases

Mockups:
https://drive.google.com/drive/folders/1mIPB4_VpFYe7gv_-SWDrJlj-KbQTalko

Additional info
Examples of multi record queries:

  • Search for holdings based on item record location, barcode
  • Search for holdings based on instance ISBN, ISSN, OCLC number
  • Search items based on holdings location
  • Search for users with a specific permission
  • Search for SRS holdings based on Inventory holdings administrative data
  • Search for users with open loans
  • Search for users with outstanding fines


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