[Archivesspace_Users_Group] ASpace 3.4.0 and new ILMS Bib Number length

Joshua D. Shaw Joshua.D.Shaw at dartmouth.edu
Mon Aug 7 07:48:00 EDT 2023

Hi Mark

The fields are defined in the db (via the migrations). The real_x fields (and integer_x and string_x fields) in user_defined are varchars, so any limits you're hitting aren't in the db. There's also nothing in the plugin that would limit the field lengths - unless you've customized the plugin.

What issue are you seeing?


From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Mark Cyzyk <mcyzyk at gmail.com>
Sent: Sunday, August 6, 2023 12:56 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] ASpace 3.4.0 and new ILMS Bib Number length


We recently upgraded to ASpace 3.4.0.  Everything is fine except for one

Insofar as we also recently migrated our ILMS here, our Bib Numbers are
now larger strings than before.  They are now 18 characters.

How/where can I Up this field length?  I've looked in the various
Locales files.

As far as I can tell, Bib Number is in the
resource_user_defined__real_1_ field, but I'm not finding where the
length of that field is limited.

FYI, we are using the User Defined in Basic plugin.

Advice appreciated,


Mark Cyzyk, M.A., M.L.S.
Library Applications Group
The Sheridan Libraries
The Johns Hopkins University
mcyzyk at jhu.edu

Verba volant, scripta manent.

Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20230807/a5ae7f44/attachment.html>

More information about the Archivesspace_Users_Group mailing list