FW: Delete duplikaat ETD asb

17 views
Skip to first unread message

Van der Westhuizen, Ansie

unread,
Apr 16, 2021, 10:16:43 AM4/16/21
to DSpace Community, Esterhuyse, Karen, Vierbergen, Marcel

Dear Colleagues

 

We are using Dspace 6.3.  I have created a group with admin rights in DSpace for our Cataloguers, who are responsible for uploading, QA and editing of items in the UnisaETD collection. Occasionally they have to delete duplicate items. It has now been reported that they are no longer able to delete items. I would like to know if this is a default setting of the system and if there is a way to customise the system to provide the right to collection level rights for collection administrators to delete items if necessary.

 

Your advice would be much appreciated.

 

Kind regards

 

e-mail-sig-photo

 

e-mail-sig-logo2

Ansie van der Westhuizen

Non-Commercial Digital Developer (Institutional Repository)

Department of Library Services

vdwe...@unisa.ac.za

 

 

 

            e-mail-sig-F    e-mail-sig-TW    e-mail-sig-L    e-mail-sig-Y     

http://www.unisa.ac.za

 

 

 

 

 

 

Authorization denied for action OBSOLETE.docx

FILIPPOS KOLOVOS

unread,
Apr 16, 2021, 1:18:37 PM4/16/21
to Van der Westhuizen, Ansie, DSpace Community, Esterhuyse, Karen, Vierbergen, Marcel
Dear Sir/Madam,

From the error message, I see that it is the BITSTREAM that hinders the deletion of the item from the community/collection administrators. If an item does not have any bitstreams but just metadata, then the community/collection admin can delete it. 

This is a known bug in dspace 6.3, where if a user is a community or a collection administrator (and not a FULL administrator of the whole repository) cannot delete the bitstreams of the items, even though he should be able to, resulting in failure to delete the whole item. There are two ways to solve this problem. 

You can implement the code mentioned in the bug and recompile DSpace, or you can replace the BundleServiceImpl.class I am sending you with the class located in the directory of your running dspace instance. This will probably be in /dspace/webapps/jspui/WEB-INF/classes/org/dspace/content/BundleServiceImpl.class, if you use JSPUI, or in /dspace/webapps/xmlui/WEB-INF/classes/org/dspace/content/BundleServiceImpl.class if you use XMLUI. Normally, the dspace running directory is located in /dspace, otherwise you must find it manually and replace the class in the corresponding directories.

Restart tomcat and you will be good to go.

Nevertheless, take care to keep a backup of the files you will replace, just in case. The compiled class I am sending you is for DSpace 6.3

I hope that this helps you.

Best Regards,

-Fk

--
All messages to this mailing list should adhere to the Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups "DSpace Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dspace-communi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-community/AM0PR01MB518665A1F8E9EC8FC4EDE8378B4C9%40AM0PR01MB5186.eurprd01.prod.exchangelabs.com.
BundleServiceImpl.class
Reply all
Reply to author
Forward
0 new messages