Awesome this will be extremely helpful for us!!

Hi Working on it now

I just created this job profile using a static match, instead of true/false data in the MARC record, and it worked great!

Job profile: https://bugfest-lotus.int.aws.folio.org/settings/data-import/job-profiles/view/0979e752-2ed2-4ed1-8d96-531e233fbfbc?query=suppress&sort=name
Static Match profile: https://bugfest-lotus.int.aws.folio.org/settings/data-import/match-profiles/view/41b85df3-50f4-4717-85f7-0d20acc8891f?sort=name
Lotus BF Import job number: 8438

please add test cases into the TestRail for this bug. This needs to not lose a track of this issue in the future. Thank you

Hi

Tested on Lotus Bugfest using this profile: https://bugfest-lotus.int.aws.folio.org/settings/data-import/job-profiles/view/b5e24e32-b399-4c8f-a8d9-b9adc1dc81cd?query=modinv&sort=name and the Neuromancer record.

1. Make sure there are several instances with the same OCLC number, and that only 1 of them is marked Suppressed from discovery

   • Create a job profile

   • Match 1: OCLC number

   • Match 2: 951$a = Instance suppress from discovery (MARC value was true)

   • Update instance with a new statistical code

2. Import the Neuromancer file (make sure 951 $a true)

3. Check the log to be sure 1 instance was updated

4. Doublecheck in Inventory by searching on the OCLC number and title

Closing this issue. Add Lotus and Kiwi release notes to explain the matching situation (don't start with a large match, e.g. all instances suppressed from discovery)

Moved to Awaiting release. Will add release note to remind users to use more restrictive match at top of hierarchy. will also create separate Morning Glory issue, so that we can link to MG feature and release version.