<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=utf-8">
<meta name="Generator" content="Microsoft Word 15 (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:"Segoe UI Emoji";
panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Segoe UI Symbol";
panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",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;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.im
{mso-style-name:im;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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="font-family:"Calibri",sans-serif">Along this line I’ve been struggling with finding an authoritative data dictionary for all of ASpace’s model classes and all the possible endpoint parameters. The API documentation provides
much of this but not seemingly all, esp. mixins.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif">For example: I would like an application developer to modify the Digital Object CSV importer to add specific Note fields that do not exist in the DO import template or data map at
<a href="http://archivesspace.org/using-archivesspace/migration-tools-and-data-mapping/">
http://archivesspace.org/using-archivesspace/migration-tools-and-data-mapping/</a>. I can’t reasonably expect a developer to “learn by doing”, read code or test documents, or watch YouTube videos -- nor will their managers allow them to do any of that.</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif">Having such an authoritative data dictionary would help to build external stakeholder confidence in ASpace as a documented, robust, authoritative data management application.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif">Or perhaps I’m missing some boat entirely?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">John<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">John P. Rees<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Archivist and Digital Resources Manager<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">History of Medicine Division<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">National Library of Medicine<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">301-827-4510<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Galligan, Patrick [mailto:PGalligan@rockarch.org]
<br>
<b>Sent:</b> Monday, November 13, 2017 9:14 AM<br>
<b>To:</b> Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org><br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] batch delete dates saga continues<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Hey all,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I think a great place to get started learning about Python, APIs, and ArchivesSpace would be some of the API tutorials that members of the ArchivesSpace community
have taught.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Lora Woodford from JHU taught a workshop about 4 months ago and made the materials available on Github:
<a href="https://github.com/jhu-archives-and-manuscripts/ASpace_API_Workshop">https://github.com/jhu-archives-and-manuscripts/ASpace_API_Workshop</a>.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Personally, I’ve found that I learn best by doing. So I learned what I did about the AS JSON responses by downloading Postman (<a href="https://www.getpostman.com/">https://www.getpostman.com/</a>)
and performing a few API calls against our development database. Also, back in 2014, Maureen Callahan and a few other archivists ran a blog about dealing with legacy data. They have some posts about AS API work. I personally liked this post as a beginner:
<a href="https://icantiemyownshoes.wordpress.com/2014/08/01/a-very-brief-guide-to-deleting-records-with-the-archivesspace-api-from-a-total-tyro/">
https://icantiemyownshoes.wordpress.com/2014/08/01/a-very-brief-guide-to-deleting-records-with-the-archivesspace-api-from-a-total-tyro/</a>.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">This is a great resource for learning python:
<a href="https://automatetheboringstuff.com/">https://automatetheboringstuff.com/</a>.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I’m sure there are a ton of other resources out there, but those are the few off the top of my head. I’m willing to jump in and give some more recommendations
as needed.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">-Patrick Galligan<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">
<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-bounces@lyralists.lyrasis.org</a> [<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org</a>]
<b>On Behalf Of </b>Margaret Kidd<br>
<b>Sent:</b> Friday, November 10, 2017 5:31 PM<br>
<b>To:</b> Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@lyralists.lyrasis.org</a>><br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] batch delete dates saga continues<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">I second that last part of Lydia's remarks about where to begin learning more about XML, JSON, python, ruby, etc. and applying it to ArchivesSpace. I want to learn, but it is overwhelming to know where to begin and my time to devote to
it is rather limited. Every time I start trying to teach myself I have other work priorities that take up all my time and soon forget whatever progress I have made.<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Margaret<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><br clear="all">
<o:p></o:p></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black">
<hr size="2" width="100%" align="center">
</span></div>
<p style="margin:0in;margin-bottom:.0001pt"><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#646464">Margaret T. Kidd</span></b><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#646464">Project Archivist, Special Collections & Archives</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#646464">VCU Libraries | Tompkins-McCaw Library for the Health Sciences</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#8D8D8D">509 N. 12th Street / Box 980582, Richmond, VA 23298-0582</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#8D8D8D">(804) 828-3152</span><o:p></o:p></p>
<p class="MsoNormal"><a href="https://twitter.com/VCUTMLibrary" target="_blank"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1155CC;text-decoration:none"><img border="0" id="_x0000_i1026" src="https://lh3.googleusercontent.com/CvwxmA9bdbubHH0SSvacsiCM35wJ3MMtdY8qFmOw7soBA46uNNHXG89hFi99w8XCP3MCPTkbSx7uxdAcW5YyV2eqviun-t6OoCTFe7aUbHhv3JJNonLo6sEH49IczUqAHOw8B8w" alt="em_twitter.png"></span></a><a href="https://www.facebook.com/VCUTMLib" target="_blank"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1155CC;text-decoration:none"><img border="0" id="_x0000_i1027" src="https://lh6.googleusercontent.com/bBkgQaDHlTe4cYH8-0RSwlNxAs91Xv-D8Jewu8tOyHXmx4Efy0m8hspT1EvUAnFQTuqH8NcCOb8OndayaOVeZeKkpPxKcC8yI0Guylmkdithc0ZWyxfzPPFHt_6NDWmVNoQvr3M" alt="em_fb.png"></span></a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><a href="http://www.vcu.edu/" target="_blank"><span style="text-decoration:none"><img border="0" id="_x0000_i1028" src="http://identity.vcu.edu/images/photos/vcu_brand_mark_email_sig.jpg"></span></a> <a href="http://vaheritage.org" target="_blank"><span style="text-decoration:none"><img border="0" width="200" height="99" style="width:2.0833in;height:1.0312in" id="_x0000_i1029" src="http://pages.shanti.virginia.edu/Virginia_Heritage/files/2013/01/vhpban.jpg"></span></a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Fri, Nov 10, 2017 at 12:02 PM, Tang, Lydia <<a href="mailto:ltang5@lib.msu.edu" target="_blank">ltang5@lib.msu.edu</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<p class="MsoNormal" style="margin-bottom:12.0pt">Mark,<br>
Thank you for identifying my problem! Just for the sake of technological dummies like me, what should I do? Everything there (besides removing the <unitid> tags is exactly as it spat out of ArchivesSpace, so I wonder if the export allowed the invalid characters?
I also wonder if the importing process could be improved within the ArchivesSpace code to search for “aspace_" and not batch add it as well as recognize (or not export out in the first place) the "Linear Feet" / linear_feet controlled vocabulary? Ideally,
after establishing with the database that linear_feet should publish as Linear Feet, I wish it would continue to recognize that rule when new stuff is imported in.<br>
I was also meaning poll people on “how do I even get started” with learning more about working the ArchivesSpace guts? I can understand EAD but obviously don’t know the wizardry possible with XML, there’s JSON, python, etc, and I would be interested in starting
courses with Code Academy to learn, but I don’t even know where to begin. Advice appreciated!<br>
Lydia<br>
<br>
From: <<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-bounces@lyralists.lyrasis.org</a>> on behalf of "Custer, Mark" <<a href="mailto:mark.custer@yale.edu">mark.custer@yale.edu</a>><br>
Reply-To: Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@lyralists.lyrasis.org</a>><br>
Date: Friday, November 10, 2017 at 11:50 AM<br>
<span class="im">To: Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@lyralists.lyrasis.org</a>></span><br>
<span class="im">Subject: Re: [Archivesspace_Users_Group] batch delete dates saga continues</span><br>
<br>
<span class="im">Lydia,</span><br>
<br>
<span class="im">In the EAD files that you attached, both have invalid XML characters in them (Unicode: 0x14). Those are easy to remove before re-importing in an XML editor like oXygen, but I'm curious how they got into ASpace in the first place? In any
event, it's possible that that's what's blocking your imports this time around, and if that's the issue, if you just fix on those issues, then the ASpace importer won't tell you about the next issue until it runs again.</span><br>
<br>
<span class="im">In any event, I'd also suggest making the following changes to your XML file before re-importing, so perhaps the snag is a good thing for now
</span><span class="im"><span style="font-family:"Segoe UI Emoji",serif">😊</span> :</span><br>
<br>
<span class="im">· ASpace adds "aspace_" to all of the @id values in the EAD file upon export. If you don't remove those before reimporting, then on the next export you'll get "aspace_aspace_". Removing them will invalidate the EAD file, but ASpace
doesn't care whether the file is valid or not upon re-importing it.</span><br>
<span class="im">· ASpace expects to have the database values for the controlled value terms in the exports, not the translation values. So, if you don't change things like "Linear Feet" to linear_feet and "Mixed Materials" to mixed_materials, then
you'll wind up with new database values in ASpace after the import. Those of course can be merged after the fact, but that's another step, and it would be unfortunate to have to do that on every occasion.</span><br>
<br>
<span class="im">There's a lot more to say on the practice of re-importing EAD into ASpace, but I haven't still come up with a great strategy for that, so basically we try to avoid it
</span><span class="im"><span style="font-family:"Segoe UI Emoji",serif">😊</span></span><br>
<br>
<span class="im">Mark</span><br>
<br>
<br>
<span class="im">-----Original Message-----</span><br>
<span class="im">From: <a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">
archivesspace_users_group-bounces@lyralists.lyrasis.org</a> [mailto:<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-bounces@lyralists.lyrasis.org</a>] On Behalf Of Tang, Lydia</span><br>
<span class="im">Sent: Friday, 10 November, 2017 10:47 AM</span><br>
<span class="im">To: Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@lyralists.lyrasis.org</a>></span><br>
<span class="im">Subject: Re: [Archivesspace_Users_Group] batch delete dates saga continues</span><br>
<br>
<span class="im">Wizardry! Thank you, Olivia! I would have NEVER figured that out. It seemed to take out the <unitdate> tags perfectly but I ended up getting snagged on importing because of, um, a seemingly benign line which was marked as not well-formed.
Oof, so close, but snagged up!</span><br>
<span class="im">Lydia</span><br>
<br>
<span class="im">From: <<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-bounces@lyralists.lyrasis.org</a>> on behalf of Olivia S Solis <<a href="mailto:livsolis@utexas.edu">livsolis@utexas.edu</a>></span><br>
<span class="im">Reply-To: Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@lyralists.lyrasis.org</a>></span><br>
<span class="im">Date: Friday, November 10, 2017 at 10:36 AM</span><br>
<span class="im">To: Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@lyralists.lyrasis.org</a>></span><br>
<span class="im">Subject: Re: [Archivesspace_Users_Group] batch delete dates saga continues</span><br>
<br>
<span class="im"><unitda[^>]+>[^<]+<\/unitdate></span><o:p></o:p></p>
<div>
<div>
<p class="MsoNormal">_______________________________________________<br>
Archivesspace_Users_Group mailing list<br>
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@lyralists.lyrasis.org</a><br>
<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" target="_blank">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a><o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>