<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;}
@font-face
{font-family:Aptos;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:12.0pt;
font-family:"Aptos",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
font-size:12.0pt;
font-family:"Aptos",sans-serif;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Aptos",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:151609206;
mso-list-template-ids:250395624;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
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:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
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:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
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:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
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:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
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:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
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:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
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:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
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:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></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-CA" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;mso-fareast-language:EN-US">Hi Kathy,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;mso-fareast-language:EN-US">Gina, Elizabeth, and I did a conference session last year on scheduling upgrades and what Bibliomation, PaILS/Spark, and BC Libraries Cooperative do -
<a href="https://youtu.be/3snbbNN8-x4?feature=shared">https://youtu.be/3snbbNN8-x4?feature=shared</a><o:p></o:p></span></p>
<ul type="disc">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
What is your current upgrade schedule for major releases? Do you typically upgrade one release at a time or do you skip releases?<o:p></o:p></li><ul style="margin-top:0cm" type="circle">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level2 lfo1"><span style="font-size:11.0pt;mso-fareast-language:EN-US">We generally do one major release a year and skip a version. This year is atypical as we didn’t upgrade last year due to
moving our servers and so we’re jumping from 3.11.1 to 3.14.4 in April. We prefer to go to at least X.1.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level2 lfo1"><span style="font-size:11.0pt;mso-fareast-language:EN-US">We’ve often upgraded to the most recent release available though that has presented issues for us in the past when the release
schedule has changed or when releases have been delayed.<o:p></o:p></span></li></ul>
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
Do you typically perform point release upgrades in addition to major upgrades? Do you just load bug fixes as you need them? Or do you do both (or neither)?<o:p></o:p></li><ul type="circle">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo1">
We’ve done both over the years, really depends on the circumstances. We generally try to avoid doing point releases due to the work required around testing and training but sometimes it has made more sense than backporting a bunch of fixes. Ideally we go
live with a version of Evergreen that doesn’t have anything major that we’ll need to patch ahead of our next upgrade.<o:p></o:p></li></ul>
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
Has your upgrade schedule changed over the years that you’ve been on Evergreen? If so, how has it changed and what factors influenced your decision to make those changes?<o:p></o:p></li><ul type="circle">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo1">
Our upgrade window moves around year to year. It depends in part on when it makes most sense to have downtime, the Evergreen release schedule, and what else is going on that year (migrations, other projects at the Co-op, staff vacations, etc.) to ensure we
have an adequate testing, training, updating resources (docs and videos) window.
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo1">
We used to always do a long weekend due to the amount of time we were offline but in recent years we’ve found that unnecessary as we’re generally offline for less than 24 hours which has given us more flexibility for picking a date.<o:p></o:p></li></ul>
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
If your upgrade schedule is annual or even less frequent, is there any frustration among your libraries about delays in getting new features?<o:p></o:p></li><ul type="circle">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo1">
I’ll echo Benjamin, we hear more frustration from our libraries when new features don’t work (or existing ones break) with an upgrade. I suspect many of our libraries are unaware of upcoming features until we start promoting them ahead of an upgrade.<o:p></o:p></li></ul>
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
Our upgrade webpage is here: <a href="https://bc.libraries.coop/support/sitka/evergreen-3-14-upgrade/">
https://bc.libraries.coop/support/sitka/evergreen-3-14-upgrade/</a><o:p></o:p></li><ul type="circle">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo1">
We’ll be adding a 3.14 preview page next week to coincide with our first upgrade webinar. Generally we just do a What’s New in Evergreen webinar plus new/updated resources but this year we’re doing webinars for acquisitions and the reporter as well due to
how much has changed between 3.11 and 3.14. (If anyone is interested we now post all our webinars to YouTube -
<a href="https://www.youtube.com/playlist?list=PLdwlgwBNnH4q9cGZ9VXh131RRteFo7ddC">
https://www.youtube.com/playlist?list=PLdwlgwBNnH4q9cGZ9VXh131RRteFo7ddC</a>. Acq should be up by the end of next week and the general what’s new should be up mid March.)<o:p></o:p></li></ul>
</ul>
<p class="MsoNormal"><span style="font-size:11.0pt;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;mso-fareast-language:EN-US">Hope that helps,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;mso-fareast-language:EN-US">Jennifer<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">--<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Jennifer Pringle (she/her)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Co-op Support - Training Lead<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">BC Libraries Cooperative<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Toll-free: 1-888-848-9250<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Email:jennifer.pringle@bc.libraries.coop<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Website: <a href="http://bc.libraries.coop">
<span style="color:#467886">http://bc.libraries.coop</span></a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Gratefully acknowledging that I live and work in the unceded Traditional Territory of the St'at'yemc Nations.<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Evergreen-general <evergreen-general-bounces@list.evergreen-ils.org>
<b>On Behalf Of </b>Murphy, Benjamin via Evergreen-general<br>
<b>Sent:</b> February 21, 2025 10:46 AM<br>
<b>To:</b> Evergreen Discussion Group <evergreen-general@list.evergreen-ils.org><br>
<b>Cc:</b> Murphy, Benjamin <Benjamin.Murphy@dncr.nc.gov><br>
<b>Subject:</b> Re: [Evergreen-general] [External] Tell us about your upgrade schedules!<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">Our consortium upgrades annually in the fall and we typically skip a version (3.11.3 to 3.13.5 for instance.) We usually install the target version on a test machine in early summer and then invite
staff in consortium libraries to kick the tires over the summer so we can make/seek patches to issues and prepare solid training of what to expect. We have a mailing list (Basecamp group) targeted specifically to testing that we invite people to join and discuss
issues they encounter. (Let me add a plug for the session at the upcoming conference about Collaborative Testing. This is something we're trying to wrap our heads around and I'm interested to hear what they have to say.) After testing over the summer, we then
have webinars for the larger community to discuss and prepare for upgrade changes. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">We have our upgrade documentation here:
<a href="https://nccardinalsupport.org/index.php?pg=kb.book&id=10" id="OWA07f02116-eefd-10ab-721f-78aedd211a79">
https://nccardinalsupport.org/index.php?pg=kb.book&id=10</a> including our working list of known but unresolved bugs. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">This past year we were chasing the latest version which I don't think we're going to do again. We weren't able to test the Reporter changes in 3.13, so we got hit with a lot of tickets for bugs
once it went live. Some of them we were able to chase fixes for, some we had to just report on Launchpad and hope someone took them on. This is frustrating for our users, so we're thinking about being more conservative about upgrading to the latest version.
That's one of the challenges of an open source project, if you're on the cutting edge, find a bug and don't have the resources to fix it yourself, you might be stuck with the problem for a while. Your user base doesn't always understand that. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">"Do you just load bug fixes as you need them?" We did one "mini-upgrade" in spring a few years back, but generally we have to be offline for ~36-48 hours for an upgrade, deal with training and
all the other logistics so we usually just stick to once a year.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">"is there any frustration among your libraries about delays in getting new features?" We've heard some excitement about new features for member library staff that are plugged into the larger Evergreen
community, but we hear more frustration when new things don't work.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">After our most recent upgrade, we decided as a team that we're going to treat our upgrades more like a new library migration, where we're all focused on some aspect of the upgrade for a period
of time and try to be more deliberate about testing, user engagement, etc. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">I'm interested to hear what other folks have to say on the topic.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div id="Signature">
<p style="background:white"><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Benjamin Murphy</span></b><o:p></o:p></p>
<p style="background:white"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">NC Cardinal Program Manager</span><o:p></o:p></p>
<p style="background:white"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">State Library of North Carolina</span><o:p></o:p></p>
<p style="background:white"><u><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#0563C1"><a href="mailto:benjamin.murphy@dncr.nc.gov">benjamin.murphy@dncr.nc.gov</a>
</span></u><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"> |
<a href="https://statelibrary.ncdcr.gov/services-libraries/nc-cardinal" id="OWA808305d1-4c2c-d926-cb02-ec732df032a0">
https://statelibrary.ncdcr.gov/services-libraries/nc-cardinal</a></span><o:p></o:p></p>
<p style="background:white"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">109 East Jones Street | 4640 Mail Service Center </span><o:p></o:p></p>
<p style="background:white"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Raleigh, North Carolina 27699-4600</span><o:p></o:p></p>
<p style="margin-top:6.0pt;background:white"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">The State Library is part of the NC Department of Natural & Cultural Resources.</span><o:p></o:p></p>
<p style="background:white"><i><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Email correspondence to and from this address is subject to the North Carolina Public Records Law and may be disclosed to third parties.</span></i><o:p></o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"><o:p> </o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="98%" align="center">
</div>
<div id="divRplyFwdMsg">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> Evergreen-general <<a href="mailto:evergreen-general-bounces@list.evergreen-ils.org">evergreen-general-bounces@list.evergreen-ils.org</a>>
on behalf of Lussier, Kathy via Evergreen-general <<a href="mailto:evergreen-general@list.evergreen-ils.org">evergreen-general@list.evergreen-ils.org</a>><br>
<b>Sent:</b> Friday, February 21, 2025 11:48 AM<br>
<b>To:</b> Evergreen Discussion Group <<a href="mailto:evergreen-general@list.evergreen-ils.org">evergreen-general@list.evergreen-ils.org</a>><br>
<b>Cc:</b> Lussier, Kathy <<a href="mailto:klussier@noblenet.org">klussier@noblenet.org</a>><br>
<b>Subject:</b> [External] [Evergreen-general] Tell us about your upgrade schedules!</span>
<o:p></o:p></p>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div style="border:solid #9C6500 1.0pt;padding:2.0pt 2.0pt 2.0pt 2.0pt">
<p class="MsoNormal" style="line-height:12.0pt;background:#FFEB9C"><b><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:red">CAUTION:</span></b><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black"> External email. Do
not click links or open attachments unless verified. Report suspicious emails with the Report Message button located on your Outlook menu bar on the Home tab.</span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Hi all and Happy Friday!<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">NOBLE is reevaluating its upgrade schedule and would like to hear how other libraries / consortia handle their upgrades. Since we moved to Evergreen, we've been on a schedule to do a major release upgrade twice per year, following the community's
schedule of two releases per year, and usually upgrade to the release that's one version behind the latest release. We don't typically do point release upgrades, but will load patches for bug fixes that are important to our libraries. We also hold off on upgrades
in cases where we see bugs that will cause too much of a hardship for our libraries. This typically happens when an entire interface is replaced before it supports all of the features used by our libraries.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">We are considering a move to a one-upgrade-per-year schedule. Under this schedule, we would skip a release to ensure we stay on a release that still receives security fixes. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Tell us about your upgrade schedules.<o:p></o:p></p>
</div>
<ul type="disc">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
What is your current upgrade schedule for major releases? Do you typically upgrade one release at a time or do you skip releases?<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
Do you typically perform point release upgrades in addition to major upgrades? Do you just load bug fixes as you need them? Or do you do both (or neither)?<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
Has your upgrade schedule changed over the years that you’ve been on Evergreen? If so, how has it changed and what factors influenced your decision to make those changes?<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
If your upgrade schedule is annual or even less frequent, is there any frustration among your libraries about delays in getting new features?<o:p></o:p></li></ul>
<div>
<p class="MsoNormal">Feel free to add any information about what you like or dislike about your current schedule.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Adding a #CatTax in appreciation for your feedback.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><img border="0" width="349" height="262" style="width:3.6369in;height:2.7261in" id="Picture_x0020_1" src="cid:image001.jpg@01DB8450.2DB63E90"><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Kathy<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">--<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Kathy Lussier<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">she/her<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Executive Director<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">NOBLE: North of Boston Library Exchange<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Danvers, MA<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">978-777-8844 x201<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><a href="http://www.noblenet.org/" id="OWAd1fddfa5-9077-aa70-6a7e-8ba9e81e5e1c">www.noblenet.org</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" align="center">
</div>
<p class="MsoNormal"><span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:gray"><br>
Email correspondence to and from this address may be subject to the North Carolina Public Records Law and may be disclosed to third parties by an authorized state official.<br>
</span>This message originated from outside the M365 organisation. Please be careful with links, and don't trust messages you don't recognise.
<o:p></o:p></p>
</div>
</body>
</html>