<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Francine,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">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: <a href="https://www.pivotaltracker.com/story/show/71019508">https://www.pivotaltracker.com/story/show/71019508</a>
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">According to the “Import Mapping for Resources from EAD2002 to ArchivesSpace” document (available here,
<a href="http://www.archivesspace.org/importexport">http://www.archivesspace.org/importexport</a>), <daogrp> elements should be supported by the ArchivesSpace import process.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Regarding your question about the format of the unit title, “</span>Rebay, Hilla (2 folders)(1 restricted)”: <span style="color:#1F497D">in general, I would record extent information separately in a physdesc
element, like so:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:black">
</span><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:#000096"><physdesc></span><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:black"><br>
</span><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:#000096"><extent></span><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:black">2 folders</span><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:#000096"></extent></span><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:black"><br>
</span><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:#000096"></physdesc><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:#000096"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-top:12.0pt"><span style="color:#1F497D">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.
</span><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:#000096"><container</span><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:#F5844C"> type</span><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:#FF8040">=</span><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:#993300">"Folder"</span><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:#000096">></span><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:black">1-2</span><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:#000096"></container></span><span style="color:#1F497D">).
If the folders weren’t numbered and it was still important to provide a folder count, then that would be a different story.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-top:12.0pt"><span style="color:#1F497D">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.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-top:12.0pt"><span style="color:#1F497D">All my best,<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-top:12.0pt"><span style="color:#1F497D">Mark Custer<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-top:12.0pt"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-top:12.0pt"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> archivesspace_users_group-bounces@lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org]
<b>On Behalf Of </b>Francine Snyder<br>
<b>Sent:</b> Thursday, May 08, 2014 5:40 PM<br>
<b>To:</b> archivesspace_users_group@lyralists.lyrasis.org<br>
<b>Subject:</b> [Archivesspace_Users_Group] daogrp import supported?<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hello – <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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>?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">If yes, our structure is:<o:p></o:p></p>
<p class="MsoNormal"><c04 level="file"><o:p></o:p></p>
<p class="MsoNormal"><did><o:p></o:p></p>
<p class="MsoNormal"><container type="box">44</container><o:p></o:p></p>
<p class="MsoNormal"><container type="folder">1-2</container><o:p></o:p></p>
<p class="MsoNormal"><unittitle>Rebay, Hilla (2 folders)(1 restricted)</unittitle><o:p></o:p></p>
<p class="MsoNormal"><unitdate type="inclusive">undated, 1955</unitdate><o:p></o:p></p>
<p class="MsoNormal"><daogrp><o:p></o:p></p>
<p class="MsoNormal"><daodesc><p> info here</p></daodesc><o:p></o:p></p>
<p class="MsoNormal"><daoloc href="<a href="http://..">http://..</a>” title="image one" role="image/jpeg"/><o:p></o:p></p>
<p class="MsoNormal"><daoloc href="<a href="http://..">http://..</a>” title="image two" role="image/jpeg"/><o:p></o:p></p>
<p class="MsoNormal"><daoloc href="<a href="http://..">http://..</a>” title="image two verso" role="image/jpeg"/><o:p></o:p></p>
<p class="MsoNormal">etc.<o:p></o:p></p>
<p class="MsoNormal"></daogrp><o:p></o:p></p>
<p class="MsoNormal"></did><o:p></o:p></p>
<p class="MsoNormal"></c04><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Troubleshooting so far:<o:p></o:p></p>
<p class="MsoNormal">Single <dao> import fine.<o:p></o:p></p>
<p class="MsoNormal">Swapped out @title for @label = still not recognized/imported.<o:p></o:p></p>
<p class="MsoNormal">Created and exported test EAD file that had multiple digital object instances attached to a file. Noticed exported EAD uses multiple <dao> not <daogrp>.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">All ideas welcome. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
<p class="MsoNormal">Francine<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Francine Snyder<br>
Director of Library and Archives<br>
Solomon R. Guggenheim Museum<br>
345 Hudson Street, 12<sup>th</sup> floor<br>
New York, NY 10014 4502<br>
Phone 212 360 4222<br>
Fax 917 386 1427<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>