Re: [Evergreen-general] ANNOUNCMENT - Welcome to the New Director of the Evergreen Indiana Library Consortium

[Lussier, Kathy via Evergreen-general]

Welcome to the community Courtney! If you need any guidance as you get
familiar with the Evergreen community, feel free to reach out!

Kathy
--
Kathy Lussier
she/her
Executive Director
NOBLE: North of Boston Library Exchange
Danvers, MA
978-777-8844 x201
www.noblenet.org




On Thu, Apr 25, 2024 at 12:25 PM Frasur, Ruth via Evergreen-general <
evergreen-general@list.evergreen-ils.org> wrote:

> Hello Evergreen Community,
>
> I am pleased to announce the appointment of Courtney Brown as the incoming
> Director of the Evergreen Indiana Library Consortium.  Courtney is well
> known to many of you based on her roles as Southwest Regional Coordinator
> from the Indiana State Library, as well as her time at Plainfield-Guilford
> Township Public Library and the Indianapolis Public Library.  Courtney has
> been a long-time advocate and resource for Evergreen Indiana and has served
> and led in many ways throughout the years.  Courtney will enter into her
> role beginning Monday, April 29, and I will be working with her until May
> 24.
>
> We are excited to welcome Courtney into the Evergreen Indiana Library
> Consortium.
>
> Ruth Frasur Davis (she/they)
>
> Coordinator
>
> *Evergreen Indiana Library Consortium*
>
> Indiana State Library
>
> 140 N. Senate Ave.
>
> Indianapolis, IN 46204
>
> (317) 232-3691
>
>
> ___
> Evergreen-general mailing list
> Evergreen-general@list.evergreen-ils.org
> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general
>
___
Evergreen-general mailing list
Evergreen-general@list.evergreen-ils.org
http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general

Re: [Evergreen-general] SMS Messages Not Being Received

[Lussier, Kathy via Evergreen-general]

Hi,

One thing to keep in mind is that Evergreen's core text messaging
functionality was created more than 10 years ago when the wireless service
provider market was much less complex. We now have carriers that use
multiple networks, each with its own email gateway. Does the typical patron
know which network their discount carrier may happen to run on? Some
carriers don't even provide an email gateway, or make it very difficult to
find. If I were to write up development requirements for this feature in
2024, they would be entirely different from what they were in 2011ish.

NOBLE is planning to move to a third-party text messaging service soon.
Although I can't speak to how this provider works yet, in my previous job,
I used a service that relied on Twilio, and it was a much better
experience. Patrons didn't have to worry about getting the precise carrier
listed. It did not fix the sending / receipt for every single text message,
but it did handle text messaging in a modern way with sophisticated error
reporting letting us know the reason for the failed delivery, which helped
staff better manage these errors.

Kathy
--
Kathy Lussier
she/her
Executive Director
NOBLE: North of Boston Library Exchange
Danvers, MA
978-777-8844 x201
www.noblenet.org




On Mon, Apr 8, 2024 at 12:50 PM Lolis, John via Evergreen-general <
evergreen-general@list.evergreen-ils.org> wrote:

> I don't know about anyone else's mileage, but in the past few weeks I've
> had reports of even personal text messages failing delivery.  T'would be a
> shame if we end up chasing our tails trying to fix something we have no
> control over.  I'm not saying this is definitely the case, but it bears
> consideration.
>
> John Lolis
> Coordinator of Computer Systems
>
> 100 Martine Avenue
> White Plains, NY  10601
> tel: 1.914.422.1497
> fax: 1.914.422.1452
>
> https://whiteplainslibrary.org/
>
> *“I would rather have questions that can’t be answered than answers that
> can’t be questioned.”*
> — Richard Feynman
> ,
> theoretical physicist and recipient of the Nobel Prize in Physics in 1965
>
>
> On Mon, 8 Apr 2024 at 09:17, Elizabeth Davis via Evergreen-general <
> evergreen-general@list.evergreen-ils.org> wrote:
>
>> Hi Jon,
>>
>> We went with Unique’s MessageBee.  We manage is on the consortium level
>> so there’s no customization for individual libraries, but it’s been working
>> great.
>>
>>
>>
>> *Elizabeth Davis* (she/her), *Support & Project Management Specialist*
>>
>> *Pennsylvania Integrated Library System **(PaILS) | SPARK*
>>
>> (717) 256-1627 | elizabeth.da...@sparkpa.org
>> 
>> support.sparkpa.org | supp...@sparkpa.org
>>
>>
>>
>> *From:* Evergreen-general <
>> evergreen-general-boun...@list.evergreen-ils.org> *On Behalf Of *JonGeorg
>> SageLibrary via Evergreen-general
>> *Sent:* Friday, April 5, 2024 6:13 PM
>> *To:* Evergreen Discussion Group <
>> evergreen-general@list.evergreen-ils.org>
>> *Cc:* JonGeorg SageLibrary 
>> *Subject:* Re: [Evergreen-general] SMS Messages Not Being Received
>>
>>
>>
>> Elizabeth, what 3rd party service did you end up using and how well has
>> it been working for your libraries?
>>
>> -Jon
>>
>>
>>
>> On Fri, Apr 5, 2024 at 11:29 AM Elizabeth Davis via Evergreen-general <
>> evergreen-general@list.evergreen-ils.org> wrote:
>>
>> Hi Will
>>
>>
>>
>> We’ve had several issues with most of the carriers on SMS issues.
>> Sometimes SMS messages were throttled, and patrons would get them days or
>> weeks later if at all.  Some carriers just stopped sending them totally.
>> Sometimes the messages to a specific carrier would deliver for one library
>> in the consortium but not others.  We tried changing from sending SMS to
>> MMS with no luck.  Also we were getting asked to add new carriers that
>> don’t have gateways and so we were unable to provide SMS service to those
>> patrons.In the end we moved to a third-party option to deliver SMS
>> notifications.
>>
>>
>>
>>
>>
>> *Elizabeth Davis *(she/her), *Support & Project Management Specialist*
>>
>> *Pennsylvania Integrated Library System (PaILS) | SPARK*
>>
>> (717) 256-1627 | elizabeth.da...@sparkpa.org
>> 
>> support.sparkpa.org
>> 
>> | supp...@sparkpa.org
>>
>>
>>
>> *From:* Evergreen-general <
>> evergreen-general-boun...@list.evergreen-ils.org> *On Behalf Of *Szwagiel,
>> Will via Evergreen-general
>> *Sent:* Friday, April 5, 2024 2:13 PM
>> *To:* Szwagiel, Will via Evergreen-general <
>> evergreen-general@list.evergreen-ils.org>
>> *Cc:* Szwagiel, Will 
>> *Subject:* [Evergreen-general] SMS Messages Not Being Received
>>
>>
>>
>> Good afternoon,

Re: [Evergreen-general] Minors and Self Registration

[Lussier, Kathy via Evergreen-general]

Hi Gina,

We're using Quipu for self-registration at NOBLE. Even though it isn't the
Evergreen self-registration form, I can speak to how we handled minors at
NOBLE and also at my previous consortium, which was in the process of
implementing Quipu when I left.

In both cases, we looked to how libraries were handling the issuance of
physical library cards to minors to inform our policy on how to handle
registration through our online form. In my previous consortium, we found
that the form parents signed on behalf of their children in most of the
public libraries included an agreement that parents are solely responsible
for their child's use of library materials. Since our eCard allows access
to electronic resources, like Overdrive, it raised the question of how
parents could agree to this term if they didn't know their child had
registered for a card. All of the other terms they agreed to did not apply
to the use of e-resources (e.g. to be financially responsible for the loss
or damage of physical materials). In cases where a minor self registered
and then decided to pick up a physical card, the library's requirement for
the parental signature was applicable, so we only worried about the
e-resource use. In this case, the libraries agreed to a policy where
children under 13 could not self register for a card. If a minor of the age
of 14-15 self registered, Quipu requested a parental email address and sent
an email at registration informing the parent that the child had registered
for a card.

At NOBLE, we went in a different direction. Very few of our libraries ask
that parents agree that they are solely responsible for their child's use
of library materials. Our libraries ultimately decided against setting any
age restrictions. There also is no email sent to parents of minors.

Does Bilbliomation's self-registration allow for access to electronic
resources? If not, I would think the best way to approach this is for
libraries to continue to follow local policies for requiring parental
signatures when the minor picks up the physical card.

I hope this helps!
Kathy
--
Kathy Lussier
she/her
Executive Director
NOBLE: North of Boston Library Exchange
Danvers, MA
978-777-8844 x201
www.noblenet.org




On Mon, Apr 1, 2024 at 10:27 AM Gina Monti via Evergreen-general <
evergreen-general@list.evergreen-ils.org> wrote:

> Hi Everyone,
>
> I had a conversation with a library director in regards to the self
> registration page.  I know that there is support in developing a
> customizable page, but in the meantime, I wanted to ask how other
> libraries/consortia handle minors wanting to self-register for cards.
>
> I have mentioned to this director that we can add a DOB, but the main
> problem is having an actual acknowledgement of the library policy to
> protect minors given the current climate in regards to censorship.  This I
> completely understand, and I'm interested in your replies of how
> Evergreen can address this issue if possible.
>
> Thanks!
>
> --
> Gina Monti (she/her)
> Evergreen Systems Manager
> Bibliomation, Inc.
> (203) 577-4070 ext. 109
> English, American Sign Language
> ___
> Evergreen-general mailing list
> Evergreen-general@list.evergreen-ils.org
> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general
>
___
Evergreen-general mailing list
Evergreen-general@list.evergreen-ils.org
http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general

Re: [Evergreen-general] Sharing plans for changing library selector in Angular staff catalog

[Lussier, Kathy via Evergreen-general]

ttings, notice setup, hold/circ policies,
> proximity adjustment, and many, many more -- that having "Add to
> custom tree(s) for search" as a checklist item that takes less than a
> minute seems reasonable.
>
> Actually, having typed out that partial list of new-org tasks, I think
> some may see it as a significant benefit to have the option of a
> custom tree "in front" of the natural tree, because then staff, like
> patrons, cannot stumble upon a half-configured org -- or, from the
> admin's perspective, central admins don't have to do everything in one
> go as quickly as possible (or late at night), and get to control when
> staff start having access to the new org for search.
>
> > Thanks Mike!
>
> Thank you as well!
>
> --Mike
>
> > Kathy
> >
> > --
> > Kathy Lussier
> > she/her
> > Executive Director
> > NOBLE: North of Boston Library Exchange
> > Danvers, MA
> > 978-777-8844 x201
> > www.noblenet.org
> >
> >
> >
> >
> > On Wed, Jan 24, 2024 at 12:51 PM Mike Rylander via Evergreen-general <
> evergreen-general@list.evergreen-ils.org> wrote:
> >>
> >> Hi all,
> >>
> >> As Andrea mentioned, we've been working on functionality adjacent to
> >> the main topic of this thread for a bit.  The pullrequest branch is
> >> attached to the Library Groups LP bug she pointed to, and you can find
> >> it here:
> >>
> >>
> https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/miker/lp-1949109-staff-catalog-lassos-loc_groups
> >>
> >> To reiterate the reason we kept the library groups and location groups
> >> selector separate from the library (org unit) selector, and also
> >> combined them into one UI element: both library and location groups
> >> are NOT subordinate to org units, because they can cross hierarchical
> >> boundaries, and they are mutually exclusive, because they represent
> >> different, competing, non-hierarchical search contexts.  Instead their
> >> applicability is /dependent/ on the context ("search", yes, but not
> >> only search) org, and essentially /replaces/ it in the search.
> >> Especially for large installations with many org units, using either
> >> of these grouping mechanisms becomes untenable if we try to shove them
> >> all into the same dropdown as the libraries, because they would have
> >> to be duplicated in many places and would thereby make the long org
> >> list even longer and harder to use.
> >>
> >> Regarding the main "hide certain orgs" concept from the OP, on
> >> balance, it definitely feels to me like a job for custom org trees
> >> with a new "purpose" (the one existing purpose being: "opac"),
> >> especially given the variable shape of the tree mentioned up-thread in
> >> some cases.  While there does exist a way to hide "intermediate" org
> >> units today, it requires the interaction of multiple configuration
> >> points (opac_visible flags, and the "inherit visibility" library
> >> setting(s)), which makes it feel flimsy in comparison to an explicitly
> >> defined tree.  A single "this is what my staff should see *in this
> >> interface*" option seems (1) conceptually simpler, (2) more flexible,
> >> and (3) more maintainable.
> >>
> >> If we were/are voting, that'd definitely get my vote.
> >>
> >> Thanks!
> >>
> >> --
> >> Mike Rylander
> >> Research and Development Manager
> >> Equinox Open Library Initiative
> >> 1-877-OPEN-ILS (673-6457)
> >> work: mi...@equinoxoli.org
> >> personal: mrylan...@gmail.com
> >> https://equinoxOLI.org
> >>
> >> On Tue, Jan 23, 2024 at 12:01 PM Andrea Buntz Neiman via
> >> Evergreen-general  wrote:
> >> >
> >> > Chiming in to note that Equinox recently completed work on these
> related bugs:
> >> >
> >> > https://bugs.launchpad.net/evergreen/+bug/1949109 - Add Library
> Groups to Angular Staff Catalog
> >> > https://bugs.launchpad.net/evergreen/+bug/1861701 - Angular staff
> catalog copy location group filtering support
> >> >
> >> > We will be sharing a branch shortly.
> >> >
> >> > ABN
> >> >
> >> > On Tue, Jan 23, 2024 at 11:39 AM Tina Ji via Evergreen-general <
> evergreen-general@list.evergreen-ils.org> wrote:
> >> >>
> >> >

Re: [Evergreen-general] Evergreen 3.11.4 & 3.12.2 Released

[Lussier, Kathy via Evergreen-general]

A big thank you to Jane, Andrea, Ruth, and Stephanie for their work in
getting this point release out the door (and apologies if I missed anyone
on the team). It looks like there is a lot of good stuff in there.

Kathy
--
Kathy Lussier
she/her
Executive Director
NOBLE: North of Boston Library Exchange
Danvers, MA
978-777-8844 x201
www.noblenet.org




On Mon, Feb 26, 2024 at 11:24 AM Frasur, Ruth via Evergreen-general <
evergreen-general@list.evergreen-ils.org> wrote:

> The Evergreen development team is pleased to announce the release of
> Evergreen 3.11.4 and 3.12.2.
>
> Both releases contain several bug fixes over their prior versions.  Please
> read the linked release notes for more details.
>
>- Release Notes - 3.11.4
>
> 
>- Release Notes - 3.12.2
>
> 
>
>
> Downloads are available at https://evergreen-ils.org/egdownloads/.
>
> Thanks to everyone who participated in submitting bugs, patches, and
> testing among the myriad other things that go into Evergreen ILS releases.
>
>
> Ruth Frasur Davis (she/they)
>
> Coordinator
>
> *Evergreen Indiana Library Consortium*
>
> *Evergreen Community Development Initiative*
>
> Indiana State Library
>
> 140 N. Senate Ave.
>
> Indianapolis, IN 46204
>
> (317) 232-3691
>
>
> ___
> Evergreen-general mailing list
> Evergreen-general@list.evergreen-ils.org
> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general
>
___
Evergreen-general mailing list
Evergreen-general@list.evergreen-ils.org
http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general

[Evergreen-general] Seeking volunteers to help organize a program at ALA

[Lussier, Kathy via Evergreen-general]

Hi all,

I am working with the Outreach Committee to revitalize the Evergreen
program that we used to regularly sponsor at ALA.

For many years, the Evergreen Outreach Committee organized meetups and
programs at the ALA Midwinter (now LibLearn X) meeting and Annual
Conference to try to raise
the visibility of the project to the larger library community. Those
programs ended in 2020 when in-person conferences were suspended, and it
would be good to see Evergreen promoted at a national event once again.

A list of previous project ALA activities is available at
https://wiki.evergreen-ils.org/doku.php?id=outreach:ala

If you are willing to help out to organize the program, please let me know.
You don't need to attend ALA to help, but, if you are going to ALA, so much
the better because we will need people to facilitate or present the
program.

Because the deadline to submit a meeting room request is Friday,  we don't
have much time to come up with a general idea of what we want to do. We can
refine it later, but we should have a solid idea of what we'll be
discussing before the request is submitted. This project will also need
approval from the Evergreen Project board on Thursday before we submit the
request to ALA.

Feel free to let me know if you have questions!
Kathy

--
Kathy Lussier
she/her
Executive Director
NOBLE: North of Boston Library Exchange
Danvers, MA
978-777-8844 x201
www.noblenet.org
___
Evergreen-general mailing list
Evergreen-general@list.evergreen-ils.org
http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general

Re: [Evergreen-general] Sharing plans for changing library selector in Angular staff catalog

[Lussier, Kathy via Evergreen-general]

athy Lussier
> > she/her
> > Executive Director
> > NOBLE: North of Boston Library Exchange
> > Danvers, MA
> > 978-777-8844 x201
> > www.noblenet.org
> >
> >
> >
> >
> > On Wed, Jan 24, 2024 at 12:51 PM Mike Rylander via Evergreen-general <
> evergreen-general@list.evergreen-ils.org> wrote:
> >>
> >> Hi all,
> >>
> >> As Andrea mentioned, we've been working on functionality adjacent to
> >> the main topic of this thread for a bit.  The pullrequest branch is
> >> attached to the Library Groups LP bug she pointed to, and you can find
> >> it here:
> >>
> >>
> https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/miker/lp-1949109-staff-catalog-lassos-loc_groups
> >>
> >> To reiterate the reason we kept the library groups and location groups
> >> selector separate from the library (org unit) selector, and also
> >> combined them into one UI element: both library and location groups
> >> are NOT subordinate to org units, because they can cross hierarchical
> >> boundaries, and they are mutually exclusive, because they represent
> >> different, competing, non-hierarchical search contexts.  Instead their
> >> applicability is /dependent/ on the context ("search", yes, but not
> >> only search) org, and essentially /replaces/ it in the search.
> >> Especially for large installations with many org units, using either
> >> of these grouping mechanisms becomes untenable if we try to shove them
> >> all into the same dropdown as the libraries, because they would have
> >> to be duplicated in many places and would thereby make the long org
> >> list even longer and harder to use.
> >>
> >> Regarding the main "hide certain orgs" concept from the OP, on
> >> balance, it definitely feels to me like a job for custom org trees
> >> with a new "purpose" (the one existing purpose being: "opac"),
> >> especially given the variable shape of the tree mentioned up-thread in
> >> some cases.  While there does exist a way to hide "intermediate" org
> >> units today, it requires the interaction of multiple configuration
> >> points (opac_visible flags, and the "inherit visibility" library
> >> setting(s)), which makes it feel flimsy in comparison to an explicitly
> >> defined tree.  A single "this is what my staff should see *in this
> >> interface*" option seems (1) conceptually simpler, (2) more flexible,
> >> and (3) more maintainable.
> >>
> >> If we were/are voting, that'd definitely get my vote.
> >>
> >> Thanks!
> >>
> >> --
> >> Mike Rylander
> >> Research and Development Manager
> >> Equinox Open Library Initiative
> >> 1-877-OPEN-ILS (673-6457)
> >> work: mi...@equinoxoli.org
> >> personal: mrylan...@gmail.com
> >> https://equinoxOLI.org
> >>
> >> On Tue, Jan 23, 2024 at 12:01 PM Andrea Buntz Neiman via
> >> Evergreen-general  wrote:
> >> >
> >> > Chiming in to note that Equinox recently completed work on these
> related bugs:
> >> >
> >> > https://bugs.launchpad.net/evergreen/+bug/1949109 - Add Library
> Groups to Angular Staff Catalog
> >> > https://bugs.launchpad.net/evergreen/+bug/1861701 - Angular staff
> catalog copy location group filtering support
> >> >
> >> > We will be sharing a branch shortly.
> >> >
> >> > ABN
> >> >
> >> > On Tue, Jan 23, 2024 at 11:39 AM Tina Ji via Evergreen-general <
> evergreen-general@list.evergreen-ils.org> wrote:
> >> >>
> >> >>
> >> >> On Mon, Jan 22, 2024 at 12:09 PM Lussier, Kathy via
> Evergreen-general  wrote:
> >> >> > #2 introduces new behavior that hasn't been used in previous staff
> >> >> > catalogs. We could not think of a use case where an org unit
> >> >> > should be invisible in the public catalog when performing a
> >> >> > search, but should be visible in the staff catalog search. However,
> >> >> >  if there is one, let us know so that we can add an option,
> >> >> > most likely a global flag.
> >> >>
> >> >>
> >> >> One of our library system does central cataloguing at its
> headquarter, which is not open to the public. It's OPAC invisible, but
> needed on the staff catalogue.
> >> >

Re: [Evergreen-general] Sharing plans for changing library selector in Angular staff catalog

[Lussier, Kathy via Evergreen-general]

ent to
> the main topic of this thread for a bit.  The pullrequest branch is
> attached to the Library Groups LP bug she pointed to, and you can find
> it here:
>
>
> https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/miker/lp-1949109-staff-catalog-lassos-loc_groups
>
> To reiterate the reason we kept the library groups and location groups
> selector separate from the library (org unit) selector, and also
> combined them into one UI element: both library and location groups
> are NOT subordinate to org units, because they can cross hierarchical
> boundaries, and they are mutually exclusive, because they represent
> different, competing, non-hierarchical search contexts.  Instead their
> applicability is /dependent/ on the context ("search", yes, but not
> only search) org, and essentially /replaces/ it in the search.
> Especially for large installations with many org units, using either
> of these grouping mechanisms becomes untenable if we try to shove them
> all into the same dropdown as the libraries, because they would have
> to be duplicated in many places and would thereby make the long org
> list even longer and harder to use.
>
> Regarding the main "hide certain orgs" concept from the OP, on
> balance, it definitely feels to me like a job for custom org trees
> with a new "purpose" (the one existing purpose being: "opac"),
> especially given the variable shape of the tree mentioned up-thread in
> some cases.  While there does exist a way to hide "intermediate" org
> units today, it requires the interaction of multiple configuration
> points (opac_visible flags, and the "inherit visibility" library
> setting(s)), which makes it feel flimsy in comparison to an explicitly
> defined tree.  A single "this is what my staff should see *in this
> interface*" option seems (1) conceptually simpler, (2) more flexible,
> and (3) more maintainable.
>
> If we were/are voting, that'd definitely get my vote.
>
> Thanks!
>
> --
> Mike Rylander
> Research and Development Manager
> Equinox Open Library Initiative
> 1-877-OPEN-ILS (673-6457)
> work: mi...@equinoxoli.org
> personal: mrylan...@gmail.com
> https://equinoxOLI.org
>
> On Tue, Jan 23, 2024 at 12:01 PM Andrea Buntz Neiman via
> Evergreen-general  wrote:
> >
> > Chiming in to note that Equinox recently completed work on these related
> bugs:
> >
> > https://bugs.launchpad.net/evergreen/+bug/1949109 - Add Library Groups
> to Angular Staff Catalog
> > https://bugs.launchpad.net/evergreen/+bug/1861701 - Angular staff
> catalog copy location group filtering support
> >
> > We will be sharing a branch shortly.
> >
> > ABN
> >
> > On Tue, Jan 23, 2024 at 11:39 AM Tina Ji via Evergreen-general <
> evergreen-general@list.evergreen-ils.org> wrote:
> >>
> >>
> >> On Mon, Jan 22, 2024 at 12:09 PM Lussier, Kathy via Evergreen-general <
> evergreen-general@list.evergreen-ils.org> wrote:
> >> > #2 introduces new behavior that hasn't been used in previous staff
> >> > catalogs. We could not think of a use case where an org unit
> >> > should be invisible in the public catalog when performing a
> >> > search, but should be visible in the staff catalog search. However,
> >> >  if there is one, let us know so that we can add an option,
> >> > most likely a global flag.
> >>
> >>
> >> One of our library system does central cataloguing at its headquarter,
> which is not open to the public. It's OPAC invisible, but needed on the
> staff catalogue.
> >>
> >>
> >> 
> >> From: Evergreen-general <
> evergreen-general-boun...@list.evergreen-ils.org> on behalf of Terran
> McCanna via Evergreen-general 
> >> Sent: Tuesday, January 23, 2024 7:13 AM
> >> To: Evergreen Discussion Group <
> evergreen-general@list.evergreen-ils.org>
> >> Cc: Terran McCanna 
> >> Subject: Re: [Evergreen-general] Sharing plans for changing library
> selector in Angular staff catalog
> >>
> >> About disused Org Units - even after a branch closes completely and all
> of the active materials and patrons have been moved off of it so we don't
> want it to appear in most dropdown lists, we sometimes still need to run
> reports on it. It would be nice to have the option in the reporter to
> include non-staff-visible branches. Maybe that is as simple as adding a new
> report source in the fieldmapper that can be used instead of the normal Org
> Unit source when desired?
> >>
> >> O

Re: [Evergreen-general] Sharing plans for changing library selector in Angular staff catalog

[Lussier, Kathy via Evergreen-general]

Thanks for the links Andrea! To be clear, the copy location group work adds
those groups as a separate filter, rather than a part of the library
selector, right?

Kathy
--
Kathy Lussier
she/her
Executive Director
NOBLE: North of Boston Library Exchange
Danvers, MA
978-777-8844 x201
www.noblenet.org




On Tue, Jan 23, 2024 at 12:01 PM Andrea Buntz Neiman via Evergreen-general <
evergreen-general@list.evergreen-ils.org> wrote:

> Chiming in to note that Equinox recently completed work on these related
> bugs:
>
> https://bugs.launchpad.net/evergreen/+bug/1949109 - Add Library Groups to
> Angular Staff Catalog
> https://bugs.launchpad.net/evergreen/+bug/1861701 - Angular staff catalog
> copy location group filtering support
>
> We will be sharing a branch shortly.
>
> ABN
>
> On Tue, Jan 23, 2024 at 11:39 AM Tina Ji via Evergreen-general <
> evergreen-general@list.evergreen-ils.org> wrote:
>
>>
>> On Mon, Jan 22, 2024 at 12:09 PM Lussier, Kathy via Evergreen-general <
>> evergreen-general@list.evergreen-ils.org> wrote:
>> > #2 introduces new behavior that hasn't been used in previous staff
>> > catalogs. We could not think of a use case where an org unit
>> > should be invisible in the public catalog when performing a
>> > search, but should be visible in the staff catalog search. However,
>> >  if there is one, let us know so that we can add an option,
>> > most likely a global flag.
>>
>>
>> One of our library system does central cataloguing at its headquarter,
>> which is not open to the public. It's OPAC invisible, but needed on the
>> staff catalogue.
>>
>>
>> --
>> *From:* Evergreen-general <
>> evergreen-general-boun...@list.evergreen-ils.org> on behalf of Terran
>> McCanna via Evergreen-general 
>> *Sent:* Tuesday, January 23, 2024 7:13 AM
>> *To:* Evergreen Discussion Group <
>> evergreen-general@list.evergreen-ils.org>
>> *Cc:* Terran McCanna 
>> *Subject:* Re: [Evergreen-general] Sharing plans for changing library
>> selector in Angular staff catalog
>>
>> About disused Org Units - even after a branch closes completely and all
>> of the active materials and patrons have been moved off of it so we don't
>> want it to appear in most dropdown lists, we sometimes still need to run
>> reports on it. It would be nice to have the option in the reporter to
>> include non-staff-visible branches. Maybe that is as simple as adding a new
>> report source in the fieldmapper that can be used instead of the normal Org
>> Unit source when desired?
>>
>> On Mon, Jan 22, 2024 at 5:46 PM Galen Charlton via Evergreen-general <
>> evergreen-general@list.evergreen-ils.org> wrote:
>>
>> Hi,
>>
>> On Mon, Jan 22, 2024 at 12:09 PM Lussier, Kathy via Evergreen-general <
>> evergreen-general@list.evergreen-ils.org> wrote:
>> > #2 introduces new behavior that hasn't been used in previous staff
>> > catalogs. We could not think of a use case where an org unit
>> > should be invisible in the public catalog when performing a
>> > search, but should be visible in the staff catalog search. However,
>> >  if there is one, let us know so that we can add an option,
>> > most likely a global flag.
>>
>> I can think of several:
>>
>> - Library joining a consortium. Most any migration workflow I can imagine
>> will result in a period of at least a few days, and sometimes longer, where
>> an OU exists and has holdings attached to it but shouldn't be visible in
>> the OPAC, but where staff nonetheless need to be able to do staff-side
>> searches limited to that OU.
>> - Library opening a new branch with an opening day collection. This could
>> lead to an even longer period where the OU exists but is not yet ready to
>> be visible to patrons
>> - An explicitly hidden or resource collection
>>
>> Does NOBLE have OUs that are completely disused?
>>
>> Regards,
>>
>> Galen
>> --
>> Galen Charlton
>> Implementation and IT Manager
>> Equinox Open Library Initiative
>> g...@equinoxoli.org
>> https://www.equinoxOLI.org
>> phone: 877-OPEN-ILS (673-6457)
>> direct: 770-709-5581
>> ___
>> Evergreen-general mailing list
>> Evergreen-general@list.evergreen-ils.org
>> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general
>>
>> This message originated from outside the M365 organisation. Please be
>> careful with links, and don't trust messages you don't recognise

Re: [Evergreen-general] Sharing plans for changing library selector in Angular staff catalog

[Lussier, Kathy via Evergreen-general]

Hi all,

This is a great discussion. Thanks for the feedback on this project.
Unfortunately, I was away from email yesterday and am just catching up with
these suggestions. I'll try to respond in the order that the messages were
sent.

[1] As Jason Stephenson suggested, adding a staff_visible column to
> actor.org_unit. However, if this is intended to have similar semantics to
> the opac_visible column - i.e., to suppress results from the staff catalog
> _search results_ additional work would be needed for the search engine.


This is a good point and not something we had thought about. I may have
assumed the same behavior occurred with the custom org tree. Currently, we
suppress the view of the system level for most of our libraries using opac
visibility, with the corresponding "Org Units Do Not Inherit Visibility"
flag enabled, in the public catalog, but we suppress it in the tpac staff
catalog using the custom org tree, as you suggest doing in #4. I just did
searches in both to see if I could figure out what the real-world impact is
using one over the other.

In the public catalog where we use OPAC visibility, on the record page, I
don't see the hidden system level in the holdings information. See below:
[image: image.png]

In the old tpac staff catalog where we use the custom org tree, the system
level shows:
[image: image.png]

I'm guessing this difference in display is because the custom org tree
isn't touching the search? I'll have to run this question by my team here.
I have a vague memory that, when the custom org tree development was
initially done, we were unhappy that org units removed from the tree
displayed in the bib record. This may give us an opportunity to fix
something that never exactly work the way we wanted, but I also may be
misremembering.

[2] Adding a "deleted" column to actor.org_unit to signify that the OU no
> longer exists. Logical deletion would allow certain types of information to
> be retained for historical reporting, but would require touching (at
> minimum) all of the org unit selectors.
> [3] Adding an "active" column to actor.org_unit. This would be
> intentionally softer than a "deleted" column, with the idea being that if
> an OU needs to be deleted, to go through the trouble of fully deleting it
> from the database. This option would also require touching all of the org
> unit selectors.


I love both of these ideas for disused OU's, and would support seeing this
work done so that we could remove those OU's from all selectors.. However,
we also have what we consider to be the far greater issue of removing the
system-level OUs from the search selector. Since the solution to that issue
would also result in our ability to remove disused OU's from the search
selector, I think we'll need to contain our project to this one selector.

[4] If the concern is more about the visibility of the org unit in the
> _catalog search form selector_, extending the custom OU tree mechanism.
> Probably less effort.


I had been  thinking the custom org tree, which provides so much more
flexibility for re-ordering org units than we need for this particular
project, was too big of a tool for dealing with simple visibility issues,
but, as I said above, we'll reconsider this decision.

[5] Adding a library setting (tied to the workstation) to list OUs that
> should not be included in the selector. Also less effort, and might offer
> some nice flexibility  - i.e., somebody at a branch just sees the active
> OUs on the selector, while somebody at a central tech services office might
> see everything.


We don't need that level of flexibility. There are lots of reasons we want
everyone working with the same set of org units in a search selector. One
less issue to troubleshoot if org units suddenly disappear is one of them.

Thanks for thinking through our options!

Kathy

--
Kathy Lussier
she/her
Executive Director
NOBLE: North of Boston Library Exchange
Danvers, MA
978-777-8844 x201
www.noblenet.org




On Tue, Jan 23, 2024 at 10:13 AM Galen Charlton  wrote:

> Hi,
>
> On Mon, Jan 22, 2024 at 5:57 PM Lussier, Kathy 
> wrote:
> > It sounds like an option is in order then, and I'm now wondering
> > if a global flag is appropriate or something that allows us to
> > determine staff catalog visibility on an OU by OU basis.
>
> Various options I see are.
>
> [1] As Jason Stephenson suggested, adding a staff_visible column to
> actor.org_unit. However, if this is intended to have similar semantics to
> the opac_visible column - i.e., to suppress results from the staff catalog
> _search results_ additional work would be needed for the search engine.
> [2] Adding a "deleted" column to actor.org_unit to signify that the OU no
> longer exists. Logical deletion would allow certain types of information to
> be retained for historical reporting, but would require touching (at
> minimum) all of the org unit selectors.
> [3] Adding an "active" column to actor.org_unit. This would be
> intentionally softer 

Re: [Evergreen-general] Sharing plans for changing library selector in Angular staff catalog

[Lussier, Kathy via Evergreen-general]

Hi all,

Thanks for the use cases. We will definitely add an option for this, most
likely in the way that Jason suggested.

Kathy
--
Kathy Lussier
she/her
Executive Director
NOBLE: North of Boston Library Exchange
Danvers, MA
978-777-8844 x201
www.noblenet.org




On Tue, Jan 23, 2024 at 9:35 AM Josh Stompro 
wrote:

> We have several locations that staff make use of but are hidden from the
> public catalog.
>
> ILL Locations - We have a central ILL OU for each region.  That isn't
> something that most staff need, only the ILL staff.  We have a local
> customization to hide ILL items from staff search results unless the ILL
> location is specifically selected.  But only ILL staff need that, and they
> log in with a workstation with the same OU.  So maybe an OU could be
> visible in the list if it equals the workstation OU?
>
> We have a book truck location for one branch that is hidden in the public
> catalog but staff would use.  It doesn't have a permanent collection, just
> things pulled together for short term use.
>
> Josh
>
>
> On Mon, Jan 22, 2024 at 11:09 AM Lussier, Kathy via Evergreen-general <
> evergreen-general@list.evergreen-ils.org> wrote:
>
>> Hi all,
>>
>> NOBLE is proceeding with a project to make some changes to the library
>> selector in the Angular staff catalog. I'm sharing our requirements with
>> the community first to ensure the project doesn't conflict with any desired
>> behavior for the selector.
>>
>> The full requirements are available at the bottom of this email, but the
>> short version is:
>>
>>
>>1. We plan to restore shelving location groups in the selector,
>>similar to the way they appear in the public catalog.
>>2. We plan to make the library selector for the staff catalog search
>>honor the visibility settings used for the public catalog library 
>> selector.
>>
>> #1 is the restoration of a feature from the old staff catalog.
>> #2 introduces new behavior that hasn't been used in previous staff
>> catalogs. We could not think of a use case where an org unit should be
>> invisible in the public catalog when performing a search, but should be
>> visible in the staff catalog search. However, if there is one, let us know
>> so that we can add an option, most likely a global flag.
>>
>> Please send us any feedback or concerns by the end of the day Friday so
>> that we can move forward with finalizing the requirements for this project.
>>
>>
>>  Angular Staff Catalog: Library Selector Improve...
>> <https://docs.google.com/document/d/1Aioe5GfQXHXrWVF90r_xdsbMhm1PjHP1vFOyyO0R3DY/edit?usp=drive_web>
>>
>> Thank you!
>> Kathy
>> --
>> Kathy Lussier
>> she/her
>> Executive Director
>> NOBLE: North of Boston Library Exchange
>> Danvers, MA
>> 978-777-8844 x201
>> www.noblenet.org
>>
>>
>> ___
>> Evergreen-general mailing list
>> Evergreen-general@list.evergreen-ils.org
>> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general
>>
>
___
Evergreen-general mailing list
Evergreen-general@list.evergreen-ils.org
http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general

Re: [Evergreen-general] Sharing plans for changing library selector in Angular staff catalog

[Lussier, Kathy via Evergreen-general]

Thanks Galen.

It sounds like an option is in order then, and I'm now wondering if a
global flag is appropriate or something that allows us to determine staff
catalog visibility on an OU by OU basis.

Yes, NOBLE has OUs that left the consortium that are completely disused.
Another issue is that, in Massachusetts, we have very few multi-branch
libraries. Displaying a system level and the branch level in the catalog
search selector is redundant for all but four of our libraries. We also
need an org unit for our statewide sharing system, which is not something
that gets searched. There may be some other use cases, but, overall, we've
found it very useful to have control over how the org units display in that
specific library selector.

Kathy
--
Kathy Lussier
she/her
Executive Director
NOBLE: North of Boston Library Exchange
Danvers, MA
978-777-8844 x201
www.noblenet.org




On Mon, Jan 22, 2024 at 5:46 PM Galen Charlton  wrote:

> Hi,
>
> On Mon, Jan 22, 2024 at 12:09 PM Lussier, Kathy via Evergreen-general <
> evergreen-general@list.evergreen-ils.org> wrote:
> > #2 introduces new behavior that hasn't been used in previous staff
> > catalogs. We could not think of a use case where an org unit
> > should be invisible in the public catalog when performing a
> > search, but should be visible in the staff catalog search. However,
> >  if there is one, let us know so that we can add an option,
> > most likely a global flag.
>
> I can think of several:
>
> - Library joining a consortium. Most any migration workflow I can imagine
> will result in a period of at least a few days, and sometimes longer, where
> an OU exists and has holdings attached to it but shouldn't be visible in
> the OPAC, but where staff nonetheless need to be able to do staff-side
> searches limited to that OU.
> - Library opening a new branch with an opening day collection. This could
> lead to an even longer period where the OU exists but is not yet ready to
> be visible to patrons
> - An explicitly hidden or resource collection
>
> Does NOBLE have OUs that are completely disused?
>
> Regards,
>
> Galen
> --
> Galen Charlton
> Implementation and IT Manager
> Equinox Open Library Initiative
> g...@equinoxoli.org
> https://www.equinoxOLI.org
> phone: 877-OPEN-ILS (673-6457)
> direct: 770-709-5581
>
___
Evergreen-general mailing list
Evergreen-general@list.evergreen-ils.org
http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general

Re: [Evergreen-general] Sharing plans for changing library selector in Angular staff catalog

[Lussier, Kathy via Evergreen-general]

Hi Ruth,

Great question! Yes, that piece is included in the more detailed
requirements, but was not mentioned in my email.  It's the piece of the
project that we're willing to save for a future date if it turns out to be
too complex to incorporate in this project, but we're hoping we can make
that happen.

Kathy
--
Kathy Lussier
she/her
Executive Director
NOBLE: North of Boston Library Exchange
Danvers, MA
978-777-8844 x201
www.noblenet.org




On Mon, Jan 22, 2024 at 12:30 PM Frasur, Ruth 
wrote:

> Kathy,
>
>
>
> Just a question – in the NOBLE public catalog, I see where the library
> shelving location groups appear in the Advanced Search.  I notice that when
> a library shelving location group is selected, it does not populate the
> included shelving locations in the “location” field in the same way
> shelving locations are populated there when an org unit is selected.  Is
> there a desire within the staff catalog to include that functionality (and
> hopefully also eventually bpac)?
>
>
>
> Also, thanks for sharing this.
>
>
>
> Ruth Frasur Davis (she/they)
>
> Coordinator
>
> *Evergreen Indiana Library Consortium*
>
> *Evergreen Community Development Initiative*
>
> Indiana State Library
>
> 140 N. Senate Ave.
>
> Indianapolis, IN 46204
>
> (317) 232-3691
>
>
>
> *From:* Evergreen-general <
> evergreen-general-boun...@list.evergreen-ils.org> *On Behalf Of *Lussier,
> Kathy via Evergreen-general
> *Sent:* Monday, January 22, 2024 12:09 PM
> *To:* Evergreen Discussion Group  >
> *Cc:* Lussier, Kathy 
> *Subject:* [Evergreen-general] Sharing plans for changing library
> selector in Angular staff catalog
>
>
>
>  This is an EXTERNAL email. Exercise caution. DO NOT open attachments
> or click links from unknown senders or unexpected email. 
> --
>
> Hi all,
>
>
>
> NOBLE is proceeding with a project to make some changes to the library
> selector in the Angular staff catalog. I'm sharing our requirements with
> the community first to ensure the project doesn't conflict with any desired
> behavior for the selector.
>
>
>
> The full requirements are available at the bottom of this email, but the
> short version is:
>
>
>
>1. We plan to restore shelving location groups in the selector,
>similar to the way they appear in the public catalog.
>2. We plan to make the library selector for the staff catalog search
>honor the visibility settings used for the public catalog library selector.
>
> #1 is the restoration of a feature from the old staff catalog.
>
> #2 introduces new behavior that hasn't been used in previous staff
> catalogs. We could not think of a use case where an org unit should be
> invisible in the public catalog when performing a search, but should be
> visible in the staff catalog search. However, if there is one, let us know
> so that we can add an option, most likely a global flag.
>
>
>
> Please send us any feedback or concerns by the end of the day Friday so
> that we can move forward with finalizing the requirements for this project.
>
>
>
>
>
> * Angular Staff Catalog: Library Selector Improve...
> <https://protect2.fireeye.com/v1/url?k=31323334-50bba2bf-31367a34-4544474f5631-72d20d3cf6093551=1=f1ee8472-6072-48e0-ab15-e15f80abd34b=https%3A%2F%2Fdocs.google.com%2Fdocument%2Fd%2F1Aioe5GfQXHXrWVF90r_xdsbMhm1PjHP1vFOyyO0R3DY%2Fedit%3Fusp%3Ddrive_web>*
>
>
>
> Thank you!
>
> Kathy
>
> --
>
> Kathy Lussier
>
> she/her
>
> Executive Director
>
> NOBLE: North of Boston Library Exchange
>
> Danvers, MA
>
> 978-777-8844 x201
>
> www.noblenet.org
> <https://protect2.fireeye.com/v1/url?k=31323334-50bba2bf-31367a34-4544474f5631-7104298d45dbc571=1=f1ee8472-6072-48e0-ab15-e15f80abd34b=http%3A%2F%2Fwww.noblenet.org%2F>
>
>
>
>
>
___
Evergreen-general mailing list
Evergreen-general@list.evergreen-ils.org
http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general

[Evergreen-general] Sharing plans for changing library selector in Angular staff catalog

[Lussier, Kathy via Evergreen-general]

Hi all,

NOBLE is proceeding with a project to make some changes to the library
selector in the Angular staff catalog. I'm sharing our requirements with
the community first to ensure the project doesn't conflict with any desired
behavior for the selector.

The full requirements are available at the bottom of this email, but the
short version is:


   1. We plan to restore shelving location groups in the selector, similar
   to the way they appear in the public catalog.
   2. We plan to make the library selector for the staff catalog search
   honor the visibility settings used for the public catalog library selector.

#1 is the restoration of a feature from the old staff catalog.
#2 introduces new behavior that hasn't been used in previous staff
catalogs. We could not think of a use case where an org unit should be
invisible in the public catalog when performing a search, but should be
visible in the staff catalog search. However, if there is one, let us know
so that we can add an option, most likely a global flag.

Please send us any feedback or concerns by the end of the day Friday so
that we can move forward with finalizing the requirements for this project.


 Angular Staff Catalog: Library Selector Improve...


Thank you!
Kathy
--
Kathy Lussier
she/her
Executive Director
NOBLE: North of Boston Library Exchange
Danvers, MA
978-777-8844 x201
www.noblenet.org
___
Evergreen-general mailing list
Evergreen-general@list.evergreen-ils.org
http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general

Re: [Evergreen-general] TEP board meeting January 18th

[Lussier, Kathy via Evergreen-general]

Hi all,

The report from the Membership Model Subcommittee is below:

 Membership Model Subcommittee January Board Report


I will be unable to attend the meeting, but Ruth and Galen both attended
the last Membership Model Subcommittee meeting and can answer any questions.

Kathy
--
Kathy Lussier
she/her
Executive Director
NOBLE: North of Boston Library Exchange
Danvers, MA
978-777-8844 x201
www.noblenet.org




On Wed, Jan 17, 2024 at 12:28 PM Katie Greenleaf Martin via
Evergreen-general  wrote:

> Hello all,
>
>
>
> The Evergreen Project Board will be meeting January 18th, 2024 at 11 a.m.
> PT / 1 p.m. CT / 2 p.m. ET.
>
>
>
> The agenda and connection details for the meeting are at
> https://wiki.evergreen-ils.org/doku.php?id=governance:minutes:2024-01-18
>
> This meeting is public and community members are encouraged to attend.
>
>
>
> Thanks!
>
> Katie
>
>
>
> TEP board secretary
>
>
>
>
>
>
>
> *Katie Greenleaf Martin *(she/her), *Executive Director*
>
> *Pennsylvania Integrated Library System (PaILS) | SPARK*
>
> (717) 873-9461 | k...@sparkpa.org
> support.sparkpa.org | supp...@sparkpa.org
>
>
> ___
> Evergreen-general mailing list
> Evergreen-general@list.evergreen-ils.org
> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general
>
___
Evergreen-general mailing list
Evergreen-general@list.evergreen-ils.org
http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general

Re: [Evergreen-general] [Evergreen-dev] Happy Bug Squashing Week!

[Lussier, Kathy via Evergreen-general]

Welcome to the community Brian!


--
Kathy Lussier
she/her
Executive Director
NOBLE: North of Boston Library Exchange
Danvers, MA
978-777-8844 x201
www.noblenet.org

On Mon, Aug 21, 2023, 7:26 PM Jason Stephenson via Evergreen-dev <
evergreen-...@list.evergreen-ils.org> wrote:

> Hi, all.
>
> It may be worth noting that we added a key for a new user to access the
> working repository today in addition to the usual bug squashing week
> activity.
>
> Welcome to the community, Brian Kennedy of SITKA!
>
> Jason
>
> On 8/21/23 09:34, Terran McCanna via Evergreen-dev wrote:
> > Good morning!
> >
> > Bug Squashing Week has begun and I there are already folks who have
> > dived in to begin updating Launchpad tickets.
> >
> > The list of community test servers with the fixes and features that have
> > been added to each is available here - one of them is ready to go and a
> > couple of others are being built:
> >
> >
> https://docs.google.com/spreadsheets/d/1kAdsJ9Hk9iW6cW9S9uAiosutIo_eBtFE7zRQy8iczbY/edit?usp=sharing
> <
> https://docs.google.com/spreadsheets/d/1kAdsJ9Hk9iW6cW9S9uAiosutIo_eBtFE7zRQy8iczbY/edit?usp=sharing
> >
> >
> > See the top of the first tab for useful links (general overview, list of
> > logins for the test servers, old bugs that need to be checked for
> > validity, new bugs that haven't been confirmed yet, etc.)
> >
> > Happy Squashing!
> > Terran
> >
> >
> >
> > Terran McCanna, PINES Program Manager
> >
> > 
> >
> > Georgia Public Library Service | University System of Georgia
> >
> > 2872 Woodcock Blvd, Suite 250 l Atlanta, GA 30341
> >
> > (404) 235-7138| tmcca...@georgialibraries.org
> > 
> >
> > http://help.georgialibraries.org  |
> > h...@georgialibraries.org 
> >
> >
> > <
> https://www.twitter.com/georgialibs><
> https://www.instagram.com/georgialibraries/><
> https://www.twitter.com/georgialibs>
> >
> > Join our email list for stories of Georgia
> > libraries making an impact in our communities.
> >
> >
> >
> > ___
> > Evergreen-dev mailing list
> > evergreen-...@list.evergreen-ils.org
> > http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-dev
> ___
> Evergreen-dev mailing list
> evergreen-...@list.evergreen-ils.org
> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-dev
>
___
Evergreen-general mailing list
Evergreen-general@list.evergreen-ils.org
http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general