Assumptions/Questions

• Vendor will supply one METS file per "master" oral history session & one METS file per "rendered" oral history session.
  
• The METS file will include file-level DC metadata, a file list with paths relative to the delivery medium, and a structure map (always unitary)
  
• Currently the vendor is supplying MD5 checksum as a separate file; ok this way?
  
• DC metadata for individual sessions should include "relation" element to link session with parent metadata record; is there an abstracted alternative to a textual description of the parent object?

1.  Proposed File & Metadata Delivery Bundle (path & file names relative to delivery media)

2.  Sample DC Elements for Master Record for Oral History Interview

NB: Vendor has only this limited bibliographic information from us.

<dc:creator>Baldwin, James</dc:creator>
<dc:title>Reminiscences</title></dc:title>
<dc:relation>Collection: Biographical Interviews</dc:relation>
<dc:identifier>CLIO: 4077385</identifier>
<dc:type>Sound</dc:type>

3.  Schematic METS File for Single Session

<mets>
 <dmdSec>
  <mdWrap>
    <xmlData>
      <dc:creator>Baldwin, James</dc:creator>
      <dc:title>Session 1 of 4</dc:title>
      <dc:identifier>CLIO: 4077385</dc.identifier>
      <dc:identifier>Project: 6a</dc:identifier>
      <dc:date>1963-10-09</dc:date>
      <dc:relation>Baldwin, James. Reminiscences</dc:relation>
    </xmlData>
   </mdWrap>
 </dmdSec>

 <fileSec>
  <fileGrp ID="Master">
    <file ID="Baldwin_James_4077385_01_m.wav" MIMETYPE="audio/x-wav">
    <FLocat LOCTYPE="OTHER">Baldwin_James_4077385/Master/Baldwin_James_4077385_01_m.wav
    </Flocat>
    </file>
    <file ID="Baldwin_James_4077385_01_m.md5" MIMETYPE="text/plain">
    <FLocat LOCTYPE="OTHER">Baldwin_James_4077385/Master/Baldwin_James_4077385_01_m.md5
    </Flocat>
    </file>
  </fileGrp>
 </fileSec>

 <structMap>
   <div ID="Master">
   <fptr FILEID="Baldwin_James_4077385_01_m.wav" />
   <fptr FILEID="Baldwin_James_4077385_01_m.md5" />
   </div>
 </strucMap>
</mets>