To the great DSpace programming gods,
The documentation on the GROUPS authorization is a little vague, so
here's the
question:
Is it necessary to create new groups to create a collection policy
that allows someone
to upload/delete bitstreams to a particular record? People can edit
metadata, but not
necessarily change the bitstreams.
If so, creating a new group, such as BITSTREAM_39_EDIT would be
appropriate?
How about a BUNDLE_39_EDIT would be appropriate?
I've got users who need to update a record with more bitstreams or
delete a bitstream
and cannot do this.
TIA,
Jeff
Jeffrey Trimble
Systems Librarian
Maag Library
Youngstown State University
330-941-2483 (Office)
[EMAIL PROTECTED]
http://www.maag.ysu.edu
http://digital.maag.ysu.edu
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
