EPrints Technical Mailing List Archive

See the EPrints wiki for instructions on how to join this mailing list and related information.

Message: #08987

< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First

Re: [EP-tech] Return WITHOUT notification

Hi James,

I forgot to mention that you will need to specify that the Screen::EPrint::Remove plugin will need to be set to appear in the eprint_actions_bar_buffer.  E.g.:

$c->{plugins}->{"Screen::EPrint::Remove"}->{appears}->{eprint_actions_bar_buffer} = 1000;

I have compared the 3.4.3 and 3.3.12 codebases and I cannot see anything that would lead to the Remove button being present on 3.3.12 and not on 3.4.3.  As far as I can tell, by default the Remove button should have never been present in the EPrints action bar when an item is under review, only the Remove (with notification) button. 

The Remove button should only ever be able to appear under the eprint's actions tab, the actions next to an eprint on the Manage Deposits page and the eprint's action bar once it is in the live archive.  However, if EPrints is working correctly it should only be able to appear in any of these locations if the user meets the appropriate permission criteria.  Without the +eprint/buffer/remove:editor permission added to the editor/admin user type (as described in my earlier email), even with the above screen plugin configuration, the Remove button will still not appear.

What is baffling for 3.3.12, is that both the Screen::EPrint::Remove plugin does not specify that the Remove button should appear under the eprint's action bar when is under review.  Even if it did there is no user type that has a permission to allow for the Remove button to appear in that location.  Therefore, EPrints 3.4.3 correctly implements where the Remove button should appear.  It also has the further new requirement to add another permission to allow items that are or have been in the live archive to be (completely) removed.

Regards

David Newman

On 29/06/2022 10:43 am, David R Newman wrote:

Hi James,

I think the "remove without notification" got removed by default partly to ensure better traceability, so editors/admins did not delete items without notifying the user but also as this caused button clutter in the actions bar and  also indecision with editors/admins on which option they should use.  You can re-enable this by adding the following two lines to your archive's cfg/cfg.d/user_roles.pl for both/either the of the editor/admin roles:

    +eprint/inbox/remove:editor
    +eprint/buffer/remove:editor

You may need to copy user_roles.pl from flavours/pub_lib/cfg.d/ to your archive, so you can edit an archive specific copy.  Once done, obviously reload your webserver to apply the changes. 

I will endeavour to add this to the known issues at:

https://wiki.eprints.org/w/EPrints_3.4.3#Known_Issues

I should also not that a further feature was added in 3.4.3 to prevent deletion of items that are in or have at some point been in the live archive.  You will need to add the following user role (probably to just specific admin users you trust through their user profile):

    +eprint/remove_once_archived

Regards

David Newman

On 29/06/2022 9:46 am, James Kerwin via Eprints-tech wrote:
CAUTION: This e-mail originated outside the University of Southampton.
Hi All,

Hope everyone is well.

I recently upgraded our Data Repository server and version of EPrints. We have two issues outstanding. One is with Apache mod_status and the other is with emails being sent when returning an item to the work area.

Is there any way to return an item without a notification? I've been away at Glastonbury and had tried quite a bit to sort this before leaving, but was struggling to find where to make changes. This repository is on Ubuntu 20 with EPrints version 3.4.3

Any guidance will be gratefully received!

Thanks,
James

*** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
*** Archive: http://www.eprints.org/tech.php/
*** EPrints community wiki: http://wiki.eprints.org/