Export/Import digital object metadata info in EAD template

[Martín]

Hi,

I've just exported some Archival Descriptions in XML EAD format. I can modify the output XML and upload it, so I can get a new Archival Description based on the first one. Everything works fine, except for the Digital Object linked to the first description. I can't see any reference to it in the XML file (and neither, of course, in the new Archivad description created after the import).

My question is: how can I export the reference (metadata) from the first object? I've read about DAO tag, but I could't find any actual example of its usage. My aim is to create an XML file to import a relative big collection of Archival descriptions, all of them pointing (referencing) a single photograph (file). Yeah, I've read about CSV, but I find more understandable the XML format.

My output XML looks like the following:

<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE ead PUBLIC "+//ISBN 1-931666-00-8//DTD ead.dtd (Encoded Archival Description (EAD) Version 2002)//EN" "http://lcweb2.loc.gov/xmlcommon/dtds/ead2002/ead.dtd">
<ead>
<eadheader langencoding="iso639-2b" countryencoding="iso3166-1" dateencoding="iso8601" repositoryencoding="iso15511" scriptencoding="iso15924" relatedencoding="DC">
  <eadid encodinganalog="Identifier">000099</eadid>  <filedesc>
    <titlestmt>
      <titleproper encodinganalog="Title">Nueva foto</titleproper>
      <author encodinganalog="Creator">Modificado por: martín
</author>
    </titlestmt>
  </filedesc>
  <profiledesc>
    <creation>
      Generated by qubit 1.3
      <date normal="2013-01-31">2013-01-31 10:14:UTC</date>
    </creation>
    <langusage>
      <language langcode="spa" encodinganalog="Language">español</language>
    </langusage>
  </profiledesc>
</eadheader>
<!-- TODO <frontmatter/> -->
<archdesc level="item" relatedencoding="ISAD(G)v2">
  <did>
    <unittitle encodinganalog="3.1.2">Debería ser el título</unittitle>
    <unitid  encodinganalog="3.1.1">000099</unitid>
    <unitdate datechar="creación" normal="1910/1910" encodinganalog="3.1.3">08/1910</unitdate>
    <origination encodinganalog="3.2.1">
      <name>Pacheco</name>
    </origination>
    <physdesc>
      <extent encodinganalog="3.1.5">9012 Papel positivo B/N</extent>
    </physdesc>
  </did>
  <scopecontent encodinganalog="3.3.1"><p>gorras, barranco</p></scopecontent>  <controlaccess>
    <corpname role="Productor">Pacheco</corpname>
    <subject source="">MIXTO</subject>
  </controlaccess>
  <phystech encodinganalog="3.4.3"><p>3 000099.jpg</p></phystech>  <altformavail encodinganalog="3.5.2"><p>000087.jpg</p></altformavail>
  <dsc type="combined">
  </dsc>
</archdesc>
</ead>

Thank you.

 

[Martín]

I believe my post might not be easy to understand.

I have a set of 1000 photographs. They are stored in my server, in a newly created directory inside the ICA_ATOM root.

I have (manually) added to IcaATom two of these 1000 photographs. Each photo is a "Item" (child node) inside a "Fonds" (parent node). So, now I have a parent node (Fonds 1) and two child nodes (Photo1, Photo2)

I've exported an XML of Photo2 in EAD format, which results in what I've pasted into my last post.

I need to generate an XML file with the remaining 998 photos. I've successfully imported the description of these 998 photographs (date, name, title, author, etc) but I don't know how to reference in the XML file which photo (i.e. the URL of the photo already uploaded in the server) should be imported to each Archival Description (Item).... so I get the miniatures and all that stuff properly created.

Thank you guys.

[David Juhasz]

Hi Martin,

The current version of ICA-AtoM (Release 1.3) does not support linking digital objects within the EAD-XML export.  Adding this functionality through use of the EAD <daogrp> element is scheduled for Release 1.4, see <https://projects.artefactual.com/issues/2589>.

Regards,
David

--
You received this message because you are subscribed to the Google Groups "Qubit Toolkit Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qubit-dev+...@googlegroups.com.
To post to this group, send email to qubi...@googlegroups.com.
Visit this group at http://groups.google.com/group/qubit-dev?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--

David Juhasz
Director, Technical Services

Artefactual Systems Inc.
www.artefactual.com

[jes...@artefactual.com]

This issue has been fixed and verified. The fix will be included in the next release.

Jessica Bushey