[OAI-implementers] Moving records in and out of sets

[Hickey,Thom]

We are planning to change set names on all the NDLTD theses records we put
up for harvesting to use the MARC Organization codes instead of the ad-hoc
names we have been using so far.  But we don't want to change the ID's
associated with the records and break any links into the repository that
might exist, so I'd say deletion/creation with a new ID might be a cure
worse than the problem it is solving.

I suspect our solution will be to just add additional sets and at some
future date delete the older set names.

--Th

> -----Original Message-----
> From: Alan Kent [mailto:ajk@mds.rmit.edu.au]
> Sent: Tuesday, October 21, 2003 12:29 AM
> To: oai-implementers@oaisrv.nsdl.cornell.edu
> Subject: Re: [OAI-implementers] Moving records in and out of sets
> 
> 
> On Mon, Oct 20, 2003 at 02:06:06PM -0400, Steve Sarapata wrote:
> > I have this exact issue to deal with in the next few weeks. 
> I need to
> > change the <setSpec> value on ~300 records of a ~2700 record set.
> > 
> > Steve
> 
> Best easiest solution I could see was to say records could not change
> their set membership. If they need to, then create a new record with
> a new id.
> 
> Problems arise because records can belong to multiple sets. A 
> harvester
> may collect using two sets from the one repository. 
> Generating 'set update'
> messages or something gets nasty and confusing. I think its better to
> come up with a solution that does not require any additions 
> to the spec
> in terms of new packets etc.
> 
> Maybe another way is to delete then create the item (and hence all
> records derived from that item) so harvesters think the 
> record (with the
> old set membership) goes away first, then comes back to life 
> again (with
> the new set membership).
> 
> Alan
> _______________________________________________
> OAI-implementers mailing list
> List information, archives, preferences and to unsubscribe:
> http://oaisrv.nsdl.cornell.edu/mailman/listinfo/oai-implementers
>