[Archivesspace_Users_Group] ASpace v2.7.1 languages issue

Benn Joseph benn.joseph at northwestern.edu
Thu Aug 27 12:45:50 EDT 2020


Hi all,
We are upgrading from ArchivesSpace v2.4.1 to v2.7.1 as part of a plan to eventually get to 2.8-it was recommended that we to go to 2.7.1 first and sort out changes to the Languages sub-record first, so that's what we're doing. So far we've gone from 2.4.1 to 2.7.1 on our sandbox, and have discovered an unexpected behavior with languages for Archival Objects. Here's what we expected to happen (from the Atlas support site):
"If you have values in both Basic Information > Language of Materials and under Notes > Language of Materials in any version prior to v2.7.0 (which we do for many records):

  *   The values in Basic Information > Language of Materials will migrate to the new controlled value list under the new Languages sub-record in your Resource records as part of the update to v2.7.0. The presence of this information fulfills the requirement of the sub-record. You will not have to take any additional action for these records.
  *   The notes in Notes > Language of Materials will move from under the Notes heading to under the Language of Materials sub-record. They will display as text. Though this note alone does not meet the requirements of the sub-record, since it is paired with a Language (per the above), so you will not need to take any additional actions on these records."
This process worked successfully for Resource records, but for Archival Objects with both of the above values this is the result we're seeing:


*         The values in Basic Information > Language of Materials AND Notes > Language of Materials have both disappeared from the Archival Object.

*         There is now a new Language of Materials sub-record in the Archival Object that contains no data (just a blank text sub-note).

Upon moving to v2.7.1 we ran the batch_update_lang_and_script<https://github.com/archivesspace-plugins/batch_update_lang_and_script>  plugin; but it doesn't seem like this would have affected the Archival Objects in the way are seeing.

Has anyone else experienced this issue? We are following up with our hosting service too just in case there is a step we missed.

Best,
--Benn

Benn Joseph
Head, Collections Services
McCormick Library of Special Collections & University Archives
Northwestern University Libraries
Northwestern University
www.library.northwestern.edu
benn.joseph at northwestern.edu<mailto:benn.joseph at northwestern.edu%0d>
847.467.6581

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


More information about the Archivesspace_Users_Group mailing list