Hello, In version 1.6.1 we created a sub-community and a collection in that sub-community. The same persons & group were given Administrative rights to the sub-community and collection. Next we used the batch metadata load to create new records in the collection (therefore these have no attached bitstreams). The Collection Administrators can do everything to the new records (edit metadata, delete the records) except adding a new bitstream. When they attempt to Upload a new bitstream, they receive this message:
"You need the ADD & WRITE privilege on at least one bundle to be able to upload new bitstreams." If we manually create a record and include a bitstream during the submission process, then the collection administrator upload a new bitstream and also delete bitstreams. It appears that if the all the bitstreams are deleted, that person can not then upload a new bitstream. Only full DSpace Administrators can upload bitstreams to "empty" items. This is a real problem, because we envision a workflow where the metadata is batch imported and student-workers/staff then attach the file(s) or bitstreams. (We have the meta-data in another system which easily generates csv files. But that old system was just a 'finding aid' and did not include the bitstreams.) Is there a work around to this issue? Can this be fixed in later releases? Richard Jizba Creighton University ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
