'NOT holdings.discoverySuppress==true' search excludes instances that have non-suppressed holdings

Description

Overview:
Steps to Reproduce:

Summary:

Search for an instance that has two holdings.  One of the holdings should be suppressed from discovery.

Steps:
  1. Log into juniper bugfest as any user

  2. Go to the inventory module

  3. Perform an instance 'query' search using this query:

  4. title=Taishun ding bu long and (id=* NOT discoverySuppress==true NOT holdingsRecords.discoverySuppress==true)

Expected Results:

One instance should be returned: hrid# in11620128
Actual Results:

Zero instances are returned.

If you 'un-suppress' the suppressed holding record (so both holdings are un-suppressed), the instance is returned.

These results can also be seen with this graphql query:
 

 

This query should return one instance and one holding record and an empty result is what is being returned.  This impacts the z39.50 results when configured to exclude suppressed holdings.

Additional Information:
URL:
Interested parties:


Update by :

*Following query: title=Taishun ding bu long and id= NOT discoverySuppress==true NOT holdingsRecords.discoverySuppress==true using the Query search option in Bugfest Juniper  does not return any result:

URL: https://bugfest-juniper.folio.ebsco.com/inventory?qindex=querySearch&query=title%3DTaishun%20ding%20bu%20long%20and%20id%3D%2A%20NOT%20discoverySuppress%3D%3Dtrue%20NOT%20holdingsRecords.discoverySuppress%3D%3Dtrue&sort=title

the same query in Bugfest Kiwi do:

URL: https://bugfest-kiwi.folio.ebsco.com/inventory?qindex=querySearch&query=title%3DTaishun%20ding%20bu%20long%20and%20id%3D%2A%20NOT%20discoverySuppress%3D%3Dtrue%20NOT%20holdingsRecords.discoverySuppress%3D%3Dtrue&segment=holdings&sort=title

 

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

4

Checklist

hide

TestRail: Results

Activity

Show:

Mike TaylorDecember 17, 2021 at 10:01 PM

Wait ... you closed this because it's not a UI issue? But it's not filed as one, it's filed in MODINV. And it's certainly not resolved.

AnyaDecember 13, 2021 at 3:16 PM

this is not an UI issue - tracked on zf-60 

Marc JohnsonDecember 13, 2021 at 3:03 PM

(on behalf of the Support SIG)

Given that this issue represents the incorrect exclusion of instances based upon suppressed holdings challenge and that is considered a low priority (as it was raised as part of investigating the more pressing challenge), can this issue be updated with a lower priority and removed from the Support SIGs agenda?

Mike TaylorDecember 10, 2021 at 11:47 AM

Nothing here looks wrong to me.

Philip RobinsonDecember 9, 2021 at 3:08 PM

 you summarized everything very well. Thanks for helping sort this out!

Won't Do

Details

Assignee

Reporter

Labels

Priority

Sprint

Development Team

Prokopovych

Affected Institution

Cornell
TAMU

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created September 24, 2021 at 3:42 PM
Updated December 6, 2023 at 10:52 PM
Resolved December 13, 2021 at 3:16 PM
TestRail: Cases
TestRail: Runs