[Archivesspace_Users_Group] daogrp import supported?

[Custer, Mark]

Francine,

Thank you for discovering this issue and testing it out so thoroughly!  I've created a bug report for this issue, which you can track with this link:  https://www.pivotaltracker.com/story/show/71019508

According to the "Import Mapping for Resources from EAD2002 to ArchivesSpace" document (available here, http://www.archivesspace.org/importexport), <daogrp> elements should be supported by the ArchivesSpace import process.

Regarding your question about the format of the unit title, "Rebay, Hilla (2 folders)(1 restricted)":  in general, I would record extent information separately in a physdesc element, like so:

                           <physdesc>
                               <extent>2 folders</extent>
                           </physdesc>

In your example, however, I probably wouldn't record that physdesc statement at all since you already indicate that there are two folders based on the container information (i.e. <container type="Folder">1-2</container>).  If the folders weren't numbered and it was still important to provide a folder count, then that would be a different story.
Additionally, I would use the <accessrestrict> element to indicate any sort of restriction statements that pertain to access, but in that case it might be better to split this level of description up into two separate statements, since the restriction only applies to one of the two folders.
All my best,
Mark Custer




From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Francine Snyder
Sent: Thursday, May 08, 2014 5:40 PM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] daogrp import supported?

Hello -

Has anyone had success importing EAD files with <daogrp>? When tried, the <daogrp> and nested digital objects have not been recognized or imported into AS. EAD imports fine; there are no import error messages. File listings / box instances are created, just not the digital object instances. Does AS support <daogrp>?

If yes, our structure is:
<c04 level="file">
<did>
<container type="box">44</container>
<container type="folder">1-2</container>
<unittitle>Rebay, Hilla (2 folders)(1 restricted)</unittitle>
<unitdate type="inclusive">undated, 1955</unitdate>
<daogrp>
<daodesc><p> info here</p></daodesc>
<daoloc href="http://.." title="image one" role="image/jpeg"/>
<daoloc href="http://.." title="image two" role="image/jpeg"/>
<daoloc href="http://.." title="image two verso" role="image/jpeg"/>
etc.
</daogrp>
</did>
</c04>

Troubleshooting so far:
Single <dao> import fine.
Swapped out @title for @label = still not recognized/imported.
Created and exported test EAD file that had multiple digital object instances attached to a file. Noticed exported EAD uses multiple <dao> not <daogrp>.

All ideas welcome.

Added curiosity (since it is in my example) for anyone dealing with legacy finding aids that have folder count or restrictions in the title, ie. Rebay, Hilla (2 folders)(1 restricted), what AS fields are or will you be using for this data?

Thanks,
Francine

Francine Snyder
Director of Library and Archives
Solomon R. Guggenheim Museum
345 Hudson Street, 12th floor
New York, NY 10014 4502
Phone 212 360 4222
Fax 917 386 1427

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