Skip to main content
ExLibris

Knowledge Assistant

BETA
 
  • Subscribe by RSS
  • Back
    Aleph

     

    Ex Libris Knowledge Center
    1. Search site
      Go back to previous article
      1. Sign in
        • Sign in
        • Forgot password
    1. Home
    2. Aleph
    3. Knowledge Articles
    4. The OWN check doesn't block a Total Delete

    The OWN check doesn't block a Total Delete

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    No headers
    • Article Type: General
    • Product: Aleph
    • Product Version: 20

    Description:
    If you bring up a bib record that has an OWN different from the OWN of the signed in user, you should not be allowed to change or delete the record. If you push the record back to the server or click on "Delete Record from Server" the user is blocked from doing the requested action.

    BUT, if the user clicks on "Total Delete" under the "Record Manager" tab, the Total Delete proceeds without checking to see if the OWN of the bib matches the OWN of the logged in user. This is a serious hole in record protection on consortium servers.

    Resolution:
    Corrected by:

    v20 rep_change 3297
    v21 rep_ver 17088


    • Article last edited: 10/8/2013
    View article in the Exlibris Knowledge Center
    1. Back to top
      • The links sent by email have incorrect addresses
      • The page cannot be displayed" in trying to connect to the www_server
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Language
      English
      Product
      Aleph
    2. Tags
      1. 20
      2. contype:kba
      3. Prod:Aleph
      4. Type:General
    1. © Copyright 2025 Ex Libris Knowledge Center
    2. Powered by CXone Expert ®
    • Term of Use
    • Privacy Policy
    • Contact Us
    2025 Ex Libris. All rights reserved