<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 12 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
p.msochpdefault, li.msochpdefault, div.msochpdefault
{mso-style-name:msochpdefault;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:10.0pt;
font-family:"Times New Roman","serif";}
span.emailstyle18
{mso-style-name:emailstyle18;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.emailstyle19
{mso-style-name:emailstyle19;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.emailstyle20
{mso-style-name:emailstyle20;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Tahoma","sans-serif";
color:black;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.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="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>I know this isn’t a workable solution for everyone, but you should also check out what Artefactual is working on with Archivematica for both the Bentley Historical Library and us here at the RAC.<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'>We’re working on two separate projects to help link up digital objects to description in ArchivesSpace. You can learn more about them if you check out the Integrations information: https://archivesspace.atlassian.net/wiki/display/ADC/Integrations+and+Other+Community+Projects<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal><span style='color:#1F497D'>Patrick Galligan<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Rockefeller Archive Center<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Assistant Digital Archivist<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>914-366-6386<o:p></o:p></span></p></div><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>Kennedy, Nancy<br><b>Sent:</b> Tuesday, April 26, 2016 3:27 PM<br><b>To:</b> Archivesspace Users Group<br><b>Subject:</b> Re: [Archivesspace_Users_Group] Is it possible to include a summary note in a digital object CSV?<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>Angela,<o:p></o:p></span></p><div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>Just a thought re: "</span><i><span style='color:black'>we'll still have to manually create the archival object records and manually link each one to its corresponding digital object."</span></i><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'> <o:p></o:p></span></p><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>If your archival objects don't yet exist, have you considered importing via EAD? You could build out the archival objects and associated digital objects at the same time, saving yourself the trouble of manual linking. Especially if you’re already working from a spreadsheet and just want ‘glorified linking’.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>If you already have a spreadsheet to work from: consider using excel to build out the EAD <dsc>, one row per archival object and set up column(s) for the <dao> while you're at it. Convert excel/csv to xml, by using the column names as element names (which means that it’s fairly easy to add new elements as new columns, rather than a behemoth spreadsheet with 60 columns…). Excel macros can do it, or ruby. Once the data is in xml, it’s just an XSLT to set up as EAD and apply local rules before import. If you’d like to see examples, feel free to get in touch. I have files set up to do this for AT, and in initial testing, these seem to work as well for ArchivesSpace.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>Nancy<o:p></o:p></span></p></div><div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'><o:p> </o:p></span></p><div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>Nancy Kennedy <o:p></o:p></span></p><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>EAD Coordinator <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>Smithsonian Institution<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'><a href="mailto:KennedyN@si.edu">KennedyN@si.edu</a><o:p></o:p></span></p></div></div></div></div><div><div class=MsoNormal align=center style='text-align:center'><span style='font-size:12.0pt;font-family:"Times New Roman","serif";color:black'><hr size=2 width="100%" align=center></span></div><div id=divRpF57237><p class=MsoNormal style='margin-bottom:12.0pt'><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'> <a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-bounces@lyralists.lyrasis.org</a> [archivesspace_users_group-bounces@lyralists.lyrasis.org] on behalf of Angela Kroeger [akroeger@unomaha.edu]<br><b>Sent:</b> Friday, April 22, 2016 12:07 PM<br><b>To:</b> Archivesspace Users Group<br><b>Subject:</b> Re: [Archivesspace_Users_Group] Is it possible to include a summary note in a digital object CSV?</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif";color:black'><o:p></o:p></span></p></div><div><div><p class=MsoNormal><span style='color:black'>Mark,<o:p></o:p></span></p><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>Thank you for your helpful reply! I'll start by mentioning that I'm not a programmer and have never used an API before, so I don't know how to do it, but knowing that it CAN be done is a good start. <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>I looked at your digital object converter code, and I see that there is a bioghist note in it. I imagine a summary note could be added the same way, copying that code? Again, I'm not sure where to put this code or how to use it, but seeing it gives me hope.<o:p></o:p></span></p><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>I found the documentation for the ArchivesSpace RESTful API on github (<a href="http://archivesspace.github.io/archivesspace/doc/file.API.html" target="_blank">http://archivesspace.github.io/archivesspace/doc/file.API.html</a>), but it's somewhat beyond my present level of knowledge and understanding.<o:p></o:p></span></p><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>Since I know essentially nothing about APIs, I'm going to follow the advice in the University of Michigan's blog post on ArchivesSpace APIs (<a href="http://archival-integration.blogspot.com/2015/09/the-archivesspace-api.html" target="_blank">http://archival-integration.blogspot.com/2015/09/the-archivesspace-api.html</a>) and look at the ArchivesSpace Developer Screencasts (<a href="https://www.youtube.com/playlist?list=PLJFitFaE9AY_DDlhl3Kq_vFeX27F1yt6I" target="_blank">https://www.youtube.com/playlist?list=PLJFitFaE9AY_DDlhl3Kq_vFeX27F1yt6I</a>). <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>Can you recommend any other resources or tutorials I should look at to get started?<o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>We are hosted by LYRASIS, if that changes anything.<o:p></o:p></span></p><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>Thanks also for the advice about not using the user defined fields for this. I'll throw that idea away.<o:p></o:p></span></p><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>You asked how we were using digital objects. You used the phrase "glorified linking mechanism," and that's pretty close to how we're using them. A lot (most) of the information is duplicated between our digital objects and the archival objects they're linked to.<o:p></o:p></span></p><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>Here's a sample digital object from our institution:<o:p></o:p></span></p><p class=MsoNormal><span style='color:black'><a href="http://unomaha-public.lyrasistechnology.org/repositories/4/digital_objects/211" target="_blank">http://unomaha-public.lyrasistechnology.org/repositories/4/digital_objects/211</a><o:p></o:p></span></p><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>And here's its corresponding archival object:<o:p></o:p></span></p><p class=MsoNormal><span style='color:black'><a href="http://unomaha-public.lyrasistechnology.org/repositories/4/archival_objects/33757" target="_blank">http://unomaha-public.lyrasistechnology.org/repositories/4/archival_objects/33757</a><o:p></o:p></span></p><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>We had considered creating series-level archival objects and linking all appropriate digital objects to them, but after the advice from several folks on this list (discussion in early February), we went with a one-to-one relationship between item-level archival objects and digital objects.<o:p></o:p></span></p><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>We've been manually adding digital objects and archival objects from our spreadsheet one at a time, and it is painfully slow. I saw the digital object import as a way of cutting out one of the steps. After importing the CSV of digital object records, as far as I can tell, we'll still have to manually create the archival object records and manually link each one to its corresponding digital object. Or can that also be done with an API?<o:p></o:p></span></p><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>Thanks, again!<o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>--Angela<o:p></o:p></span></p><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>Angela Kroeger<o:p></o:p></span></p><p class=MsoNormal><span style='color:black'><a href="mailto:akroeger@unomaha.edu" target="_blank"><span style='color:windowtext'>akroeger@unomaha.edu</span></a><o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>Archives and Special Collections Associate<o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>Dr. C.C. and Mabel L. Criss Library<o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>University of Nebraska at Omaha<o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>(402) 554-4159<o:p></o:p></span></p><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p></div></div></div></div></div></div></div></body></html>