importing from Archon

78 views
Skip to first unread message

anne...@gmail.com

unread,
Apr 26, 2017, 1:01:40 PM4/26/17
to AtoM Users
I was wondering if anyone had experience migrating EAD finding aids from Archon. I'm doing them one at a time through the import menu. It is mostly going fine, with a couple of minor changes to the EAD File. 

Because we didn't have that many finding aids in Archon to begin with, and there is unfortunately quite a bit of junk in Archon I don't want to migrate to AtoM (the finding aids were so poor it is easier to start over in some cases) I am finding the one at a time migrating is going all right. I'm not well versed in this, but I think we could do a bulk import with a CSV file, but I wasn't sure how to set it up, and by the time I got it working I figured I could have most of our finding aids in AtoM the one at a time method.

Anyone migrating from Archon have any wisdom? 

Dan Gillean

unread,
Apr 26, 2017, 2:29:57 PM4/26/17
to ICA-AtoM Users
Hi Anne,

If you have access to the command-line, you can try importing your EAD XML in bulk that way - see:

I'm also attaching a sort of crosswalk, which I find can be helpful for understanding how AtoM has implemented its EAD. Essentially, I've filled out every field in the various templates with the content standard's name, and then used the EAD export - you can look at this in a text editor and/or try importing it to see the kind of EAD XML encoding that AtoM expects for each element.

We love using OpenRefine during our data migrations to help clean up data - it's well known for managing CSV files and the like, but you can also use it with XML. If you discover some data loss due to differences in mapping from your Archon EAD and AtoM, you might try using something like OpenRefine to help clean it up without having to make individual manual cleanups.

For migration advice in general, I've made a recent post here with some tips for users, which also links to an earlier post with further advice.

The advice focuses a bit more on CSV migrations, but much of the initial steps and considerations are the same for EAD XML.


I hope this helps a bit - good luck with the migration!


Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
604-527-2056
@accesstomemory

--
You received this message because you are subscribed to the Google Groups "AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-users+unsubscribe@googlegroups.com.
To post to this group, send email to ica-atom-users@googlegroups.com.
Visit this group at https://groups.google.com/group/ica-atom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/72667aeb-c053-4d03-aacb-6b204bcd55d3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

isad-ead-crosswalk-2.3.xml
dacs-crosswalk-2.4.xml
Reply all
Reply to author
Forward
0 new messages