<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <style type="text/css">td {border: 1px solid #cccccc;}br {mso-data-placement:same-cell;}</style>All,<br>
    <br>
    I've setup two servers for Feedback Fest. The first one is vanilla
    Evergreen 3.14 Beta:<br>
    <a href="https://bugsquash.mobiusconsortium.org/eg/staff"
      class="moz-txt-link-freetext">https://bugsquash.mobiusconsortium.org/eg/staff</a><br>
    Login: admin / demo123<br>
    Postgres 15 and Redis on test server<br>
    Enchanced Concerto<br>
    <br>
    The second is Evergreen main (pretty much 3.14), plus the
    aforementioned Patron edit/search/registration Angular interface
    patch (<a href="https://bugs.launchpad.net/evergreen/+bug/2065344">Bug
      2065344</a> and <a
      href="https://bugs.launchpad.net/evergreen/+bug/2080438">Bug <br>
      2080438</a><br>
    <br>
    It's the same patch as what you can find on the butternut server but
    this server provides the enhanced concerto dataset as well as i18n
    languages.<br>
    <br>
    As well as three more patches from Stephanie! sleary++<br>
    <br>
    Bootstrap OPAC: Pending Address Change" Header in the Patron
    Preferences have not been marked for translation <br>
    <a href="https://bugs.launchpad.net/evergreen/+bug/2077627"
      class="moz-txt-link-freetext">https://bugs.launchpad.net/evergreen/+bug/2077627</a><br>
    <br>
    Dynamic staff portal doesn't work well in non-English languages    <br>
    <a href="https://bugs.launchpad.net/evergreen/+bug/2037426"
      class="moz-txt-link-freetext">https://bugs.launchpad.net/evergreen/+bug/2037426</a><br>
    <br>
    Redirect from AngularJS Login to Angular Staff Portal Page Causes
    Delays<br>
     <a href="https://bugs.launchpad.net/evergreen/+bug/1983500"
      class="moz-txt-link-freetext">https://bugs.launchpad.net/evergreen/+bug/1983500</a><br>
    <br>
    <br>
    second server accessible here:<br>
    <a href="https://bugsquash2.mobiusconsortium.org/eg/staff"
      class="moz-txt-link-freetext">https://bugsquash2.mobiusconsortium.org/eg/staff</a><br>
    Login: admin / demo123<br>
    Postgres 15 and Redis on test server<br>
    Enchanced Concerto<br>
    <style type="text/css">td {border: 1px solid #cccccc;}br {mso-data-placement:same-cell;}</style><br>
    Feedback welcome!<br>
    <br>
    Happy Feedback Fest everyone!<br>
    <br>
    <pre class="moz-signature" cols="72">-Blake-
Conducting Magic
Will consume any data format
MOBIUS

</pre>
    <br>
    <div class="moz-cite-prefix">On 10/7/2024 4:57 PM, Terran McCanna
      via Evergreen-general wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CALh4dLAsEs5rw+k+DqkkAY3+aJS9oqTx3W3OrAerOCEh+RZEjA@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="auto">I'll also mention that the Angularization of the
        circulation interfaces has been a work in progress for several
        years, and the community has tested it at each phase of
        development on public test servers. The current code has an
        earlier version of the experimental interface already merged
        that can be enabled via a library setting on any server, and
        this updated code will also be controlled by the same settng
        once it is merged. 
        <div dir="auto"><br>
        </div>
        <div dir="auto">Because the circulation interface has so many
          components, there is no intent to add any new functionality or
          change any existing behavior.  All of the behavior you see
          while testing should work exactly as it does in the
          out-of-support AngularJS code. The differences in the layout
          are there due to standardization with the rest of the Angular
          interfaces and components, and to bring them up to current
          accessibility standards and responsiveness standards. (With
          enormous thanks to Stephanie and her highly specialized
          skillset, who is dragging us kicking and screaming into
          compliance!)</div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">Proposed changes to functionality should be
          opened as separate bugs outside the scope of this project. </div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">Staff at all levels are highly encouraged to
          test and report problems, as always. </div>
        <div dir="auto"><br>
        </div>
        <div dir="auto"> 
          <div dir="auto"><br>
          </div>
          <div dir="auto"><br>
          </div>
        </div>
        <br>
        <br>
        <div class="gmail_quote" dir="auto">
          <div dir="ltr" class="gmail_attr">On Mon, Oct 7, 2024, 5:34 PM
            Andrea Buntz Neiman <<a
              href="mailto:abneiman@equinoxoli.org"
              moz-do-not-send="true" class="moz-txt-link-freetext">abneiman@equinoxoli.org</a>>
            wrote:<br>
          </div>
          <blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div dir="auto">Confirmed, all the intended changes are
              strictly for the Experimental Circ interfaces, which are
              still not complete and not ready for production even with
              these pending changes.
              <div dir="auto"><br>
              </div>
              <div dir="auto">I'd like to see these latest pieces merged
                to get more community eyes on it and facilitate the next
                pieces of work. </div>
              <div dir="auto"><br>
              </div>
              <div dir="auto">ABN </div>
            </div>
            <br>
            <div class="gmail_quote">
              <div dir="ltr" class="gmail_attr">On Mon, Oct 7, 2024,
                5:20 PM Terran McCanna via Evergreen-general <<a
                  href="mailto:evergreen-general@list.evergreen-ils.org"
                  target="_blank" rel="noreferrer"
                  moz-do-not-send="true" class="moz-txt-link-freetext">evergreen-general@list.evergreen-ils.org</a>>
                wrote:<br>
              </div>
              <blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
                <div dir="auto">
                  <div>It is only in the experimental stage at this
                    point so needs testing to catch bugs, but it will
                    not be the production interface until Evergreen
                    4.0. </div>
                  <div dir="auto"><br>
                  </div>
                  <div dir="auto"><br>
                    <br>
                    <div class="gmail_quote" dir="auto">
                      <div dir="ltr" class="gmail_attr">On Mon, Oct 7,
                        2024, 5:11 PM Lussier, Kathy <<a
                          href="mailto:klussier@noblenet.org"
                          rel="noreferrer noreferrer" target="_blank"
                          moz-do-not-send="true"
                          class="moz-txt-link-freetext">klussier@noblenet.org</a>>
                        wrote:<br>
                      </div>
                      <blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
                        <div dir="ltr">Hi Terran,
                          <div><br>
                          </div>
                          <div>Thank you for sharing this info, Terran,
                            and for sending the link to the test server
                            running this code! </div>
                          <div><br>
                          </div>
                          <div>What a big change to the circulation
                            interfaces! Modernizing the
                            circulation interfaces is probably a project
                            that is long overdue, and I'm sure there are
                            a lot of good UI improvements on top of the
                            accessibility improvements. I don't have
                            specific feedback on the interface, but I
                            have a question and also a concern related
                            to the process for introducing a major UI
                            change to Evergreen.</div>
                          <div><br>
                          </div>
                          <div>My question is whether this code is being
                            considered for 3.14. From my review, it
                            clearly falls in the camp of new feature,
                            and, with the beta release already
                            available, my understanding is that we
                            should  no longer be introducing new
                            features into the release. Am I
                            misunderstanding our release policy?</div>
                          <div><br>
                          </div>
                          <div>Here is my concern. As a community, I
                            think we need to do a better job of
                            communicating potential major changes to the
                            software before coding starts.. By giving
                            the community the opportunity to provide
                            feedback at an early stage, we can better
                            ensure that these changes are going to meet
                            the needs of the majority of libraries using
                            our community software. I have this
                            expectation of my community partners
                            primarily because, when I first arrived in
                            the Evergreen community and started asking
                            questions about development, other community
                            members emphatically told me that I needed
                            to share my plans early on. I listened. When
                            I share NOBLE's plans for a development
                            project via the general list, I do so
                            precisely because I want to find out if the
                            development is likely to cause problems for
                            others using the software. This worked well
                            for the last project NOBLE funded. We
                            thought the OPAC visible flag should also
                            determine visibility in the staff catalog.
                            We asked the question. Other Evergreen
                            libraries told us they have use cases for
                            seeing in the staff catalog an org unit that
                            is not visible in the public catalog. We
                            updated our requirements to incorporate this
                            feedback. My hope is that everyone gets what
                            they want when that code is eventually
                            merged into the software.</div>
                          <div><br>
                          </div>
                          <div>This update to circulation is a
                            significant change to a place in the
                            software that is often used by part-time
                            staff. Because they are part time, training
                            can be a challenge because there are
                            specific issues they may only encounter
                            occasionally, and they need an intuitive way
                            to help them address it. Rolling out a major
                            interface change will be tricky, and I would
                            like to know that our circ experts in this
                            community have had enough time to fully
                            engage with this proposed interface and
                            provide feedback before it gets merged. I
                            know it will not be forced upon people in
                            the next release because it's still in
                            experimental mode, but once it gets merged,
                            we've essentially made the decision on
                            behalf of the community that it is okay for
                            the circulation interface to make this
                            shift.</div>
                          <div><br>
                          </div>
                          <div>When I first came on board at NOBLE a
                            little over a year ago, we had not performed
                            an upgrade in over a year because of another
                            major interface change that lost some
                            features our libraries depend upon. We have
                            since upgraded with the most critical of
                            these features restored, but I know of at
                            least one other consortium that has still
                            held off on upgrading. That's what happens
                            when we make major overhauls to an interface
                            without adequate community feedback in the
                            development at all stages of the development
                            process. The new interface may meet the
                            needs of a handful of libraries/consortia,
                            but other Evergreen libraries then need to
                            make tough decisions about upgrading despite
                            a critical feature missing or staying on an
                            older release as it moves out of community
                            support. Greater community engagement won't
                            fix all of these problems, but it goes a
                            long way in mitigating them. </div>
                          <div><br>
                          </div>
                          <div>I heard that the cataloging interest
                            group recently had a meeting that included a
                            demo of the interface changes introduced to
                            buckets. I think a great next step for this
                            project would be a similar presentation for
                            those heavily involved in circulation (I
                            don't know if we have an active circulation
                            interest group.) Such a demo will ensure
                            that more community partners buy into the
                            change to the interface and maybe even
                            provide suggestions for making it work
                            better for those who work at their circ
                            desk, thereby benefiting everyone else in
                            the community who may have a similar
                            concern.</div>
                          <div><br>
                          </div>
                          <div>Beyond this project, I would love to see
                            a set of best practices for communicating
                            with the community when embarking on a
                            development project, particularly when that
                            development makes a significant change to
                            people's current workflows. I volunteer to
                            work on this and am willing to pull
                            something together by myself, but I'm also
                            happy to work with others if anyone else
                            wants to incorporate their feedback into the
                            best practices. After all, we are a
                            community, and I know incorporating
                            everyone's feedback into this best practices
                            document will make it better for everyone. </div>
                          <div><br>
                          </div>
                          <div>Just my two cents for what it's worth. </div>
                          <div><br>
                          </div>
                          <div>Kathy</div>
                          <div><br>
                          </div>
                          <div><br clear="all">
                            <div>
                              <div dir="ltr" class="gmail_signature"
                                data-smartmail="gmail_signature">
                                <div dir="ltr">
                                  <div>--</div>
                                  Kathy Lussier
                                  <div>she/her<br>
                                    <div>Executive Director</div>
                                    <div>NOBLE: North of Boston Library
                                      Exchange</div>
                                    <div>Danvers, MA</div>
                                    <div>978-777-8844 x201</div>
                                    <div><a
                                        href="http://www.noblenet.org"
rel="noreferrer noreferrer noreferrer" target="_blank"
                                        moz-do-not-send="true">www.noblenet.org</a></div>
                                    <div><br>
                                    </div>
                                    <div><br>
                                    </div>
                                  </div>
                                </div>
                              </div>
                            </div>
                            <br>
                          </div>
                        </div>
                        <br>
                        <div class="gmail_quote">
                          <div dir="ltr" class="gmail_attr">On Mon, Oct
                            7, 2024 at 4:07 PM Terran McCanna via
                            Evergreen-circ <<a
href="mailto:evergreen-circ@list.evergreen-ils.org"
                              rel="noreferrer noreferrer noreferrer"
                              target="_blank" moz-do-not-send="true"
                              class="moz-txt-link-freetext">evergreen-circ@list.evergreen-ils.org</a>>
                            wrote:<br>
                          </div>
                          <blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
                            <div dir="ltr"><br>
                              Hello everyone - <br>
                              <br>
                              During Feedback Fest this week, please
                              take a look at the updated (Angularized)
                              circulation interfaces that are loaded
                              onto <a
href="https://butternut.evergreencatalog.com/eg/staff"
                                rel="noreferrer noreferrer noreferrer"
                                target="_blank" moz-do-not-send="true"
                                class="moz-txt-link-freetext">https://butternut.evergreencatalog.com/eg/staff</a>
                              and available through the "Circulation
                              (Experimental)" menu. <br>
                              <br>
                              Note that these elements are still missing
                              from the new interface because they are
                              not yet complete: Hold groups, refresh
                              penalties, display alerts options. <br>
                              <br>
                              Also note that the old/current interfaces
                              will still be the default in Evergreen
                              3.14, but the default will most likely
                              change to these new interfaces in
                              Evergreen 4.0 <br>
                              <br>
                              Please add any issues you find with the
                              new interfaces to the omnibus ticket here:
                              <a
href="https://bugs.launchpad.net/evergreen/+bug/2065344"
                                rel="noreferrer noreferrer noreferrer"
                                target="_blank" moz-do-not-send="true"
                                class="moz-txt-link-freetext">https://bugs.launchpad.net/evergreen/+bug/2065344</a><br>
                              <br>
                              <div>Thank you!</div>
                              <div><br>
                              </div>
                              <div><br>
                              </div>
                              <div>
                                <div>
                                  <div dir="ltr" class="gmail_signature">
                                    <div dir="ltr">
                                      <div dir="ltr"
                                        style="margin-left:30.75pt"
                                        align="left">
                                        <table
style="border:none;border-collapse:collapse">
                                          <colgroup><col width="76"><col
                                              width="7"><col width="64"><col
                                              width="437"></colgroup><tbody>
                                            <tr style="height:74.25pt">
                                              <td colspan="2"
style="vertical-align:top;overflow:hidden">
                                                <p dir="ltr"
style="line-height:1.2;text-align:right;margin-top:0pt;margin-bottom:0pt"><a
href="https://georgialibraries.org/" style="text-decoration:none"
rel="noreferrer noreferrer noreferrer" target="_blank"
moz-do-not-send="true"><span
style="font-size:11pt;font-family:Arial,sans-serif;color:rgb(17,85,204);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:underline;vertical-align:baseline;white-space:pre-wrap"><span
style="border:none;display:inline-block;overflow:hidden;width:75px;height:75px"><img
alt="logo with link to Georgia Public Library Service website"
src="https://lh7-us.googleusercontent.com/7iakLpvBVw94n5VZhrTwpD9vZUyz1VQ0lMyVAqyNNUaT9HJowpRoWOfVcBKHDEMHUDKwNEnjOLpAyz9mETAcGxszeJGJcxDQjrzZSqxEh5DkL2NjTi7gs9Kx8RMN_4ap0t19KLBq70WnyGNunRrYWek"
                                                    width="75"
                                                    height="75"
style="margin-left:0px;margin-top:0px" moz-do-not-send="true"></span></span></a></p>
                                              </td>
                                              <td colspan="2"
style="vertical-align:top;padding:5pt;overflow:hidden">
                                                <p dir="ltr"
style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span
style="font-size:13pt;font-family:Verdana,sans-serif;color:rgb(30,67,155);background-color:transparent;font-weight:700;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Terran McCanna, </span><span
style="font-size:12pt;font-family:Verdana,sans-serif;color:rgb(30,67,155);background-color:transparent;font-weight:700;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">PINES Program Manager
</span></p>
                                                <hr>
                                                <p dir="ltr"
style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span
style="font-size:12pt;font-family:Verdana,sans-serif;color:rgb(0,0,0);background-color:transparent;font-weight:700;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap"></span><span
style="font-size:12pt;font-family:Verdana,sans-serif;color:rgb(30,67,155);background-color:transparent;font-weight:700;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Georgia Public Library Service</span></p>
                                                <p dir="ltr"
style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span
style="font-size:12pt;font-family:Verdana,sans-serif;color:rgb(30,67,155);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap"><a
href="https://www.google.com/maps/search/2872+Woodcock+Blvd,+Suite+250+%7C+Atlanta,+GA+30341?entry=gmail&source=g"
rel="noreferrer noreferrer" target="_blank" moz-do-not-send="true">2872 Woodcock Blvd, Suite 250 | Atlanta, GA 30341</a></span></p>
                                                <p dir="ltr"
style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span
style="font-size:12pt;font-family:Verdana,sans-serif;color:rgb(30,67,155);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">(404) 235-7138 | <a
href="mailto:tmccanna@georgialibraries.org"
rel="noreferrer noreferrer noreferrer" target="_blank"
                                                  moz-do-not-send="true"
class="moz-txt-link-freetext">tmccanna@georgialibraries.org</a></span></p>
                                                <p dir="ltr"
style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span
style="font-size:12pt;font-family:Verdana,sans-serif;color:rgb(30,67,155);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap"><a
href="https://help.georgialibraries.org"
rel="noreferrer noreferrer noreferrer" target="_blank"
                                                  moz-do-not-send="true"
class="moz-txt-link-freetext">https://help.georgialibraries.org</a> | <a
href="mailto:help@georgialibraries.org"
rel="noreferrer noreferrer noreferrer" target="_blank"
                                                  moz-do-not-send="true"
class="moz-txt-link-freetext">help@georgialibraries.org</a>
</span></p>
                                              </td>
                                            </tr>
                                            <tr style="height:36pt">
                                              <td colspan="2"
style="vertical-align:top;overflow:hidden"><br>
                                              </td>
                                              <td colspan="2"
style="vertical-align:top;padding:5pt;overflow:hidden">
                                                <p dir="ltr"
style="line-height:1.2;margin-top:0pt;margin-bottom:0pt"><a
href="https://www.facebook.com/georgialibraries"
style="text-decoration:none" rel="noreferrer noreferrer noreferrer"
                                                    target="_blank"
moz-do-not-send="true"><span
style="font-size:9pt;font-family:Verdana,sans-serif;color:rgb(17,85,204);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:underline;vertical-align:baseline;white-space:pre-wrap"><span
style="border:none;display:inline-block;overflow:hidden;width:36px;height:36px"><img
alt="logo with link to Georgia Public Library Service Facebook page"
src="https://lh7-us.googleusercontent.com/6w_oGavvmanlJjopnWjQasuhDGEEJEVEE84xTswu-HcAjkQQP6stG0dYmWee4gqG7tpuLb9dxEu_kkdKn1w1ZqNO5TG9JSCU55rEOq6s7B-1vDTaEJC4b6iAr_8EJKpJmPbMBRpL6xQuI7A-_thfq1k"
                                                    width="36"
                                                    height="36"
style="margin-left:0px;margin-top:0px" moz-do-not-send="true"></span></span></a><a
href="https://www.instagram.com/georgialibraries/"
style="text-decoration:none" rel="noreferrer noreferrer noreferrer"
                                                    target="_blank"
moz-do-not-send="true"><span
style="font-size:11pt;font-family:Verdana,sans-serif;color:rgb(17,85,204);background-color:transparent;font-weight:700;font-style:normal;font-variant:normal;text-decoration:underline;vertical-align:baseline;white-space:pre-wrap"><span
style="border:none;display:inline-block;overflow:hidden;width:34px;height:34px"><img
alt="logo with link to Georgia Public Library Service Instagram page"
src="https://lh7-us.googleusercontent.com/ets1wTG4VgvmoyrYQy9d1VgccTloy5BMwZp38qoKrBB9Cel8Yw9vCat-yv4MAnndeSReKSMsOUYyRKCoAx3ukwt-hbFrz5a2PIQILIgADpp2lDcYDAOyynfBANukdYsaDcZHtI6ojUb6XU3_xxFYDmI"
                                                    width="34"
                                                    height="34"
style="margin-left:0px;margin-top:0px" moz-do-not-send="true"></span></span></a><a
href="https://www.linkedin.com/company/georgia-public-library-service/"
style="text-decoration:none" rel="noreferrer noreferrer noreferrer"
                                                    target="_blank"
moz-do-not-send="true"><span
style="font-size:9pt;font-family:Verdana,sans-serif;color:rgb(17,85,204);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:underline;vertical-align:baseline;white-space:pre-wrap"><span
style="border:none;display:inline-block;overflow:hidden;width:36px;height:36px"><img
alt="logo with link to Georgia Public Library Service LinkedIn page"
src="https://lh7-us.googleusercontent.com/L1Fdzro7GGVA7PGFptQUgxZyXHP2qFoIXReXmf32F9YuOEssDwwAbKl1978orkQlmrnGO_Wg0TLmUrfZyXtHj6-sp3_QjbOKJ6Sq8TlpLxtYC7yHhSCUv7HWDK2GhdovAjNNHAt-wnTj8HZ0IGCgT38"
                                                    width="36"
                                                    height="36"
style="margin-left:0px;margin-top:0px" moz-do-not-send="true"></span></span></a><a
href="https://www.threads.net/@georgialibraries"
style="text-decoration:none" rel="noreferrer noreferrer noreferrer"
                                                    target="_blank"
moz-do-not-send="true"><span
style="font-size:11pt;font-family:Verdana,sans-serif;color:rgb(17,85,204);background-color:transparent;font-weight:700;font-style:normal;font-variant:normal;text-decoration:underline;vertical-align:baseline;white-space:pre-wrap"><span
style="border:none;display:inline-block;overflow:hidden;width:34px;height:34px"><img
alt="logo with link to Georgia Public Library Service Threads page"
src="https://lh7-us.googleusercontent.com/yTssqUWYNvGAfzsSQez79IscEAuQINHwN1vUnHkuedcP5wCIUa_v-zeD2qRUgnMkG9xin18BP9LNgTL05aShQACXP5P9cowXyP8m5Rg4fUciXmByursG-41yt_6wHdqlSo847rFUiRk3GJ7TfPI6hnI"
                                                    width="34"
                                                    height="34"
style="margin-left:0px;margin-top:0px" moz-do-not-send="true"></span></span></a></p>
                                              </td>
                                            </tr>
                                            <tr
style="height:1.06581e-14pt">
                                              <td colspan="2"
style="vertical-align:top;overflow:hidden"><br>
                                              </td>
                                              <td colspan="2"
style="vertical-align:top;padding:5pt;overflow:hidden"><br>
                                              </td>
                                            </tr>
                                          </tbody>
                                        </table>
                                      </div>
                                      <br>
                                      <br>
                                    </div>
                                  </div>
                                </div>
                              </div>
                            </div>
_______________________________________________<br>
                            Evergreen-circ mailing list<br>
                            <a
href="mailto:Evergreen-circ@list.evergreen-ils.org"
                              rel="noreferrer noreferrer noreferrer"
                              target="_blank" moz-do-not-send="true"
                              class="moz-txt-link-freetext">Evergreen-circ@list.evergreen-ils.org</a><br>
                            <a
href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-circ"
rel="noreferrer noreferrer noreferrer noreferrer" target="_blank"
                              moz-do-not-send="true"
                              class="moz-txt-link-freetext">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-circ</a><br>
                          </blockquote>
                        </div>
                      </blockquote>
                    </div>
                  </div>
                </div>
                _______________________________________________<br>
                Evergreen-general mailing list<br>
                <a
                  href="mailto:Evergreen-general@list.evergreen-ils.org"
                  rel="noreferrer noreferrer" target="_blank"
                  moz-do-not-send="true" class="moz-txt-link-freetext">Evergreen-general@list.evergreen-ils.org</a><br>
                <a
href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general"
                  rel="noreferrer noreferrer noreferrer" target="_blank"
                  moz-do-not-send="true" class="moz-txt-link-freetext">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general</a><br>
              </blockquote>
            </div>
          </blockquote>
        </div>
      </div>
      <br>
      <fieldset class="moz-mime-attachment-header"></fieldset>
      <pre wrap="" class="moz-quote-pre">_______________________________________________
Evergreen-general mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Evergreen-general@list.evergreen-ils.org">Evergreen-general@list.evergreen-ils.org</a>
<a class="moz-txt-link-freetext" href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>