Hi Rob,

It looks like the manual is out of date.  The latest version of the 
ArchonMigrator tool https://github.com/archivesspace/ArchonMigrator supports 
1.4.2 (the last release before the container management features were added).  
Other than that, I would say you have the right approach.  Archon -> ASpace 
1.4.2 -> the current version of ASpace.  I do this semi-regularly, and it works 
well.

Now for the geeky questions. :-)

Brian


— 
Brian Harrington
Migration Specialist
LYRASIS
brian.harring...@lyrasis.org
Skype: abbistani


> On Jul 7, 2017, at 9:47 AM, Rob Green <rob.gr...@uni.edu> wrote:
> 
> Hi!  No difficult geeky questions, I promise!   
> 
> I'm leading my University's effort to bring Archon content into 
> ArchivesSpace, and see that the migration manual is intended for moving from 
> Archon 3.21-rev2  to ArchivesSpace 1.0.4.   I'm thinking the most prudent 
> approach will be to install ASpace 1.0.4 on our servers, do the migration, 
> and then update to ASpace 2.0.x.   
> 
> From your guys' experience, is there anything dumb / misguided / foolhardy / 
> horrifying about that approach?  Just want to cover my bases before 
> committing to this approach...
> 
> Thanks!
> Rob
> 
> a.k.a. The New Guy
> 
> 
> 
> Rob Green   rob.gr...@uni.edu
> Web Developer III
> Chair, Library Organizational Development Committee
> UNI P&S Council: At-Large Rep & Employee Relations Chair 
> Rod Library, University of Northern Iowa (Room 231)
> Cedar Falls, Iowa 50613-3675   | (319) 273-6273 
> about.me/robgreeniowa  | "Campaigner" (ENFP)
> 
> * Report web problems via https://servicehub.uni.edu *
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Reply via email to