<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><br class=""></div>Hi Ryan,<div class=""><br class=""></div><div class="">I’ve updated the readmes.</div><div class=""><br class=""></div><div class="">I believe the ArchivesSpace team is planning to merge the CM plugin with the core, so I would recommend waiting for that.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Cheers,</div><div class="">James</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><div class=""><blockquote type="cite" class=""><div class="">On Aug 6, 2015, at 7:10 AM, Ryan Rotter <<a href="mailto:rrotter@umich.edu" class="">rrotter@umich.edu</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">So, to be clear, if we want to use the CM plugin with a current version of AS container_management_dartmouth is the best version at present? Since I'm not a client of hudmol I don't have much ground to ask you for anything, but it would be helpful if the README.md or release notes made it clear what releases of AS your plugin was compatible with.</div><div class="gmail_extra"><br class=""><div class="gmail_quote">On 5 August 2015 at 02:43, James Bullen <span dir="ltr" class=""><<a href="mailto:james@hudmol.com" target="_blank" class="">james@hudmol.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class=""><div class=""><br class=""></div>Hi Steve,<div class=""><br class=""></div><div class="">Just on the container management repos:</div><div class=""><br class=""></div><div class="">hudmol/container_management is the version developed for Yale which currently works against AS v1.1.</div><div class=""><br class=""></div><div class="">hudmol/container_management_dartmouth is a fork developed for Dartmouth that includes support for AS v1.3 and the ability to print container labels.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Cheers,</div><div class="">James</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><blockquote type="cite" class=""><div class=""><div class="h5"><div class="">On Aug 5, 2015, at 2:25 PM, Steven Majewski <<a href="mailto:sdm7g@virginia.edu" target="_blank" class="">sdm7g@virginia.edu</a>> wrote:</div><br class=""></div></div><div class=""><div class=""><div class="h5"><div style="word-wrap:break-word" class=""><div class=""><br class=""></div><div class="">We made an initial attempt to migrate EAD from our test server onto a production server by exporting with ead_export.sh script on the test server and importing on production server. Everything appeared to work OK, but on further inspection we found that the barcodes were not imported. Further inspection showed that the barcodes are not exported in EAD. </div><div class=""><br class=""></div><div class="">Looking at the export/import mappings spreadsheet, I see that a mapping is given for barcodes in ArchivesSpace to EAD, but not in EAD to ArchivesSpace mappings. </div><div class=""><br class=""></div><div class="">Looking further, I find a Jira issue reporting this:</div><div class=""><a href="https://archivesspace.atlassian.net/browse/AR-983?jql=text%20~%20%22container%20label%22" target="_blank" class="">https://archivesspace.atlassian.net/browse/AR-983?jql=text%20~%20%22container%20label%22</a></div><div class=""><br class=""></div><div class="">pointing me to the Yale-ead-exporter plugin:</div><div class=""><br class=""></div><div class=""><a href="https://github.com/archivesspace/yale-ead-exporter" target="_blank" class="">https://github.com/archivesspace/yale-ead-exporter</a></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">I downloaded and installed the yale-ead-exporter. </div><div class="">ArchivesSpace fails to restart do to a syntax error. </div><div class=""><br class=""></div><div class="">I fixed and reported syntax error:</div><div class=""><a href="https://github.com/archivesspace/yale-ead-exporter/issues/1" target="_blank" class="">https://github.com/archivesspace/yale-ead-exporter/issues/1</a></div><div class=""><br class=""></div><div class="">and restarted successfully. </div><div class="">I installed plugin on both servers and did another export and import cycle. </div><div class=""><br class=""></div><div class="">This appeared to mostly work, except that instances of Type "Graphic Materials” with a barcode were imported as Type “Graphic” with a barcode of “Materials” . I changed the delimiter in both the export and import methods of the plugin from a space (“ “ ) to a bar ( “|” ). So far this seems to work. </div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">The main reason I bring this up in detail rather than just forking and fixing it is that my impression from the export/import mappings, JIRA thread, etc. is that these issues were unresolved due to a lack of consensus on how (or even whether) barcodes should be encoded. I’m hoping for some discussion and consensus on that issue now. </div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">I also understand that barcodes and location information might be something that some may not want published. Typically, one might use an @audience attribute to tag things in the EAD that shouldn’t be published, but that’s not available when encoding the barcode itself as an attribute. However, if we’re using EAD as the standard for transmission and archiving we need to include that info. Perhaps we need an export option that turns this feature off and on ( like the :use_numbered_c_tags or :include_daos flags ): this would need more extensive changes than the current plugin. </div><div class=""><br class=""></div><div class="">I’m also wondering if this is either addressed by the Yale Container Management work or if any changes here might conflict with that. I see many mentions of barcodes, but I didn’t see anything that looked like the export/import changes in the yale-ead-exporter plugin. </div><div class=""><br class=""></div><div class="">BTW: Is this the best and current repo for that work:</div><div class=""><a href="https://github.com/hudmol/container_management" target="_blank" class="">https://github.com/hudmol/container_management</a></div><div class=""><br class=""></div><div class="">I also see a container_management_dartmouth and a container branch on archivespace/archivesspace. </div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">— Steve Majewski</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div></div></div></div>_______________________________________________<br class="">Archivesspace_Users_Group mailing list<br class=""><a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org" target="_blank" class="">Archivesspace_Users_Group@lyralists.lyrasis.org</a><br class=""><a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" target="_blank" class="">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a><br class=""><br class=""><br class=""><br class=""></div></blockquote></div><br class=""></div><br class="">_______________________________________________<br class="">
Archivesspace_Users_Group mailing list<br class="">
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org" class="">Archivesspace_Users_Group@lyralists.lyrasis.org</a><br class="">
<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank" class="">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a><br class="">
<br class=""></blockquote></div><br class=""></div>
!DSPAM:55c27bd8191905858113537!
_______________________________________________<br class="">Archivesspace_Users_Group mailing list<br class=""><a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org" class="">Archivesspace_Users_Group@lyralists.lyrasis.org</a><br class=""><a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" class="">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a><br class=""><br class=""><br class="">!DSPAM:55c27bd8191905858113537!<br class=""></div></blockquote></div><br class=""></div></body></html>