kt3q2nb7vz.profile.xml

<?xml version="1.0" encoding="UTF-8"?>
<METS_Profile xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:noNamespaceSchemaLocation="http://www.loc.gov/standards/mets/profile_docs/mets.profile.v1-0.xsd">
    <URI LOCTYPE="URL">http://ark.cdlib.org/ark:/13030/kt3q2nb7vz</URI>
    <title>EAD DAO* extracted object</title>
    <abstract>Encoded Archival Description provides a mechanism to define objects in is dao and
        dapgrp tags. This profile is for METS object created by a batch extraction process from EAD
        Finding Aids in the Online Archive of California.</abstract>
    <date>2004-03-13T09:40:00-08:00</date>
    <contact>
        <name>Brian Tingle</name>
        <address>California Digital Library; University of California Office of the President; 415
            20th Street, 4th Floor; Oakland, CA 94612-2901</address>
    </contact>
    <related_profile URI="http://ark.cdlib.org/ark:/13030/kt0t1nb6x7">METS for the parent EADs</related_profile>
    <extension_schema>
        <URI>http://findaid.oac.cdlib.org/mets/profiles/2002/OAC-extracted-image/oac-ead.xsd</URI>
        <context>use with xmlns http://www.loc.gov/EAD/</context>
        <note>Right now, this schema just checks that there is a &lt;c&gt; tag. The c, or
            component from EAD, is constructed from EAD tags, but is not valid EAD. [to do,
            construct a schema for "item level EAD", explain how it is created from EAD]</note>
    </extension_schema>
    <extension_schema>
        <URI>http://ark.cdlib.org/schemas/appqualifieddc/appqualifieddc.xsd</URI>
        <context>use with xmlns http://ark.cdlib.org/schemas/appqualifieddc/</context>
        <note>This is a wrapper "application schema" for qualified Dublin Core. It does the schema
            validation for xmlns:dcterms="http://purl.org/dc/terms/" xmlns:dc="http://purl.org/dc/elements/1.1/"</note>
    </extension_schema>
    <description_rules>
        <p>The EAD finding aids that the objects are extracted from are encoded following the OAC's
            EAD encoding guideline, found on page.
            These have varied somewhat over time. Some projects, such as MOAC, have more specific
            guidelines. </p>
        <p/>
    </description_rules>
    <controlled_vocabularies></controlled_vocabularies>
    <structural_requirements>
        <metsHdr>
            <requirement>
                <p>none at this time</p>
            </requirement>
        </metsHdr>
        <dmdSec>
            <requirement>
                <p>mdWrap MDTYPE=EAD contains and EADish &lt;c&gt; extracted from FA</p>
		<p>ID="dsc"</p>
            </requirement>
            <requirement>
                <p>mdRef points to the parent FA</p>
		<p>ID="ead"</p>
            </requirement>
            <requirement>
                <p>Dublin Core record for the parent Repository. The record has one title, and two
                    identifiers. The first identifier is the ARK of the repo, and the second is the
                    URL for a web page to contact the repository</p>
		<p>ID="repo"</p>
            </requirement>
        </dmdSec>
        <fileSec>
            <requirement>
                <p>The ID of the thumbnail is 'thumbnail'.</p>
                <p>Other files have have the same ID</p>
            </requirement>
        </fileSec>
        <structMap>
            <requirement>
                <p>For "simple" images, The root level div has a LABEL that is the same as
                    /mets/@LABEL, underthat div, there needs to be one div for each size</p>
            </requirement>
            <requirement>
                <p>For moderatly complex objects, use ORDER=1..x on the divs, with LABELs like photo
                    1..x. Use the USE attribute 'thumbnail' on the div with the thumbnail for the
                    parent div's ORDER.</p>
                <p>use one fptr per div</p>
            </requirement>
            <requirement>
                <p>divs with TYPE=hidden should be supressed from display, content files referenced
                    should have access controls</p>
            </requirement>
        </structMap>
        <multiSection>
            <requirement>
                <p>The OBJID attribute of the root mets element is the ARK of the object.</p>
                
            </requirement>
            <requirement>
                <p>/mets/@TYPE = image</p>
            </requirement>
        </multiSection>
    </structural_requirements>
    <technical_requirements>
        <content_files>
            <requirement>
                <p>Every item should have a thumbnail and at least on larger image.  In some cases, 
                    there is a thumbnail, and a link to a MOA2 object.</p>
                <p>There may be a non-functioning link to the master tiff image.  The tiffs should 
                follow CDL scanning guidelines.</p>
            </requirement>
        </content_files>
        <metadata_files>
            <requirement>
                <p>generated from EAD</p>
            </requirement>
        </metadata_files>
    </technical_requirements>
    <tool>
        <agency>California Digital Library</agency>
        <URI>http://ark-dev.cdlib.org:8086/xslt/extract-dc/kt3q2nb7vz.qdc2.xslt</URI>
        <description>
            <p ID="toQDC">Ths XSLT is used to extract a Dublin Core record from the object</p>
        </description>
    </tool>
    <tool>
        <agency>California Digital Library</agency>
        <URI>http://ark.cdlib.org/xslt/mets-page/kt3q2nb7vz.xslt</URI>
        <description>
            <p ID="toHTML">This XSLT is used by the ARK resolver to display the object in HTML.</p>
        </description>
    </tool>
    <Appendix NUMBER="1">
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="http://ark.cdlib.org/raw/ark:/13030/kt5s200700/"/>
    </Appendix>
</METS_Profile>