<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
        {font-family:Wingdings;
        panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:#0563C1;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:#954F72;
        text-decoration:underline;}
span.EmailStyle17
        {mso-style-type:personal-compose;
        font-family:"Calibri",sans-serif;
        color:windowtext;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-family:"Calibri",sans-serif;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
/* List Definitions */
@list l0
        {mso-list-id:195704213;
        mso-list-template-ids:-2030003630;}
@list l0:level1
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level2
        {mso-level-number-format:bullet;
        mso-level-text:o;
        mso-level-tab-stop:1.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:"Courier New";
        mso-bidi-font-family:"Times New Roman";}
@list l0:level3
        {mso-level-number-format:bullet;
        mso-level-text:\F0A7;
        mso-level-tab-stop:1.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l0:level4
        {mso-level-number-format:bullet;
        mso-level-text:\F0A7;
        mso-level-tab-stop:2.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l0:level5
        {mso-level-number-format:bullet;
        mso-level-text:\F0A7;
        mso-level-tab-stop:2.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l0:level6
        {mso-level-number-format:bullet;
        mso-level-text:\F0A7;
        mso-level-tab-stop:3.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l0:level7
        {mso-level-number-format:bullet;
        mso-level-text:\F0A7;
        mso-level-tab-stop:3.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l0:level8
        {mso-level-number-format:bullet;
        mso-level-text:\F0A7;
        mso-level-tab-stop:4.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l0:level9
        {mso-level-number-format:bullet;
        mso-level-text:\F0A7;
        mso-level-tab-stop:4.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l1
        {mso-list-id:811336116;
        mso-list-template-ids:-248631960;}
@list l1:level1
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l1:level2
        {mso-level-number-format:bullet;
        mso-level-text:o;
        mso-level-tab-stop:1.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:"Courier New";
        mso-bidi-font-family:"Times New Roman";}
@list l1:level3
        {mso-level-number-format:bullet;
        mso-level-text:\F0A7;
        mso-level-tab-stop:1.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l1:level4
        {mso-level-number-format:bullet;
        mso-level-text:\F0A7;
        mso-level-tab-stop:2.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l1:level5
        {mso-level-number-format:bullet;
        mso-level-text:\F0A7;
        mso-level-tab-stop:2.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l1:level6
        {mso-level-number-format:bullet;
        mso-level-text:\F0A7;
        mso-level-tab-stop:3.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l1:level7
        {mso-level-number-format:bullet;
        mso-level-text:\F0A7;
        mso-level-tab-stop:3.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l1:level8
        {mso-level-number-format:bullet;
        mso-level-text:\F0A7;
        mso-level-tab-stop:4.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l1:level9
        {mso-level-number-format:bullet;
        mso-level-text:\F0A7;
        mso-level-tab-stop:4.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l2
        {mso-list-id:906377566;
        mso-list-template-ids:876220324;}
@list l2:level1
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l2:level2
        {mso-level-number-format:bullet;
        mso-level-text:o;
        mso-level-tab-stop:1.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:"Courier New";
        mso-bidi-font-family:"Times New Roman";}
@list l2:level3
        {mso-level-number-format:bullet;
        mso-level-text:\F0A7;
        mso-level-tab-stop:1.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l2:level4
        {mso-level-number-format:bullet;
        mso-level-text:\F0A7;
        mso-level-tab-stop:2.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l2:level5
        {mso-level-number-format:bullet;
        mso-level-text:\F0A7;
        mso-level-tab-stop:2.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l2:level6
        {mso-level-number-format:bullet;
        mso-level-text:\F0A7;
        mso-level-tab-stop:3.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l2:level7
        {mso-level-number-format:bullet;
        mso-level-text:\F0A7;
        mso-level-tab-stop:3.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l2:level8
        {mso-level-number-format:bullet;
        mso-level-text:\F0A7;
        mso-level-tab-stop:4.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l2:level9
        {mso-level-number-format:bullet;
        mso-level-text:\F0A7;
        mso-level-tab-stop:4.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l3
        {mso-list-id:2107386541;
        mso-list-template-ids:-1362343052;}
@list l3:level1
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l3:level2
        {mso-level-number-format:bullet;
        mso-level-text:o;
        mso-level-tab-stop:1.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:"Courier New";
        mso-bidi-font-family:"Times New Roman";}
@list l3:level3
        {mso-level-number-format:bullet;
        mso-level-text:\F0A7;
        mso-level-tab-stop:1.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l3:level4
        {mso-level-number-format:bullet;
        mso-level-text:\F0A7;
        mso-level-tab-stop:2.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l3:level5
        {mso-level-number-format:bullet;
        mso-level-text:\F0A7;
        mso-level-tab-stop:2.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l3:level6
        {mso-level-number-format:bullet;
        mso-level-text:\F0A7;
        mso-level-tab-stop:3.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l3:level7
        {mso-level-number-format:bullet;
        mso-level-text:\F0A7;
        mso-level-tab-stop:3.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l3:level8
        {mso-level-number-format:bullet;
        mso-level-text:\F0A7;
        mso-level-tab-stop:4.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l3:level9
        {mso-level-number-format:bullet;
        mso-level-text:\F0A7;
        mso-level-tab-stop:4.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
ol
        {margin-bottom:0in;}
ul
        {margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in">
<span style="color:black"><img width="624" height="145" style="width:6.5in;height:1.5069in" id="Picture_x0020_2" src="cid:image001.jpg@01D34677.9DADC520" alt="ASpaceOrgHome.jpg"></span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in">
<b><span style="color:black">October 2017 Update</span></b><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in">
<span style="color:black">This month’s update includes a variety of highlights. We have a pre-release version of the Archivists' Toolkit migration tool that migrates directly into ArchivesSpace version 2.1.2, and we need help testing this before it goes live.
 We’re still accepting applications for a new DevOps Specialist to support the ArchivesSpace community. And read on for details on the upcoming PUI implementation strategies webinar on October 26!</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in">
<b><span style="color:black">Development</span></b><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in">
<span style="color:black">The ArchivesSpace team is pleased to release version 2.2.0!</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in">
<span style="color:black">You can download the new release from Github at</span><a href="https://github.com/archivesspace/archivesspace/releases/tag/v2.2.0"><span style="color:black">
</span><span style="color:#1155CC">https://github.com/archivesspace/archivesspace/releases/tag/v2.2.0</span></a><span style="color:black">. Please see the
</span><a href="http://archivesspace.github.io/archivesspace/user/upgrading-to-a-new-release-of-archivesspace/"><span style="color:#1155CC">technical documentation</span></a><span style="color:black"> for information on how to upgrade your ArchivesSpace installations.</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in">
<span style="color:black">We are especially pleased because this release includes two new areas of long-desired functionality contributed by community members:</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in">
<span style="color:black">Tufts University subsidized a new assessment module, based very closely on a community-authored specification and hewing closely to the functionality previously available in Archivists’ Toolkit. The development was done by Hudson Molonglo.
 Dan Santamaria and Adrienne Pruitt took the lead on the Tufts side in working closely with HM developers James Bullen, Mark Triggs, and Payten Giles. They also coordinated putting the module out for wider testing, in which people at institutions including
 the Smithsonian, Smith College, University of Michigan Special Collections, and the Historical Society of Pennsylvania participated.</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in">
<span style="color:black">Trevor Thornton of North Carolina State University and Noah Huffman of Duke University partnered to create an EAD3 exporter, based on a community-distributed specification. Trevor did the development and Noah did extensive and iterative
 testing. We are excited to have this first level of support for EAD3 in ArchivesSpace and see this as a building block for additional EAD3 support in future releases. Thanks also to Mark Custer at Yale for providing testing feedback.</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in">
<span style="color:black">Thank you so much to Dan, Adrienne, Trevor, and Noah for all their work in bringing these projects to completion and making the results available to the entire ArchivesSpace community. If your institution would like to get involved
 in subsidizing or working on development prioritized by the ArchivesSpace community, please get in touch with me or Laney.</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in">
<span style="color:black">This release also includes some bug fixes and improvements contributed by community members Steve Majewski, Chris Fitzpatrick, Mark Cooper, Payten Giles, and Christian von Kleist, as well as development work by our Tech Lead Laney
 McGlohon.</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in">
<span style="color:black">I want to note that this release does not include improvements to the relevancy ranking for search results in the new Public User Interface (JIRA issues:</span><a href="https://archivesspace.atlassian.net/browse/ANW-201"><span style="color:black">
</span><span style="color:#1155CC">https://archivesspace.atlassian.net/browse/ANW-201</span></a><span style="color:black"> and</span><a href="https://archivesspace.atlassian.net/browse/AR-1882"><span style="color:black">
</span><span style="color:#1155CC">https://archivesspace.atlassian.net/browse/AR-1882</span></a><span style="color:black">). Knowing how important this is for many users, we have prioritized it for a fix and been working on it since the tickets were first filed;
 unfortunately due to the complexity of the problem, we have not yet been able to address it satisfactorily enough to include a fix in this release. Rather than further delay releasing the new functionality that our community members have worked so hard on,
 we have chosen to put out this release now and will keep working on the PUI indexer issue. We intend to have another minor release, that hopefully includes those improvements, later in October or early in November.</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in">
<span style="color:black">Thanks as always to all who contributed to this release, by identifying needed improvements, writing specifications, writing code, testing, and providing technical support. We truly appreciate all that so many of you do in coordination
 with the ArchivesSpace team to make each release of the ArchivesSpace application possible.</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in">
<b><span style="color:black">Webinar on the new PUI: October 26, 1-2:30 EST</span></b><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in">
<span style="color:black">Join us on October 26 as we take a close look at a variety of implementation strategies on the new ArchivesSpace PUI!</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in">
<span style="color:black">Mark Custer (Archivist and Metadata Coordinator, Yale University) and Susan Pyzynski (Associate Librarian of Houghton Library for Technical Services, Harvard University) were deeply entrenched in the public interface as they led the
 community effort to shape this essential access point for archival collections. Now they have moved onto their next great challenge -- implementing the PUI at their own institutions. Mark and Susan will each share the strategies they have created to roll out
 the new PUI. Both institutions aim to be using the new PUI by early next year.</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in">
<span style="color:black">Grand Valley State University has been using the ArchivesSpace PUI since 2014 and have already rolled out the new public interface. Annie Benefiel (Archivist for Collection Management, GVSU) and Leigh Rupinski (Archivist for Public
 Services & Community Engagement, GVSU) will share valuable insight on how the PUI has affected their day-to-day responsibilities as well as public reception and adapting their instruction for students and researchers.</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in">
<span style="color:black">Please join us on October 26 at 1-2:30 EST as Mark, Susan, Annie, and Leigh as they share their experiences. Please feel free to bring any questions you have on the new public interface!</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in">
<span style="color:black">The webinar will be available through: </span><a href="http://lyrasis.adobeconnect.com/rnz7zrtmy04h/">http://lyrasis.adobeconnect.com/rnz7zrtmy04h/</a><span style="color:black"> and the recording will be available at a later date.</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in">
<span style="color:black">No registration required. The session is limited to the first 100 participants. Please feel free to host a webinar viewing group.</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in">
<span style="color:black">If you have any questions about this webinar, please contact Kim at
</span><a href="mailto:christine.kim@lyrasis.org"><span style="color:#1155CC">christine.kim@lyrasis.org</span></a><span style="color:black">. We look forward to seeing you at the webinar!</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in">
<b><span style="color:black">Call for Testers – Archivists' Toolkit to ArchivesSpace Migration</span></b><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in">
<span style="color:black">The ArchivesSpace Program Team is looking for people who haven't yet migrated from Archivists' Toolkit to ArchivesSpace to test updates to the Archivists' Toolkit migration tool.</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in">
<span style="color:black">We have developed a pre-release version of the Archivists' Toolkit migration tool that migrates directly into ArchivesSpace version 2.1.2. In addition to the updates we have already made, we are planning to add the assessment information
 from AT to the migration tool once the assessment module is available in a production release of ArchivesSpace.</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in">
<span style="color:black">If you’re interested, please email Laney at </span><a href="mailto:laney.mcglohon@lyrasis.org"><span style="color:#1155CC">laney.mcglohon@lyrasis.org</span></a><span style="color:black">.</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in">
<b><span style="color:black">Request for Proposals for Container Management Development</span></b><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in">
<span style="color:black">ArchivesSpace is seeking proposals from individuals or firms interested in providing development for a limited scope project to add functionality to the container management area of the application. We are prioritizing this work for
 engagement of an outside contractor based on expressed interest from a number of members, including one that may have funding to pay for it. Please feel free to forward this RFP on to people you think may be interested and qualified to do this work.
<br>
<br>
We are asking that people please email proposals to Christine (</span><a href="mailto:christine.dibella@lyrasis.org"><span style="color:#1155CC">christine.dibella@lyrasis.org</span></a><span style="color:black">) by October 27, 2017. Proposals should include
 a proposed action plan, pricing, timeline, names and contact information for at least two client references, and examples of relevant work in ArchivesSpace or other applications. If people have questions about the RFP, feel free to send them my way as well.
 Laney can answer technical questions about the application and how delivery of code would work.<br>
<br>
Issuing RFPs for specific projects is another strategy we are using to diversify our pool of available developers and continue to making substantial forward progress on the application. If you have any questions, or if you have suggestions for projects that
 may be particularly appropriate for this type of treatment, please just let us know.</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in">
<b><span style="color:black">We’re hiring! DevOps Specialist supporting ArchivesSpace</span></b><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in">
<span style="color:black">Announced in last month’s update, we are still accepting applications for the DevOps Specialist position supporting the ArchivesSpace community and the ArchivesSpace program team.<br>
<br>
LYRASIS, the organizational home for ArchivesSpace, recently approved an additional staff position based in Technology Services to support ArchivesSpace technical needs. The position description can be found at</span><a href="https://www.lyrasis.org/job/Pages/LYRASIS-Positions.aspx"><span style="color:black">
</span><span style="color:#1155CC">https://www.lyrasis.org/job/Pages/LYRASIS-Positions.aspx</span></a><span style="color:black">. While the position will report to the Director of Technology Services, the person in the position will work closely with the ArchivesSpace
 program team to provide technical support for ArchivesSpace members as well as coding and other technical assistance for the application. Over time the person will have additional responsibilities for supporting LYRASIS hosting clients.</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in">
<span style="color:black">This position is ideal for someone who is familiar with ArchivesSpace or other archival/collection management systems and likes to help people with their technical questions. Previous experience with multiple platforms (Linux, Mac,
 Windows), MySQL, Java, Ruby, and Apache Solr is required.</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in">
<span style="color:black">We are excited about this additional support within the organizational home for ArchivesSpace technical needs. If you are interested in applying, or know someone who is, applications, including a cover letter and resume, are being
 accepted via email at </span><a href="mailto:human.resources@lyrasis.org"><span style="color:#1155CC;background:white">human.resources@lyrasis.org</span></a><span style="color:black;background:white">. If you have questions about the position, feel free to
 reach out to Christine (</span><a href="mailto:christine.dibella@lyrasis.org"><span style="color:#1155CC;background:white">christine.dibella@lyrasis.org</span></a><span style="color:black;background:white">) or Laney (</span><a href="mailto:laney.mcglohon@lyrasis.org"><span style="color:#1155CC;background:white">laney.mcglohon@lyrasis.org</span></a><span style="color:black;background:white">).</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in">
<b><span style="color:black">Introducing a new blog series: All About Community!</span></b><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in">
<span style="color:black">ArchivesSpace is community-supported software. But what does that mean? With a current program staff of only 3.75 FTE, ArchivesSpace owes its dynamic growth primarily to the active user community, currently over 300 members strong.</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in">
<span style="color:black">Without this community, the progress ArchivesSpace has made since its first release in 2013 could not be possible. So how do we all work together?</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in">
<i><span style="color:black">All About Community</span></i><span style="color:black"> is a blog series that highlights the many teams and groups that contribute to the growth and development of ArchivesSpace. This series aims to provide insight on how our diverse
 community comes together with a shared vision to preserve permanently valuable records and provide access to our researchers.</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in">
<span style="color:black">Every month, we’ll take a close look at each team, group, council, etc to highlight their major accomplishments and activities. Follow along:
</span><a href="http://archivesspace.org/category/all-about-community/"><span style="color:#1155CC">http://archivesspace.org/category/all-about-community/</span></a><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in">
<span style="color:black">Have ideas, questions, feedback, or your own stories you’d like to share? Email Kim at
</span><a href="mailto:christine.kim@lyrasis.org"><span style="color:#1155CC">christine.kim@lyrasis.org</span></a><span style="color:black">.</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in">
<b><span style="color:black">Membership Update</span></b><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in">
<span style="color:black">Our new members since September 21 include: </span><o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li style="color:black;margin-top:0in;margin-bottom:0in;margin-left:0in;margin-bottom:.0001pt;mso-list:l3 level1 lfo3;vertical-align:baseline">
University of Mary Washington<o:p></o:p></li><li style="color:black;margin-top:0in;margin-bottom:0in;margin-left:0in;margin-bottom:.0001pt;mso-list:l3 level1 lfo3;vertical-align:baseline">
Organ Historical Society Library and Archives<o:p></o:p></li><li style="color:black;margin-top:0in;margin-bottom:0in;margin-left:0in;margin-bottom:.0001pt;mso-list:l3 level1 lfo3;vertical-align:baseline">
Tyrrell Historical Society <o:p></o:p></li><li style="color:black;margin-top:0in;margin-bottom:0in;margin-left:0in;margin-bottom:.0001pt;mso-list:l3 level1 lfo3;vertical-align:baseline">
College of Charleston<o:p></o:p></li><li style="color:black;margin-top:0in;margin-bottom:8.0pt;margin-left:0in;mso-list:l3 level1 lfo3;vertical-align:baseline">
Northwest Texas Conference of the United Methodist Church<o:p></o:p></li></ul>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in">
<span style="color:black">New educational member:</span><o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li style="color:black;margin-top:0in;margin-bottom:8.0pt;margin-left:0in;mso-list:l0 level1 lfo4;vertical-align:baseline">
Cairo University<o:p></o:p></li></ul>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in">
<span style="color:black">As of October 12, we have 332 General members, 16 Educational Program members, and 3 Registered Service Providers. If you are interested in your institution becoming a member of ArchivesSpace, please email us at
</span><a href="mailto:ArchivesSpaceHome@lyrasis.org"><span style="color:#1155CC">ArchivesSpaceHome@lyrasis.org</span></a><span style="color:black"> for more information.</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in">
<i><span style="color:black">ArchivesSpace monthly updates provide news about ArchivesSpace community and program activities and are sent to our member listservs, the ArchivesSpace Google Group, and SAA’s Collection Management Tools roundtable listserv, as
 well as being posted on the ArchivesSpace website. Please feel free to share this update with people you know who have an interest in ArchivesSpace but may not be on one of these lists.</span></i><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>