[Archivesspace_Users_Group] Plugin for bulk data cleanup of language information

Thu Jan 9 09:31:12 EST 2020

Thank you. I will share this with our web technology group.

Donnelly Lancaster Walton
Archival Access Coordinator, Special Collections
University Libraries
The University of Alabama<https://www.ua.edu/>
W. S. Hoole Library, Mary Harmon Bryant Hall
Box 870266
Tuscaloosa, AL 35487
Office 205-348-0505<tel:205-348-0505>
dfwalton at ua.edu<mailto:dfwalton at ua.edu> | https://www.lib.ua.edu/libraries/hoole/
[The University of Alabama]<https://www.ua.edu/>

From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Majewski, Steven Dennis (sdm7g)
Sent: Wednesday, January 8, 2020 1:15 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Plugin for bulk data cleanup of language information

In most cases, the info displayed in the staff webapp comes from the database but info displayed in the public view usually comes from the SOLR index.  When you edit and save records in the staff interface, the update triggers a SOLR reindex of that record. If you make “back door” changes thru MySQL or the API, the SOLR reindex may not get triggered. So probably not unexpected (although I don’t see it noted in the readme for that script).

Editing and saving the record triggers the reindex, but rather than doing that manually for all of the updated records, you can trigger a SOLR reindex by deleting the files in data/indexer_state/ and data/indexer_pui_state/ on the server.
( Or you can be more specific, if you know exactly what needs to be reindexed. )

— Steve M.

On Jan 8, 2020, at 1:19 PM, Walton, Donnelly <dfwalton at ua.edu<mailto:dfwalton at ua.edu>> wrote:

We are upgrading to 2.7.0 (on a test server first). We noticed that in the PUI, our Finding Aid data showed Language of Description as “Undetermined” and Script of Description as “Code for Undetermined Script”  in every record. I used the https://github.com/archivesspace-plugins/batch_update_lang_and_script plugin to fix this problem. This corrected the problem in the staff side, but when I look at the public side, the data still shows “Undetermined” and “Code for Undetermined Script” in the PUI.  I noticed that if I go to the  record in the staff interface in edit mode, then save, the change will show up in the PUI.  Is this what is expected in the cleanup process, or did something go wrong?

I accidentally sent this to the Member Reps group first. Sorry for any duplication.

Thanks,

Donnelly Lancaster Walton
Archival Access Coordinator, Special Collections
University Libraries
The University of Alabama<https://www.ua.edu/>
W. S. Hoole Library, Mary Harmon Bryant Hall
Box 870266
Tuscaloosa, AL 35487
Office 205-348-0505<tel:205-348-0505>
dfwalton at ua.edu<mailto:dfwalton at ua.edu> | https://www.lib.ua.edu/libraries/hoole/
<image001.gif><https://www.ua.edu/>

From: archivesspace_member_reps-bounces at lyralists.lyrasis.org<mailto:archivesspace_member_reps-bounces at lyralists.lyrasis.org> <archivesspace_member_reps-bounces at lyralists.lyrasis.org<mailto:archivesspace_member_reps-bounces at lyralists.lyrasis.org>> On Behalf Of Christine Di Bella
Sent: Wednesday, November 6, 2019 11:31 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>; Archivesspace Member Reps <archivesspace_member_reps at lyralists.lyrasis.org<mailto:archivesspace_member_reps at lyralists.lyrasis.org>>; archivesspace_tac at lyralists.lyrasis.org<mailto:archivesspace_tac at lyralists.lyrasis.org>; archivesspace_uac at lyralists.lyrasis.org<mailto:archivesspace_uac at lyralists.lyrasis.org>
Subject: [Archivesspace_member_reps] plugins available for bulk data cleanup of language information/RDE template issue

As mentioned in the release announcement for ArchivesSpace v2.7.0, the changes in the languages area will require data cleanup to existing records for some people. Upon upgrade, existing language information is migrated to the new or newly structured fields. While some ways of recording information could be easily accommodated in this migration, because there are so many different ways language information could have been recorded previously, some situations will require data cleanup.

We’ve put together three plugins that you can use, or use as examples, to handle some common situations. These only run on resource records. They are:

  *   Batch update language and script of description in resource records to one language and/or script of description value:https://github.com/archivesspace-plugins/batch_update_lang_and_script - for cases where all or most of your description is done in one language and script, this will help you do a global or repository-specific update.

  *   Batch update language of materials in resource records currently lacking a controlled value language:https://github.com/archivesspace-plugins/batch_update_langmaterials - for situations where all or most of your materials that do not currently have a language value are in one language, this will help you do a global or repository-specific update.

  *   Batch update language of materials records for resource records currently lacking a controlled value language by matching a text string in a note: https://github.com/archivesspace-plugins/batch_update_langmaterials_from_note - for situations where specific note text can be easily parsed into a controlled value language, this will help you do a targeted update. You will be able to choose whether to keep or delete the notes after running this job.

As with any plugins that change information in records, we strongly recommend you backup your data before running them and review the results in records afterwards before moving on to do more work in your ArchivesSpace. These plugins make changes to your records that cannot be undone, though you can edit individual records or run the plugins again at any point. Once you’ve run the plugin(s) and are satisfied with the results, you can disable the plugins at any time.

Also, we have been alerted to an issue where previously created RDE templates do not display correctly in v2.7.0 due to the language changes. This will be corrected in the next release, but we are working on a plugin that can provide a fix for people who need it quicker than that. In the interim, feel free to reach out to us if you need guidance on fixing this locally.

We hope these resources are helpful. Please let us know if you need help with them or have other languages-related questions.

Christine

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

<image003.jpg>

_______________________________________________
Archivesspace_member_reps mailing list
Archivesspace_member_reps at lyralists.lyrasis.org<mailto:Archivesspace_member_reps at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_member_reps
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto: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/20200109/b1bff285/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 6052 bytes
Desc: image001.gif
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200109/b1bff285/attachment.gif>