Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

[RRT] Instance nature of content term field is populated with "{}" value that causes to harvesting process failure

RCA Group

Implementation coding issue

Description

This issue comes from the thread “OAI-PMH Catalog harvesting issue with prod tenant for Wellesley College|ousp|Orchid-SP-6“ in RRT channel about harvesting issue. There was reported that “{ }” value is set to the instance "natureOfContentTermIds" field if MARC field specified for nature of content term field mapping is absent in incoming record. That in turn causes to error in inventory-storage module during harvesting process.

Environment

None

Potential Workaround

None

Checklist

hide

Activity

Show:

Ruslan LavrovApril 4, 2024 at 12:58 PM
Edited

During the investigation RRT request found that the described issue is not reproduced for Quesnelia release. At the beginning could not reproduce the issue on the snapshot env and dev-rancher env. Later doublechecked the issue on the Quesnelia BF environment using the file and mapping described in the bug MODDATAIMP-1039. For 3-rd and 4-th records related instances do not contain invalid value “{}” at the "natureOfContentTermIds" field https://bugfest-quesnelia.int.aws.folio.org/data-import/job-summary/77029210-9853-4130-8097-0940e73c2611.
But at the same time, it was spotted if the nature of content term name specified in the incoming record does not match any nature of content term in the inventory settings, then it is set to the instance "natureOfContentTermIds" field as-is, that can cause the same error in the inventory-storage module during harvesting process.

The described issue will be addressed in the scope of .

Done

Details

Assignee

Reporter

Labels

Priority

Story Points

Sprint

Development Team

Folijet

Parent

Release

Ramsons (R2 2024)

Affected releases

Poppy (R2 2023)
Orchid (R1 2023)

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created April 4, 2024 at 12:30 PM
Updated April 11, 2024 at 9:27 AM
Resolved April 11, 2024 at 9:26 AM
TestRail: Cases
TestRail: Runs