<html><head><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><div class="">Yes: I think publish/publish-all was a design error that has caused much confusion for users. </div><div class="">First, “publish” is a verb that’s being used as an attribute. It should have been “public” . </div><div class="">And the “publish all” button, which is a verb, just made if more confusing. </div><div class=""><br class=""></div><div class="">In most cases, for most libraries, public is a better default. </div><div class="">If public was the default and the checkbox was “internal” , there would be less need for a button to change the status of all children to “publish” . ( Maybe there is a way to make the defaults for different records configurable, or make the defaults for different kinds of notes different. ) </div><div class=""><br class=""></div><div class="">But there is still a use case for a “publish” (as a verb) button, that would trigger PUI indexing and perhaps some other actions. </div><div class="">As it works currently, incomplete records that are correctly marked to be public go out to the PUI and OAI endpoints. </div><div class="">Changing the finding aid status to complete does not trigger any action. </div><div class=""><br class=""></div><div class="">So perhaps there should be a “publish” button that changes finding aid status, creates an event record that indicates that the resource was published, and triggers PUI indexing. </div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">— Steve Majewski</div><div class=""><br class=""></div><br class=""><div><blockquote type="cite" class=""><div class="">On Sep 13, 2018, at 9:54 AM, Kennedy, Nancy <<a href="mailto:KennedyN@si.edu" class="">KennedyN@si.edu</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="WordSection1" style="page: WordSection1; font-family: Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class="">Thanks, Noah, Brian.<span class="Apple-converted-space"> </span><o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class="">Noah – re:<span class="Apple-converted-space"> </span></span><span style="color: rgb(31, 73, 125);" class="">“we keep track of the publication status of a finding aid using the Finding Aid Status field” . We do the same thing, using Finding Aid Status to drive the EAD export.<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class="">Using FA Status has worked pretty well… except that screen labels like “publish?” leads to some (I’d say legitimately!) confused users. Especially when there is, say, a network slow down and people try to troubleshoot by clicking on lots of inviting buttons… like “publish all”. We try to train everyone on what “Publish?” checkbox means, but it’s easy to confuse.<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class="">I’ve considered relabeling the ‘’Publish?” field to something like ‘External Audience’ … but I don’t want to move us far afield form the core archivesspace code/documentation. If I change the display label, my users will understand that we mean<span class="Apple-converted-space"> </span><i class="">audience</i><span class="Apple-converted-space"> </span>and not<span class="Apple-converted-space"> </span><i class="">status</i><span class="Apple-converted-space"> </span>. The problem is changing labels means our views will drift away from the main core archivesspace documentation, screencasts etc. And the term ‘publish” appears in many places. Label translation seems like a band aid (and not a very good one). A 2<sup class="">nd</sup><span class="Apple-converted-space"> </span>element specific to audience would probably be much better than a label change.<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class="">Nancy<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div class=""><div style="border-style: solid none none; border-top-width: 1pt; border-top-color: rgb(225, 225, 225); padding: 3pt 0in 0in;" class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><b class="">From:</b><span class="Apple-converted-space"> </span><a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" class="">archivesspace_users_group-bounces@lyralists.lyrasis.org</a> <<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" class="">archivesspace_users_group-bounces@lyralists.lyrasis.org</a>><span class="Apple-converted-space"> </span><b class="">On Behalf Of<span class="Apple-converted-space"> </span></b>Brian Thomas<br class=""><b class="">Sent:</b><span class="Apple-converted-space"> </span>Thursday, September 13, 2018 9:22 AM<br class=""><b class="">To:</b><span class="Apple-converted-space"> </span>'Archivesspace Users Group' <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org" class="">archivesspace_users_group@lyralists.lyrasis.org</a>><br class=""><b class="">Subject:</b><span class="Apple-converted-space"> </span>Re: [Archivesspace_Users_Group] Publish All workflows<o:p class=""></o:p></div></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Hi all,<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">I cannot speak to Noah’s questions re how to keep track of published vs. unpublished elements as I am more on the techy side here in electronic records v. the processing side. But I wanted to voice an agreement with Nancy that having an internal audience only checkbox that blocks publication would be a good enhancement. That way one can in a fell swoop still publish all things intended for the public, without having to go back and unpublish all the things that should not have been.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Thanks,<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Brian Thomas<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Electronic Records Specialist<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Texas State Library and Archives Commission<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">1201 Brazos Street<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Austin, TX 78701<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">PH: (512) 475-3374<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">e-mail:<span class="Apple-converted-space"> </span><a href="x-msg://1/bthomas@tsl.texas.gov" style="color: rgb(149, 79, 114); text-decoration: underline;" class=""><span style="color: blue;" class="">bthomas@tsl.texas.gov</span></a><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><a href="http://tsl.texas.gov/" style="color: rgb(149, 79, 114); text-decoration: underline;" class=""><span style="color: blue;" class="">tsl.texas.gov</span></a><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class=""><span id="cid:image001.png@01D44B47.CBEA2CF0"><image001.png></span></span><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div class=""><div style="border-style: solid none none; border-top-width: 1pt; border-top-color: rgb(225, 225, 225); padding: 3pt 0in 0in;" class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><b class="">From:</b><span class="Apple-converted-space"> </span><a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" style="color: rgb(149, 79, 114); text-decoration: underline;" class="">archivesspace_users_group-bounces@lyralists.lyrasis.org</a><span class="Apple-converted-space"> </span><<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" style="color: rgb(149, 79, 114); text-decoration: underline;" class="">archivesspace_users_group-bounces@lyralists.lyrasis.org</a>><span class="Apple-converted-space"> </span><b class="">On Behalf Of<span class="Apple-converted-space"> </span></b>Noah Huffman<br class=""><b class="">Sent:</b><span class="Apple-converted-space"> </span>Thursday, September 13, 2018 8:10 AM<br class=""><b class="">To:</b><span class="Apple-converted-space"> </span>Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org" style="color: rgb(149, 79, 114); text-decoration: underline;" class="">archivesspace_users_group@lyralists.lyrasis.org</a>><br class=""><b class="">Subject:</b><span class="Apple-converted-space"> </span>Re: [Archivesspace_Users_Group] Publish All workflows<o:p class=""></o:p></div></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class="">Hi Nancy,<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class="">We ran into a similar problem to the one you describe—folks accidentally clicking “publish all” when a resource record contained some archival objects that should remain unpublished.<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class="">To try to prevent this, we have a general local practice that if a resource record contains any archival objects that should remain unpublished (internal only), then we make a note of that in the Repository Processing Note field. The Repository Processing Note is an internal-only field and fairly easy to review before clicking “publish all.” We also have some scripts that batch export EADs and publish all at the same time. Those scripts will print out the content of the Repository Processing Note field and require confirmation before proceeding. This isn’t a fail-proof solution, but has helped mitigate the problem of publishing things we didn’t intend to publish. We’re also not currently using the ASpace PUI, so we have at least some mediation before publishing records as EAD.<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class="">RE: the audience vs. publish distinction, we keep track of the publication status of a finding aid using the Finding Aid Status field (e.g. in-progress, completed, published, under review, etc.). That has no effect on the visibility of a record in the public interface, but allows us to record the workflow state of a resource record in one field and the audience/visibility in another.<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class="">I’m also curious how others keep track of the publish/unpublish status on records that may contain a mix of published and unpublished archival objects. It would be nice if there was a way to know (at the top level) if a resource contained unpublished descendants, or if there was a way to quickly view all of the unpublished archival objects in any given resource record. As far as I can tell you can do an advanced search to locate all unpublished archival objects, but there is no obvious way to limit that search to a particular resource.<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class="">-Noah<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 10pt; font-family: 'Arial Narrow', sans-serif; color: rgb(64, 64, 64);" class="">================<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 10pt; font-family: 'Arial Narrow', sans-serif; color: rgb(64, 64, 64);" class="">Noah Huffman<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 10pt; font-family: 'Arial Narrow', sans-serif; color: rgb(64, 64, 64);" class="">Archivist for Metadata, Systems, and Digital Records<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 10pt; font-family: 'Arial Narrow', sans-serif; color: rgb(64, 64, 64);" class="">David M. Rubenstein Rare Book & Manuscript Library<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 10pt; font-family: 'Arial Narrow', sans-serif; color: rgb(64, 64, 64);" class="">Duke University | 919-660-5982<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 10pt; font-family: 'Arial Narrow', sans-serif; color: rgb(64, 64, 64);" class=""><a href="https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flibrary.duke.edu%2Frubenstein%2F&data=02%7C01%7Cbthomas%40tsl.texas.gov%7C6e19455dbaae4ca5842408d6197a40da%7Ca4597bff9f384145a0334a2168399a5e%7C0%7C0%7C636724410210278412&sdata=ITwIeJKvxl3wQ25VbQtDPbpEJTyDLV1fvhdXXSBOJxk%3D&reserved=0" style="color: rgb(149, 79, 114); text-decoration: underline;" class=""><span style="color: rgb(64, 64, 64);" class="">http://library.duke.edu/rubenstein/</span></a><o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div class=""><div style="border-style: solid none none; border-top-width: 1pt; border-top-color: rgb(225, 225, 225); padding: 3pt 0in 0in;" class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><b class="">From:</b><span class="Apple-converted-space"> </span><a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" style="color: rgb(149, 79, 114); text-decoration: underline;" class="">archivesspace_users_group-bounces@lyralists.lyrasis.org</a><span class="Apple-converted-space"> </span><<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" style="color: rgb(149, 79, 114); text-decoration: underline;" class="">archivesspace_users_group-bounces@lyralists.lyrasis.org</a>><span class="Apple-converted-space"> </span><b class="">On Behalf Of<span class="Apple-converted-space"> </span></b>Kennedy, Nancy<br class=""><b class="">Sent:</b><span class="Apple-converted-space"> </span>Thursday, September 13, 2018 8:21 AM<br class=""><b class="">To:</b><span class="Apple-converted-space"> </span>Archivesspace Users Group (<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org" style="color: rgb(149, 79, 114); text-decoration: underline;" class="">archivesspace_users_group@lyralists.lyrasis.org</a>) <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org" style="color: rgb(149, 79, 114); text-decoration: underline;" class="">archivesspace_users_group@lyralists.lyrasis.org</a>><br class=""><b class="">Subject:</b><span class="Apple-converted-space"> </span>[Archivesspace_Users_Group] Publish All workflows<o:p class=""></o:p></div></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Hello all,<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">We have had a few cases where users hit the ‘Publish All’ button for collections containing ‘internal’ archival_objects or notes (i.e. where the EAD @audience is ”internal”). <o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">I wonder how other institutions handle collections with ‘internal’ content? What workflows or fail-safes do you use? Given that publish all can result in thousands of internal ao or notes flipping to public, without an easy undo, I wonder what kinds of plugins or workflow steps we can take to prevent this happening again. <o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">In our situation, an ideal solution would be to separate ‘publish’ into 2 distinct checkboxes : one for status (publish true/false) and one for audience (internal / external). Which would of course be quite involved. It does however seem like it would be helpful all around if ‘Publish?’ vs ‘Audience?’ could be separate elements, so that I can protect internal audience material from publishing.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">What do you all think?<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Nancy<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Nancy Kennedy<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Smithsonian Institution<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><a href="mailto:kennedyn@si.edu" style="color: rgb(149, 79, 114); text-decoration: underline;" class="">kennedyn@si.edu</a><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div></div><span style="font-family: Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">_______________________________________________</span><br style="font-family: Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">Archivesspace_Users_Group mailing list</span><br style="font-family: Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class=""><a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org" class="">Archivesspace_Users_Group@lyralists.lyrasis.org</a></span><br style="font-family: Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class=""><a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" class="">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a></span></div></blockquote></div><br class=""></body></html>