[Archivesspace_Users_Group] checking the success of migration from AT to Aspace

[Galligan, Patrick]

Jen,

Create fake records in AT for all of the different sections (Resources, Accessions, Digital Objects, Subjects, etc.). Put the field names as the content for each field whenever possible, or pick a date that you will recognize. Utilize all possible fields in this test record.

This way, you can look down a list of fields in AT, check where they migrated to in AS, and whether they act as you would expect. It will also tell you if there are any fields missing from the AT to AS migration (this shouldn’t happen unless you got thrown some error messages). Using the field names as the content just help you do quick eye checks of the data.

Doing this will at least give you a way to make sure everything is mapping to where you expect.

Patrick Galligan
Rockefeller Archive Center
Assistant Digital Archivist
914-366-6386

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Jennifer King
Sent: Tuesday, November 24, 2015 2:39 PM
To: Archivesspace Users Group
Subject: [Archivesspace_Users_Group] checking the success of migration from AT to Aspace

Hello all,

We have completed our first test migration from AT to Aspace and are in the midst of planning a thorough review to ensure our data all moved and mapped appropriately. Does anyone have advice for a methodology they employed that worked well or warnings about what did not work well?

Thank you,

Jen

--
Jennifer King
Interim Collections Coordinator and Manuscripts Librarian
Special Collections Research Center
George Washington University
Jenking at gwu.edu<mailto:Jenking at gwu.edu>
202-994-0628
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20151124/fa0b8b8d/attachment.html>