|
||||||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||||||
------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
_______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
Based on the configs available in the "Delegate Admin" section of dspace.cfg, it looks as though the "Delegate Admin" concept initially assumed you could only delete an object if you were an Admin of its *parent* object. Notice the ability to tweak the "delete-subelement" permissions here: https://github.com/DSpace/DSpace/blob/master/dspace/config/dspace.cfg#L349