[Archivesspace_Users_Group] Migration error: character limit

[Custer, Mark]

Hi all,

I wanted to revive this thread:  are others encountering the character limit issue?  if so, how are you handling it?

Also, is this something that will be addressed within the ArchivesSpace application?  There are lots of finding aids that won't always have notes that are less than 65,000 characters. Furthermore, since it seems that both the AT and Archon permitted much more than that, and since it's not a limitation imposed by the MySQL database, is there a way to identify what's imposing the limit in ArchivesSpace and see if that dependency can be removed or circumvented somehow?

Mark



From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Holland, Andrew S
Sent: Thursday, January 08, 2015 1:46 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Migration error: character limit

I just removed a bunch of the text before I migrated. I can't actually remember if I tried adding it back in after the successful migration or not.

If you are on SQL server, you can run something like:
SELECT * FROM tblCollections_Collections WHERE (LEN(field_name) > 65000)

If LEN gives you an error, try DATALENGTH

I think on mysql you just swap out LEN for LENGTH.

-Andrew

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 Colleen McFarland
Sent: Thursday, January 08, 2015 10:48 AM
To: archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Migration error: character limit

Good morning:

We're encountering migration errors of "must be less than 65,000 characters" (TEXT field) for fields in Archon which are MEDIUMTEXT and which are quite lengthy. So far in testing we've resolved these by deleting that data. One, is there a way to migrate these large text fields, given that we were allowed more space in Archon? Two, is there a query we can do on the Archon database to identify these large fields before finding them one-by-one as errors in the migration process?

Thanks in advance!

Best,
Colleen

Colleen McFarland, Director of Archives and Records Management, Mennonite Church USA
colleenm at mennoniteusa.org<mailto:colleenm at mennoniteusa.org>, 1700 S. Main St. Goshen, IN 46526, 574-523-3039 (direct), 1-866-866-2872 ext. 23039 (toll-free)
www.mennoniteusa.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.mennoniteusa.org_&d=AwMFAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=s7ciGQfUJeaV_ryx908hbeXDoU9aqDwDN0Z0VbfsJ3Y&m=tfu8dRqphtXTeNkhOkJFqQNAyeXi54xQAmkFbpqwmbA&s=MIS-jT_OX8UjDcRLRKb6z5yd2KwyEN_1eCmqOVF6w_U&e=>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20150324/7dbc2be4/attachment.html>