[Archivesspace_Users_Group] daogrp ?

[Custer, Mark]

Steven,

When testing this earlier today I stumbled across the fact that you can get DAOs to import as long as they contain a <daodesc> (even though the <daodesc> won't be imported itself).

Example of what will work (right now, at least):

                   <c04 level="file">
                       <did>
                           <container type="Box">48</container>
                           <unittitle>1 dao outside of the did</unittitle>
                           <unitdate type="inclusive">undated, 1955</unitdate>
                       </did>
                       <dao xlink:title="required-title-2" xlink:href="somewhere" ><daodesc><p>needs a desc, really?</p></daodesc></dao>
                   </c04>

I'm sure that doesn't help much right now, but you could get stuff to import by converting the EAD beforehand, converting each daogrp/daoloc into a dao with a daodesc....  Or something like that.

Mark

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Steven Majewski
Sent: Tuesday, March 11, 2014 10:47 PM
To: Archivesspace Users Group
Subject: [Archivesspace_Users_Group] daogrp ?


No digital objects were created on importing my EAD.

>From the import mappings   Data Import and Export Maps<http://www.archivesspace.org/importexport>  it appears that  <dao>, <daogrp>, <daoloc> & <daodesc> all have assigned mappings,
but I only see a template for 'dao' in ead_converter.rb.

We are using <daogrp> in our files, as typically we have links to several page images that make up a letter.
( This will likely change as those images do into our repository and become part of a Fedora object. )

As a test, I've tried in one file, removing the <daogrp>'s and turning the <daoloc>'s into <dao>'s, but I get this error:



Error: Unexpected Object Type in Queue: Expected archival_object got file_version


Import Mapping for Resources from EAD2002 to ArchivesSpace















Last Updated:

8/31/13









































DAO's















<dao>



instance.instance_type = digital_object



  @title



instance.digital_object.title



  @role



instance.digital_object.file_versions[].use_statement



  @href



instance.digital_object.file_versions[].uri



  @actuate



instance.digital_object.file_versions[].xlink_actuate_attribute



  @show



instance.digital_object.file_versions[].xlink_show_attribute











<daogrp>

EACH <daoloc> within <daogrp> treated as individual file_versions within a single digital_object instance.

instance.instance_type = digital_object

Should these end up being components?

  @role



instance.digital_object.file_versions[].use_statement



  @href



instance.digital_object.file_versions[].uri



  @label



instance.digital_object.file_versions[].title



  <daodesc>



instance.digital_object.title











-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20140509/d2ba5ce2/attachment.html>