Bulk Edit (UXPROD-868)

[UXPROD-3785] Bulk edit - query tool - FE Created: 20/Aug/22  Updated: 30/Nov/23  Resolved: 10/Aug/23

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Poppy (R2 2023)
Parent: Bulk Edit

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

Issue links:
Cloners
is cloned by UXPROD-4149 Bulk edit - query tool - BE In Progress
Defines
is defined by UIBULKED-164 Query tab permissions Closed
is defined by UIBULKED-165 Bulk edit - Query tab changes Closed
is defined by UIBULKED-167 Spike - populating dropdowns on the ... Closed
is defined by UIBULKED-168 Spike - investigate query parsing Closed
is defined by UIBULKED-169 Spike - CSV file reader Closed
is defined by UIPQB-1 Query plugin - project setup Closed
is defined by UIPQB-2 String containing UUIDs : field-actio... Closed
is defined by UIPQB-3 UUID not enforced: field-action-value... Closed
is defined by UIPQB-4 UUIDs: field-action-value component Closed
is defined by UIPQB-5 Field-action-value component: String Closed
is defined by UIPQB-6 Array property type - action-value co... Closed
is defined by UIPQB-7 Integer property type - action-value ... Closed
is defined by UIPQB-8 Boolean property type - action-value ... Closed
is defined by UIPQB-9 Date-time property format - action-va... Closed
is defined by UIPQB-10 Object property type - action-value c... Closed
is defined by UIPQB-11 Enum property type - action-value com... Closed
is defined by UIPQB-13 Query form elements Closed
is defined by UIPQB-14 Build query string Closed
is defined by UIPQB-15 Build query string - adding statement Closed
is defined by UIPQB-16 Removing statements Closed
is defined by UIPQB-17 Test query Closed
is defined by UIPQB-18 Run query Closed
is defined by UIPQB-19 Closing the Query tool form after tes... Closed
is defined by UIPQB-20 Viewer - preview top 100 records Closed
is defined by UIPQB-21 Viewer - display all matching records Closed
is defined by UIPQB-24 Add refreshing functionality for quer... Closed
is defined by UIPQB-25 Only one option can be selected after... Closed
is defined by UIPQB-26 Validate value entered for integer pr... Closed
is defined by UIPQB-28 Update QueryBuilder Component to work... Closed
is defined by UIPQB-29 Add "initialValues" Prop to ResultsVi... Closed
is defined by UIPQB-33 Aborting long running query Closed
is defined by UIPQB-34 Localize total number of records Closed
is defined by UIPQB-35 Incorrect parsing for multiselect values Closed
is defined by UIPQB-36 Add X button for closing the form Closed
is defined by UIPQB-37 Reset form to original state after us... Closed
is defined by UIPQB-39 Add new props to query plugin Closed
is defined by UIPQB-40 Change rendering behavior with IN ope... Closed
Release: Poppy (R2 2023)
Epic Link: Bulk Edit
Front End Estimate: XXL < 30 days
Front End Estimator: Magda Zacharska
Front-End Confidence factor: 80%
Back End Estimate: Out of scope
Back End Estimator: Magda Zacharska
Back-End Confidence factor: 70%
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 operators (AND, OR, NOT)
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. Users can narrow down the list from the records matching the query by selecting rows

Existing bulk edit operations will remain unchangeds
1. Users still can download matching results in .csv format.
2. Users can preview the list of selected records before the update is committed.

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 Molly Driscoll [ 10/Oct/22 ]

Another example that arose in the Oct. 10, 2022 RA SIG meeting is being able to search by patron expiration/patron group to use those results to bulk edit related loans and requests.

Comment by Erin Nettifee [ 12/Oct/22 ]

Hi Magda Zacharska - you have both Orchid and Poppy in the "fix version" but the release version is blank - can we clarify what release this is currently targeted for? Thank you!

Comment by Magda Zacharska [ 14/Oct/22 ]

Erin Nettifee - the work will start in Orchid but will continue until Poppy.

Comment by Oleksii Petrenko [ 16/Oct/22 ]

Hey Magda Zacharska

I keep only one fix version - Orchid

For Poppy separate UXPROD will be required.

Thank you

Comment by Magda Zacharska [ 17/Oct/22 ]

Oleksii Petrenko - the work will span through several releases - we start working in Orchid and it will significant part of the front end development capacity but we might not release the tool until Poppy release.

Comment by Oleksii Petrenko [ 18/Oct/22 ]

That is fine. Let's keep only one release in your case it should be Poppy.

Sorry, Magda. If my understanding is correct we expect to point only one release in FixVersion field.

Khalilah Gambrell Please correct me if I'm wrong

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