Update instance import overwrites instance status update date when profile is not editing the instance status (Morning Glory)

Overview: When an inventory instance is updated and there is an instance status assigned and instance status update date value, and the import profile does not define a change of the instance status the instance status updated date is overwritten as null. The behavior appears to exist from Juniper forward.

Steps to Reproduce:

1. Log into folio-snapshot.
2. Create an instance (manually or via Inventory single record import
3. Manually edit the status of the Instance (select from the available statuses in the dropdown list)
4. Save the instance and confirm that there is an Instance status term and updated date below the term.
5. Search for the newly-created instance, so that you have a search result in the second pane
6. Export the instance from FOLIO, using the Export instance (MARC) option from the results pane Action menu
7. Go to Data Export and click on the quick-export file name at the top of the log list to download the MARC file
8. Edit the exported MARC file to add a 500 note or a 650 subject heading. Do NOT edit the 001 or 999 ff. Then recompile into a MARC file.
9. In data import settings create a Field mapping profile:
   1. Incoming record type: MARC
   2. Folio record type: Instance
   3. Do not include any edits in the field mapping
   4. NOTE: The same behavior is observed if edits are included in the Instance field mapping profile (e.g. Statistical codes, Admin notes), as long as there is no edit to the Instance Status field in the field mapping profile
   5. Save as profile and close.
10. In data import settings create an Action profile
    1. Action: Update
    2. Folio record type: Instance
    3. Link to the field mapping profile created in the previous step.
11. In data import settings create a match profile
    1. Incoming records: MARC Bibliographic
    2. Existing Records: Instance
    3. MARC Bibliographic field in incoming record: Field: 001
    4. Existing instance record field: Admin data: Instance HRID.
    5. Save as profile & Close
12. Create a new job profile
    1. Accepted data type: MARC
    2. Add the Match profile created in the previous step.
    3. Add the Action profile created in the previous step.
13. In Data Import, import the MARC record exported from FOLIO using the import profile created in the previous steps.
14. Confirm that the instance was updated by looking at the Record updated metadata.

Expected Results:

• Instance status term is the equivalent of what it was before the import.
• Instance status updated date is the equivalent of what it was before the import.

Actual Results:

• Instance term is the equivalent of what it was before the import.
• Instance status updated date is no longer present in the record.
• Other scenarios:
  • If the same Instance status is included as a field mapping in the Update instance field mapping profile, the Status updated date/time is removed. Expected behavior would be
    • Retain the date/time that the instance was originally set to that status, if possible
    • If that is not possible, assign updated date/time to the Instance status field (matching the Record last updated date/time
  • If a different Instance status is included as a field mapping in the Update instance field mapping profile, the Status updated date/time is updated properly

NOTE: I have created 4 import jobs to test these 4 varieties. We probably should include in the Testrail as well.

1. Update instance - no changes (video part 2)
2. Update instance - with changes but not Status (video part 2)
3. Update instance - with changes and Same status update (video part 3)
4. Update instance - with changes and Different status update (video part 3)

Interested parties: University of Chicago