[OAI-implementers] Question about sets

[Thomas G. Habing]

Agreed.  In our case, the harvested OAI records can eventually become 
disassociated from the OAI request that was used to harvest the record. 
  In other words, we won't know if a record resulted from a harvest of a 
particular set or not, but we hope that we can count on the setSpec in 
the header to identify to which sets a particular record belongs, and we 
often do use this information to control how we process records.

Tom

Simeon Warner wrote:
> 
> I think so too:
> 
> http://www.openarchives.org/OAI/2.0/openarchivesprotocol.htm#Set
> ...
> When a repository defines a set organization it _must_ include set 
> membership information in the headers of items returned in response to 
> the ListIdentifiers , ListRecords and GetRecord requests.
> ...
> 
> Cheers,
> Simeon
> 
> On Sun, 12 Feb 2006, Chris Wilper wrote:
>> Hi Dean,
>>
>> I believe if sets are supported, the expectation is that the response
>> contains all relevent setSpec elements for each record.  So if an item 
>> is a
>> member of two sets, and a request specifies a specific set, the returned
>> record would still need to list both.  That's how I've always 
>> interpreted it.
>>
>> Cheers,
>> Chris
>>
>> -----Original Message-----
>> From: oai-implementers-bounces at openarchives.org on behalf of Cummins, 
>> Dean
>> Sent: Sun 2/12/2006 10:15 PM
>> To: oai-implementers at openarchives.org
>> Subject: [OAI-implementers] Question about sets
>>
>> Hi all,
>>
>>
>>
>> I wish to use sets (setspec etc), however is it mandatory to include
>> this with all metadata elements, even if that page was called with the
>> setSpec tag? (thus it would be just informing the user about what it
>> already knows - that the resource is part of a specific setSpec).
>>
>>
>>
>> Just after some clarification,
>>
>>
>>
>> Dean
>>
>>
>> **********************************************************************
>> This message is intended for the addressee named and may contain
>> privileged information or confidential information or both. If you
>> are not the intended recipient please delete it and notify the sender.
>> **********************************************************************
>>
>>
> 
> _______________________________________________
> OAI-implementers mailing list
> List information, archives, preferences and to unsubscribe:
> http://www.openarchives.org/mailman/listinfo/oai-implementers
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: thabing.vcf
Type: text/x-vcard
Size: 319 bytes
Desc: not available
Url : http://openarchives.org/pipermail/oai-implementers/attachments/20060213/3f152b74/thabing.vcf