You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once an item is live it should not be removable (only retireable). If you remove an item that have been live even if it has previously been retired it can effect third-party application trying to sync metadata user OAI-PMH. It may also have impact on other aspects of EPrints, especially involving export.
It maybe should still be possible to remove (once) live items but this should be very difficult. E.g. require a permission that even admin users do not have by default. Also when an admin with this advanced permission tries to remove an item (once) live they should receive a much more strict warning about the consequences of removing such an item.
The text was updated successfully, but these errors were encountered:
RequestRemoval already includes in its intro "Please note that we strongly discourage removal of items from the repository". So I don't think there is a need to add anything further to this page.
I think my latest commit meets the requirements discussed. I have added info about the new permission being required to explain why "Destroy Item" will not be an option for some items on the review page, if they have previously been live. However, I cannot think of anywhere appropriate to make repository admins more generally aware of this and how they might re-enable such a permission. I can already imagine frantic emails on the tech list saying: "I cannot remove item X that has confidential information in it."
Once an item is live it should not be removable (only retireable). If you remove an item that have been live even if it has previously been retired it can effect third-party application trying to sync metadata user OAI-PMH. It may also have impact on other aspects of EPrints, especially involving export.
It maybe should still be possible to remove (once) live items but this should be very difficult. E.g. require a permission that even admin users do not have by default. Also when an admin with this advanced permission tries to remove an item (once) live they should receive a much more strict warning about the consequences of removing such an item.
The text was updated successfully, but these errors were encountered: