On Thu, Apr 29, 2010 at 03:04:36PM -0500, Dorothea Salo wrote: > > I’ve given Add, Write, and Remove rights to the submitter and I also > > included the submitter as part of the Collection Administrators. I even > > tried the wildcard policy admin tool. But the submitter still cannot > > remove/edit the bitstreams. Is this an expected behavior? Any help will be > > much appreciated!! > > Expected, though in my opinion wrongheaded, behavior. No one under the > rank of Administrator in DSpace can remove or alter bitstreams. > > DSpace has a superlatively overoptimistic idea of the human capacity > for perfection on the first try...
Well, given the purpose for which DSpace was built, I think it makes sense to have embodied the policy that it's better to keep too much (temporarily) than to lose anything at all, or that you should have to explain the problem to someone else before something can be removed. However, it should be possible to alter (default) policy. Maybe it's time to step back and review how authorization is done throughout the product. -- Mark H. Wood, Lead System Programmer [email protected] Balance your desire for bells and whistles with the reality that only a little more than 2 percent of world population has broadband. -- Ledford and Tyler, _Google Analytics 2.0_
pgpnMxO09GEUZ.pgp
Description: PGP signature
------------------------------------------------------------------------------
_______________________________________________ Dspace-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-general
