[Archivesspace_Users_Group] Status migration advice
annee at radcliffe.harvard.edu
Wed Mar 30 15:15:10 EDT 2016
Apparently AS-76 is now AR-1426? This still seems to be unresolved. Harvard University continues to advocate for:
* The restoration of processing status to collection management records
* No reverse migration of data
* Processing event records should stay
Harvard University Member Representative
Head, Collection Services
Schlesinger Library, Radcliffe Institute
10 Garden St.
Cambridge, MA 02138
Find the Schlesinger Library on Facebook at https://www.facebook.com/SchlesingerLibrary
From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Valerie Addonizio
Sent: Tuesday, March 29, 2016 1:31 PM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Status migration advice
Hopkins is working to address a legacy problem with our Processing Status in preparation for going live with ASpace. However, knowing that processing_status is in a state of flux given the discussions around AR-1426<https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_browse_AR-2D1426&d=CwMFAg&c=WO-RGvefibhHBZq3fL85hQ&r=QRZODf9XXD3bgxGHWgBXsAvw7uhg6gGfVUJ1KmSajT8&m=m2Uufu22sE3bSzHY8ICmFBbBB6TH3itiM_v5IRLUleg&s=njmu4GjXhNSoJpJt5M7ng0sbuSlrZlDs6ctHkS4YAAw&e=>, we're wondering whether it will make sense to update AT with our accurate processing_status before migrating, rather than through the API after migrating. I am asking because I see mention of a plugin being written to move this field back for institutions that want it (I hesitatingly believe we are one such institution), and am wondering where that plugin will be looking, and whether putting the updated process_status into AT will simply make this easier in the future. Any comments welcome.
The Sheridan Libraries
Johns Hopkins University
vaddoniz at jhu.edu<mailto:vaddoniz at jhu.edu>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Archivesspace_Users_Group