Print

---

Another way of doing this sort of thing is illustrated by a METS profile
submitted by the University of Illinois at Urbana-Champaign:
http://www.loc.gov/standards/mets/profiles/00000015.html
and
http://www.loc.gov/standards/mets/profiles/00000016.html
(this one has the example).

They use digiProv with premis:event to track the provenance of the 
metadata within the METS document. EventType tells you that it
concerns metadata, e.g. eventType="METADATA_SOURCE". (This is a fragment,
see also the above example).

Example:
<digiprovMD ID="APP3_PROV1">
   <mdWrap MDTYPE="PREMIS">
     <xmlData>
       <event xmlns="http://www.loc.gov/standards/premis/v1">
         <eventIdentifier>
            <eventIdentifierType>INTERNAL_XML_ID</eventIdentifierType>
            <eventIdentifierValue>PROV1</eventIdentifierValue>
         </eventIdentifier>
         <eventType>METADATA_CREATION</eventType>
         <eventDateTime>2006-08-22</eventDateTime>
         <eventDetail> Descriptive metadata was generated from the OCLC
          WAW tool on September 21, 2006. </eventDetail>
         <linkingAgentIdentifier LinkAgentXmlID="APP3_AGENT1">
            <linkingAgentIdentifierType>URI</linkingAgentIdentifierType>
            <linkingAgentIdentifierValue> mailto:[log in to unmask]
            </linkingAgentIdentifierValue>
            <linkingAgentRole>EVENT_INITIATOR</linkingAgentRole>
         </linkingAgentIdentifier>
        <linkingAgentIdentifier LinkAgentXmlID="APP3_AGENT3">
            <linkingAgentIdentifierType>URI</linkingAgentIdentifierType>
            <linkingAgentIdentifierValue>
            http://loki.grainger.uiuc.edu:8082/
            </linkingAgentIdentifierValue>
            <linkingAgentRole>METADATA_SOURCE</linkingAgentRole>
        </linkingAgentIdentifier>
       </event>
     </xmlData>
   </mdWrap>
 </digiprovMD>

 <digiprovMD ID="APP3_AGENT1">
   <mdWrap MDTYPE="PREMIS">
      <xmlData>
       <agent xmlns="http://www.loc.gov/standards/premis/v1">
         <agentIdentifier>
            <agentIdentifierType>URI</agentIdentifierType>
            <agentIdentifierValue> mailto:[log in to unmask]
            </agentIdentifierValue>
         </agentIdentifier>
         <agentName>Tom Habing</agentName>
         <agentType>PERSON</agentType>
       </agent>
     </xmlData>
   </mdWrap>
 </digiprovMD>

Obviously this is an implementation specific solution outside of the
PREMIS data dictionary. The question is whether the need for source is
something implementation specific, or whether it is "core" preservation
metadata that the data dictionary should address.

Rebecca 

On Tue, 16 Oct 2007, Susan Thomas wrote:

> Hi,
> 
> I was wondering whether it would it be possible to add a source 
> attribute to certain container semantic units/elements in the next 
> versions of the premis data dictionary/object xml schema. We'd like to 
> be able to record the names of the tools used to extract particular bits 
> of metadata, as has been done in the Statistics New Zealand Prototype 
> PREMIS Creation Tool (http://pigpen.lib.uchicago.edu:8888/pigpen/40). I 
> realise we could create a local schema to do it, but we'd prefer to use 
> an official one if possible. Would this be useful to others too?
> 
> Best,
> 
> Susan
> 
> -- 
> 
>       Susan Thomas
>       Project Manager/Digital Archivist
>       Paradigm & Cairo projects
>       Bodleian Library
> 
> Post: Oxford University Library Services
>       Osney One Building
>       Osney Mead
>       OXFORD OX2 0EW
> Web : http://www.paradigm.ac.uk
>       http://cairo.paradigm.ac.uk	
> Tel : +44 (0) 1865 283821
>