| Page Properties | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Background
The manner in which records are suppressed can affect collection analysis, statistics and may affect the way it displays discovery in Primo.This policy addresses methods to minimize the impact of bib suppression on the above.
Policy Statement
In a shared network environment, CSU libraries should suppress records at the holdings level only, not at the bibliographic level.
Suppress bibliographic records at the holdings level for several reasons:
...
Holdings-level suppression does not adversely affect collection analysis and statistics, but
...
achieves the same ends.
Once implementation is complete,
...
To suppress at the holdings level, open the holdings record in the Metadata Editor. Select Tools > Set Management Tags > and Suppress from Discovery.
If a library’s last copy is withdrawn, the bib record should be unlinked from the NZ using the “Copy to catalog” function in Alma. Then the record may be suppressed in the IZ at the bib level or deleted.
Host bibliographic records for bound-withs in a library’s IZ should be suppressed. Suppression of these records at the bib level helps reduce confusing displays in Primo.
Procedures in Alma
Navigating the MD Editor Pagethis policy should be revisited
Procedures in Alma
Action log
| Section | Point Person | Expected Completion Date | Last action taken | Next action required |
|---|---|---|---|---|
Articulate the need for the policy (background) | Cataloging Task Force |
| Needed policy to mandate methods for suppression of records for physical inventory | To be discussed with the TS Working Group. |
Finalize Policy Statement | Cataloging Task Force |
| ||
Revised | Cataloging Task Force | | ||
Where applicable, identify and write up procedures in Alma | Cataloging Task Force |
|