Thanks for the questions!
We don't have a clear idea yet and we are looking for a system now. The basic idea is that we'll deposit some licensed materials for some department and open them only to that group. I guess a local account would be ok, of course, if a campus account can be recognized, that's better. They'll need to log in to see the document if it's not ip restricted, right? IP restriction might not be the best way since faculty members will not always be in their departments.
From: Code for Libraries [[log in to unmask]] On Behalf Of Mark Jordan [[log in to unmask]]
Sent: Wednesday, October 20, 2010 5:08 PM
To: [log in to unmask]
Subject: Re: [CODE4LIB] DL Systems (allowing search within documents and access restrictions)?
It might help some of us on the list to understand what types of access control you need if you can describe some of the ways that the allowed users (people and/or departments, to use your examples) will identify themselves? Will they have already logged into the system with a local (to the system) account, or with a campus account that knows that they are part of a specific department? Will they need to log into he system when they request to see a specific document? Will where they are sitting matter (i.e., restricted by IP address)?
Head of Library Systems
W.A.C. Bennett Library, Simon Fraser University
Burnaby, British Columbia, V5A 1S6, Canada
Voice: 778.782.5753 / Fax: 778.782.3023 / Skype: mark.jordan50
[log in to unmask]
----- Original Message -----
> Thanks for the information!
> Greenstone has full text search, but I heard that its access control
> is much weaker than DSpace. Will it be able to allow certain documents
> open only to certain people or certain departments?
> From: Code for Libraries [[log in to unmask]] On Behalf Of Bill
> Janssen [[log in to unmask]]
> Sent: Wednesday, October 20, 2010 4:31 PM
> To: [log in to unmask]
> Subject: Re: [CODE4LIB] DL Systems (allowing search within documents
> and access restrictions)?
> Deng, Sai <[log in to unmask]> wrote:
> > For access restriction, I mean we would like to have certain
> > documents
> > open only to certain communities (UpLib cannot do that, right?).
> OK, that's not I typically think of when I hear "DRM". "Access
> is (I think) the way it's usually put.
> No, UpLib has no built-in access control system, though the hooks are
> there, and I know that some have used them to do access control. I
> of one UpLib application which requires incoming connections to
> a client certificate, which it uses to give different clients
> access rights. Probably overkill for most uses.
> You'd probably want to do an application-specific Web UI, though --
> could put the access restrictions there. I recently saw a Tomcat app
> which uses the UpLib Java client-side library to search for documents,
> then provided a completely custom UI.
> > On second thought, I searched for "DSpace full text search" and
> > found
> > this:
> > https://wiki.duraspace.org/display/DSPACE/Configure+full+text+indexing
> > However, I haven't seen any instance which shows the full text
> > search
> > results as I would see from vendor databases.
> > Any idea on what system might be good/best for search within
> > documents and DRM?
> How about Greenstone?