Andrea, >> My need is pretty simple: for a given collection, a list of >> authenticated users can post, > > Create a group, say "Submitters collection A" > Add all users who should be able to submit to collection A to this group > Add this group to the "Submitters" role for collection A > >> but the item should be kept invisible >> until a riviewer has edited/accepted it. The list of reviewers is also >> collection dependant. > > Create a group, say "Approvers collection A" > Add all users who should review items for collection A to this group > Add this group to the "Approve/reject/edit metadata" role for collection A > > Technically, the two groups are not needed (you can add the users > directly to the roles) but if several collections share the same groups > then this approach is easier to manage in the long run. > > The wording may be a little different, especially for JSPUI. > > You might also like to review the DSpace Course module on item > submission workflows, see http://hdl.handle.net/2160/628 -- the material > is a few years old but the fundamental concepts haven't changed since then.
Thanks a lot, that's exactly what I wanted to acheive. When reading DSpace doc, I though some programming was needed, while it is enough to provide the right values to the right parameters and the underlying mechanism is already available. Best regards, Olivier ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Dspace-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-general
