[UXPROD-120] Bulk edit Inventory records Created: 18/Jan/18  Updated: 14/Aug/23

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

Type: Epic Priority: P1
Reporter: Cate Boerema (Inactive) Assignee: Magda Zacharska
Resolution: Unresolved Votes: 0
Labels: cornell-priority, crossplatform, inventory, marccat, post-v1, reserves, round_iv
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
blocks UXPROD-1622 Bulk manipulation of item state for s... Closed
Defines
is defined by UXPROD-3469 Bulk Edit - in app approach - item st... Closed
is defined by UXPROD-3523 Bulk Edit - in app approach - item lo... Closed
is defined by UXPROD-3736 Bulk create inventory items Draft
Relates
relates to UXPROD-868 Bulk Edit In Progress
relates to UXPROD-949 Rewrite Cornell's Web based LS-Tools Closed
Potential Workaround: CW: This feature is ranked 'go-live' for all libraries except Chalmers. But Export (and re-import updated records) can be a workaround for the mvp.
It seems better to use this workaround and take the time to develop something that is truly better, and long term solution.
Estimation Notes and Assumptions: Assume we create a general bulk edit feature for searchandsort apps

Assume doing the change 1x1 won't scale

Needs new operation
Kiwi Planning Points (DO NOT CHANGE): 280
PO Rank: 112
Rank: BNCF (MVP Feb 2020): R1
Rank: Chalmers (Impl Aut 2019): R2
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R1
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R1
Rank: FLO (MVP Sum 2020): R1
Rank: GBV (MVP Sum 2020): R2
Rank: hbz (TBD): R1
Rank: Hungary (MVP End 2020): R1
Rank: Lehigh (MVP Summer 2020): R1
Rank: Leipzig (Full TBD): R1
Rank: Leipzig (ERM Aut 2019): R1
Rank: MI State-Lib of MI (Sum 2021): R2
Rank: MO State (MVP June 2020): R2
Rank: TAMU (MVP Jan 2021): R1
Rank: Trinity College (Jun 2021): R1
Rank: U of AL (MVP Oct 2020): R1
Start date (migrated):
End date:

 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 savvy users (in-app approach).

The planned functional areas for bulk edit include:

  • Inventory -instances, holdings and items
  • SRS (bib records, holdings, authority)
  • Tags (can be a part of each functional area)

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:

Out of scope:

  1. Information about what was changed and if the change was made as a result of manual or batch process. However the standard metadata information (who and when) about the records updates is present
  2. Selecting items from a list of search results. The bulk edit works on entire list of records matching search criteria or submitted list of identifiers.


 Comments   
Comment by Cate Boerema (Inactive) [ 25/Apr/18 ]

Marking post-v1 as the reserves sub-group prioritized a courses app for v1 over bulk edit of item location.

Comment by Chris Manly [ 10/May/18 ]

Cornell has a need for the ability for batch/bulk manipulation of metadata records to replace the LSTools application that we have as an adjunct to Voyager. We had envisioned generalizing it in FOLIO so other institutions could use it. We should explore whether it could be generalized (possibly with the help of the workflow engine) to apply to other kids of data within FOLIO.

Comment by Cate Boerema (Inactive) [ 14/May/18 ]

Thanks, Chris Manly. This was definitely envisioned as a general-purpose bulk-edit feature for records and data in FOLIO, starting with item bulk edit. That said, it has been deprioritized by the Reserves sub-group.

What type of metadata records does Cornell need to bulk edit? If this feature is a top priority for Cornell for other use cases, let's identify that in the upcoming early adopters gap analysis.

Comment by Ann-Marie Breaux (Inactive) [ 12/Jul/18 ]

In Batch Loader subgroup mtg today, we were talking about LS Tools, Bulk Edit, and Open Refine. Chris Manly I linked LS Tools and Bulk Edit since whatever development happens on these apps/services seems like it should be done in the context of each other. Christie Thomas Also need to be taking scripts into account. And will need to think about how this may fit with Workflows app.

Comment by Rui Francisco [ 30/Jan/19 ]

will there be a preview mode ?

it would be important as sometimes the institution makes changes that do not produced the desired result .

Preview can be made for a sample of 10 records

Comment by Ann-Marie Breaux (Inactive) [ 30/Jan/19 ]

Hi Rui Francisco we're planning a preview option in Data Import app, so that anticipated changes can be reviewed and adjusted before the final commit. It may be that bulk edit could use something similar. We have not created the final design for the screen(s) involved in preview yet. It will be some type of log screen showing the draft changes related to each imported record, in each affected app - then with options to adjust or run (commit).

Comment by Charlotte Whitt [ 20/Mar/19 ]

Hi Cate Boerema - Would it be relevant to do a UXPROD story for each app, where we'll implement bulk edit, e.g. Bulk edit of instance, holdings, item, container records in Inventory.

Requirement from the MM-SIG;
a) Transferring holdings and items:

  • Transferring holdings and items should retain any relationships established via app integrations, e.g., orders, etc.
Comment by Cate Boerema (Inactive) [ 21/Mar/19 ]

Hi Charlotte Whitt. This is an epic that hasn't been assigned to a PO so it doesn't have any granular UXPROD features defined. The PC asked that, in these cases, we create a single UXPROD feature which essentially clones the epic so they can apply their go-live rankings to something. We will further flesh out the features when we have a PO on the project. Harry and the PC are currently doing a refreshed epic ranking which will help determine which epic gets prioritized when a PO becomes available. Last time we did the epic ranking, this one was ranked highly.

Comment by Anya [ 29/Mar/19 ]

Comment from the March meeting: maybe should be broken down into bulk edit per app or per record type?

Comment by Charlotte Whitt [ 01/Apr/19 ]

Hi Anya - I have suggested (see comment here, dated 3/20/2019) to add UXPROD stories for bulk edit of Inventory instance, holdings, item, and container records.

Cate Boerema recommends to wait having this further fleshed out until a PO has been assigned.

Comment by Cate Boerema (Inactive) [ 01/Apr/19 ]

Anya would the early implementers like to provide different rankings for the various apps? If so, separating this into different features would make sense. Otherwise, I think we can just leave as-is until we have a PO.

Comment by Anya [ 01/Apr/19 ]

Cate Boerema- I will ask

Comment by Jenn Colt [ 03/Jul/19 ]

Just for clarity, the epic parent of this issue specifically says it is not about editing MARC records. There is a MARC Cat bulk edit issue here: https://folio-org.atlassian.net/browse/UXPROD-1722

(I'm just trying to clarify issues I'm tracking for us, whatever is decided is fine with me)

Comment by Charlotte Whitt [ 03/Jul/19 ]

ups - I missed UXPROD-1722 Closed . Thanks Jenn Colt - will move the comment to that issue

Comment by Cate Boerema (Inactive) [ 12/Jul/19 ]

Anya, I see you assigned this to Kelly Drake and assigned a fix version of Q4 2020? Can you help me to understand why you made these changes?

Comment by Anya [ 12/Jul/19 ]

Cate Boerema- I did assign this to Kelly Drake, I unless I was supposed to keep it, but it was written in the context of courses. I did not realize I had changed the fixed date, that was unintended - would you like me to blank it out?

Comment by Cate Boerema (Inactive) [ 15/Jul/19 ]

Thanks Anya, while bulk edit will be useful for Courses, it's a more general feature and I don't think it should be assigned to Kelly Drake (at least not now). I will remove her and the fix version.

Comment by Charlotte Whitt [ 25/Jul/19 ]

The MM-SIG is working on Batch editing usecases: https://docs.google.com/spreadsheets/d/1VTRg7CmF_UeZOqp62NVAhDsmqNn4-fqL4N-aH4phSx0/edit#gid=0

Discussed at MM-SIG meeting 7/25/2019 - see meeting minutes: https://folio-org.atlassian.net/wiki/display/MM/2019-07-25+Metadata+Management+Meeting+notes

Comment by Jacquie Samples [ 23/Sep/20 ]

Charlotte Whitt Cate Boerema Hkaplanian I am concerned about the general work-around to export and bulk edit outside by a 3rd-party piece of software. In general, this is not a suitable short to medium term solution. I also want to point out that not every piece of data is in a MARC format, so using MARCedit for many types of bulk editing is just not possible. I would like it if the person suggesting a work-around test that work around for the types of data in question before adding suggestions to the Jiras.

This is also a very old work-around which wasn't developed. Updates on the work around to the work around.

Comment by Hkaplanian [ 23/Sep/20 ]

Jacquie Samples, I deleted that comment. It's very old and out dated.

Comment by Jacquie Samples [ 23/Sep/20 ]

Thanks for the update Hkaplanian

Comment by Marie Widigson [ 02/Dec/20 ]

We think our original R4 ranking was a mistake, now changing it to R2.

Comment by Anya [ 05/Feb/21 ]

Hkaplanian... any word on this ?

Comment by Hkaplanian [ 05/Feb/21 ]

Anya, We 1st need someone to build a solid set of requirements for this.

Comment by Anya [ 05/Feb/21 ]

Steve Bischof/ Former user please see Hkaplanian's comment ... do you know someone that could champion this?

Comment by Magda Zacharska [ 20/May/22 ]

Changing this feature to epic as it covers several areas that require implementation that will span through several releases.

Comment by Magda Zacharska [ 20/May/22 ]

Charlotte Whitt - could you help me understand what is meant in by "item type (permanent, temporary)" that is mentioned in the description?

Comment by Charlotte Whitt [ 31/May/22 ]

Magda Zacharska, yes what Cate Boerema meant was Item loan type ... I have updated the description

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