<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)">
<style><!--
/* Font Definitions */
@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:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-compose;
font-family:"Arial",sans-serif;
color:black;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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:845284492;
mso-list-template-ids:645807008;}
@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:\F0B7;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1
{mso-list-id:1475103691;
mso-list-template-ids:-427642330;}
@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:\F0B7;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
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="blue" vlink="purple">
<div class="WordSection1">
<p><span style="color:black">Hello,<o:p></o:p></span></p>
<p><span style="color:black">Once again, on behalf of the entire project team, I would like to provide an update on our effort to implement a new search and discovery platform for special collections and archives at Yale. We are
<b>three months into the project</b>, or about 1/3 of the way through the estimated time frame. In many projects, this is a good and
<b>natural point to pause and reflect</b> on the original plan and assumptions made. The 1/3 mark is not technically a milestone, but for me it is an ideal time to reflect on not just if we are on schedule, but also if we are on point. At this stage there is
time to apply course correction if needed, examine the work completed and work that remains, and review if it is in the spirit of the original stated business need. As some of you know, my Halloween costume was a Project Management Classic,
<b>scope creep</b>, and this is exactly to what I refer. Scope creep is hard to avoid. It happens because a few weeks into the project you might discover something you hadn’t considered in the project ideation/initiation phase, or because people involved with
the project get a new idea as a natural outcome of rolling up their sleeves. The role of the project manager is to document as much of the anticipated environment as possible during ideation, including requirements, risks, and what’s in and out of scope due
to budget, time, FTE, or technology. A significant part of <b>project management is expectation management</b>, and hopefully always locating the middle ground.
</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"><o:p></o:p></span></p>
<p><span style="color:black">For the implementation of the ArchivesSpace PUI, Yale had a
<b>core business need to improve the search and discovery experience for users of special collections and archives</b>. The work of the
<b>project teams has focused on how best to accomplish that need</b>. The Public User Interface Enhancements team is spending time reviewing the current search and discovery experience for users and staff, including how the current YFAD is used, meeting with
each special collection repository in ArchivesSpace to document their typical/model search cases, and examining the default ArchivesSpace PUI for how to improve it. The
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_spreadsheets_d_1-2DLtn10yW2K9JPoWbt-2Dz42gPS-2DZ16pPxi6u307RBNNJg_edit-3Fusp-3Dsharing&d=DwMFAg&c=cjytLXgP8ixuoHflwc-poQ&r=nTeyk-U4CZBqtEsuDPTxMJ5Ukixi2letL2sC1p3IUMQ&m=JG4srydO5NwIiaifym8JlfyjxlMy2OpAkBs3FKmzgHA&s=atwitoYUwuczazxWGyBxfCQ8brD4_486-aHvbUxlDc0&e=">
model search case effort</a> is particularly interesting because it documents how people are searching for archival materials, and what they expect to happen with the search and the results. Each of these model searches has been cast in YFAD, then recast in
the PUI to make note of consistencies, differences, or loss/gain of search and discovery experience. It is challenging to work with a newer version of software, because the vendor/open source community publishes it at a certain state of viability, but often
locally the needs or standards are not all met. Although ideally I wish for some purely creative opportunity for the group (because they are a dream team), much of their early work is to underscore with Lyrasis
<b>some very basic features we still need in the PUI</b>. The PUI Enhancements team is not only helping achieve Yale’s business need to improve search and discovery, they are also helping every user of the ArchivesSpace PUI, present and future.
</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"><o:p></o:p></span></p>
<p><span style="color:black">The <b>User Experience and Accessibility testing</b> is also on point to support the stated business need.
<b>In order to know if Yale has improved the search and discovery experience, we must understand more about the current experience and environment, and find ways to measure and document improvements</b>, both from a user perspective and technical/data presentation
experience. This is an iterative process, with a baseline analysis of YFAD search and discovery, a baseline analysis of minimally customized PUI, and a follow up analysis a little later in the soft-launch timeframe. The stated business need of the improved
experience reflects a very open-ended objective, but the process of <b>establishing targets and measures</b>, as in a project scorecard method, is a great way to provide a framework and boundaries to this phase of the project.
</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"><o:p></o:p></span></p>
<p><span style="color:black">The <b>Technical Integrations team</b> is also upholding the core business need by discussing and
<b>planning in advance how best to make the transition to a soft-launch with both YFAD and the PUI available</b> to users. These are considered discussions to determine
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1mlq-5FMbubACMqnI5pXlAYXj0RTkc3shXw2yvIkQLPSfg_edit-3Fusp-3Dsharing&d=DwMFAg&c=cjytLXgP8ixuoHflwc-poQ&r=nTeyk-U4CZBqtEsuDPTxMJ5Ukixi2letL2sC1p3IUMQ&m=JG4srydO5NwIiaifym8JlfyjxlMy2OpAkBs3FKmzgHA&s=JK3R9C5LdgLnyw3yQLNAF1BeYRn-P8TKMVl_f-2J1n4&e=">
what we want out of a soft-launch period</a>, why it matters, and how it will affect staff and users. We are working to make the transition to a soft-launch as smooth as possible, and Steve and I will be emailing folks soon with a more detailed set of decision
points he has referenced in this <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_presentation_d_1Q2Fzl5kIVUZCiLorPbEHJ8Etc10yaZlWzjZPq-2DHFtjg_edit-3Fusp-3Dsharing&d=DwMFAg&c=cjytLXgP8ixuoHflwc-poQ&r=nTeyk-U4CZBqtEsuDPTxMJ5Ukixi2letL2sC1p3IUMQ&m=JG4srydO5NwIiaifym8JlfyjxlMy2OpAkBs3FKmzgHA&s=TsFXrya6rme4u8X5u9RqfrUS-RsZ7wTvF1sBsoNomD0&e=">
slide deck</a> concerning publication to the Library’s front door and individual library web pages.
<o:p></o:p></span></p>
<p><span style="color:black">The complete <b>minutes of the November Monthly PUI Stakeholder meeting</b> are available
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1VHs5-5FnOBLhQgIZ6-2DcFMdGcFhVBoMxeY8v-2DFZTPT0TG8_edit-3Fusp-3Dsharing&d=DwMFAg&c=cjytLXgP8ixuoHflwc-poQ&r=nTeyk-U4CZBqtEsuDPTxMJ5Ukixi2letL2sC1p3IUMQ&m=JG4srydO5NwIiaifym8JlfyjxlMy2OpAkBs3FKmzgHA&s=ugUEZhn99oOriCbF7bCzegIGgO1qo0zwO_mj8NCmcnU&e=">
here</a>. There are several <b>“Key Conversations”</b> to follow up on from today’s meeting and the details are in the minutes, along with links to other presentation materials. In addition to the monthly minutes, please review the list of major project updates
since the last month. We are trying to adopt a model of publishing updates ahead of the monthly meetings, so that there can be more active discussion during the hour on broader issues. A reminder that
<b>every monthly stakeholder meeting is open to any interested staff</b>, and our minutes will always be shared. Our intention is to keep the project, particularly decision points, as timely and transparent as possible. We continue to
<a href="https://campuspress.yale.edu/yalearchivesspace/">blog about the project</a> and project management at the Yale Archival Management Systems (YAMS) site.
<o:p></o:p></span></p>
<p><span style="color:black">Please feel free to <b>ask any member of the project team or repository representative for more information</b> about the project. Our roster is
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1OBKC1nQSkjuIHKEqhRsu810u3J05tYVd57d2Z6tSoK0_edit-3Fusp-3Dsharing&d=DwMFAg&c=cjytLXgP8ixuoHflwc-poQ&r=nTeyk-U4CZBqtEsuDPTxMJ5Ukixi2letL2sC1p3IUMQ&m=JG4srydO5NwIiaifym8JlfyjxlMy2OpAkBs3FKmzgHA&s=JgD_BBxsomXZiexOF93jeMAQlqqFWjLhyF60lT2Y_wo&e=">
here</a>. </span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"><o:p></o:p></span></p>
<p><span style="color:black"> Thank you for time and attention to read through this update. This truly is a major effort, but I know we will succeed.
<o:p></o:p></span></p>
<p><span style="color:black">Melissa Wisner<o:p></o:p></span></p>
<p><span style="color:black">Yale Library IT <o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p><span style="color:black"> <b>From:</b> Wisner, Melissa <br>
<b>Sent:</b> Friday, September 22, 2017 2:15 PM<br>
<b>To:</b> yulibl@mailman.yale.edu<br>
<b>Subject:</b> Project Update: Implementing a new Public User Interface for Special Collections and Archives at Yale<o:p></o:p></span></p>
</div>
</div>
<p><span style="color:black"> <o:p></o:p></span></p>
<p><span style="color:black">Hello,<o:p></o:p></span></p>
<p><span style="color:black"> <o:p></o:p></span></p>
<p><span style="color:black">On behalf of the entire project team, I would like to provide an update on
<b>a major effort</b> currently underway to <b>implement a new search and discovery platform for special collections and archives at Yale</b>. Many of you may be familiar with the existing platform, Yale Finding Aids Database (<a href="http://drs.library.yale.edu/fedoragsearch/rest"><span style="color:#0563C1">YFAD</span></a>).
This tool was developed locally, many years ago, and is starting to age out, both technically and with user expectations. For example, New York Public Library offers this presentation for its archival materials,
<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__archives.nypl.org_&d=DwMFAg&c=cjytLXgP8ixuoHflwc-poQ&r=nTeyk-U4CZBqtEsuDPTxMJ5Ukixi2letL2sC1p3IUMQ&m=JG4srydO5NwIiaifym8JlfyjxlMy2OpAkBs3FKmzgHA&s=Y2dJD8gIvWK5KcwQnGypVP-XT3ma_IXxY7x9qc8p_BM&e="><span style="color:#0563C1">http://archives.nypl.org/</span></a>.
<o:p></o:p></span></p>
<p><span style="color:black"> <o:p></o:p></span></p>
<p><span style="color:black">After a few years of intense technical development, a
<b>new public user interface for ArchivesSpace is available for implementation</b>. Yale implemented ArchivesSpace as an archival management tool for staff several years ago, and with it for the first time, a
<b>standard tool used across almost all libraries, museums, and galleries on campus with archival materials</b>. The extension of the ArchivesSpace platform to include a public user interface, will provide new opportunities for systems integration, more seamless
staff workflows, and an improved user experience for researchers. <o:p></o:p></span></p>
<p><span style="color:red"> </span><span style="color:black"><o:p></o:p></span></p>
<p><span style="color:black">The project at Yale to implement the new user platform for special collections and archives had a three month pre-planning process, involving the project sponsors and administrative stakeholders. I am serving as the Project Manager,
and Mark Custer, is serving as Ex Officio, due to his role as Project Manager of the technical development and design phase. We are sponsored by E.C. Schroeder and Chris Weideman. The project has a roster of approximately 30 staff members, and a larger number
of stakeholders. <o:p></o:p></span></p>
<p><span style="color:black"> <o:p></o:p></span></p>
<p><span style="color:black">There is <b>significant work to accomplish and preparations for changes</b>, before we debut the new service to our users. When we are ready, we will
<b>begin with a soft-rollout of the new discovery platform, while continuing to keep YFAD available</b>. We anticipate a period when both tools are available through the Library website, as final adjustments are made for
<b>the transition from YFAD to ArchivesSpace</b>. As of today, we anticipate an <b>
early 2018 soft-launch</b>. <o:p></o:p></span></p>
<p><span style="color:black"> <o:p></o:p></span></p>
<p><span style="color:black">The <b>project is utilizing several key working groups to manage the tasks of implementation</b>. These include-<o:p></o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:black;margin-left:0in;mso-list:l0 level1 lfo3">
Public User Interface Enhancements & Ideas, led by Alison Clemens<o:p></o:p></li><li class="MsoNormal" style="color:black;margin-left:0in;mso-list:l0 level1 lfo3">
Data Cleanup & Enhancement, led by Alicia Detelich and Christy Tomecek<o:p></o:p></li><li class="MsoNormal" style="color:black;margin-left:0in;mso-list:l0 level1 lfo3">
Staff Training & Documentation, led by Emily DiLeo<o:p></o:p></li><li class="MsoNormal" style="color:black;margin-left:0in;mso-list:l0 level1 lfo3">
Technical Integrations, led by Steve Wieda<o:p></o:p></li><li class="MsoNormal" style="color:black;margin-left:0in;mso-list:l0 level1 lfo3">
Usability & Accessibility, led by Jenn Nolte<o:p></o:p></li><li class="MsoNormal" style="color:black;margin-left:0in;mso-list:l0 level1 lfo3">
Marketing & Branding, led by Mike Morand<o:p></o:p></li></ul>
<p><span style="color:black"> <o:p></o:p></span></p>
<p><span style="color:black">We are <b>using several different tools to organize and manage the work and communication of the project</b>. These include Asana for the project plan, a Slack channel for day-to-day project team communication, Google Drive for
file sharing, GitHub, and the local yulaspace email distribution list. We will also be sending a monthly update on our progress to the yulib distribution list. We are also blogging about the project and aspects of project management on the
<a href="https://campuspress.yale.edu/yalearchivesspace/"><span style="color:#0563C1">Yale ArchivesSpace blog</span></a>.
<o:p></o:p></span></p>
<p><span style="color:black"> <o:p></o:p></span></p>
<p><span style="color:black">We also <b>extend an invitation to attend the monthly All Project Member/Stakeholder meetings</b>. These meetings are open to everyone with an interest in the new user interface, special collections, or an interest in teaching users
about finding aids, archives, and special collections at Yale. The monthly meeting for October is Tuesday Oct, 31, 2017. It will be held in Bass Library L01 & L02 from 3-4pm.
<o:p></o:p></span></p>
<p><span style="color:black"> <o:p></o:p></span></p>
<p><span style="color:black">Thank you,<o:p></o:p></span></p>
<p><span style="color:black">Melissa Wisner<o:p></o:p></span></p>
</div>
</body>
</html>