[Archivesspace_Users_Group] AT Migration problem with repository processing note

Brad Westbrook brad.westbrook at lyrasis.org
Fri Jan 29 12:03:49 EST 2016

Hi, Ian,

Repository processing notes at the component level are not mapped by the AT migration script.  It appears the reason for this might be that the Repository Processing Note was added to the component level subsequent to the migration mapping, as the map indicates there is (was) target for the field in ArchivesSpace.

The map for the AT migrator is at http://archivesspace.org/migrations.

May I ask what kind of data GWU has recorded in this note?

Brad W.

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Hardy, Ian
Sent: Friday, January 29, 2016 9:15 AM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] AT Migration problem with repository processing note


We noticed that the repository processing note field did not migrate from Toolkit to Aspace for items below the collection level. We've been using the Harvard Plugin. I searched the Aspace DB for some sample note text and found those notes did not make it to Aspace at all.

Has anyone else experienced a similar problem, or resolved a similar problem?



Ian Hardy
Systems Specialist
GW Libraries
ihardy at gwu.edu<mailto:ihardy at email.gwu.edu>
helpdesk: (202) 994-8278
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20160129/d7158843/attachment.html>

More information about the Archivesspace_Users_Group mailing list