lib-ir: a couple of dspace notes

["JQ Johnson" <jqj@darkwing.uoregon.edu>]

1/ both communities and collections must be created by a dspace
administrator.  Policies (i.e. the groups associated with various
actions) must also be created by an administrator.  So there isn't much
decentralization of control yet.  I imagine that the only
decentralization we'll have will be a group of community-admins for each
community, and that we'll add that group as an approval step in most
collection workflows.

2/ when you create a collection, make sure to also create a
corresponding group of submittors for the collection, and give that
group ADD privileges for the collection.  The DSpace documentation
strongly recommends that you name the new group
	COLLECTION_nn_ADD
where nn is the collection number.  See
http://ir.uoregon.edu/dspace-docs-1.1-1/admin-ui.html#groups
You can leave the group empty for now if you want, in which case only
administrators will be able to add items to the collection.

3/ various annoyances with the user interface.  For example, the
submission process presents a list of all collections on the system, not
just the list of collections which you have ADD access to.  This will
confuse people when we get a lot of collections, and suggests that the
names of collections should be globally unique (rather than just unique
within a community).

JQ Johnson                    	Office: 115F Knight Library
Academic Education Coordinator	e-mail: jqj@darkwing.uoregon.edu
1299 University of Oregon     	1-541-346-1746 (v); -3485 (fax)
Eugene, OR  97403-1299        	http://darkwing.uoregon.edu/~jqj