[Dspace-general] Harvesting OAI dark archive collections

[Scott Yeadon]

Hi Leonie,

To fix this you probably need to provide a filter in the Harvest class 
(inner class or alternative db queries) so that no "hidden" records are 
passed up to the OAI response processing.

Scott.

> Date: Mon, 6 Aug 2007 21:23:47 +0100 (BST)
> From: Clive Gould <clive at ce.bromley.ac.uk>
> Subject: Re: [Dspace-general] Harvesting OAI dark archive collections
> To: dspace-general at mit.edu
> Cc: l.hayes at auckland.ac.nz
> Message-ID: <1312.195.69.92.72.1186431827.squirrel at ce.bromley.ac.uk>
> Content-Type: text/plain;charset=iso-8859-1
>
> Hi Leonie
>
> I was asking myself the same question this afternoon and came across the
> following in the DSpace 1.3.2 documentation.
>
> Best wishes
>
> Clive
>
> "Access control
> OAI provides no authentication/authorisation details, although these could
> be implemented using standard HTTP methods. It is assumed that all access
> will be anonymous for the time being.
>
> A question is, "is all metadata public?" Presently the answer to this is
> yes; all metadata is exposed via OAI-PMH, even if the item has restricted
> access policies. The reasoning behind this is that people who do actually
> have permission to read a restricted item should still be able to use
> OAI-based services to discover the content.
>
> If in the future, this 'expose all metadata' approach proves
> unsatisfactory for any reason, it should be possible to expose only
> publicly readable metadata. The authorisation system has separate
> permissions for READing and item and READing the content (bitstreams)
> within it. This means the system can differentiate between an item with
> public metadata and hidden content, and an item with hidden metadata as
> well as hidden content. In this case the OAI data repository should only
> expose items those with anonymous READ access, so it can hide the
> existence of records to the outside world completely. In this scenario,
> one should be wary of protected items that are made public after a time.
> When this happens, the items are "new" from the OAI-PMH perspective."
>
>
> Message: 1
> Date: Mon, 6 Aug 2007 11:50:26 +1200
> From: "Leonie Hayes" <l.hayes at auckland.ac.nz>
> Subject: [Dspace-general] Harvesting OAI dark archive collections
> To: <dspace-general at mit.edu>
> Message-ID:
>         <A30994AC067CB646AAD4698C727A1A0202F88219 at libex1.lbr.auckland.ac.nz>
> Content-Type: text/plain;        charset="us-ascii"
>
> Hi all
> I am hoping you can help out with a question about limited access
> collections.
>
> We have 2 PhD collections, one is a restricted access PhD collection,
> where only the adminsitrator can access the collection, the users can
> only see the browse by author or title or date, you cannot view the
> metadata record. The reason is we do not have consents for open access,
> or if we have the consents, it is in our backlog and they are waiting
> for processing.
>
> I have been told I need to configure DSpace to limit this, I did quite a
> bit of research to see if you can create your own customised OAI output
> but did not make a lot of progress.
>
> I see there are quite a few sites with collections like ours, Cambridge
> Dark Archive Collection.
>
> Could anyone give me an explanation of how this works and what I need to
> do so end users don't get confused picking up restricted items from the
> harvesters.
>
> Many thanks
> Leonie Hayes
> Project Manager
> Institutional Repositories Aotearoa
> University of Auckland Library
> New Zealand
> www.ira.auckland.ac.nz
>
>
>
>
>
>
>
>
> ------------------------------
>
> _______________________________________________
> Dspace-general mailing list
> Dspace-general at mit.edu
> http://mailman.mit.edu/mailman/listinfo/dspace-general
>
>
> End of Dspace-general Digest, Vol 49, Issue 5
> *********************************************
>
>