[Archivesspace_Users_Group] Importing legacy accession records

Galligan, Patrick PGalligan at rockarch.org
Thu Jul 7 14:41:20 EDT 2016


If you mean just importing through background jobs into the AS database, you'll be totally fine.

It may throw an error if your Accession identifier is not unique and already exists in the system, but that's as bad I'd expect it to get.

Patrick Galligan
Rockefeller Archive Center
Assistant Digital Archivist

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Faith F. Charlton
Sent: Thursday, July 07, 2016 2:33 PM
To: Archivesspace Users Group
Subject: [Archivesspace_Users_Group] Importing legacy accession records

Hello everyone-

I have a (somewhat paranoid) question for the many of you who have already experienced the lovely joys of migrating or importing legacy accession records. I'm wondering whether anyone has had an issue importing legacy data when there were existing accession records in the application. We intend to start creating new accession records while simultaneously planning the "fun" task of importing our legacy records (which will require the manipulation of 3 data sets: spreadsheets, a legacy access database, and Word docs--Yip), and I just want to make sure that having existing records won't muck anything up when we finally import the legacy stuff (presuming that that data is clean as a whistle ;).

Faith Charlton
Lead Processing Archivist, Manuscript Division Collections
Princeton University Library
One Washington Road
Princeton, NJ 08540
faithc at princeton.edu<mailto:faithc at princeton.edu>

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

More information about the Archivesspace_Users_Group mailing list