<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:Calibri;
panose-1:2 15 5 2 2 2 4 3 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-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@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"><o:p> </o:p></p>
<p class="MsoNormal">I’m curious about how other very small institutions are doing with the transition to ArchivesSpace. We at Mennonite Church USA are stalled because the installation and support of the software itself has been very difficult and time-consuming.
We had an instance of ArchivesSpace up and running briefly (with a lot of help from Chris Fitzpatrick), but then it stopped working, and we haven’t been able to get it started again. Because we’ve not been able to achieve basic functionality of the software
yet (and we’ve been working at it for several months now), we’ve not begun the migration of data from Archon to ArchivesSpace. I have to confess that I’m really worried that we won’t get it done before migration support for charter members ends. And based
on the messages I see here, it seems that migration is not easy, and we will need all the help we can get.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">If you work at a very small institution, I’d like to hear how things are going. Feel free to respond either privately or on the list.
<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"><o:p> </o:p></p>
<p class="MsoNormal">Colleen<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b><span style="font-family:"Arial","sans-serif"">Colleen McFarland</span></b><span style="font-family:"Arial","sans-serif"">, Director of Archives and Records Management, Mennonite Church USA<br>
<a href="mailto:colleenm@mennoniteusa.org">colleenm@mennoniteusa.org</a>, 1700 S. Main St. Goshen, IN 46526, 574-523-3039 (direct), 1-866-866-2872 ext. 23039 (toll-free)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""><a href="http://www.mennoniteusa.org/">www.mennoniteusa.org</a>
<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>