import profiles -- need the option to leave suppression codes "as is"
When creating an import profile, the “set management tags” option is to either suppress record/s from publish/delivery, or to not suppress. This is for the entire file.
We need a third option to leave the existing suppress status unchanged for replaced and merged records. (We had this option in Voyager, and it worked well)
Rational: All GPO weekly brief Marcive records are loaded suppressed. When the monthly bib records overlay the weekly brief records, the suppress status needs to remain as is. “If” the bib record is suppressed, the cataloger will unsuppress at the point of cataloging
mcorby
shared this idea
-
Karl Lehtonen
commented
we have had so many issues with this, and found it to be a poorly implemented concept over all. would love the option in import profiles to retain existing suppression status.
-
Lynne Billington
commented
YES. We export records out of Alma to globally update them and then re-import them but we don't want the suppression tag to change, either all suppressed or all unsuppressed, we want them to just stay the same as they were already.
-
Stacie Traill
commented
We would like this option, as well. We frequently pull batches of records out of Alma for external enhancement, and it's necessary to create an itemized set of all records in the original set that were suppressed before overlaying with the enhanced versions, so that the right records can be re-suppressed after the import job runs. This is a lot of extra steps we'd like to avoid.