[Archivesspace_Users_Group] Data migration report

Nathan Hosburgh NHOSBURGH at Rollins.edu
Thu Oct 9 09:17:59 EDT 2014

I would be interested if anyone has produced a similar report regarding migration from Archon to ArchivesSpace.


From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Emma Jolley
Sent: Wednesday, October 08, 2014 10:50 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Data migration report

Dear All

I wonder if there has been any other official responses to the excellent migration report prepared by Harvard. We experienced many of the same issues in our migration testing and would be interested in knowing whether the issues identified are schedule to have work done on them.

Many thanks


Emma Jolley| Curator of Digital Archives, Pictures and Manuscripts Branch|National Library of Australia Canberra ACT 2600
e: emma.jolley at nla.gov.au<mailto:emma.jolley at nla.gov.au>|t: 02 6262 1456| www.nla.gov.au/ms<http://www.nla.gov.au/ms>

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Nathan Stevens
Sent: Tuesday, 30 September 2014 12:11 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Data migration report

Unfortunately, ArchivesSpace requires valid URIs<http://en.wikipedia.org/wiki/File_URI_scheme#Windows> for external links, hence the addition of file:// to document locations.  I could try adding a thrid slash which may solve this, but if it doesn't, there really isn't much that can be done on the migration tool side until this requirements changes in ASpace.
Subdivisions types for Subjects and Name are required in the AT (You cannot save a record through the AT interface if those types are not selected).  The only way I know of they can be incorrect, or are missing, is when data is ingested directly into the AT database which the migration tool cannot account for.

As such, entering correct values for these sub types must done through the AT backend database directly, and not through the migration tool.

On Fri, Sep 26, 2014 at 5:13 PM, Wise, Rachel <rwise at hbs.edu<mailto:rwise at hbs.edu>> wrote:

Attached is a report of some issues we encountered migrating data from Archivists Toolkit to ArchivesSpace here at Harvard.  We’ve compiled our issues into a single document recognizing that some of these issues may have been noted in separate emails from other institutions.

The report includes:

•         Data Migration issues

•         User support issues

•         User interface issues

•         Reporting and printing needs

•         Critical Bug

•         Searching, Facets, and Record Lists
If you have any question let me know.
Rachel (sending on behalf of Harvard Archivists Toolkit/ArchivesSpace users)

Rachel Wise, HBS Archivist
Knowledge & Library Services
Harvard Business School
Baker Library | Bloomberg Center 123K
Boston, MA 02163
(617) 496-6822<tel:%28617%29%20496-6822>

Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>

Nathan Stevens
Digital Library Technology Services
New York University

ns96 at nyu.edu<mailto:ns96 at nyu.edu>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20141009/8c0dbf9a/attachment.html>

More information about the Archivesspace_Users_Group mailing list