Updating an instance with data import erases administrative note (Lotus BF)

Description

Overview:
Steps to Reproduce:

  1. Log into Lotus bugfest

  2. Add an administrative note to an instance and save

  3. Export the instance with data export

  4. Reload the instance with data import using a profile like the one called "basic update" which updates the instance MARC and some instance fields

  5. Check the instance to see if your administrative note is still there

Expected Results:

The administrative note is still there

Actual Results:

The administrative note is gone
NOTE A-M tested on folio-snapshot; admin note only disappears if the job profile has an "Update instance" action in it, but NOT if the job profile only has "Modify MARC Bib" or "Update MARC Bib" action in it.

Additional Information:

My test instance: https://bugfest-lotus.int.aws.folio.org/inventory/view/d3a30c70-2244-4887-a83f-a405d083dbbb

Update job profile: https://bugfest-lotus.int.aws.folio.org/data-import/job-profile/view/0a037351-2e63-44f9-9a5e-43d240b03f71?sort=name

URL:
Interested parties:

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

1

Checklist

hide

TestRail: Results

Activity

Show:

Marc Johnson April 20, 2022 at 4:14 PM

Yes, I guess I can test e.g. the Orders app. It seems weird if check out/check in would cause any damage on the instance records, or Request?

I don't know. The suggestion for testing came from .

I think that is about understanding FOLIO's processes e.g. I don't know if the instance level requests work means that circulation changes instances.

Charlotte Whitt April 20, 2022 at 2:51 PM

Hi - Yes, I guess I can test e.g. the Orders app. It seems weird if check out/check in would cause any damage on the instance records, or Request?

Round tripping using Data Export - would that be a problem, – will you check that. Thanks

Marc Johnson April 19, 2022 at 2:55 PM

if there are any other apps or processes that act on Inventory Instances, Holdings, Items, I think you'll want to test them all to make sure they do not accidentally affect the Admin notes. Since it's a new field, I imagine there may be settings in other apps or other code that does not take the new field into account. Better it's figured out sooner rather than later.

Ideally, our systems would be modelled to automatically accommodate new optional properties (by ignoring them on read, and including them on updates).

I concur that it is quite possible this is not how some of FOLIO is implemented and thus we need to be diligent when we add new properties.

please let me know if you need anything from me to facilitate this.

Ann-Marie Breaux April 18, 2022 at 9:40 AM

Tested on Lotus bugfest with 1) Update instance job profile, and 2) Overlay a source = FOLIO Instance with single record import. In both cases, the Instance admin note was retained. All looks good!

Oleksii Petrenko April 15, 2022 at 10:34 AM

Deployed to Lotus BF. Please proceed with verification

Done

Details

Assignee

Reporter

Priority

Story Points

Development Team

Folijet Support

Fix versions

Release

Lotus (R1 2022) Bug Fix

RCA Group

Incomplete/missing requirements

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created April 13, 2022 at 11:27 AM
Updated June 22, 2022 at 1:41 PM
Resolved April 15, 2022 at 7:08 AM
TestRail: Cases
TestRail: Runs