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!
--
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.