As I understand it, authorization is item specific. Now, if you set up a
collection and you give say read permissions to bitstreams to a certain
group of epeople, then when items are submitted to the collection, the items
will inherit these permissions, and if you change the permissions on the
collection, the items in the collection retain the permissions they had, but
any items deposited from then on will inherit the permissions new
permissions.
The out of the box DSpace does not allow you to setup permissions based on
IP, but there is a patch that can help with this ( I think ). What the
patch basically does is determine the ip address of the item and then based
on this makes the user a member of a group that you need to have setup to
have permissions for the items. This membership is carried on the context
and expires when the user ends the session.
-Jose
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Eric Luhrs
Sent: Friday, April 20, 2007 11:08 AM
To: DSpace-tech@lists.sourceforge.net
Subject: [Dspace-tech] granularity of authentication for undergrad theses
Hello all,
Lafayette College is in the planning stages for a DSpace repository.
While our planning team (which includes a few faculty members) is
interested in providing public access to undergraduate honors theses,
some other faculty members have expressed concerns. In looking at
permission forms used by other institutions, I see that students are
often given a choice of the level of access they desire: world,
on-campus, or none.
This, for me, raises questions about the granularity of
authentication. I had thought that authentication was controlled at
the collection level, but now I wonder if it can be controlled at the
item level. So far, I have only installed an open system with no
authentication, so I'm in uncharted water.
My questions: Is it possible to have a single collection that
provides open access to certain documents, and IP or LDAP restricted
access to others? If this level of granularity is possible, is it
difficult to implement? Do others have advice for dealing with these
issues (either politically, and technically)?
Thanks for whatever help you can provide.
Eric Luhrs
Digital Initiatives Librarian
Lafayette College
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
