[Archivesspace_Users_Group] Upgrading across multiple versions

Andrew Morrison andrew.morrison at bodleian.ox.ac.uk
Thu Oct 12 04:11:27 EDT 2023


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.

Andrew.


On 12/10/2023 08:59, Andrew Morrison wrote:
>
> 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:
>
> https://www.loc.gov/ead/eadschema.html
>
> I never used 1.x. But assuming there was an API method to export it as 
> there is now...
>
> https://archivesspace.github.io/archivesspace/api/#get-an-ead-representation-of-a-resource
>
> ...you could export then import into a blank 3.4.1 system with this...
>
> https://archivesspace.github.io/archivesspace/api/?shell#create-a-new-job-and-post-input-files
>
> 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.
>
> 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:
>
> https://archivesspace.org/archives/7151
>
> 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.)
>
> Andrew.
>
>
> On 11/10/2023 23:06, Dudeck, John wrote:
>>
>> Greetings.
>>
>> I am an IT professional newly serving as pro-bono technical advisor 
>> to a non-profit’s small archives.
>>
>> 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.
>>
>> 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.
>>
>> 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.
>>
>> Thanks.
>>
>> John Dudeck              Tel: +1-704-588-9891  Cell: +1-803-504-8065
>> john.dudeck at sim.org                        Charlotte, North Carolina
>>
>>
>> _______________________________________________
>> Archivesspace_Users_Group mailing list
>> Archivesspace_Users_Group at lyralists.lyrasis.org
>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231012/448f5cf0/attachment.html>


More information about the Archivesspace_Users_Group mailing list
http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/2023-October/010423.html
lyralists.lyrasis.org
CC-MAIN-2024-33
8825
application/http; msgtype=response
sha1:D6DOUJWSC4P6Q5H62L3Z2ILLGAOCVIIJ
<urn:uuid:1d8d87b1-284a-45de-b7d1-31a3ac0506f8>
2024-08-10T02:07:11Z
75.77.204.231
text/html
sha1:YD4OUMUZ2CM6QG2FS7Y3YMX67Q2PW6ZW
<urn:uuid:84345220-18aa-45f4-92ce-99f040852207>
http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/2023-October/010423.html
response
<urn:uuid:60664041-52eb-4170-96fc-2ea76e7ea212>
isPartOf: CC-MAIN-2024-33
publisher: Common Crawl
description: Wide crawl of the web for August 2024
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-138
software: Apache Nutch 1.20 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.5-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/