Please add the "suppress bibliographic record" to the log of the "view versions" in the MD editor
Hello,
We would like to have the ability to know when and by whom a bibliographic record was suppressed, when checking the "view versions" in the MD editor.
Thanks.
Dafna
-
Dear all, I would like to update on our planned solution:
Starting with the release of this feature, when a record's management tag is changed, a version will be created to show this change. Restoring a previous version will continue to only restore the metadata itself, and not impact other information shown in the versions (such as cataloging level or management tags).Please note - record versions created before this change will have a null value for all management tags. The management tags' values will only be recorded when the record is next updated in any way, and start showing in the next version (that will be created for that update). It may therefore appear as though the user making the first update following the release of this feature updated the management tags from null to their current value.
-
Carol commented
History would be nice - Who last touched the record.
-
Jung Ah Lee commented
I was just looking into ways to track suppression history of bib records too and I just voted for the idea.
-
Patricia Farnan commented
Gave it a vote - good idea!
-
Katrina Beaudoin commented
Just ran into an issue with a suppressed record and wondered if there was any plan for tracking the changes. Thank you!
-
Lara Corazalla commented
I agree this would be useful. There's a similar idea with a lot of votes here: https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/43286817-please-add-the-suppress-bibliographic-record-to
-
Dean Lingley commented
Been wanting this for awhile too!
-
François Renaville commented
This would indeed be helpful! Thanks for submittig this idea!
-
Elizabeth York commented
In Alma, automated processes and jobs can suppress and unsuppress bibliographic records. It is also possible to suppress and unsuppress individual bib records using the metadata editor. However, Alma does not track the history of record suppressions and unsuppressions.
This means that when we come across an incorrectly suppressed record in Alma, we have no way to determine when it was suppressed and what job (or which Alma user) suppressed it. This makes it more difficult to correct workflow problems and monitor automated processes that may be acting in unexpected ways.
This idea proposes that Alma should track bibliographic record suppressions and unsuppressions. Each suppression event should include the date and time and the identifier of the job/process or Alma user who suppressed the record.
-
Chris Sloan commented
I would like to vote for this, but currently out of votes. It's something we've been missing since migration in 2013.
-
Anonymous commented
I support!
-
Ruhama Amouyal commented
I support the idea.
It can be indicated as a separate record of versions.