[Archivesspace_Users_Group] DB Migration Question

Lora Woodford lwoodford at jhu.edu
Tue Sep 19 14:44:03 EDT 2017

Heya, Christine/all,

We haven’t upgraded yet, but I have a few 2.1.2 local test instances running with our production data in them to do some testing/api script rewrites in advance of upgrading.  I can confirm that I have seen this non-utf8 error message multiple times (but have ignored it since it didn’t impede my testing and aspace still booted up fine).

But, yes, I’ve seen this warning.


From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Christine Di Bella
Sent: Tuesday, September 19, 2017 2:39 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] DB Migration Question

Hi Chelsea,

Version 2.1 of ArchivesSpace included an expanded rights statements module and setup-database has a data migration to move previous rights data to the new model (migration 088). The purpose of the rights_statement_pre_088 table is to serve as a backup of your previous rights statement data in case you find that your rights data did not migrate as expected. It is not needed if you’re happy with the way the data migrated.

As to why ArchivesSpace would throw an error saying it was not set to UTF8, I would be curious if anyone else has experienced that during or post-upgrade. We have not heard of that occurring previously.


Christine Di Bella
ArchivesSpace Program Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
cdibella13 (Skype)


From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chelsea Lobdell
Sent: Tuesday, September 19, 2017 2:25 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] DB Migration Question

Hi Aspace!
I just upgraded our instance of Archivesspace from v2.0.1 to v2.1.2 on our development server.
After running setup-database.sh to migrate the data I noticed an odd table in the database called rights_statement_pre_088.
The application starts up and runs fine but recently a staff member was editing labels in en.yml and config.rb for the new PUI and had to force a re-index. After the re-index, Archivesspace was complaining that rights_statement_pre_088 was not set to use UTF8 for its character encoding.
I was able to resolve the issue by dropping and then re-creating our dev DB from our live DB but I am curious about rights_statement_pre_088. The table still exists though no errors are currently being thrown.
Has anyone else encountered this or have any advice?
Chelsea Lobdell
Library Web Developer/ Swarthmore College
clobdel1 at swarthmore.edu<mailto:clobdel1 at swarthmore.edu> / (610)690-6818
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170919/bf914e9b/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 4009 bytes
Desc: image001.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170919/bf914e9b/attachment.jpg>

More information about the Archivesspace_Users_Group mailing list