<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=utf-8">
<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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",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
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.hoenzb
{mso-style-name:hoenzb;}
span.m-5497637338200583504hoenzb
{mso-style-name:m_-5497637338200583504hoenzb;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Consolas",serif;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.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;}
--></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 class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I am sorry I’m weighing a bit late. Yesterday was our Users Group conference. Thank you, Grace, for sharing your thoughts. I also appreciated hearing everyone’s
responses. As a newbie on the board, I need to ask a few questions, and I apologize in advance if this was already been discussed numerous times. Given the size of the Evergreen community, do we think 140 is a reasonable number of attendees? Also, do we have
any theories as to why we did not see an increase from last year given that the Evergreen community is growing and not shrinking? Prior to putting out a Call for Proposals for 2019 (and I am all in favor of Kathy’s suggestion of advancing the deadline), should
we survey the community about the conference? It can start with a Did you attend? Y/N and, if N, we can try to find out why. We can also ask them to rate what is most and least important in terms of the conference experience. If you are all amenable to this,
I will volunteer to take the lead with the survey.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Scott<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> eg-oversight-board [mailto:eg-oversight-board-bounces@list.evergreen-ils.org]
<b>On Behalf Of </b>Amy Terlaga<br>
<b>Sent:</b> Tuesday, May 23, 2017 12:49 PM<br>
<b>To:</b> Kathy Lussier <klussier@masslnc.org><br>
<b>Cc:</b> Grace Dunbar <grace@equinoxinitiative.org>; Oversight Board <eg-oversight-board@list.evergreen-ils.org><br>
<b>Subject:</b> Re: [Eg-oversight-board] Final conference thoughts<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">All good suggestions, Kathy!<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Amy<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Tue, May 23, 2017 at 12:43 PM, Kathy Lussier <<a href="mailto:klussier@masslnc.org" target="_blank">klussier@masslnc.org</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<p>Hi,<o:p></o:p></p>
<p>I haven't read the document closely, but some pieces (new sponsor/exhibitor rates) may be something we can implement sooner while # of rooms, food expenditures, and other contract items can be planned out for 2019. Another thought I've had is that we might
want to consider putting out the call for the 2019 conference earlier this year. Although we put out the call about 16 months ahead of time, I know some locations are already fully booked by that time. Maybe we can plan for putting the next Call for Proposals
out in August / September and plan on resolving these questions by then so that the 2019 planners know what the new requirements are.<o:p></o:p></p>
<p>In addition to reducing costs, the other advantage to reducing the number of rooms is that it increases the number of conference hotels that can accommodate us.<o:p></o:p></p>
<p><span style="color:#888888">Kathy<o:p></o:p></span></p>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On 05/23/2017 12:28 PM, Amy Terlaga wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">These are some very intriguing suggestions for future conferences. I'm all for reducing the overall cost to help the project make money. Unfortunately, contract signing with the conference venue for 2018 is wrapping up today or tomorrow.
I followed this year's plan. I stuck with the formula. I needed something to go on and felt the pressure of locking in the venue as the local committee has been working out a plan with them since before the 2017 conference.
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I'm sorry some of this can't be executed for 2018, but the work has been laid out for 2019.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Grace, you've done so much work - it is much appreciated. Your insights and expertise are invaluable..<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Amy<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Tue, May 23, 2017 at 11:39 AM, Grace Dunbar <<a href="mailto:grace@equinoxinitiative.org" target="_blank">grace@equinoxinitiative.org</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">I thought it might be useful to provide my suggestions for the Evergreen conference and changes we may want to consider for the future. Apologies in advance if this is either rambling or redundant, or both.<o:p></o:p></p>
</div>
<p class="MsoNormal">The conference operates on thin margins.<o:p></o:p></p>
</div>
<p class="MsoNormal">Every year the conference committee is confident (perhaps overly confident) that this year they will increase attendance numbers and increase sponsorships. The problem is that we can't increase our sponsorships without increasing our attendance.
And our attendees who increase our numbers are generally just employees of a library in an existing consortia. This exact complaint was brought up by multiple vendors - essentially, the Evergreen conference is really only between 8 and 10 "clients" and having
more circ or cataloging staff attendees at the conference doesn't increase their ROI. And that's fair.
<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">And the attendees who can increase our numbers (local staff) seem to want very specifically targeted information related to them at the conference. The conference surveys have been pretty clear that end-user
staff want and expect *training* from the conference. But that hasn't traditionally been the aim of the conference, nor can we reliably provide that since the programs are solicited from volunteers in the community. Also complicating things for "training"
on Evergreen features is that Evergreen is so customizable that "training" or explanations of how to use certain features may not jive with local policy for their consortia or library system. Regardless, I believe we can, to some extent, provide that kind
of training in the pre-conference sessions. However, we will need to be very selective in the process of recruiting the pre-conference presenters (trainers) if we're going to try to actively meet that need.<o:p></o:p></p>
</div>
<p class="MsoNormal">Also, I firmly believe that the conference should make money for the project. With that money, the project can provide outreach, build infrastructure, and promote the community. We want to provide a good conference with stellar programs
and a welcoming environment. But the conference is also for building relationships, allowing developers and community leaders to conduct business and brainstorm, as well as providing space for the EOB, committees, and interest groups to meet. IOW, we're
trying to meet a lot of needs and there needs to be balance - we can't make everyone happy all the time. If you look at the breakdown of attendees, systems administrators and developers are roughly 1/3, end-users are roughly 1/3, and admin/consortia leaders
are roughly 1/3. Those are all stakeholders that are important but their needs are very different.<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">To reduce overhead for the conference and to try to give <u>
everyone</u> the best experience we should at least look at making some changes. Based off of my experience and the results of conference surveys, I have some suggestions for changes to the structure and the sponsorships.
<br>
Note that the proposed reduction of the conference to two tracks had wide support in the survey and the track reduction and changes to pre-conferences and when/where IGs, etc. meet, should reduce the overhead for costs associated with meeting rooms, A/V, signage,
labor, etc.<br>
See attached doc for details.<o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thanks for sticking with the rambling...<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">And as always, this is just a suggestion based on my experience - I leave it to y'all to decide what to take away from the information and what direction to go.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Cheers!<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#888888">Grace<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal">p.s. Exhibitor and attendee surveys also attached. For anyone who prefers visual representations, just let me know and I can share the Google form with you.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><br>
<br clear="all">
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">-- <o:p></o:p></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal">+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+<o:p></o:p></p>
</div>
<p class="MsoNormal">Amy Terlaga<o:p></o:p></p>
</div>
<p class="MsoNormal">Director of Member Services<o:p></o:p></p>
</div>
<p class="MsoNormal">Bibliomation, Inc.<o:p></o:p></p>
</div>
<p class="MsoNormal">24 Wooster Avenue<o:p></o:p></p>
</div>
<p class="MsoNormal">Waterbury, CT 06708<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><a href="tel:(203)%20577-4070" target="_blank">(203)577-4070 x101</a><o:p></o:p></p>
</div>
<p class="MsoNormal"><a href="mailto:terlaga@biblio.org" target="_blank">terlaga@biblio.org</a><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<pre>-- <o:p></o:p></pre>
<pre>Kathy Lussier<o:p></o:p></pre>
<pre>Project Coordinator<o:p></o:p></pre>
<pre>Massachusetts Library Network Cooperative<o:p></o:p></pre>
<pre><a href="tel:(508)%20343-0128" target="_blank">(508) 343-0128</a><o:p></o:p></pre>
<pre><a href="mailto:klussier@masslnc.org" target="_blank">klussier@masslnc.org</a><o:p></o:p></pre>
<pre>Twitter: <a href="http://www.twitter.com/kmlussier" target="_blank">http://www.twitter.com/kmlussier</a><o:p></o:p></pre>
</div>
</blockquote>
</div>
<p class="MsoNormal"><br>
<br clear="all">
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">-- <o:p></o:p></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal">+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+<o:p></o:p></p>
</div>
<p class="MsoNormal">Amy Terlaga<o:p></o:p></p>
</div>
<p class="MsoNormal">Director of Member Services<o:p></o:p></p>
</div>
<p class="MsoNormal">Bibliomation, Inc.<o:p></o:p></p>
</div>
<p class="MsoNormal">24 Wooster Avenue<o:p></o:p></p>
</div>
<p class="MsoNormal">Waterbury, CT 06708<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">(203)577-4070 x101<o:p></o:p></p>
</div>
<p class="MsoNormal"><a href="mailto:terlaga@biblio.org" target="_blank">terlaga@biblio.org</a><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>