Bulk Edit (UXPROD-868)

[UXPROD-3318] User records - bulk edit - pilot implementation Created: 21/Sep/21  Updated: 09/Dec/22  Resolved: 03/Mar/22

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Morning Glory (R2 2022)
Parent: Bulk Edit

Type: New Feature Priority: P2
Reporter: Magda Zacharska Assignee: Magda Zacharska
Resolution: Done Votes: 0
Labels: bulk-edit-pilot
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
defines UXPROD-3225 Bulk Edit - User data - Pilot Closed
is defined by FEXPCMN-1 Create new utility module export-common Closed
is defined by FEXPCMN-2 Migrate all the common resources to t... Closed
is defined by MODEXPS-47 Reuse common schemas Closed
is defined by MODEXPW-52 Reuse export-common library Closed
is defined by MODEXPW-59 Create API to start bulk-edit job exe... Closed
is defined by MODEXPW-69 Records processing preview handling Closed
is defined by MODBULKED-9 [SPIKE] Save and retrieve matching re... Closed
is defined by MODBULKED-16 Extend JobCommand schema Closed
is defined by MODEXPS-48 Remove expired files Closed
is defined by MODEXPW-44 Implement the preview of matched records Closed
is defined by MODEXPW-47 Save errors in csv format Closed
is defined by MODEXPW-48 Remove uploaded edit records if user ... Closed
is defined by MODEXPW-49 Get matching records CSV file by user... Closed
is defined by MODEXPW-51 Records processing errors handling Closed
is defined by MODEXPW-53 Process submitted records Closed
is defined by MODEXPW-56 Return the number of records in a file Closed
is defined by UIBULKED-7 Add Query component to Set criteria pane Closed
is defined by UIBULKED-17 Start bulk edit Closed
is defined by UIBULKED-18 Download matched records (CSV) Closed
is defined by UIBULKED-19 Download errors (CSV) Closed
is defined by UIBULKED-20 Bulk edit confirmation modal Closed
is defined by UIBULKED-21 Bulk Edit progress bar Closed
is defined by UIBULKED-22 Completion of the bulk edit Closed
Epic Link: Bulk Edit
Front End Estimate: XL < 15 days
Front End Estimator: Uladislau Samets
Front-End Confidence factor: Medium
Back End Estimate: XXXL: 30-45 days
Back End Estimator: Viachaslau Khandramai (Inactive)
Estimation Notes and Assumptions: Estimate might be updated based on the tech approach
Development Team: Firebird
PO Rank: 0
Rank: Cornell (Full Sum 2021): R3
Rank: Duke (Full Sum 2021): R2

 Description   

Current situation or problem:

Once the records are identified, users need to be to download the file with the matching records, make changes on the local copy of the file and then upload the file. Once the file is uploaded the system will post the changes, letting the user know about the encountered problems via error logs that can be downloaded as well.

In scope

  • Save the file with the records that match the search criteria
  • Upload the modified file so that the changes are posted
  • Handle exceptions
  • Notify user about the exceptions

Out of scope

  • Bulk updates to other than user records
  • Bulk deletions

Use cases:

Links to additional info

Questions:

  • Handling permissions
  • Handling fees and fines
  • Handling loans


 Comments   
Comment by Erin Nettifee [ 19/Oct/21 ]
  • Permissions are a different record type than users - the edit case is there, but I think that is expanding the scope of the initial pilot and has the potential to introduce complexity that doesn't need to be there yet (if it ever does)
  • Fees and fines are financial transaction based and should not be edited directly. Perhaps the app can use the business logic pieces, but I'm skeptical that the bulk edit app is the appropriate place for that kind of work to happen. You can define bulk actions that have use cases - say, I want to waive all the fines that occurred during a particular time period - but I think it would be really difficult for one app to manage all of the possible use cases and associated APIs.
  • Same for loans - loans have logical pieces associated to them that need to be accounted for (item status changes, notice generation, fee/fine applications) and you would should not be regularly editing the underlying loan record. I worry a lot that trying to build in the logical pieces to the app will generate complexity that could really derail the development of a solid app infrastructure...
Comment by leeda.adkins@duke.edu [ 26/Oct/21 ]

I'm concerned that the pilot project is still focused on ETL/export-transform-load, which is what we are doing currently to edit MARC data in FOLIO, but was understood to be a stop-gap until the ability to perform targeted edits within the system was developed. Every time you export data out of the system to edit and reload, you introduce the potential for error; so it's not ideal as a routine workflow.

Comment by Victoria_Smelova [ 24/Jan/22 ]

Magda Zacharska All related items are closed. Could you please review?

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