<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<p>Whether it would be easier to upgrade or migrate data to a new
system depends on what you mean by "a couple thousand records". If
you mean a couple of thousand resource records, that would be a
couple of thousand EAD files. If you mean a couple of thousand
rows in the biggest table, those may well be archival objects,
which are sub-records, and so it just be a dozen EAD files, in
which case it could be done via the staff interface, and not
require use of the API at all.</p>
<p>Andrew.</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 12/10/2023 08:59, Andrew Morrison
wrote:<br>
</div>
<blockquote type="cite" cite="mid:76f96ac2-f1fd-431e-bc28-c0040bfb8542@bodleian.ox.ac.uk">
<p>If you haven't already, I would recommend assessing whether
there is any data in your 1.1.2 system that wouldn't be included
if you exported your records as EAD:</p>
<p><a class="moz-txt-link-freetext" href="https://www.loc.gov/ead/eadschema.html" moz-do-not-send="true">https://www.loc.gov/ead/eadschema.html</a></p>
<p>I never used 1.x. But assuming there was an API method to
export it as there is now...</p>
<p><a class="moz-txt-link-freetext" href="https://archivesspace.github.io/archivesspace/api/#get-an-ead-representation-of-a-resource" moz-do-not-send="true">https://archivesspace.github.io/archivesspace/api/#get-an-ead-representation-of-a-resource</a></p>
<p>...you could export then import into a blank 3.4.1 system with
this...</p>
<p><a class="moz-txt-link-freetext" href="https://archivesspace.github.io/archivesspace/api/?shell#create-a-new-job-and-post-input-files" moz-do-not-send="true">https://archivesspace.github.io/archivesspace/api/?shell#create-a-new-job-and-post-input-files</a></p>
<p>Note that it needs to be EAD 2002, not the newer EAD3. And it
is best to import one EAD file per job, as it can cause indexing
problems if you do too many in one job.</p>
<p>A big change in recent years is that, since 3.2.0,
ArchivesSpace no longer comes packaged with the search engine.
Now you have to set up and run your own separate Solr server:<br>
</p>
<p><a class="moz-txt-link-freetext" href="https://archivesspace.org/archives/7151" moz-do-not-send="true">https://archivesspace.org/archives/7151</a></p>
<p>Also, if your old ArchivesSpace system was just set up as a
trial, it may be using the built-in Apache Derby database. But
that is only recommended for demonstration purposes, so you will
need to set up and run your own MySQL or MariaDB database (or
use some cloud solution.)<br>
</p>
<p>Andrew.</p>
<p> <br>
</p>
<div class="moz-cite-prefix">On 11/10/2023 23:06, Dudeck, John
wrote:<br>
</div>
<blockquote type="cite" cite="mid:SA1PR10MB6414CC62E46EDC21E27924F3ECCCA@SA1PR10MB6414.namprd10.prod.outlook.com">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style>@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;}p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-ligatures:standardcontextual;}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;}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]-->
<div class="WordSection1">
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Greetings.<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">I am
an IT professional newly serving as pro-bono technical
advisor to a non-profit’s small archives.<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">About
8 years ago a previous archivist started an Archives Space
installation, but then left the organization, and
knowledge of their Archives Space system disappeared.
Recently by asking the right questions I found the Virtual
Machine containing our instance, fully intact and
operational. There are a couple thousand records in the
database.<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">This
instance of Archives Space is version 1.1.2. I tried doing
an upgrade from 1.1.2 to a recent version (3.3.0 I think)
a while back, which was not successful, as could be
expected.<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">So
assuming that I need to do the upgrade in several steps, I
would like to know what intermediate versions would be the
key steps to upgrade to in order to get all of the
database migrations. Or alternatively, can somebody point
me to information on how to migrate the database over that
span of 1.1.2 to 3.4.1 ? I scoured the online information
on upgrading A.S., and have not found anything
sufficiently helpful.<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Thanks.<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black;mso-ligatures:none">John
Dudeck Tel: +1-704-588-9891 Cell:
+1-803-504-8065<br>
<a class="moz-txt-link-abbreviated moz-txt-link-freetext" href="mailto:john.dudeck@sim.org" moz-do-not-send="true">john.dudeck@sim.org</a>
Charlotte, North Carolina</span><o:p></o:p></p>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Archivesspace_Users_Group mailing list
<a class="moz-txt-link-abbreviated moz-txt-link-freetext" href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org" moz-do-not-send="true">Archivesspace_Users_Group@lyralists.lyrasis.org</a>
<a class="moz-txt-link-freetext" href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" moz-do-not-send="true">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a>
</pre>
</blockquote>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Archivesspace_Users_Group mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@lyralists.lyrasis.org</a>
<a class="moz-txt-link-freetext" href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a>
</pre>
</blockquote>
</body>
</html>