Skip to content

How can we improve Alma?

← Alma

Prevent deletion of portfolios with access type perpetual or current plus perpetual

When deleting portfolios individually or through a batch process, add a feature to flag/warn about portfolios with perpetual or current plus perpetual for the access type before they are deleted. It could be similar to the message and process you run into upon trying to delete a portfolio with an active po line or a physical holding with an active po line. My library's portfolios attached to larger collections often do not have PO lines (as much of this work was done in our former library system prior to Alma migration). Adding a perpetual access type to portfolios is relatively easy to do. If tied to deletion prevention, it would help secure content a library does not want to delete. Thanks for your consideration.

134 votes
Vote

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
Jennifer Rusk shared this idea  ·   ·  Admin →
Accepted  ·  AdminLiza Voloshin (Product Owner, Alma Resource Management, Ex Libris) responded  · 

Hi all,

Thank you for supporting this idea and for the constructive comments.

Recognizing how important it is for libraries to preserve owned content, we’re committed to supporting these goals.

Regarding the discussion around CZ-linked owned resources, I’d like to bring a related idea to your attention—one that might help complete the picture. https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/44864398-create-option-to-keep-czutl-deleted-portfolios-act

Show previous admin responses (1)

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Klara Ramnath commented  · 

    1. Preferred behavior: completely block deletion
    2. We generally localize any perpetually licensed portfolios from the CZ. But it would be great if portfolios have a Retention-like feature so you can easily identify at the portfolio-level why you wish to block deletion.

  • Kristen Fredericksen commented  · 

    Maybe it could be a configuration setting. Set it to true if the system should completely block deletion and set it to false if the system should display a warning, but still allow the deletion.

  • Lydia Herring commented  · 

    I agree that portfolios with perpetual access linked to the CZ should be added to a report when they are deleted from the CZ to facilitate evaluation. They can be treated like "portfolios deleted from non auto-delete electronic service" are now. For deletions by a user, it is simpler for the system to display a warning but still allow the deletion if the user affirms that it is correct.

  • Kari Petryszyn commented  · 

    I agree 100% with Erin Loree that the system should block deletion and CZ-linked portfolios should be added to the Community Zone Updates Task List as a new report type.

  • Erin Loree commented  · 

    We would prefer that the system block deletion. For CZ linked portfolios, they should be added to the Community Zone Updates Task List as a new report type.

  • Michelle Weston commented  · 

    I would prefer the behavior: The system completely block deletion (unless the access type is changed).

  • Alicia Morris commented  · 

    I wholeheartedly support this idea. tracking and managing resources to which the library has perpetual access is very difficult right now. We need better ways to retain for the long term this material.

Alma: Resource Management - Electronic

Categories

Feedback and Knowledge Base

(thinking…)