[OAI-implementers] Open Archives Initiative Protocol for Metadata Harvesting Version 2 news

ePrints Support support@eprints.org
Tue, 5 Feb 2002 09:36:57 +0000


OK. This all sounds sensible. Maybe openarchives.org could have the
"bare minimum howto" which tells you how to neatly do the bare minimum to
support the protocol. 

The next version sounds like it will be more complex, but that complexity
will be optional. 

We should make it clear to people "checking it out" that it's easy to meet
the minimum requirements.

Is there a plan to add some more characters to the setSpec regexp? Preferably
everything other than ":" or near enough.

thanks, Chris G / eprints.

On Mon, Feb 04, 2002 at 11:22:37PM -0500, Simeon Warner wrote:
> 
> On Mon, 4 Feb 2002, Josie Imlay wrote:
> 
> > I was thinking that on the sets being optional it would make more sence
> > if a particular archive does not want to use sets for their to be a
> > standard responce, or way to handle this.
> 
> The standard way to say 'I do not implement sets' is a to list no
> sets in the ListSets response.
> 
> > To me the way to do this is to make sets manditory, but say that if you
> > don't want to use them then just have one set called "all" or something.
> > This is hardly makes it any more dificult from the standpoint of the
> > developer because he can just have a static responce. But from the
> > harvester that's programmed to deal with sets, it doesn't even notice
> > that there is a difference.
> 
> no setSpec => universal set => all records
> 
> Consider two cases where a harvester might want to use sets:
> 
> 1) to harvest part of a repository. This requires prior (outside the
> protocol) knowledge of the set structure and hence the set or sets to be
> harvested cannot be determined automatically.
> 
> 2) to mirror/harvest the whole repository including the set structure. In
> v1.1 it is necessary for a harvester to harvest from all sets and from the
> universal set (no setSpec) to be able to deduce the set structure. In v2
> all records will include set membership information so it will be
> only be necessary to harvest the universal set.
> 
> Cheers,
> Simeon
> 
> 
> _______________________________________________
> OAI-implementers mailing list
> OAI-implementers@oaisrv.nsdl.cornell.edu
> http://oaisrv.nsdl.cornell.edu/mailman/listinfo/oai-implementers

-- 

 Christopher Gutteridge                   support@eprints.org 
 ePrints Developer                        +44 23 8059 4833