Permission vs System preference
We are interested at some point in a development that would hide the "Edit items in batch"; "Delete items in batch"; and "Delete all items" options in the Edit menu of the detail.pl page through either a user permission or a system preference. It was suggested I contact the developers list to see what community developers think about this as a permission vs system preference. In our consortial environment, these are not good features to have available to anyone. Right now we have these options hidden through some hardcoding, but of course this has to be added manually after every upgrade by our support vendor. Any thoughts/input would be greatly appreciated. Thanks, Heather Braum Digital and Technical Services Librarian Northeast Kansas Library System hbraum@nekls.org "The illiterate of the 21st century will not be those cannot read and write, but those who cannot learn, unlearn, and relearn." ~Alvin Toffler, *Rethinking the Future*
Hi, On Wed, Jul 31, 2013 at 12:33 PM, Heather Braum (NEKLS) <hbraum@nekls.org>wrote:
We are interested at some point in a development that would hide the "Edit items in batch"; "Delete items in batch"; and "Delete all items" options in the Edit menu of the detail.pl page through either a user permission or a system preference. It was suggested I contact the developers list to see what community developers think about this as a permission vs system preference.
I'm in favor of permissions (and also a little confused) because ... two of those menu options are already protected by permissions, specifically tools/items_batchdel and tools/items_batchmod. There is no permission (other than the general permission that grants the ability to edit items) guarding the 'Delete all items' permission, but I think it would be reasonable to add one or two, perhaps along the lines of: editcatalogue/delete_items editcatalogue/delete_all_items Regards, Galen -- Galen Charlton Manager of Implementation Equinox Software, Inc. / The Open Source Experts email: gmc@esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org
On Wed, Jul 31, 2013 at 4:43 PM, Galen Charlton <gmc@esilibrary.com> wrote:
Hi,
On Wed, Jul 31, 2013 at 12:33 PM, Heather Braum (NEKLS) <hbraum@nekls.org>wrote:
We are interested at some point in a development that would hide the "Edit items in batch"; "Delete items in batch"; and "Delete all items" options in the Edit menu of the detail.pl page through either a user permission or a system preference. It was suggested I contact the developers list to see what community developers think about this as a permission vs system preference.
I'm in favor of permissions (and also a little confused) because ... two of those menu options are already protected by permissions, specifically tools/items_batchdel and tools/items_batchmod.
There is no permission (other than the general permission that grants the ability to edit items) guarding the 'Delete all items' permission, but I think it would be reasonable to add one or two, perhaps along the lines of:
editcatalogue/delete_items editcatalogue/delete_all_items
As Galen points a real solution is to have permissions, but as a workaround you could try to hide those options using intranetuserjs system preference, with this code $(document).ready(function(){ var itemlinks = $("a:contains('Edit items in batch'),a:contains('Delete items in a batch'),a:contains('Delete all items')"); $(itemlinks).hide(); }); As this value is stored in the database, you don't need to change anything after an upgrade, unless the text in the options change, then you will only need to update the syspref. Only a workaround. Regards, Bernardo -- Bernardo Gonzalez Kriegel bgkriegel@gmail.com
participants (3)
-
Bernardo Gonzalez Kriegel -
Galen Charlton -
Heather Braum (NEKLS)