When job profile updates holdings/item only, Inventory hotlinks not populated

Description

Overview: When a job profile creates or updates an Instance, the log hotlinks for Instance, Holdings, and/or Item record are populated. When a job profile creates or updates a Holdings or Item, without updating an Instance, the Holdings and/or Item log hotlinks are not populated

Current workaround: Manually search for the holdings or item

Steps to Reproduce:

  1. Log into FOLIO-snapshot-load as diku_admin

  2. Go to Settings/Data Import

  3. Create the following field mapping profiles:

    • Field mapping profile 1

      • Name: Create simple instance

      • Incoming record type: MARC Bibliographic

      • FOLIO record type: Instance

      • Cataloged date: Select today from the dropdown list

      • Instance Status: Select one from the dropdown list

    • Field mapping profile 2

      • Name: Create simple holdings

      • Incoming record type: MARC Bibliographic

      • FOLIO record type: Holdings

      • Permanent location: Select Main Library (KU/CC/DI/M from the dropdown list

    • Field mapping profile 3

      • Name: Create simple item

      • Incoming record type: MARC Bibliographic

      • FOLIO record type: Item

      • Material type: Select one from the dropdown list

      • Permanent loan type: Select one from the dropdown list

      • Status: Select Available from the dropdown list

      • Permanent location: Select Main Library (KU/CC/DI/M from the dropdown list

    • Field mapping profile 4

      • Name: Update simple holdings

      • Incoming record type: MARC Bibliographic

      • FOLIO record type: Holdings

      • Temporary location: Select one from the dropdown list (anything except KU/CC/DI/M)

    • Field mapping profile 5

      • Name: Update simple item

      • Incoming record type: MARC Bibliographic

      • FOLIO record type: Item

      • Permanent loan type: Select one from the dropdown list; make sure it's different from the one used in Field mapping profile 3

  4. Create 5 parallel action profiles and link the above field mapping profiles to them

  5. Create 3 match profiles:

    • Match profile 1

      • Name: Instance match by HRID

      • Incoming record: MARC Bib

      • Existing record: Instance

      • MARC field: 001 (no indicators or subfield)

      • Exactly matches

      • Instance HRID

    • Match profile 2

      • Name: Holdings submatch by permanent location

      • Incoming record: Static value

      • Existing record: Holdings

      • Incoming value: Text KU/CC/DI/M

      • Exactly matches

      • Holdings permanent location

    • Match profile 3

      • Name: Item submatch by permanent location

      • Incoming record: Static value

      • Existing record: Item

      • Incoming value: Text KU/CC/DI/M

      • Exactly matches

      • Item permanent location

  6. Create 2 job profiles

    • Job profile 1

      • Name: Create Simple Instance, Holdings, Item

      • Accepted data type: MARC

      • Action: Create Instance

      • Action: Create Holdings

      • Action: Create Item

    • Job profile 2

      • Name: Update Simple Holdings, Item

      • Accepted data type: MARC

      • Match profile: Instance match by HRID

        • For matches: Match profile: Holdings submatch by permanent location

          • For matches: Action profile: Update simple holdings

        • For matches: Match profile: Item submatch by permanent location

          • For matches: Action profile: Update simple item

  7. Import the attached MARC file UIDATIMP-1080.mrc using the job profile Create Simple Instance, Holdings, Item

  8. Once the import finishes, check the log to ensure that there are hotlinks for the created Instance, Holdings, and Item

  9. Edit the MARC file to remove the existing 001 and 003, and replace the 001 value with the Instance HRID value

  10. Import the revised MARC file using the job profile "Update Simple Holdings, Item"

  11. Once the import finishes, check the log to ensure there are hotlinks for the updated Holdings and Item

Expected Results: There should be hotlinks for the updated holdings and item

Actual Results: There are not

Additional Information: See attached videos UIDATIMP-1080 Part 1 and Part 2

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

3
  • 19 Jan 2022, 10:31 AM
  • 19 Jan 2022, 10:31 AM
  • 19 Jan 2022, 10:31 AM

Checklist

hide

TestRail: Results

Activity

Show:

Ann-Marie BreauxMarch 21, 2022 at 9:03 AM

Tested again on folio-snapshot, and it's working properly. Closing this issue. No UI release needed, since changes were made on BE

Ann-Marie BreauxMarch 1, 2022 at 8:29 AM

Don't close this issue until item TestRail is updated with the 3 job profiles from MODINV-641

Ann-Marie BreauxFebruary 24, 2022 at 10:27 AM

Now that the related MOD stories are completed, this needs:

  • explanatory video

  • release note

  • review the testrail cases, especially for the item-only update

Ann-Marie BreauxFebruary 2, 2022 at 12:30 PM

Created separate MODSOURMAN-679 to account for the case where the item is updated, but not the holdings or instance. MODSOURMAN-676 gathers the appropriate Instance UUID needed to create the URL for the holdings and item hotlinks. MODSOURMAN-679 needs to also gather the appropriate Holdings UUID. Since the holdings is not being updated in the MODSOURMAN-679, its UUID is not automatically known.

Ann-Marie BreauxJanuary 26, 2022 at 9:54 PM

Per once MODSOURMAN-676 is finished, that should fix the UI, and no additional UI work will be needed. Leave this issue open until checked and confirmed

Done

Details

Assignee

Reporter

Priority

Story Points

Development Team

Folijet Support

Release

Lotus R1 2022

RCA Group

Implementation coding issue

Affected Institution

!!!ALL!!!

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created January 19, 2022 at 9:51 AM
Updated April 4, 2023 at 8:24 PM
Resolved March 21, 2022 at 9:04 AM
TestRail: Cases
TestRail: Runs

Flag notifications