[OAI-implementers] User Specific Archive Access

[Tim Brody]

Hi,

If I understand your problem as follows (e.g.):

An article in Journal "XML Matters" appears in 2003. User "John" has
complete access to the journal and harvests the article in 2003. User
"Daisy" has access only after one year, so in 2003 is harvesting articles
from 2002. But when Daisy asks for new articles in 2004 she won't get the
article from 2003 because she is using the datestamp ">=2004".

I think the solution to this is to change the datestamp in the user's OAI
request to be datestamp-(user's period before access), e.g.
In 2003 Daisy requests all records >=2003 - (1 year delay) = return all
records >=2002

Before any records are returned to the user you will need to check their
rights to that record (in a journal they are subscribed to, date of the
article appropriate to their subscription).

I've written this as I've worked it out, so please excuse any mistakes!

All the best,
Tim.

----- Original Message -----
From: "Michael Krot" <krot@umich.edu>
To: <oai-implementers@oaisrv.nsdl.cornell.edu>
Sent: Tuesday, April 22, 2003 1:40 PM
Subject: [OAI-implementers] User Specific Archive Access


> Hi.
>
> I am in the beginning stages of architecting an implementation of OAI
> that will provide user-specific access to our archives and was wondering
> if anyone knew of any other projects that have tackled this issue.
>
> As far as background information, we are an archive with about 400
> journal titles and millions of records.  Users will only be able to
> harvest metadata for those journals that they have subscribed to - that
> should be a problem I can handle.  Things get tricky when we start to
> look at what is available WITHIN the journal.  Some users will have
> access to the entire journal from start to finish, other users will only
> have access to records up until a certain year (usually 5 years before
> the present year).  This isn't so hard to manage either, until you start
> to think about a user asking for new or changed content.  What is "new"
> or changed will be different for each harvester, depending on their
> access rights.
>
> One possible solution to this problem is to simply give them the
> metadata and flag it as being unavailable in some way, but this is not
> an ideal solution.  An ideal solution is to restrict access to the
> metadata until such time as they are permitted to harvest it.
>
> Well, I don't expect anyone else to have encountered this specific
> problem, but if anyone has experimented with limiting access to an
> archive for specific users or user-groups, I would love to know about it.
>
> Thanks!
> Michael Krot
> Data Manager
> JSTOR
>
> _______________________________________________
> OAI-implementers mailing list
> OAI-implementers@oaisrv.nsdl.cornell.edu
> http://oaisrv.nsdl.cornell.edu/mailman/listinfo/oai-implementers