Bulk Edit (UXPROD-868)

[UXPROD-4021] Bulk Edit - in app - instance notes Created: 04/Feb/23  Updated: 05/Feb/24

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: Ramsons (R2 2024)
Parent: Bulk Edit

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

Attachments: PNG File screenshot-1.png    
Issue links:
Cloners
clones UXPROD-4020 Bulk Edit - in app - FOLIO holdings n... In Review
Defines
is defined by MODBULKOPS-188 Rendering FOLIO Instance record Notes... Draft
Epic Link: Bulk Edit
Front End Estimate: XL < 15 days
Front End Estimator: Vadym Shchekotilin
Front-End Confidence factor: 70%
Back End Estimate: XL < 15 days
Back End Estimator: Viachaslau Khandramai (Inactive)
Back-End Confidence factor: 50%
Development Team: Firebird
PO Rank: 0

 Description   

Current situation or problem:

Currently all instance notes can be updated only one by on only. Also, the existing work around by ETL does not support multiple notes for each note type.

In scope

  1. Identify records that will be updated based on a list of records identifiers (HRID, UUID, ISBN, ISSN) or a query
  2. Support :
    1. updates to administrative notes
    2. updates to all instance notes types
    3. changes from public to staff only notes
    4. changes from staff only to public notes
  3. Users should be able: add new, remove all, remove an existing note and modify existing notes
  4. Users should be able to change the note type
  5. Instance note types should be retrieved dynamically so that a newly added notes types can be supported as well
  6. Editing instances with source FOLIO and MARC are supported
  7. During the bulk edit job, users will receive a feedback about encountered errors so that they can be addressed
  8. Logs of the completed bulk edit jobs are available for defined period of time (30 days by default) and provide following information:
    1. list of recorcords affected by bulk edit (file with identifiers or query results)
    2. file with modified records before the changes are committed
    3. file with modified records after the changes are committed
    4. files with errors encountered while matching records or committing changes

Out of scope

Use case(s)

  • Have the ability to batch add or update a note or other field for all instances or holdings or items in a given set.

(Christie Thomas changed this to high as we are currently adding electronic bookplates to the holdings notes field in the absence of a donor management app and associated functionality. Because the notes are repeatable, ETL would only work if you are adding a new note to existing notes or deleting all notes and adding notes. it is not possible to replace a specific note.)

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

Links to additional info

  • Mockups: TBD


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