Suppressing Alma Records from Primo VE

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

How to Suppress Alma Records from Primo VE

You can suppress Alma records from discovery in a number of different ways.

Suppress All Records at a Physical Location

You can suppress all records at a physical location by selecting the Suppress from Discovery checkbox for a location. For more information, see Editing a Physical Location.

If the external location name or Suppress from discovery status has been changed:

For Primo, you must republish the set of physical titles related to this location.
For Primo VE, you must re-index the set of records using the Recalculate Local Resource Types Job (see Manual Jobs).

Manually Suppress an Individual Record in Alma

You can suppress an individual record by selecting the Suppress from Discovery option for the holdings or bibliographic record in the MD Editor. For more information, see Navigating the MD Editor Page. Note that suppression takes effect even without saving the record.

Suppress a Set of Bibliographic Records

You can suppress a set of bibliographic records. See Manual Jobs for more information.

Suppressing a record in the NZ (Network Zone) does not automatically suppress a record that is linked to it in the IZ (Institution Zone). If you want local records to be suppressed from discovery, you must suppress them in the IZ.

Exclude Resources with Specific Process Types

You can exclude resources with specific process types. See Excluding Resources with Specific Process Types from Publishing.

Logical Suppression of Records in Discovery

You can suppress discovery of a record under the following conditions:

When suppressBibWithDeletedHol is set to true in the Customer Parameters mapping table (Configuration Menu > Resources > General > Other Settings), the bib record is suppressed if all holding records were deleted by the operator. Note that bibliographic records that never had holdings are not suppressed from publishing by this parameter (see Configuring Other Settings).
When suppressBibWithSuppressedHol is set to true in the Customer Parameters mapping table (Configuration Menu > Resources > General > Other Settings), the bib record is suppressed if all holding records were suppressed by the operator (see Configuring Other Settings).
When logical_suppress_no_avail_inventory is set to true in the Customer Parameters mapping table (Configuration > Discovery > Other > Customer Settings), the bib record is suppressed from discovery in PrimoVE if it does not have any available inventory and does not have relations to other bib records. This applies regardless of the suppress status in Alma (eye icon) or the workflow that deleted/deactivated a resource. The suppression is logical - the Alma suppression indication does not change. (See also Discovery Customer Settings).

The existing Primo VE logic of scope definition (avail_e/avail_p/avail_d) is used to determine Available inventory as follows:
- Physical inventory availability - If there are items or holding records (if suppressBibWithSuppressedHol is set to true, suppressed holding records will be considered as no available inventory as well.)
- Electronic inventory availability - If there are active portfolios, or if it is a descriptive record of an electronic collection
- Digital inventory availability - If there are active non-Auxiliary representations
In a network, you need to set the logical_suppress_no_avail_inventory parameter to true in all members and in the network institution. The Network Zone title is only suppressed if:
- None of the bibs in the Institution Zone and the Network Zone have available inventory
- None of the bibs in the Institution Zone and the Network Zone have relations
When the value of logical_suppress_no_avail_inventory is changed, re-indexing must be performed.

Differences between the Parameters

suppressBibWithDeletedHol and suppressBibWithSuppressedHol support specific cases of "no inventory", while the logical_suppress_no_avail_inventory parameter covers all "no inventory" scenarios as described above.
The logical_suppress_no_avail_inventory parameter does logical suppression only if the bib record does not have relations, while suppressBibWithDeletedHol and suppressBibWithSuppressedHol do logical suppression regardless of whether the bib record has relations or not.
If suppressBibWithDeletedHol and suppressBibWithSuppressedHol are true, as well as logical_suppress_no_avail_inventory, then all cases covered by suppressBibWithDeletedHol and suppressBibWithSuppressedHol are still considered, as well as the additional scenarios. However, logical suppression will be done only if the bib record does not have relations.
Institutions that already have suppressBibWithDeletedHol & suppressBibWithSuppressedHol on, should turn on the new parameter only if:

They want all scenarios to be covered and...
...they want the logical suppression to be done only if the bib record has no relations.