Re: [Evergreen-general] New core committer: Stephanie Leary

[Thomsen, Elizabeth via Evergreen-general]

This is very good news indeed!  Congratulations, Stephanie!  (And
congratulations, Evergreen!)

On Tue, Feb 20, 2024 at 11:56 AM Rogan Hamby via Evergreen-general <
evergreen-general@list.evergreen-ils.org> wrote:

> Congratulations!
>
> On Tue, Feb 20, 2024 at 11:54 AM Diane Disbro via Evergreen-general <
> evergreen-general@list.evergreen-ils.org> wrote:
>
>> Thank you, Stephanie! You are a gem.
>>
>> Diane Disbro
>> Pronouns: she/her
>> Circulation Coordinator
>> Scenic Regional Library
>> 251 Union Plaza Drive
>> Union, MO 63084
>> (636) 583-0652 ext  110
>> ddis...@scenicregional.or 
>>
>>
>>
>> On Tue, Feb 20, 2024 at 10:31 AM Galen Charlton via Evergreen-general <
>> evergreen-general@list.evergreen-ils.org> wrote:
>>
>>> Hi,
>>>
>>> I am proud to announce that my colleague Stephanie Leary of the Equinox
>>> Open Library Initiative has been named as a core committer to the Evergreen
>>> Project.
>>>
>>> Stephanie has already made significant contributions to Evergreen's user
>>> interfaces and accessibility and leads the User Interface Interest Group. I
>>> look forward to her continuing efforts to improve the user experience for
>>> all Evergreen users.
>>>
>>> If you are new to the project and want to learn more about what a core
>>> committer does, please see here
>>> <https://wiki.evergreen-ils.org/doku.php?id=contributing:contributors>
>>> and here
>>> <https://wiki.evergreen-ils.org/doku.php?id=contributing:core_committer_responsibilities>
>>> .
>>>
>>> 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
>>>
>> ___
>> 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
>


-- 
Elizabeth B. Thomsen
(she/her)
Member Services Manager
NOBLE: North of Boston Library Exchange
Danvers, Mass.
978-777-8844
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] Invitation to apply to participate in the virtual Evergreen Project Strategic Plan Stakeholder Retreat

[Rosie Le Faive via Evergreen-general]

Thank you! I'll see you then.

From: Evergreen-general  on 
behalf of Frasur, Ruth via Evergreen-general 

Sent: Monday, February 12, 2024 2:29 PM
To: Evergreen-general@list.evergreen-ils.org 

Cc: Frasur, Ruth 
Subject: [Evergreen-general] Invitation to apply to participate in the virtual 
Evergreen Project Strategic Plan Stakeholder Retreat


CAUTION: This email originated from outside of UPEI. Do not click links or open 
attachments unless you recognize the sender and know the content is safe. If 
you are uncertain, please forward to phish...@upei.ca and delete this email.


Dear Community Members,

The Evergreen Project Board has been in the process of gathering information to 
help formulate a strategic plan for The Evergreen Project, a 501(c)3 
organization established to support the Evergreen open-source ILS and its 
community of practitioners.  Feedback has been solicited from that community of 
practitioners through a variety of activities and meetings.  On February 22 and 
23, the Strategic Plan Subcommittee of the Evergreen Project Board will host a 
virtual Stakeholder Retreat facilitated by Carson Block Consulting, Inc. to 
review and compile the gathered data.  The outcome of the retreat will be a 
strategic plan to ensure the sustainability of The Evergreen Project as an 
organization and provide a path of support for the Evergreen open-source ILS.

The Evergreen Project Strategic Plan Subcommittee invites interested 
individuals to apply to fill a limited number of seats for this and will select 
from the pool of applicants at the regularly scheduled TEP Board meeting at 
2:00 p.m. ET, Thursday, February 15.  If you are interested in participating in 
the virtual retreat, please fill out this 
application<https://forms.gle/eRwYt2q5AKTJhiEG9>.  You will be notified of your 
status following the TEP Board meeting.

Strategic Plan Subcommittee members are:

  *   Ruth Frasur Davis
  *   Jeanette Lundgren
  *   Kathy Lussier
  *   Katie Greenleaf Martin

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

Re: [Evergreen-general] [Evergreen-catalogers] Using Z39.50 to Import Authority Records

[Galen Charlton via Evergreen-general]

Hi Will,

Development would be required for Evergreen to directly import authority
records from a Z39.50 target. Most of the infrastructure is in place, but
to take it all the way, it would be necessary to teach Evergreen:

- how to set up the attributes specifically used for authority record search
- how to save the authority record while avoiding duplicates
- to distinguish between Z39.50 profiles for bibs vs authorities

There didn't seem to be a bug about this in Launchpad, so I've opened a new
one: https://bugs.launchpad.net/evergreen/+bug/2054453

In the meantime, MarcEdit's Z39.50 client is capable of searching NAF and
SAF from LC's Z39.50 server. You can do it directly by setting it up as a
Z39.50 search database, although MarcEdit isn't great at display the search
results (it seems to assume that the client is used only for searching bib
records). MarcEdit's headings validation tool can also search and download
the authority records needed to authorize headings in a bib file.

Regards,

Galen

On Tue, Feb 20, 2024 at 10:34 AM Szwagiel, Will via Evergreen-catalogers <
evergreen-catalog...@list.evergreen-ils.org> wrote:

> Good morning,
>
> A member of our Cataloging Committee was inquiring about the possibility
> of using Z39.50 to import authority records in Evergreen.  It appears that
> the Library of Congress provides Z39.50 access to authority records,
> according to this FAQ:
>
> https://authorities.loc.gov/help/auth-faq.htm#3
>
> "*5) Does the Library of Congress provide Z39.50 access to authority
> records?*
>
> *Yes.* Z39.50 access to authority records is available (database updated
> weekly). Information on configuring Z39.50 access to the Name Authority
> File and the Subject Authority File is available from the LC Z39.50
> Server Configuration Guidelines <https://www.loc.gov/z3950/lcserver.html>
> ."
>
> That link takes you to the configuration guidelines here:
>
>
> https://www.loc.gov/z3950/lcserver.html
>
>
> However, while we know that we can add Z39.50 servers to Evergreen for
> bibliographic records, we are not sure about authority records.  Is this
> something that is possible in Evergreen?  And if so, have any of you done
> it (or are doing it)?  How has it worked out for you?
>
>
> Another librarian mentioned that this impacts the access points for
> everything in the catalog.  Has this proven to be an issue for you in any
> way?
>
>
> Thank you in advance for sharing any insight you might have.
>
> *William C. Szwagiel*
>
> NC Cardinal Project Manager
>
> State Library of North Carolina
>
> william.szwag...@ncdcr.gov | 919.814.6721
>
> https://statelibrary.ncdcr.gov/services-libraries/nc-cardinal
>
> 109 East Jones Street  | 4640 Mail Service Center
>
> Raleigh, North Carolina 27699-4600
>
> The State Library is part of the NC Department of Natural & Cultural
> Resources.
>
> *Email correspondence to and from this address is subject to the North
> Carolina Public Records Law and may be disclosed to third parties.*
>
>
>
> --
>
> 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.
> ___
> Evergreen-catalogers mailing list
> evergreen-catalog...@list.evergreen-ils.org
> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catalogers
>


-- 
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
<http://evergreen-ils.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] New core committer: Stephanie Leary

[Rogan Hamby via Evergreen-general]

Congratulations!

On Tue, Feb 20, 2024 at 11:54 AM Diane Disbro via Evergreen-general <
evergreen-general@list.evergreen-ils.org> wrote:

> Thank you, Stephanie! You are a gem.
>
> Diane Disbro
> Pronouns: she/her
> Circulation Coordinator
> Scenic Regional Library
> 251 Union Plaza Drive
> Union, MO 63084
> (636) 583-0652 ext  110
> ddis...@scenicregional.or 
>
>
>
> On Tue, Feb 20, 2024 at 10:31 AM Galen Charlton via Evergreen-general <
> evergreen-general@list.evergreen-ils.org> wrote:
>
>> Hi,
>>
>> I am proud to announce that my colleague Stephanie Leary of the Equinox
>> Open Library Initiative has been named as a core committer to the Evergreen
>> Project.
>>
>> Stephanie has already made significant contributions to Evergreen's user
>> interfaces and accessibility and leads the User Interface Interest Group. I
>> look forward to her continuing efforts to improve the user experience for
>> all Evergreen users.
>>
>> If you are new to the project and want to learn more about what a core
>> committer does, please see here
>> <https://wiki.evergreen-ils.org/doku.php?id=contributing:contributors>
>> and here
>> <https://wiki.evergreen-ils.org/doku.php?id=contributing:core_committer_responsibilities>
>> .
>>
>> 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
>>
> _______
> 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] New core committer: Stephanie Leary

[Diane Disbro via Evergreen-general]

Thank you, Stephanie! You are a gem.

Diane Disbro
Pronouns: she/her
Circulation Coordinator
Scenic Regional Library
251 Union Plaza Drive
Union, MO 63084
(636) 583-0652 ext  110
ddis...@scenicregional.or 



On Tue, Feb 20, 2024 at 10:31 AM Galen Charlton via Evergreen-general <
evergreen-general@list.evergreen-ils.org> wrote:

> Hi,
>
> I am proud to announce that my colleague Stephanie Leary of the Equinox
> Open Library Initiative has been named as a core committer to the Evergreen
> Project.
>
> Stephanie has already made significant contributions to Evergreen's user
> interfaces and accessibility and leads the User Interface Interest Group. I
> look forward to her continuing efforts to improve the user experience for
> all Evergreen users.
>
> If you are new to the project and want to learn more about what a core
> committer does, please see here
> <https://wiki.evergreen-ils.org/doku.php?id=contributing:contributors>
> and here
> <https://wiki.evergreen-ils.org/doku.php?id=contributing:core_committer_responsibilities>
> .
>
> 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
>
___
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] New core committer: Stephanie Leary

[Frasur, Ruth via Evergreen-general]

Congratulations Stephanie!  And also, THANK YOU.

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-dev  On Behalf Of 
Galen Charlton via Evergreen-dev
Sent: Tuesday, February 20, 2024 11:31 AM
To: Evergreen Discussion Group ; 
Evergreen Development Discussion List 
Subject: [Evergreen-dev] New core committer: Stephanie Leary

 This is an EXTERNAL email. Exercise caution. DO NOT open attachments or 
click links from unknown senders or unexpected email. 

Hi,

I am proud to announce that my colleague Stephanie Leary of the Equinox Open 
Library Initiative has been named as a core committer to the Evergreen Project.

Stephanie has already made significant contributions to Evergreen's user 
interfaces and accessibility and leads the User Interface Interest Group. I 
look forward to her continuing efforts to improve the user experience for all 
Evergreen users.

If you are new to the project and want to learn more about what a core 
committer does, please see 
here<https://protect2.fireeye.com/v1/url?k=31323334-50bba2bf-31367a34-4544474f5631-7942ca39383dcce4&q=1&e=954e2627-ed00-46cb-85f7-481d65c61768&u=https%3A%2F%2Fwiki.evergreen-ils.org%2Fdoku.php%3Fid%3Dcontributing%3Acontributors>
 and 
here<https://protect2.fireeye.com/v1/url?k=31323334-50bba2bf-31367a34-4544474f5631-b1d89bb00cdea2ff&q=1&e=954e2627-ed00-46cb-85f7-481d65c61768&u=https%3A%2F%2Fwiki.evergreen-ils.org%2Fdoku.php%3Fid%3Dcontributing%3Acore_committer_responsibilities>.

Regards,

Galen
--
Galen Charlton
Implementation and IT Manager
Equinox Open Library Initiative
g...@equinoxoli.org<mailto:g...@equinoxoli.org>
https://www.equinoxOLI.org<https://protect2.fireeye.com/v1/url?k=31323334-50bba2bf-31367a34-4544474f5631-58c7608fb94d6f45&q=1&e=954e2627-ed00-46cb-85f7-481d65c61768&u=https%3A%2F%2Fwww.equinoxoli.org%2F>
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

[Evergreen-general] New core committer: Stephanie Leary

[Galen Charlton via Evergreen-general]

Hi,

I am proud to announce that my colleague Stephanie Leary of the Equinox
Open Library Initiative has been named as a core committer to the Evergreen
Project.

Stephanie has already made significant contributions to Evergreen's user
interfaces and accessibility and leads the User Interface Interest Group. I
look forward to her continuing efforts to improve the user experience for
all Evergreen users.

If you are new to the project and want to learn more about what a core
committer does, please see here
<https://wiki.evergreen-ils.org/doku.php?id=contributing:contributors> and
here
<https://wiki.evergreen-ils.org/doku.php?id=contributing:core_committer_responsibilities>
.

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

[Evergreen-general] Using Z39.50 to Import Authority Records

[Szwagiel, Will via Evergreen-general]

Good morning,

A member of our Cataloging Committee was inquiring about the possibility of 
using Z39.50 to import authority records in Evergreen.  It appears that the 
Library of Congress provides Z39.50 access to authority records, according to 
this FAQ:

https://authorities.loc.gov/help/auth-faq.htm#3


"5) Does the Library of Congress provide Z39.50 access to authority records?

Yes. Z39.50 access to authority records is available (database updated weekly). 
Information on configuring Z39.50 access to the Name Authority File and the 
Subject Authority File is available from the LC Z39.50 Server Configuration 
Guidelines<https://www.loc.gov/z3950/lcserver.html>."

That link takes you to the configuration guidelines here:


https://www.loc.gov/z3950/lcserver.html


However, while we know that we can add Z39.50 servers to Evergreen for 
bibliographic records, we are not sure about authority records.  Is this 
something that is possible in Evergreen?  And if so, have any of you done it 
(or are doing it)?  How has it worked out for you?


Another librarian mentioned that this impacts the access points for everything 
in the catalog.  Has this proven to be an issue for you in any way?


Thank you in advance for sharing any insight you might have.


William C. Szwagiel

NC Cardinal Project Manager

State Library of North Carolina

william.szwag...@ncdcr.gov<mailto:william.szwag...@ncdcr.gov> | 919.814.6721

https://statelibrary.ncdcr.gov/services-libraries/nc-cardinal

109 East Jones Street  | 4640 Mail Service Center

Raleigh, North Carolina 27699-4600

The State Library is part of the NC Department of Natural & Cultural Resources.

Email correspondence to and from this address is subject to the North Carolina 
Public Records Law and may be disclosed to third parties.





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.
___
Evergreen-general mailing list
Evergreen-general@list.evergreen-ils.org
http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general

[Evergreen-general] Hack-A-Hosting Proposals for 2024 Now Open

[Rogan Hamby via Evergreen-general]

We are looking for a host for the annual Hack-A-Way this year in 2024.
Traditionally we have opened proposals after the conference but we are
doing it a little early this year.  For those unfamiliar with it, the
Hack-A-Way is a much smaller event than the conference and a great way for
an organization to host a community event. The Hack-A-Way focuses on
providing a means for coders and documentation writers to collaborate in
person and plan major projects for the upcoming year.

What we need:


   - A clean meeting space for 15 - 30 people.
   - Working space for laptops.
   - A TV, projector or other display.
   - Adequate bandwidth for the users.
   - A few snacks and forms of hydration and caffeine to keep blood sugar
   and productivity up.
   - Facilitate reasonable hotel accommodations (cheaper is better but no
   bed bugs).
   - Although not required it's become tradition for the host to supply
   lunches.

If your organization is interested please contact me with details of your
proposal.


Rogan Hamby (he/him/his), MLIS

Data and Project Manager

Equinox Open Library Initiative

rogan.ha...@equinoxoli.org

1-770-709-5570 x5570

www.equinoxOLI.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] Evergreen 3.11.3 & 3.12.1 Released

[Jane Sandberg via Evergreen-general]

Hi Courtney,

3.12.2 is scheduled for next week.  I know that the release team for 3.13
just assembled this week, and I don't believe a schedule has been posted
yet, but I would expect it to be posted on this page
<https://wiki.evergreen-ils.org/doku.php?id=faqs:evergreen_roadmap> once it
is decided.

Hope this helps, and wishing you well on your upgrade!

  -Jane

El vie, 16 feb 2024 a la(s) 11:46 a.m., Courtney Earl Matthews via
Evergreen-general (evergreen-general@list.evergreen-ils.org) escribió:

> Hi Ruth and all,
>
> I you're all well and congratulations on the recent releases!
>
> At UPEI we've begun discussing our next upgrade. We're using 3.8 and are
> tentatively looking at Spring/early Summer upgrade.
> Do you have a sense of when 3.12.2 and the 3.13 series will be released?
>
> Best,
>
> Courtney.
>
> ~
>
> Courtney Matthews (he/him)
>
> Systems Librarian
>
> University of Prince Edward Island
>
>
> *I acknowledge we are on Epekwitk, part of the ancestral, unceded and
> unsurrendered territory of the Mi'kmaw Nation, and on which this
> institution stands. This territory is covered by the Treaties of Peace and
> Friendship, which recognize Mi'kmaw title and establish the
> ongoing relationship between the Mi'kmaw Nation and the Crown. We are all
> treaty people.*
> --
> *From:* Evergreen-general <
> evergreen-general-boun...@list.evergreen-ils.org> on behalf of Frasur,
> Ruth via Evergreen-general 
> *Sent:* February 5, 2024 2:00 PM
> *To:* Evergreen-general@list.evergreen-ils.org <
> evergreen-general@list.evergreen-ils.org>
> *Cc:* Frasur, Ruth 
> *Subject:* [Evergreen-general] Evergreen 3.11.3 & 3.12.1 Released
>
>
> *CAUTION:* This email originated from outside of UPEI. Do not click links
> or open attachments unless you recognize the sender and know the content is
> safe. If you are uncertain, please forward to phish...@upei.ca and delete
> this email.
>
>
> The Evergreen development team is pleased to announce the release of
> Evergreen 3.11.3 and 3.12.1.
>
> Both releases contain several bug fixes over their prior versions.  Please
> read the linked release notes for more details.
>
>- Release Notes - 3.11.3
>
> <https://evergreen-ils.org/documentation/release/RELEASE_NOTES_3_11.html#_evergreen_3_11_3>
>- Release Notes - 3.12.1
>
> <https://evergreen-ils.org/documentation/release/RELEASE_NOTES_3_12.html#_evergreen_3_12_1>
>
> 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

Re: [Evergreen-general] Evergreen 3.11.3 & 3.12.1 Released

[Courtney Earl Matthews via Evergreen-general]

Hi Ruth and all,

I you're all well and congratulations on the recent releases!

At UPEI we've begun discussing our next upgrade. We're using 3.8 and are 
tentatively looking at Spring/early Summer upgrade.
Do you have a sense of when 3.12.2 and the 3.13 series will be released?

Best,

Courtney.


~

Courtney Matthews (he/him)

Systems Librarian

University of Prince Edward Island



I acknowledge we are on Epekwitk, part of the ancestral, unceded and 
unsurrendered territory of the Mi'kmaw Nation, and on which this institution 
stands. This territory is covered by the Treaties of Peace and Friendship, 
which recognize Mi'kmaw title and establish the ongoing relationship between 
the Mi'kmaw Nation and the Crown. We are all treaty people.
________
From: Evergreen-general  on 
behalf of Frasur, Ruth via Evergreen-general 

Sent: February 5, 2024 2:00 PM
To: Evergreen-general@list.evergreen-ils.org 

Cc: Frasur, Ruth 
Subject: [Evergreen-general] Evergreen 3.11.3 & 3.12.1 Released


CAUTION: This email originated from outside of UPEI. Do not click links or open 
attachments unless you recognize the sender and know the content is safe. If 
you are uncertain, please forward to phish...@upei.ca and delete this email.


The Evergreen development team is pleased to announce the release of Evergreen 
3.11.3 and 3.12.1.

Both releases contain several bug fixes over their prior versions.  Please read 
the linked release notes for more details.

  *   Release Notes - 
3.11.3<https://evergreen-ils.org/documentation/release/RELEASE_NOTES_3_11.html#_evergreen_3_11_3>
  *   Release Notes - 
3.12.1<https://evergreen-ils.org/documentation/release/RELEASE_NOTES_3_12.html#_evergreen_3_12_1>

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

[BUG] Org parser error Invalid search bound (wrong side of point) [9.7 (9.7-??-7a6bb0904 @ /Users/dougheadley/.config/emacs/.local/straight/build-29.2/org/)]

[General discussions about Org-mode.]

using org-ai seemed to cause this bug.  I wouldn't have recieved this 
error otherwise.


Never filed a bug report before.  Please ignore if this seems incomplete.



⛔ Warning (org-element): org-element--cache: Org parser error in 
2024-02-14.org::898. Resetting.

The error was: (error "Invalid search bound (wrong side of point)")
Backtrace:
" backtrace-to-string(nil)
org-element-at-point()
org-eldoc-get-src-lang()
#f(compiled-function (&rest args) \"Return breadcrumbs when on a 
headline, args for src block header-line,\\n calls other documentation 
functions depending on lang when inside src body.\" #0x16f3b50a8f808dd9>)(#f(compiled-function (string &rest plist) 
#))
apply(#f(compiled-function (&rest args) \"Return breadcrumbs when on a 
headline, args for src block header-line,\\n calls other documentation 
functions depending on lang when inside src body.\" #0x16f3b50a8f808dd9>) #f(compiled-function (string &rest plist) 
#))
org-eldoc-documentation-function(#f(compiled-function (string &rest 
plist) #))

eldoc-documentation-default()
eldoc--invoke-strategy(nil)
eldoc-print-current-symbol-info()
#()
apply(# nil)
timer-event-handler([t 0 0 50 nil #F616e6f6e796d6f75732d6c616d626461_anonymous_lambda_13> nil idle 0 nil])

"
Please report this to Org mode mailing list (M-x org-submit-bug-report).

Emacs : GNU Emacs 29.2 (build 2, x86_64-apple-darwin23.2.0, NS 
appkit-2487.30 Version 14.2.1 (Build 23C71))

of 2024-01-24
Package: Org mode version 9.7 (9.7-??-7a6bb0904 @ 
/Users/dougheadley/.config/emacs/.local/straight/build-29.2/org/)


current state:
==
(setq
org-noter--doc-goto-location-hook '(org-noter-djvu--goto-location
org-noter-nov--goto-location
org-noter-pdf--goto-location)
org-journal-date-prefix "#+TITLE: "
org-link-elisp-confirm-function nil
org-directory "~/Network/syncthing/org"
org-after-refile-insert-hook '(save-buffer)
org-indirect-buffer-display 'current-window
org-roam-db-gc-threshold 2305843009213693951
org-crypt-key nil
org-hide-emphasis-markers t
org-bibtex-headline-format-function 'org-bibtex-headline-format-default
org-log-done 'time
org-roam-mode-hook '(+org-roam-detach-magit-section-mode-map-h
turn-on-visual-line-mode)
org-roam-dailies-capture-templates '(("d" "Default" entry "** %<%H:%M> %?"
:if-new
(file+head "%<%Y-%m-%d>.org"
"#+title: %<%Y-%m-%d>\n#+STARTUP: overview\n\n* master 
[[file:~/Network/syncthing/org/todo.org][todo]], 
[[id:0261f526-24cf-43a2-83b6-f9612334b685][job hunt]]\n* coffee time\n* 
work\n* personal\n* wrap up\n* daily journal\n")

)
)
org-load-hook '(+org-init-org-directory-h +org-init-appearance-h
+org-init-agenda-h +org-init-attachments-h
+org-init-babel-h +org-init-babel-lazy-loader-h
+org-init-capture-defaults-h +org-init-capture-frame-h
+org-init-custom-links-h +org-init-export-h
+org-init-habit-h +org-init-hacks-h +org-init-keybinds-h
+org-init-popup-rules-h +org-init-smartparens-h
+org-init-roam-h)
org-journal-find-file-fn 'find-file
org-startup-folded nil
org-babel-after-execute-hook 
'(+org-redisplay-inline-images-in-babel-result-h)

org-link-abbrev-alist '(("doomdir" . "/Users/dougheadley/.config/doom/%s")
("emacsdir" . "/Users/dougheadley/.config/emacs/%s")
("doom-repo" .
"https://github.com/doomemacs/doomemacs/%s";)
("wolfram" . "https://wolframalpha.com/input/?i=%s";)
("wikipedia" . "https://en.wikipedia.org/wiki/%s";)
("duckduckgo" . "https://duckduckgo.com/?q=%s";)
("kagi" . "https://kagi.com/search?q=%s";)
("gmap" . "https://maps.google.com/maps?q=%s";)
("gimages" . "https://google.com/images?q=%s";)
("google" . "https://google.com/search?q=";)
("youtube" . "https://youtube.com/watch?v=%s";)
("github" . "https://github.com/%s";))
org-agenda-files 
'("/Users/dougheadley/Network/syncthing/org/roam/20230912175002-job_hunt.org" 
"/Users/dougheadley/Network/syncthing/org/d.passiveobserver.org" 
"/Users/dougheadley/Network/syncthing/org/roam/20230612223054-diycloud.org" 
"/Users/dougheadley/Network/syncthing/org/20240104160254-iccesar.org" 
"/Users/dougheadley/Network/syncthing/org/todo.org" 
"/Users/dougheadley/Network/syncthing/org/20231101101832-gusto.org" 
"/Users/dougheadley/Network/syncthing/org/agenda.org")

org-journal-dir "~/Network/syncthing/org/journal/"
org-journal-date-format "%a, %Y-%m-%d"
org-capture-templates '(("d" "d.passiveobserver" entry
(file "~/Documents/org/d.passiveobserver.org")
"* TODO %?")
("g" "GitHub Link Capture" entry
(file "~/Documents/org/github.org")
"* [[%?]] Entered on %U")
("t" "Personal todo" entry
(file+headline +org-capture-todo-file "Inbox")
"* %u %?\n%i\n%a" :prepend t)
("n" "Personal notes" entry
(file+headline +org-capture-notes-file "Inbox")
"* %u %?\n%i\n%a" :prepend t)
("p" "Templates for projects")
("pt" "Project-local todo" entry
(file+headline +org-capture-project-todo-file
"Inbox")
"* TODO %?\n%i\n%a" :prepend t)
("pn" "Project-local notes" entry
(file+headline +org-capture-project-notes-file
"Inbox")
"* %U %?\n%i\n%a" :prepend t)
("pc" "Project-local changelog" entry
(file+headline +

[Evergreen-general] The Evergreen Project Board - Call for nominations open!

[Frasur, Ruth via Evergreen-general]

The Evergreen Project Board nomination process is now underway! We need to fill 
four (4) open positions, three of which are for three-year terms. The fourth is 
for a one-year term that will complete the term of a seat being vacated early.

Any individual who has contributed to the Evergreen open-source ILS community 
or is employed by an institution that uses the Evergreen ILS is eligible to be 
nominated as a candidate for an Evergreen Project Board seat. The deadline for 
nominations is Friday, March 1, 2024.

You may nominate another person or nominate yourself by filling out the form at 
https://forms.gle/3ZtZwqreTdBAoNPN8.  Self-nominations are encouraged.

Voter registration will begin the week of March 11.

The slate of candidates will be announced following the Evergreen Project Board 
meeting on Thursday, March 21, and voting will occur the week of March 25.

Information about the Board and what it does for the community can be found on 
the governance page: https://evergreen-ils.org/governance/ 
<https://evergreen-ils.org/governance/>

Please feel free to contact me or any other member of the Board if you have any 
questions about serving on the board or about the nomination / election process.

Ruth Frasur Davis (she/they)
President
Evergreen Project Board
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

Re: Why is not everything reproducible yet?

[Bernhard M. Wiedemann via rb-general]

On 14/02/2024 16.19, Santiago Torres-Arias wrote:

1. can we study the conflicting interestes (i.e., above) that stop
reproducibility from happening.


Yes, that should be possible. The above summarized my experience from 
the 1000 patches and bug-reports I did and the interactions with various 
upstreams.

The links are public and recorded in the monthly reports
https://salsa.debian.org/reproducible-builds/reproducible-website/-/tree/master/_reports
and earlier weekly posts
https://salsa.debian.org/reproducible-builds/reproducible-website/-/tree/master/_blog/posts

I can probably provide more input for such a study.


2. Are misunderstandings about reproducibility getting in the way from
pushing to it (e.g., the notion that docker containers are
inherrently reproducible). Is the perfect the enemy of the good?
what notions of reproducibility exist and how can we build a
roadmap from the weak to the strong?


There are some.
One is the confusion with what we started to call "repeatable builds" = 
the ability to be able to do a second build with the same explicit 
inputs. SBOMs help with repeatable builds, but if they become embedded 
in the build output, they can even hinder some side-benefits of 
reproducible builds, because every minor change in inputs now causes a 
change in output.


The other thing was
https://web.archive.org/web/20200807033032/https://blog.cmpxchg8b.com/2020/07/you-dont-need-reproducible-builds.html
that gained some anti-r-b mindshare, even though it neglegted several 
important aspects. E.g. it mentions the risk of stealing source-code 
which obviously does not apply to FLOSS.




3. What other uses of r-b exist beyond the malicious toolchain example?
can we use them as leverage to increase interest in the space?


On a past r-b summit we collected
https://reproducible-builds.org/docs/buy-in/
e.g. in openSUSE we always pushed for some level of binary equivalence 
to do build-tree-pruning in our open-build-service to save build power, 
shorten rebuild time and save bandwidth for mirrors and users that do 
not need to update unchanged packages.
We also publish updates as delta-rpm-packages that probably were more 
compact with fewer random variations.


The page also lists the QA aspect. I did find a dozen corruption bugs 
that went unnoticed for years.


e.g. https://gitlab.gnome.org/GNOME/libxslt/-/issues/37 had this 
memorable quote from upstream:
This was caused by an interesting bug in libxml2's streaming XPath engine. I'm still puzzled why it took so long to discover this issue. 


So for your study, you could find this link in _reports/2020-04.md

another corruption bug in
_reports/2023-10.md:* 
[`OpenRGB`](https://gitlab.com/CalcProgrammer1/OpenRGB/-/issues/3675) 
([corruption-related 
issue](https://gitlab.com/CalcProgrammer1/OpenRGB/-/merge_requests/2103))



One benefit not listed is that with r-b it is possible to say "version 
1.2.3 has hash abcdef" and you can provide a signature of the file, 
without uploading the file itself. With content-addressable storage such 
as IPFS, you can then also link to such an artifact and anyone else can 
provide the correct file.


e.g. in
http://bafybeiezodttpdsrhy7gj7zuzklbs3exh42a4ezorsepnn74ar2gkicujy.ipfs.cf-ipfs.com/
if we had reproducible ISOs, I could build and sign them in a 
low-bandwidth place but build+upload from another.




Ciao
Bernhard M.


OpenPGP_signature.asc
Description: OpenPGP digital signature

[Evergreen-general] Serials question: why would receiving an issuance fail?

[Mary Llewellyn via Evergreen-general]

I've deleted the issuances, I've set up a new caption and pattern and
predicted new issuances, but even the new issuances fail to be received.
It's only one library having the problem. Other libraries on the same bib
with their own caption and pattern have their issuances succeed at being
received.

I feel like there's some conflict in a serial table somewhere that is
preventing the issuances being received, but I can't find it. How do I find
it and fix it?

Thanks in advance.

Mary


-- 
Mary Llewellyn
Database Manager
Bibliomation, Inc.
24 Wooster Ave.
Waterbury, CT 06708
mllew...@biblio.org
_______
Evergreen-general mailing list
Evergreen-general@list.evergreen-ils.org
http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general

[Evergreen-general] next meeting of the Evergreen Project board

[Katie Greenleaf Martin via Evergreen-general]

Hello all,

 The Evergreen Project Board will be meeting Thursday, February 15th 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-02-15#minutes
 This meeting is public and community members are encouraged to attend.
 Thanks!
Katie
TEP Secretary



[cid:image001.png@01DA5DA8.4549BC00]Katie Greenleaf Martin (she/her), Executive 
Director
Pennsylvania Integrated Library System (PaILS) | SPARK
(717) 873-9461 | k...@sparkpa.org<mailto:k...@sparkpa.org>
support.sparkpa.org<https://support.sparkpa.org/> | 
supp...@sparkpa.org<mailto: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] Evergreen Cataloging Interest Group – Today at 2pm (ET)

[Jennifer Weston via Evergreen-general]

*Cataloging Interest Group Today*

The Evergreen Cataloging Interest Group will meet today -- *Tuesday,
February 13, 2024, at 2pm (ET)*.



Everyone is welcome – please join us! The meeting will be recorded for any
interested parties who cannot attend.



*Evergreen Cataloging Interest Group*

*Tuesday, February 13, 2024*

*2:00pm ET*



Agenda Link: https://bit.ly/3uvSK7q



Zoom Meeting Link:

https://us06web.zoom.us/j/89440379465?pwd=TVY4anVHZmN6ZlZQRXVTM3o5eUUyZz09



Meeting ID: 894 4037 9465

Passcode: 086021

Want to dial into the call using your phone? Find your local number:
https://us06web.zoom.us/u/kcsI1s3S9P



*Topic:** Community Updates and Discussion*

This is a general open discussion to catch up on community activities and
plan for the Cat IG meetings for 2024. There is no formal program this
month so there will be plenty of time to review any launchpad bugs that
need discussing and topics you would like to see the group focus on this
year.



We hope to see you there!

Jennifer Weston,

on behalf of the Cataloging IG Organizing Committee



-

The Cataloging Interest Group usually meets on the second Tuesday of each
month. Everyone is welcome. Meetings are recorded and made available to the
community. For more information, please visit the Cat IG wiki at:
https://wiki.evergreen-ils.org/doku.php?id=cataloging:cwg

-



---

Jennifer Weston, MLIS

Product and Education Manager

Assistant Operations Manager

Equinox Open Library Initiative

jennifer.wes...@equinoxoli.org 
*www.equinoxOLI.org <http://www.equinoxOLI.org>*

877-OPEN-ILS (673-6457)

direct: 770-709-5574
___
Evergreen-general mailing list
Evergreen-general@list.evergreen-ils.org
http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general

Does this list accept html posts?

[Bug reports for and general discussion about GNU Backgammon.]

Yesterday I posted about the Temperature Map, but it doesn't seem to have 
appeared on the mailing list.

Is this because the message for formatted as html and included screen shots and 
text highlighting?

Should I only post plain text?


  *   Ian

Re: [Slony1-general] Nodes awaiting actions

[SAS via Slony1-general]

Le 17/01/2024 à 10:47, Andy Dossett via Slony1-general a écrit :

Hi

How do I determine from the master node tables which slave nodes are yet to 
process the data on the sl_log tables?


Thanks

Andy

___
Slony1-general mailing list
Slony1-general@lists.slony.info
https://lists.slony.info/cgi-bin/mailman/listinfo/slony1-general


Hello,

You may have a look at sl_status view, sl_subscribe will tell you which nodes 
are subscriber on which set.


Best,

--
Dr Stéphane Schildknecht
Contact régional PostgreSQL pour l'Europe francophone
+33 617 11 37 42
___
Slony1-general mailing list
Slony1-general@lists.slony.info
https://lists.slony.info/cgi-bin/mailman/listinfo/slony1-general

[Evergreen-general] Invitation to apply to participate in the virtual Evergreen Project Strategic Plan Stakeholder Retreat

[Frasur, Ruth via Evergreen-general]

Dear Community Members,
The Evergreen Project Board has been in the process of gathering information to 
help formulate a strategic plan for The Evergreen Project, a 501(c)3 
organization established to support the Evergreen open-source ILS and its 
community of practitioners.  Feedback has been solicited from that community of 
practitioners through a variety of activities and meetings.  On February 22 and 
23, the Strategic Plan Subcommittee of the Evergreen Project Board will host a 
virtual Stakeholder Retreat facilitated by Carson Block Consulting, Inc. to 
review and compile the gathered data.  The outcome of the retreat will be a 
strategic plan to ensure the sustainability of The Evergreen Project as an 
organization and provide a path of support for the Evergreen open-source ILS.
The Evergreen Project Strategic Plan Subcommittee invites interested 
individuals to apply to fill a limited number of seats for this and will select 
from the pool of applicants at the regularly scheduled TEP Board meeting at 
2:00 p.m. ET, Thursday, February 15.  If you are interested in participating in 
the virtual retreat, please fill out this 
application<https://forms.gle/eRwYt2q5AKTJhiEG9>.  You will be notified of your 
status following the TEP Board meeting.
Strategic Plan Subcommittee members are:

  *   Ruth Frasur Davis
  *   Jeanette Lundgren
  *   Kathy Lussier
  *   Katie Greenleaf Martin
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] 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

Display bug in Analyse, Clear Analysis, Move

[Bug reports for and general discussion about GNU Backgammon.]

The menu item for Display bug in Analyse, Clear Analysis, Move displays:

"noun|Move"

Instead of just "Move"

This appears in en_US.po, which I assume is the cause.


#: gtkgame.c:4028 gtkgame.c:4039 gtkmovelist.c:63 gtkrolls.c:198 html.c:2161


6382

#: sound.c:351

6383

msgid "noun|Move"

6384

msgstr

RE: GNUbg version 1.08.001 available

[Bug reports for and general discussion about GNU Backgammon.]

I installed the latest version, and all my settings appear intact. At least, 
the board colours and number of threads are as I remember them. 

I've tried on 2 PCs and both are OK. 

I still have the problem on my desktop where I have to move a dialog window a 
few mm before I can click a second option. The laptop is OK.

The Windows build is the same, but they are different gen processors.
Desktop: Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz   2.90 GHzWindows 
10 Pro 22H2 OS Build 19045.3930 Windows Feature Experience Pack 
1000.19053.1000.0
Laptop: 12th Gen Intel(R) Core(TM) i7-1265U   1.80 GHz  Windows 
10 Pro 22H2 OS Build 19045.3930 Windows Feature Experience Pack 
1000.19053.1000.0

-- Ian 


-Original Message-
From: bug-gnubg-bounces+ian.shaw=riverauto.co...@gnu.org 
 On Behalf Of Isaac Keslassy
Sent: Sunday, February 11, 2024 7:13 AM
To: bug-gnubg@gnu.org
Subject: Re: GNUbg version 1.08.001 available

1) SAVING SETTINGS: I have also had the problem of gnubg 1.08 not saving 
settings, or rather, reporting that it is saving them but not loading them. 
Reinstalling gnubg doesn't help. It only worked for me once I selected to 
remove all of my preferences during the installation process (you need to make 
sacrifices to help debug!). I noticed in the faulty installation that I had 
both a ".gnubgautorc" and a "gnubgautorc" file in my preferences folder. This 
may be the reason: it may save in one file and read from the other. I tried to 
correct the error in gnubg.c, but cannot do it due to the 2nd problem below:

2) WINDOWS COMPILATION: I cannot compile and run gnubg 1.08 on Windows using 
MSYS2. Once compiled, gnubg cannot open any of its needed files (MET, weights, 
textures, etc). Jon kindly helped and encountered the same issue on his 
computer. He mentioned it could be an issue with g_fopen. Any idea anyone?



On 10-Feb-24 11:56 PM, Murat K wrote:
> On 2/9/2024 10:59 PM, Murat K wrote:
> 
>> It replaced my gnubgautorc with a default file. I installed it on 
>> another computer to make sure. It did the same thing. Is this 
>> intentional? What is the fix to use my previous settings??
> 
> I had never installed 1_08_dev-20240103. I tried it and it does the 
> same thing. Interesting that nobody else noticed or complained about 
> this. I went back to 1_08_dev-20230709 and all is fine. I guess I'll 
> just have to do without the latest and greatest improvements... ;)
> 
> MK
> 
> External e-mail, be judicious when opening attachments or links

Coreutilities

[Chuck Percy via GNU coreutils General Discussion]

Hi,
I used the “copy” button on your formulae.brew.sh page for coreutils, got the 
confirmation check mark that it was copied and then pasted it into terminal and 
hit return and got this response:

cpercy@MacBook-Pro-4 ~ % brew install coreutils
zsh: command not found: brew
cpercy@MacBook-Pro-4 ~ % 

I am a total noob working with terminal and am following a tutorial to set up a 
few things.
Things have gone flawlessly, including the install of Homebrew, until the 
install of coreutils.

From the response I got “command not found” I assume it was not installed?

Again, I am a noob at terminal etc. any detailed guidance to get this installed 
would be greatly appreciated

Thanks,
Chuck

[Evergreen-general] Using Patron Point's Verify System

[Frasur, Ruth via Evergreen-general]

Have any of you implemented Patron Point's Verify system for updating patron 
accounts/registering patrons?


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] 2024 Pre & Conference Schedule Announced

[Gina Monti via Evergreen-general]

Thank you for everyone's patience!  We are proud to announce the full
schedule for the 2024 Evergreen International Online Conference and
Preconference.  Click here to view the website.
<https://evergreen-ils.org/conference/2024-evergreen-international-online-conference/2024-conference-schedule/>
Program descriptions will be added within the week so please check back
later for that info!

We had so many volunteer for presentations and we appreciate everyone who
has submitted their proposals. Please note that outside of the Circulation
and Consortial Leaders Interest Groups, all other interest groups will be
meeting at Hackfest held on Thursday, April 25, which is a free event.
Hackfest information will be posted soon.

This is also a reminder that the regular conference early bird special at
$60 will end March 1 and full rate will apply afterwards.  You can click
here to register for the event.
<https://site.pheedloop.com/event/evergreenconference2024/home/>

Pre-conference registration is also available starting today!  We are
offering two rates for the pre-conference this year: $30 for one session
and $55 for a day pass.  When registering in Pheedloop, you will find
purchasing options when completing the ticket form.  Click here to access
our pre-conference portal and register.
<https://site.pheedloop.com/event/2024egpreconference/home/>

Please message me off-list if you have additional questions!

-- 
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

Re: [Evergreen-general] Evergreen Issues

[Kate Coleman via Evergreen-general]

Sorry, been away from my desk. About a half an hour ago, I got this update:

"we've made a couple backend changes to your database that should help; if
staff have been holding off on editing records they should be able to start
back up without too much trouble. There are a couple other backend things
we'll be looking into and will be keeping an eye on things for a while."




On Thu, Feb 8, 2024 at 12:51 PM Kate Coleman  wrote:

> The latest update from my helpdesk ticket with Equinox:
>
> "It looks like something is causing bib edits to wait on each other for
> some reason and that's leading to timeouts. We don't have a fix yet but
> have staff looking into the problem in more depth."
>
>
>
>
> On Thu, Feb 8, 2024 at 11:19 AM Consortium Cataloger <
> catalo...@moevergreenlibraries.org> wrote:
>
>> I just tried to import and I cannot import any records. --Liz
>>
>>
>>
>>
>> On Thu, Feb 8, 2024 at 11:17 AM Kate Coleman 
>> wrote:
>>
>>> We are unable to save or merge records. Are there any other issues
>>> people are having?
>>>
>>>
>>>
_______
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 Issues

[Kate Coleman via Evergreen-general]

The latest update from my helpdesk ticket with Equinox:

"It looks like something is causing bib edits to wait on each other for
some reason and that's leading to timeouts. We don't have a fix yet but
have staff looking into the problem in more depth."




On Thu, Feb 8, 2024 at 11:19 AM Consortium Cataloger <
catalo...@moevergreenlibraries.org> wrote:

> I just tried to import and I cannot import any records. --Liz
>
>
>
>
> On Thu, Feb 8, 2024 at 11:17 AM Kate Coleman 
> wrote:
>
>> We are unable to save or merge records. Are there any other issues people
>> are having?
>>
>>
>>
_______
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 Issues

[Kate Coleman via Evergreen-general]

Apologies for sending this to the incorrect listserv!




On Thu, Feb 8, 2024 at 11:17 AM Kate Coleman  wrote:

> We are unable to save or merge records. Are there any other issues people
> are having?
>
>
>
___
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 Issues

[Kate Coleman via Evergreen-general]

I've asked my district if there's any circ problems I don't know about then
I was going to put in a ticket.




On Thu, Feb 8, 2024 at 11:19 AM Consortium Cataloger <
catalo...@moevergreenlibraries.org> wrote:

> I just tried to import and I cannot import any records. --Liz
>
>
>
>
> On Thu, Feb 8, 2024 at 11:17 AM Kate Coleman 
> wrote:
>
>> We are unable to save or merge records. Are there any other issues people
>> are having?
>>
>>
>>
_______
Evergreen-general mailing list
Evergreen-general@list.evergreen-ils.org
http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general

[Evergreen-general] Evergreen Issues

[Kate Coleman via Evergreen-general]

We are unable to save or merge records. Are there any other issues people
are having?
___
Evergreen-general mailing list
Evergreen-general@list.evergreen-ils.org
http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general

RE: Interesting question/experiment about value of cube ownership

[Bug reports for and general discussion about GNU Backgammon.]

It just so happens that I rolled out the opening position a few days ago for 
another reason. This was at 7-away 7-away rather than $ play, because I was 
interested in match play. I doubt that makes a huge difference.



This was using gnubg-1_08_dev-20240103-setup.exe not the newest 
gnubg-1_08_001-20240204-setup.exe that Philippe released recently.



Philippe, am I correct in thinking that the cube handling on these two versions 
is the same? Your announcement emails both include the same comment.


“Improvement to cube decisions at 0- and 1-ply and weaker levels. Cube error 
rates are approximately halved and the repartition of errors (premature doubles 
vs. missed doubles vs. take or pass errors) is now similar to higher plies 
instead of being mostly premature doubles.”



The rollout results indicate about 1% fewer wins for the roller than the 
evaluations.



4HPwATDgc/ABMA:cAngAAAE



Cube analysis

Rollout cubeless equity +0.0408 (Money: +0.0396)



Cubeful equities:

1. No double   +0.0655

2. Double, pass+1.  (+0.9345)

3. Double, take-0.2999  (-0.3654)

Proper cube action: No double, take (28.1%)



Rollout details:

Centered 1-cube:

  0.5129 0.1480 0.0083 - 0.4871 0.1351 0.0073 CL +0.0408 CF +0.0655

[0.0001 0.0002 0.0001 - 0.0001 0.0001 0.0001 CL  0.0003 CF  0.0008]

gnubg owns 2-cube:

  0.5156 0.1522 0.0091 - 0.4844 0.1375 0.0150 CL +0.1216 CF -0.2999

[0.0001 0.0002 0.0001 - 0.0001 0.0002 0.0002 CL  0.0007 CF  0.0012]

Full cubeful rollout with variance reduction

186624 games, rollout as initial position, Mersenne Twister dice generator with 
seed 823069761

Play: world class 2-ply cubeful prune [world class]

keep the first 0 0-ply moves and up to 8 more moves within equity 0.16

Skip pruning for 1-ply moves.

Cube: 2-ply cubeful prune [world class]



Cheers,

Ian



-Original Message-
From: bug-gnubg-bounces+ian.shaw=riverauto.co...@gnu.org 
 On Behalf Of MK
Sent: Thursday, February 8, 2024 2:23 AM
To: bug-gnubg@gnu.org
Subject: Interesting question/experiment about value of cube ownership



I'm chugging along with my mutant cube skill experiments as I can spare time, 
saving all games, which I will share on my web site, when I'm done, along with 
my scripts.



While doing the double at > 50% experiment, I remembered an old question I had 
asked in RGB about a year ago: What if the winner of the opening roll is 
allowed pre-double?



See thread:

https://groups.google.com/g/rec.games.backgammon/c/BVEnaqGM6dg/m/2c685q4DAAAJ



When you evaluate the opening position in GnuBG, this is what you get:



=

Position ID: 4HPwATDgc/ABMA

Match ID:cAkA



Evaluator:Contact

 Win W(g)W(bg)   L(g)L(bg)   EquityCubeful

static:  52.115.4 0.813.0 0.8   +0.067+0.084

  1 ply:  52.714.8 0.912.9 0.5   +0.076+0.098

  2 ply:  52.514.9 0.712.5 0.5   +0.076+0.099



Cube analysis

2-ply cubeless equity +0.076

52.5  14.9   0.7 -  47.5  12.5   0.5

Cubeful equities:

1. No double   +0.099

2. Double, pass+1.000  (+0.901)

3. Double, take-0.171  (-0.270)

Proper cube action: No double, take (23.0%) 
=



I have created a Python script to intervene if the human player wins the 
opening roll, to set the cube at 2 owned by the bot, and then to execute "end 
game" command, for the bot to play for both sides at the same checker and cube 
skill settings.



So, you know the equity gained by winning the opening roll and the equity lost 
by making the cube error at the same time, before the first move. Can anyone 
tell me what I will be expecting to see after, let's say,

10,000 games, in terms of which side will win/lose by what percentage?



BTW: I already know. ;) I'm asking to see how confident are you in GnuBG's 
equity and/or error calculations and how competent are you to make mathematical 
predictions?



MK

Re: vm, emacs 28.2 (debian), urls in minibuffer

[Stefan Monnier via General discussion of VM mail reader]

> This is a great start!  I will apply this to my local tree and see how
> it works.

I'd be surprised if it works well enough as-is.  But feel free to ask me
about problems you encounter (or about compiler warnings you don't know
how to address).

> So which versions of Emacs have you tested this on?

None: guaranteed 100% untested.

> I'll be testing on Emacs 28.2, and it looks like you use XEmacs,

I used to be maintainer of Emacs, so no, not XEmacs.

> just judging from the changes you made in this patch.  

The changes about (featurep 'xemacs) are made because the compiler knows
that (featurep 'xemacs) returns nil and can thus optimize things away,
whereas if you test a variable (such as `vm-xemacs-p`) the compiler
doesn't notice that this var will always be nil.


Stefan

Re: [Evergreen-general] Indexing =400 Authority MARC Fields in Author and Subject Searches

[Rosie Le Faive via Evergreen-general]

Hello,

We've recently begun asking those very same questions, and I am interested in 
hearing what others have to say.

For replacing problematic headings, I think we will need to keep a list of the 
problematic authority records to prevent them from re-entering our system 
during authority record loads. We will probably track both the (LCSH) IDs as 
well as the heading, so that we can be alerted if the problematic record has 
changed (for instance, to something less problematic, so we could go back to 
using it). Since we aren't (yet?) using an authority vendor, this'll likely be 
done in custom python scripts... but all this is still hypothetical!

I'm eager to hear if/how we can improve the Author and Subject searches by 
indexing non-preferred headings.
____
From: Evergreen-general  on 
behalf of Szwagiel, Will via Evergreen-general 

Sent: Tuesday, February 6, 2024 10:05 AM
To: evergreen-general@list.evergreen-ils.org 

Cc: Szwagiel, Will 
Subject: [Evergreen-general] Indexing =400 Authority MARC Fields in Author and 
Subject Searches


CAUTION: This email originated from outside of UPEI. Do not click links or open 
attachments unless you recognize the sender and know the content is safe. If 
you are uncertain, please forward to phish...@upei.ca and delete this email.

Good morning,

We have been discussing ways to try and make authority records more useful in 
Evergreen for staff and patrons when searching the catalog.  As it currently 
stands, if you select Author as the Catalog Field in a search and search for a 
version of an author's name that appears in a =400 field in the authority 
record, you will not receive any results.  However, if you search for that same 
version of the author's name with Keyword selected as the Catalog Field, you 
will receive results.

One potential solution that has been suggested is to index the =400 fields in 
the Author search.

This led to a broader discussion regarding a project we are currently 
undertaking to introduce less problematic or offensive local subject headings 
into our MARC records.  Basically we are planning to put together a list of 
terms that we feel are outdated or problematic and then come up with a separate 
list of terms with which to replace them.  Instead of simply adding our local 
subject headings to the records and leaving the problematic ones present as is, 
we intend to replace the problematic ones with the new terms.

This returned to the discussion of how best to handle authority records.  The 
thinking is that we would add these new terms to the existing authority records 
(presumably in =400 fields) and potentially index these fields in the Subject 
search, as well, similar to how we discussed potentially doing this with the 
Author search.

Has anyone else done anything like this before?  If so, how has it worked out 
for you?  If you have not had much luck with it, what would you recommend as an 
alternative?

Thank you in advance for any insight you may be able to provide.


William C. Szwagiel

NC Cardinal Project Manager

State Library of North Carolina

william.szwag...@ncdcr.gov<mailto:william.szwag...@ncdcr.gov> | 919.814.6721

https://statelibrary.ncdcr.gov/services-libraries/nc-cardinal

109 East Jones Street  | 4640 Mail Service Center

Raleigh, North Carolina 27699-4600

The State Library is part of the NC Department of Natural & Cultural Resources.

Email correspondence to and from this address is subject to the North Carolina 
Public Records Law and may be disclosed to third parties.





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.
_______
Evergreen-general mailing list
Evergreen-general@list.evergreen-ils.org
http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general

[Evergreen-general] REMINDER: Reports Interest Group Meeting Feburary 7th @ 2 PM Eastern

[Jessica Woolford via Evergreen-general]

Apologies for the late reminder! RIG is meeting at 2 PM EST today. See you
soon!

-- Forwarded message -
From: Jessica Woolford 
Date: Tue, Jan 30, 2024 at 11:52 AM
Subject: Reports Interest Group Meeting Feburary 7th @ 2 PM Eastern
To: Evergreen Discussion Group 


The Reports Interest Group will meet Wednesday, February 7th at 2 PM
Eastern. Please note, this deviates from our regularly scheduled meetings
the last Wednesday of the month.

In this meeting, I will be discussing some tables available in the auditor
schema and how they can be queried to answer some common troubleshooting
questions. This meeting will mostly be geared toward Evergreen support
staff and administrators who have read-only (or higher) access to their
Evergreen database, but end users might also find it useful to learn what
kinds of questions their support providers can assist with using these
tables.

Meeting details, including connection information, can be found here:
https://wiki.evergreen-ils.org/doku.php?id=evergreen-reports:meetings:2024-02-07

Hope to see you there!
Jessica

-- 

Jessica Woolford (she/her)

Director of Member Services

jwoolf...@biblio.org | (203) 577-4070 <203-577-4070>x105

» Help Desk: Open or Check a Ticket <https://helpdesk.biblio.org>

[image: Stylized turquoise book with blue swirl around it, above text
reading Bibliomation: Libraries Sharing Computerized Services]
<https://biblio.org/>


-- 

Jessica Woolford (she/her)

Director of Member Services

jwoolf...@biblio.org | (203) 577-4070 <203-577-4070>x105

» Help Desk: Open or Check a Ticket <https://helpdesk.biblio.org>

[image: Stylized turquoise book with blue swirl around it, above text
reading Bibliomation: Libraries Sharing Computerized Services]
<https://biblio.org/>
_______
Evergreen-general mailing list
Evergreen-general@list.evergreen-ils.org
http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general

Re: [Pdl-general] [Pdl-devel] naming conventions

[Ingo Schmid via pdl-general]

Hi,

I guess this is a NiceSlice thing, this one works in the pdl shell:

$f=sub{$_[0]**2};

...

Ingo

On 07.02.24 01:14, Luis Mochan wrote:

On Tue, Jan 30, 2024 at 09:40:59PM -0600, Luis Mochan wrote:

...>
On Mon, Jan 29, 2024 at 10:19:56PM -0500, David Mertens wrote:

Hello Luis,

Ever crafty, Perl gives you another way to solve this. You could put your
functions under another name space and invoke them by explicitly naming the
package and function. For example, if you have a function "do_it" in
package MY, you could invoke it as

$pdl->MY::do_it(...args...)


Found another alternative, as in:
 my $f=sub($x){$x**2}; #or $f=sub{$_[0]**2};
 print sequence(10)->$f;
Curiously, it works in general but not the sub($x){...} in the pdl REPL.





_______
pdl-general mailing list
pdl-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pdl-general

Re: [Evergreen-general] SlimPAC Removal Discussion

[Chris Sharp via Evergreen-general]

Having heard no objections (or, really, anything at all), I will continue
with developing a branch that removes SlimPAC.  Thanks!

On Fri, Jan 26, 2024 at 3:31 PM Chris Sharp 
wrote:

> Hi all,
>
> Today I opened a bug (https://bugs.launchpad.net/evergreen/+bug/2051382)
> to remove the SlimPAC code.  This is an interface that was developed
> alongside the original Evergreen OPAC to accommodate users whose browsers
> didn't support JavaScript or for users with accessibility needs.  It has
> not been updated in many years.  I have proposed removing this legacy code,
> but I want to open the floor (or the list, I guess) for discussion if
> others have been using it.  Please speak up before next Friday, February 2,
> if you have opinions you'd like to be considered before we remove it.
>
> Thank you!
>
> Chris
>
> --
>
> [image: logo with link to Georgia Public Library Service website]
> <https://georgialibraries.org/>
>
> Chris Sharp, PINES System Administrator
>
> --
>
> Georgia Public Library Service
>
> 2872 Woodcock Blvd, Suite 250 | Atlanta, GA 30341
>
> (404) 235-7147 | csh...@georgialibraries.org
>
> [image: logo with link to Georgia Public Library Service Facebook page]
> <https://www.facebook.com/georgialibraries>[image: logo with link to
> Georgia Public Library Service Instagram page]
> <https://www.instagram.com/georgialibraries/>[image: logo with link to
> Georgia Public Library Service LinkedIn page]
> <https://www.linkedin.com/company/georgia-public-library-service/>[image:
> logo with link to Georgia Public Library Service Threads page]
> <https://www.threads.net/@georgialibraries>
>
> Join our email list <http://georgialibraries.org/subscription> for
> stories of Georgia libraries making an impact in our communities.
>


-- 

[image: logo with link to Georgia Public Library Service website]
<https://georgialibraries.org/>

Chris Sharp, PINES System Administrator

--

​Georgia Public Library Service

​2872 Woodcock Blvd, Suite 250 | ​Atlanta, GA 30341

(404) 235-7147 | csh...@georgialibraries.org

[image: logo with link to Georgia Public Library Service Facebook page]
<https://www.facebook.com/georgialibraries>[image: logo with link to
Georgia Public Library Service Instagram page]
<https://www.instagram.com/georgialibraries/>[image: logo with link to
Georgia Public Library Service LinkedIn page]
<https://www.linkedin.com/company/georgia-public-library-service/>[image:
logo with link to Georgia Public Library Service Threads page]
<https://www.threads.net/@georgialibraries>

Join our email list <http://georgialibraries.org/subscription> for stories
of Georgia libraries making an impact in our communities.
___
Evergreen-general mailing list
Evergreen-general@list.evergreen-ils.org
http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general

Re: [Evergreen-general] New Core Committer! Congratulations to Blake Graham Henderson

[Tiffany Little via Evergreen-general]

Congrats Blake!!

Tiffany Little, PINES Bibliographic Projects Manager

--

Georgia Public Library Service

2872 Woodcock Blvd, Suite 250 | Atlanta, GA 30341

(404) 235-7161 | tlit...@georgialibraries.org

Join our email list <http://georgialibraries.org/> for stories of Georgia
libraries making an impact in our communities.


On Mon, Feb 5, 2024 at 2:38 PM Frasur, Ruth via Evergreen-general <
evergreen-general@list.evergreen-ils.org> wrote:

> Congratulations to Blake Graham Henderson (bmagic) on being named by the
> Evergreen Developer Group as the most recent Core Committee for the
> open-source Evergreen ILS.  Blake is Senior Development Engineer for MOBIUS
> Consortium.
>
>
>
> 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] Indexing =400 Authority MARC Fields in Author and Subject Searches

[Szwagiel, Will via Evergreen-general]

Good morning,

We have been discussing ways to try and make authority records more useful in 
Evergreen for staff and patrons when searching the catalog.  As it currently 
stands, if you select Author as the Catalog Field in a search and search for a 
version of an author's name that appears in a =400 field in the authority 
record, you will not receive any results.  However, if you search for that same 
version of the author's name with Keyword selected as the Catalog Field, you 
will receive results.

One potential solution that has been suggested is to index the =400 fields in 
the Author search.

This led to a broader discussion regarding a project we are currently 
undertaking to introduce less problematic or offensive local subject headings 
into our MARC records.  Basically we are planning to put together a list of 
terms that we feel are outdated or problematic and then come up with a separate 
list of terms with which to replace them.  Instead of simply adding our local 
subject headings to the records and leaving the problematic ones present as is, 
we intend to replace the problematic ones with the new terms.

This returned to the discussion of how best to handle authority records.  The 
thinking is that we would add these new terms to the existing authority records 
(presumably in =400 fields) and potentially index these fields in the Subject 
search, as well, similar to how we discussed potentially doing this with the 
Author search.

Has anyone else done anything like this before?  If so, how has it worked out 
for you?  If you have not had much luck with it, what would you recommend as an 
alternative?

Thank you in advance for any insight you may be able to provide.


William C. Szwagiel

NC Cardinal Project Manager

State Library of North Carolina

william.szwag...@ncdcr.gov<mailto:william.szwag...@ncdcr.gov> | 919.814.6721

https://statelibrary.ncdcr.gov/services-libraries/nc-cardinal

109 East Jones Street  | 4640 Mail Service Center

Raleigh, North Carolina 27699-4600

The State Library is part of the NC Department of Natural & Cultural Resources.

Email correspondence to and from this address is subject to the North Carolina 
Public Records Law and may be disclosed to third parties.





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.
_______
Evergreen-general mailing list
Evergreen-general@list.evergreen-ils.org
http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general

[Evergreen-general] New Core Committer! Congratulations to Blake Graham Henderson

[Frasur, Ruth via Evergreen-general]

Congratulations to Blake Graham Henderson (bmagic) on being named by the 
Evergreen Developer Group as the most recent Core Committee for the open-source 
Evergreen ILS.  Blake is Senior Development Engineer for MOBIUS Consortium.

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] Evergreen 3.11.3 & 3.12.1 Released

[Frasur, Ruth via Evergreen-general]

The Evergreen development team is pleased to announce the release of Evergreen 
3.11.3 and 3.12.1.

Both releases contain several bug fixes over their prior versions.  Please read 
the linked release notes for more details.

  *   Release Notes - 
3.11.3<https://evergreen-ils.org/documentation/release/RELEASE_NOTES_3_11.html#_evergreen_3_11_3>
  *   Release Notes - 
3.12.1<https://evergreen-ils.org/documentation/release/RELEASE_NOTES_3_12.html#_evergreen_3_12_1>

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

Re: problems with templates and ID in properties

[General discussions about Org-mode.]

> Thanks for you answer


> So that cannot be changed, do I understand correctly.



> Thanks for trying it out, I suspect it is then my setting, I just looked
> up the org-mode-hook

> And I can't find any suspicious. I will try to eyeball my org-add-ons
> files.

> What command/variable could org-mode force to have always an UUID in the
> ID property?

> I also will try to debug org-capture and org-capture-finalize
> I tried it once and cannot see when the UUID is automatically inserted.

Ok, I debugged it again, the function org-caputre-finalize adds the
property with the UUID more specifically the line

(run-hooks 'org-capture-prepare-finalize-hook)

Hm I will investigate this further 

> hm

-- 
I strongly condemn Hamas heinous despicable pogroms/atrocities on Israel
I strongly condemn Putin's war of aggression against Ukraine.
I support to deliver weapons to Ukraine's military. 
I support the EU and NATO membership of Ukraine. 



smime.p7s
Description: S/MIME cryptographic signature

Re: problems with templates and ID in properties

[General discussions about Org-mode.]

> Uwe Brauer  writes:

Thanks for you answer
> This is expected. As per `org-capture-templates' docstring, "entry"
> capture type inserts top-level entries into files:

>entry   an Org node, with a headline.  Will be filed
>as the child of the target entry or as a
>top-level entry.  Its default template is:
>  "* %?

So that cannot be changed, do I understand correctly.


> I am unable to reproduce this problem.
> May you please simplify the example, so that it can be reproduced
> starting from emacs -Q?

Thanks for trying it out, I suspect it is then my setting, I just looked
up the org-mode-hook

And I can't find any suspicious. I will try to eyeball my org-add-ons
files.

What command/variable could org-mode force to have always an UUID in the
ID property?

I also will try to debug org-capture and org-capture-finalize
I tried it once and cannot see when the UUID is automatically inserted.

hm


-- 
I strongly condemn Hamas heinous despicable pogroms/atrocities on Israel
I strongly condemn Putin's war of aggression against Ukraine.
I support to deliver weapons to Ukraine's military. 
I support the EU and NATO membership of Ukraine. 



smime.p7s
Description: S/MIME cryptographic signature

[Evergreen-general] Documentation Interest Group (DIG) Meeting Today!

[Deborah Luchenbill via Evergreen-general]

I'm sorry for the late reminder--DIG is meeting today, February 1, at 11
a.m. PDT / 2 p.m. EST on Zoom.

The agenda (including connection info) is here:
https://wiki.evergreen-ils.org/doku.php?id=evergreen-docs:dig_meetings:20240201-agenda

If you have anything else to add or edit, feel free to do so directly, or
let me know. Please include your name in parentheses to any agenda items
you add.

You can find minutes from our previous meetings (except the ones I haven't
gotten to yet) at https://wiki.evergreen-ils.org/doku.php?id=evergreen-docs
:dig_meetings

Best,
Debbie
DIG Facilitator


Debbie Luchenbill
Associate Director, Open Source Initiatives
MOBIUS
2511 Broadway Bluffs, Ste. 101
Columbia, MO  65201
deb...@mobiusconsortium.org 
573-234-4914
https://mobiusconsortium.org <http://mobiusconsortium.org>
MOSS Help Desk: h...@mobiusconsortium.org / 877-312-3517
Pronouns: She/Her or She/They (see https://pronouns.org/ to learn more)
Input | Maximizer | Intellection | Relator | Adaptability
___
Evergreen-general mailing list
Evergreen-general@list.evergreen-ils.org
http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general

[Evergreen-general] Circulation Coordinator position opening

[Diane Disbro via Evergreen-general]

Good morning -

Scenic Regional Library, headquartered in Union, MO, is looking for a
Circulation Coordinator to fill the position when I retire in April. I have
worked for Scenic eighteen years, evidence that it is a good place to be!
Administrative staff members are energetic and forward thinking. We are one
of seventy-six libraries in the state that belong to the Missouri Evergreen
Consortium. We joined in 2014, two years after the consortium's founding.
MEC is a resource sharing consortium. Our patrons have access to over five
million items.

The Union/Washington area has all the services (including shops and
restaurants) you need and we are forty-five minutes from St. Louis and all
it has to offer. The job posting can be found here.
https://scenicregional.org/about-us/employment/

Scenic Regional Library website   https://scenicregional.org/
Missouri Evergreen Consortium website   http://moevergreenlibraries.org/

Regards,
Diane Disbro
Pronouns: she/her
Circulation Coordinator
Scenic Regional Library
251 Union Plaza Drive
Union, MO 63084
(636) 583-0652 ext  110
ddis...@scenicregional.or 
___
Evergreen-general mailing list
Evergreen-general@list.evergreen-ils.org
http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general

Re: vm, emacs 28.2 (debian), urls in minibuffer

[Stefan Monnier via General discussion of VM mail reader]

> If I had any skill in (e)lisp I'd see what I could do, but I'm
> terrible at lisp and have never learned enough to do anything useful.
> I'm in IT, not software.

Maybe the first thing to do would be to move it from Bazaar to Git,
maybe over on Codeberg.


Stefan

[Evergreen-general] Reports Interest Group Meeting Feburary 7th @ 2 PM Eastern

[Jessica Woolford via Evergreen-general]

The Reports Interest Group will meet Wednesday, February 7th at 2 PM
Eastern. Please note, this deviates from our regularly scheduled meetings
the last Wednesday of the month.

In this meeting, I will be discussing some tables available in the auditor
schema and how they can be queried to answer some common troubleshooting
questions. This meeting will mostly be geared toward Evergreen support
staff and administrators who have read-only (or higher) access to their
Evergreen database, but end users might also find it useful to learn what
kinds of questions their support providers can assist with using these
tables.

Meeting details, including connection information, can be found here:
https://wiki.evergreen-ils.org/doku.php?id=evergreen-reports:meetings:2024-02-07

Hope to see you there!
Jessica

-- 

Jessica Woolford (she/her)

Director of Member Services

jwoolf...@biblio.org | (203) 577-4070 <203-577-4070>x105

» Help Desk: Open or Check a Ticket <https://helpdesk.biblio.org>

[image: Stylized turquoise book with blue swirl around it, above text
reading Bibliomation: Libraries Sharing Computerized Services]
<https://biblio.org/>
___
Evergreen-general mailing list
Evergreen-general@list.evergreen-ils.org
http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general

[Pdl-general] RESEND: Change in xvals/yvals/zvals behavior

[Diab Jerius via pdl-general]

[Apologies, the last email was sent from the wrong email address. PLEASE 
disregard]


Hey folks,

I’d like to submit some sort of fix to the change in behavior I’ve noted 
at the bottom of this issue,


https://github.com/PDLPorters/pdl/issues/330

namely that [xyz]vals return a double regardless if a smaller type has 
been requested. Here’s the symptom:


   perl -MPDL -E 'say xvals(short,2)->info'
   PDL: Double D [2]


We’re in the midst of an upgrade to modern PDL, and this is biting us 
(for a couple of reasons listed in the github issue).


I need to solve this quickly, but I’m not sure of the original aim of 
that issue.


Was it that the default should be a double if no type is specified? I 
think that makes the most sense.


Any opinions?

Thanks,
Diab

(I’ve been away from IRC for the last few months, and my irc bouncer is 
disconnected ATM, so apologies if I don’t respond there.)
_______
pdl-general mailing list
pdl-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pdl-general

[Evergreen-general] SlimPAC Removal Discussion

[Chris Sharp via Evergreen-general]

Hi all,

Today I opened a bug (https://bugs.launchpad.net/evergreen/+bug/2051382) to
remove the SlimPAC code.  This is an interface that was developed alongside
the original Evergreen OPAC to accommodate users whose browsers didn't
support JavaScript or for users with accessibility needs.  It has not been
updated in many years.  I have proposed removing this legacy code, but I
want to open the floor (or the list, I guess) for discussion if others have
been using it.  Please speak up before next Friday, February 2, if you have
opinions you'd like to be considered before we remove it.

Thank you!

Chris

-- 

[image: logo with link to Georgia Public Library Service website]
<https://georgialibraries.org/>

Chris Sharp, PINES System Administrator

--

Georgia Public Library Service

2872 Woodcock Blvd, Suite 250 | Atlanta, GA 30341

(404) 235-7147 | csh...@georgialibraries.org

[image: logo with link to Georgia Public Library Service Facebook page]
<https://www.facebook.com/georgialibraries>[image: logo with link to
Georgia Public Library Service Instagram page]
<https://www.instagram.com/georgialibraries/>[image: logo with link to
Georgia Public Library Service LinkedIn page]
<https://www.linkedin.com/company/georgia-public-library-service/>[image:
logo with link to Georgia Public Library Service Threads page]
<https://www.threads.net/@georgialibraries>

Join our email list <http://georgialibraries.org/subscription> for stories
of Georgia libraries making an impact in our communities.
___
Evergreen-general mailing list
Evergreen-general@list.evergreen-ils.org
http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general

Re: [Evergreen-general] Chromebox for computer labs?

[Miller, Jeremy via Evergreen-general]

We’ve been using Groovix for all of that for about 15 years.
(We don’t have reservations, but it is there if we wanted to.)
Most of that time we’ve run it on tiny micro-PCs of one kind or another.  (Asus 
EEEBox, Optiplex Micro, Zotac ZBox, etc)
Been very happy with it… probably the best customer support of any vendor we’ve 
had for anything.

Incidentally, I have it installed on a Chromebox (connected to a touchscreen 
and Jamex money collection machine) in a particular mode as a print release 
station.  So I suppose we do have exactly one Chromebox here, albeit for a very 
niche use, in an atypical configuration.  (Installing something other than 
Chrome on a Chromebox does require a bit of hoop jumping.)

We have discussed perhaps going with Chromebooks (and associated management 
tools) if we were to provide laptops for take-home checkouts.  But not to 
replace our on-site public workstations and laptops.


Jeremy Miller

Albany Public Library

City of Albany, Oregon


From: Evergreen-general  On 
Behalf Of Anne Savoie via Evergreen-general
Sent: Friday, January 26, 2024 10:39 AM
To: Evergreen Discussion Group 
Cc: Anne Savoie 
Subject: Re: [Evergreen-general] Chromebox for computer labs?


[WARNING!  This email came from outside our organization. Do NOT click unknown 
attachments or links in email.]
Hi Kevin,

In some of our libraries they utilize Google Workspace to manage their 
Chromebook/Chromebox devices and we use the Envisionware CloudNine Reservation 
service for managing use.  We use the Envisionware LPTOne MobilePrint product 
for print management.

Thanks,
Anne

[Image removed by sender.]

Anne Savoie (she/her/hers)
Systems/Networking Manager, C/W MARS, Inc.



[Image removed by sender. icon]asav...@cwmars.org<mailto:asav...@cwmars.org> | 
[Image removed by sender. icon] 
www.cwmars.org<https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fwww.cwmars.org%2f&c=E,1,hE7nGdqJ3IxK4mDqBaVvjrrsQWxsIf4cwgoe43y7tT00gQsfqZ9AUOsYDOFh-yP8cPcyilGrfAmYIuKVav6_t1nWzOoUUwm4aPI1CmhKpS8,&typo=1>

[Image removed by sender. icon]508-755-3323 x EXT 2


On Thu, Jan 25, 2024 at 7:59 PM Kevin Co via Evergreen-general 
mailto:evergreen-general@list.evergreen-ils.org>>
 wrote:
Greetings from Alaska!

General library tech question: Anyone out there have any experience using 
chromebox machines in their public computer labs? What are folks using for 
printing and session management?

We’re using PC’s + Cassie + Deepfreeze, but looking out for wisdom and future 
solutions.

Thanks all,

-Kevin, Homer Public Library
___
Evergreen-general mailing list
Evergreen-general@list.evergreen-ils.org<mailto:Evergreen-general@list.evergreen-ils.org>
http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general<https://linkprotect.cudasvc.com/url?a=http%3a%2f%2flist.evergreen-ils.org%2fcgi-bin%2fmailman%2flistinfo%2fevergreen-general&c=E,1,cwxx03jJw7n34vgIx3u7iyAVYuIXerXzD97NKBH4_W5tjTED7zxQhww2nq03v7qB1bsLpJt6f-ylyHvFztnDWKJgbZRrkHy7TlrZZhT-k6vFGXE,&typo=1>

__
DISCLAIMER: This email may be considered a public record of the City of Albany 
and subject to the State of Oregon Retention Schedule. This email also may be 
subject to public disclosure under the Oregon Public Records Law. This email, 
including any attachments, is for the sole use of the intended recipient(s) and 
may contain confidential and privileged information. Any unauthorized review, 
use, disclosure or distribution is prohibited. If you have received this 
communication in error, please notify the sender immediately and destroy all 
copies of the original message.
___
Evergreen-general mailing list
Evergreen-general@list.evergreen-ils.org
http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general

Re: [Evergreen-general] Claims Returned Item Status?

[Morgan, Michele via Evergreen-general]

Hi William,

We do something similar to CW MARS. We created a Claimed Returned status
for this situation. There are options to make a status not holdable and not
opac visible, both of which might be useful for this case.

1.Does the circulation remain open (still checked out to the patron)
I'll echo what John said and add that a claimed returned checkout that is
still outstanding can prevent a patron record from being purged.

2.If the circ remains open, where can staff find that information?
Also Items Out > Other/Special Circulations, but that is configurable via
library settings.

3.If staff can see that information, can it be set up so that patrons
can’t see it? If patrons can see it, they will be alarmed that they still
see this checkout, even though it is technically been forgiven.
Our patrons also cannot see their claimed returned items.

4.Staff will need to be able to retrieve that information because we
give each patron one claim returned. There are often repeat offenders with
this.
Visible in Other circulations in the patron record. There is also a claimed
returned counter in the patron record which records current outstanding
claimed returned checkouts.

Hope this helps!
Michele

--
Michele M. Morgan, Systems Support Specialist
North of Boston Library Exchange, Danvers Massachusetts
mmor...@noblenet.org



On Fri, Jan 26, 2024 at 2:33 PM John Amundson via Evergreen-general <
evergreen-general@list.evergreen-ils.org> wrote:

> Hi, William:
>
> CW MARS using a status for this that we call "Claimed Returned".
>
> Some more answers below:
>
> Claims Returned item status:
>
> 1.Does the circulation remain open (still checked out to the patron)
> Yes and No. As far as the patron is concerned, it's returned, but it does
> stay open in the database, and is still accessible from the patron's record
> in the staff client.
>
>
> 2.If the circ remains open, where can staff find that information?
>
> 1.Right now, it appears in Items Out > Other/Special Circulations
>
> This is also where it appears for us.
>
>
> 3.If staff can see that information, can it be set up so that patrons
> can’t see it? If patrons can see it, they will be alarmed that they still
> see this checkout, even though it is technically been forgiven.
>
> Our patrons can't see their currently claimed returned material. Only
> staff can. This may be the default behavior.
>
>
> 4.Staff will need to be able to retrieve that information because we
> give each patron one claim returned. There are often repeat offenders with
> this.
>
> In addition to the transaction still being accessible on the patron's
> record, staff can also run reports directly on the "Claimed Returned"
> status.
>
>
> Hope this is helpful!
>
> John
>
> John Amundson (he/him/his)
> Library Applications Supervisor, C/W MARS, Inc.
>
> ------
>
> [image: icon] jamund...@cwmars.org | [image: icon]www.cwmars.org
>
> [image: icon] 508-755-3323 x1
>
>
> On Fri, Jan 26, 2024 at 2:26 PM Diane Disbro via Evergreen-general <
> evergreen-general@list.evergreen-ils.org> wrote:
>
>> We don't use Claims Returned/Claims Never Checked Out. Patrons see those
>> items in their online account and call to say, "I told you I returned
>> that."
>>
>> After the patron and library have made a thorough search, we will forgive
>> a Claim one time. We mark the item Lost (if it hasn't already gone to
>> bills) then use the payment type Forgive so that we have a record of what
>> happened. The item is now in Lost status so it isn't holdable and will be
>> deleted according to our timeline. If the patron makes another Claim, we
>> gently explain that we have already forgiven one Claim and can't forgive
>> another. The patron needs to pay the bill.
>>
>> Diane Disbro
>> Pronouns: she/her
>> Circulation Coordinator
>> Scenic Regional Library
>> 251 Union Plaza Drive
>> Union, MO 63084
>> (636) 583-0652 ext  110
>> ddis...@scenicregional.or 
>>
>>
>>
>> On Fri, Jan 26, 2024 at 1:15 PM Daniel Guarracino via Evergreen-general <
>> evergreen-general@list.evergreen-ils.org> wrote:
>>
>>> Hi William,
>>>
>>> We are in the process of potentially changing our approach to these
>>> items. Currently, our items marked as Claims Returned have their status set
>>> to Missing. We've done so for at least ten years.
>>>
>>> We've received some feedback recently from some of our libraries that
>>> this can cause confusion because these items are sort of a "special

Re: [Evergreen-general] Chromebox for computer labs?

[Josh Stompro via Evergreen-general]

Hello Kevin, good to hear from you.

We currently use Cassie with our chromebooks that we checkout for in
library use along with Google Workspace management.  We check them out for
the day, so we don't really need the Cassie computer management, but using
it for printing made that part easy.  Printing works the same as our
windows public computers which makes it easier on staff to not have a
different method for them.  Setup was a little tricky because I kept
running into bugs, but Librarica support was able to fix issues as they
came up, or provide work arounds.  They are also pretty good at allowing
test licenses to try things out if you want to get something setup before.

Librarica has a guide to getting Cassie up and running on ChromeOS.  You
setup the cassie app to be force installed for each session in the google
admin.

I have heard of very few problems with this setup.  And upgrading cassie is
way easier for the chromebooks then having to deploy the update to windows
machines locked down with deepfreeze.

We also make use of Papercut Mobility to handle chromeos and public
wireless printing in our small sites that are open less than 10 hours a
week.  That is free, but doesn't give you any sort of release control.  It
just gets the print jobs to the printer and can deal with printers that are
not new enough to have native chromeos support.

There is also a "ChromeOS in Libraries" group that doesn't have a huge
amount of traffic, but people are usually responsive when questions are
asked.
https://groups.google.com/g/chromebooks_lib

Josh

On Thu, Jan 25, 2024 at 6:59 PM Kevin Co via Evergreen-general <
evergreen-general@list.evergreen-ils.org> wrote:

> Greetings from Alaska!
>
>
>
> General library tech question: Anyone out there have any experience using
> chromebox machines in their public computer labs? What are folks using for
> printing and session management?
>
>
>
> We’re using PC’s + Cassie + Deepfreeze, but looking out for wisdom and
> future solutions.
>
>
>
> Thanks all,
>
>
>
> -Kevin, Homer Public Library
> ___
> 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] [External] Re: Claims Returned Item Status?

[Szwagiel, Will via Evergreen-general]

Thank you!

William C. Szwagiel
NC Cardinal Project Manager
State Library of North Carolina
william.szwag...@dncr.nc.gov<mailto:william.szwag...@dncr.nc.gov> | 919.814.6721
https://statelibrary.ncdcr.gov/services-libraries/nc-cardinal
109 East Jones Street  | 4640 Mail Service Center
Raleigh, North Carolina 27699-4600
The State Library is part of the NC Department of Natural & Cultural Resources.
Email correspondence to and from this address is subject to the North Carolina 
Public Records Law and may be disclosed to third parties.

From: Evergreen-general  On 
Behalf Of John Amundson via Evergreen-general
Sent: Friday, January 26, 2024 2:33 PM
To: Evergreen Discussion Group 
Cc: John Amundson 
Subject: [External] Re: [Evergreen-general] Claims Returned Item Status?

CAUTION: 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.

Hi, William:

CW MARS using a status for this that we call "Claimed Returned".

Some more answers below:

Claims Returned item status:
1.Does the circulation remain open (still checked out to the patron)
Yes and No. As far as the patron is concerned, it's returned, but it does stay 
open in the database, and is still accessible from the patron's record in the 
staff client.

2.If the circ remains open, where can staff find that information?
1.Right now, it appears in Items Out > Other/Special Circulations
This is also where it appears for us.

3.If staff can see that information, can it be set up so that patrons can’t 
see it? If patrons can see it, they will be alarmed that they still see this 
checkout, even though it is technically been forgiven.
Our patrons can't see their currently claimed returned material. Only staff 
can. This may be the default behavior.

4.Staff will need to be able to retrieve that information because we give 
each patron one claim returned. There are often repeat offenders with this.
In addition to the transaction still being accessible on the patron's record, 
staff can also run reports directly on the "Claimed Returned" status.

Hope this is helpful!

John

[Image removed by sender.]

John Amundson (he/him/his)
Library Applications Supervisor, C/W MARS, Inc.



[Image removed by sender. 
icon]jamund...@cwmars.org<mailto:jamund...@cwmars.org> | [Image removed by 
sender. icon] www.cwmars.org<https://www.cwmars.org/>

[Image removed by sender. icon]508-755-3323 x1


On Fri, Jan 26, 2024 at 2:26 PM Diane Disbro via Evergreen-general 
mailto:evergreen-general@list.evergreen-ils.org>>
 wrote:
We don't use Claims Returned/Claims Never Checked Out. Patrons see those items 
in their online account and call to say, "I told you I returned that."

After the patron and library have made a thorough search, we will forgive a 
Claim one time. We mark the item Lost (if it hasn't already gone to bills) then 
use the payment type Forgive so that we have a record of what happened. The 
item is now in Lost status so it isn't holdable and will be deleted according 
to our timeline. If the patron makes another Claim, we gently explain that we 
have already forgiven one Claim and can't forgive another. The patron needs to 
pay the bill.

Diane Disbro
Pronouns: she/her
Circulation Coordinator
Scenic Regional Library
251 Union Plaza Drive
Union, MO 63084
(636) 583-0652 ext  110
ddis...@scenicregional.or<mailto:ddis...@scenicregional.org>



On Fri, Jan 26, 2024 at 1:15 PM Daniel Guarracino via Evergreen-general 
mailto:evergreen-general@list.evergreen-ils.org>>
 wrote:
Hi William,

We are in the process of potentially changing our approach to these items. 
Currently, our items marked as Claims Returned have their status set to 
Missing. We've done so for at least ten years.

We've received some feedback recently from some of our libraries that this can 
cause confusion because these items are sort of a "special" kind of Missing. 
Some of our libraries delete items marked Missing after a year or two but have 
found that deleting these items (marked Missing because they had been marked 
Claims Returned) causes some problems. For example, the circulation remains on 
the patron's Other/Special Circulations tab even after the item is deleted.

So, we've tested out using a new status for these items instead and are in the 
process of discussing the change with our member library directors. My 
understanding from testing a new status is that the status doesn't change the 
behavior of the circulation at all; the circ will still remain open and will 
still display on the Other/Special Circulations tab.

Dan

--
Daniel Guarracino
Automation Services Librarian
OWWL Library System
2557 State Route 21
Canandaigua, NY 14424
585.394.8260 x1104

___

Re: [Evergreen-general] [External] Re: Claims Returned Item Status?

[Szwagiel, Will via Evergreen-general]

Thank you!

William C. Szwagiel
NC Cardinal Project Manager
State Library of North Carolina
william.szwag...@dncr.nc.gov<mailto:william.szwag...@dncr.nc.gov> | 919.814.6721
https://statelibrary.ncdcr.gov/services-libraries/nc-cardinal
109 East Jones Street  | 4640 Mail Service Center
Raleigh, North Carolina 27699-4600
The State Library is part of the NC Department of Natural & Cultural Resources.
Email correspondence to and from this address is subject to the North Carolina 
Public Records Law and may be disclosed to third parties.

From: Evergreen-general  On 
Behalf Of Diane Disbro via Evergreen-general
Sent: Friday, January 26, 2024 2:26 PM
To: Evergreen Discussion Group 
Cc: Diane Disbro 
Subject: [External] Re: [Evergreen-general] Claims Returned Item Status?

CAUTION: 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.

We don't use Claims Returned/Claims Never Checked Out. Patrons see those items 
in their online account and call to say, "I told you I returned that."

After the patron and library have made a thorough search, we will forgive a 
Claim one time. We mark the item Lost (if it hasn't already gone to bills) then 
use the payment type Forgive so that we have a record of what happened. The 
item is now in Lost status so it isn't holdable and will be deleted according 
to our timeline. If the patron makes another Claim, we gently explain that we 
have already forgiven one Claim and can't forgive another. The patron needs to 
pay the bill.

Diane Disbro
Pronouns: she/her
Circulation Coordinator
Scenic Regional Library
251 Union Plaza Drive
Union, MO 63084
(636) 583-0652 ext  110
ddis...@scenicregional.or<mailto:ddis...@scenicregional.org>



On Fri, Jan 26, 2024 at 1:15 PM Daniel Guarracino via Evergreen-general 
mailto:evergreen-general@list.evergreen-ils.org>>
 wrote:
Hi William,

We are in the process of potentially changing our approach to these items. 
Currently, our items marked as Claims Returned have their status set to 
Missing. We've done so for at least ten years.

We've received some feedback recently from some of our libraries that this can 
cause confusion because these items are sort of a "special" kind of Missing. 
Some of our libraries delete items marked Missing after a year or two but have 
found that deleting these items (marked Missing because they had been marked 
Claims Returned) causes some problems. For example, the circulation remains on 
the patron's Other/Special Circulations tab even after the item is deleted.

So, we've tested out using a new status for these items instead and are in the 
process of discussing the change with our member library directors. My 
understanding from testing a new status is that the status doesn't change the 
behavior of the circulation at all; the circ will still remain open and will 
still display on the Other/Special Circulations tab.

Dan

--
Daniel Guarracino
Automation Services Librarian
OWWL Library System
2557 State Route 21
Canandaigua, NY 14424
585.394.8260 x1104


From: "Evergreen-general" 
mailto:evergreen-general@list.evergreen-ils.org>>
To: "Evergreen-general" 
mailto:evergreen-general@list.evergreen-ils.org>>
Cc: "Szwagiel, Will" 
mailto:william.szwag...@dncr.nc.gov>>
Sent: Friday, January 26, 2024 1:35:17 PM
Subject: [Evergreen-general] Claims Returned Item Status?

Good afternoon,

Currently NC Cardinal does not have a value set up at the consortium level for 
the Claim Return Copy Status, so a claims returned item remains in the Checked 
Out item status.  As a result, patrons are still able to view the item in the 
catalog and place holds on it.  We are looking at potentially transitioning 
this item status to Missing or otherwise creating an entirely new, separate 
item status.

I wanted to see how other libraries might have handled a similar situation.  Do 
you set a specific value for Claim Return?

Or if you created a completely separate item status, one library staff member 
posed these questions:

Claims Returned item status:
1.Does the circulation remain open (still checked out to the patron)
2.If the circ remains open, where can staff find that information?
1.Right now, it appears in Items Out > Other/Special Circulations
3.If staff can see that information, can it be set up so that patrons can’t 
see it? If patrons can see it, they will be alarmed that they still see this 
checkout, even though it is technically been forgiven.
4.Staff will need to be able to retrieve that information because we give 
each patron one claim returned. There are often repeat offenders with this.

We see Missing status as items that have been stolen or misplaced. We leave 
items in Missing status for one year and then 

Re: [Evergreen-general] Claims Returned Item Status?

[John Amundson via Evergreen-general]

Hi, William:

CW MARS using a status for this that we call "Claimed Returned".

Some more answers below:

Claims Returned item status:

1.Does the circulation remain open (still checked out to the patron)
Yes and No. As far as the patron is concerned, it's returned, but it does
stay open in the database, and is still accessible from the patron's record
in the staff client.


2.If the circ remains open, where can staff find that information?

1.Right now, it appears in Items Out > Other/Special Circulations

This is also where it appears for us.


3.If staff can see that information, can it be set up so that patrons
can’t see it? If patrons can see it, they will be alarmed that they still
see this checkout, even though it is technically been forgiven.

Our patrons can't see their currently claimed returned material. Only staff
can. This may be the default behavior.


4.Staff will need to be able to retrieve that information because we
give each patron one claim returned. There are often repeat offenders with
this.

In addition to the transaction still being accessible on the patron's
record, staff can also run reports directly on the "Claimed Returned"
status.


Hope this is helpful!

John

John Amundson (he/him/his)
Library Applications Supervisor, C/W MARS, Inc.

--

[image: icon] jamund...@cwmars.org | [image: icon]www.cwmars.org

[image: icon] 508-755-3323 x1


On Fri, Jan 26, 2024 at 2:26 PM Diane Disbro via Evergreen-general <
evergreen-general@list.evergreen-ils.org> wrote:

> We don't use Claims Returned/Claims Never Checked Out. Patrons see those
> items in their online account and call to say, "I told you I returned
> that."
>
> After the patron and library have made a thorough search, we will forgive
> a Claim one time. We mark the item Lost (if it hasn't already gone to
> bills) then use the payment type Forgive so that we have a record of what
> happened. The item is now in Lost status so it isn't holdable and will be
> deleted according to our timeline. If the patron makes another Claim, we
> gently explain that we have already forgiven one Claim and can't forgive
> another. The patron needs to pay the bill.
>
> Diane Disbro
> Pronouns: she/her
> Circulation Coordinator
> Scenic Regional Library
> 251 Union Plaza Drive
> Union, MO 63084
> (636) 583-0652 ext  110
> ddis...@scenicregional.or 
>
>
>
> On Fri, Jan 26, 2024 at 1:15 PM Daniel Guarracino via Evergreen-general <
> evergreen-general@list.evergreen-ils.org> wrote:
>
>> Hi William,
>>
>> We are in the process of potentially changing our approach to these
>> items. Currently, our items marked as Claims Returned have their status set
>> to Missing. We've done so for at least ten years.
>>
>> We've received some feedback recently from some of our libraries that
>> this can cause confusion because these items are sort of a "special" kind
>> of Missing. Some of our libraries delete items marked Missing after a year
>> or two but have found that deleting these items (marked Missing because
>> they had been marked Claims Returned) causes some problems. For example,
>> the circulation remains on the patron's Other/Special Circulations tab even
>> after the item is deleted.
>>
>> So, we've tested out using a new status for these items instead and are
>> in the process of discussing the change with our member library directors.
>> My understanding from testing a new status is that the status doesn't
>> change the behavior of the circulation at all; the circ will still remain
>> open and will still display on the Other/Special Circulations tab.
>>
>> Dan
>>
>> --
>> Daniel Guarracino
>> Automation Services Librarian
>> OWWL Library System
>> 2557 State Route 21
>> Canandaigua, NY 14424
>> 585.394.8260 x1104
>>
>> --
>> *From: *"Evergreen-general" 
>> *To: *"Evergreen-general" 
>> *Cc: *"Szwagiel, Will" 
>> *Sent: *Friday, January 26, 2024 1:35:17 PM
>> *Subject: *[Evergreen-general] Claims Returned Item Status?
>>
>> Good afternoon,
>>
>>
>>
>> Currently NC Cardinal does not have a value set up at the consortium
>> level for the Claim Return Copy Status, so a claims returned item remains
>> in the Checked Out item status.  As a result, patrons are still able to
>> view the item in the catalog and place holds on it.  We are looking at
>> potentially transitioning this item status to Missing or otherwise creating
>> an entirely new, separate item status.
>>
>>

Re: [Evergreen-general] Claims Returned Item Status?

[Diane Disbro via Evergreen-general]

We don't use Claims Returned/Claims Never Checked Out. Patrons see those
items in their online account and call to say, "I told you I returned
that."

After the patron and library have made a thorough search, we will forgive a
Claim one time. We mark the item Lost (if it hasn't already gone to bills)
then use the payment type Forgive so that we have a record of what
happened. The item is now in Lost status so it isn't holdable and will be
deleted according to our timeline. If the patron makes another Claim, we
gently explain that we have already forgiven one Claim and can't forgive
another. The patron needs to pay the bill.

Diane Disbro
Pronouns: she/her
Circulation Coordinator
Scenic Regional Library
251 Union Plaza Drive
Union, MO 63084
(636) 583-0652 ext  110
ddis...@scenicregional.or 



On Fri, Jan 26, 2024 at 1:15 PM Daniel Guarracino via Evergreen-general <
evergreen-general@list.evergreen-ils.org> wrote:

> Hi William,
>
> We are in the process of potentially changing our approach to these items.
> Currently, our items marked as Claims Returned have their status set to
> Missing. We've done so for at least ten years.
>
> We've received some feedback recently from some of our libraries that this
> can cause confusion because these items are sort of a "special" kind of
> Missing. Some of our libraries delete items marked Missing after a year or
> two but have found that deleting these items (marked Missing because they
> had been marked Claims Returned) causes some problems. For example, the
> circulation remains on the patron's Other/Special Circulations tab even
> after the item is deleted.
>
> So, we've tested out using a new status for these items instead and are in
> the process of discussing the change with our member library directors. My
> understanding from testing a new status is that the status doesn't change
> the behavior of the circulation at all; the circ will still remain open and
> will still display on the Other/Special Circulations tab.
>
> Dan
>
> --
> Daniel Guarracino
> Automation Services Librarian
> OWWL Library System
> 2557 State Route 21
> Canandaigua, NY 14424
> 585.394.8260 x1104
>
> ------
> *From: *"Evergreen-general" 
> *To: *"Evergreen-general" 
> *Cc: *"Szwagiel, Will" 
> *Sent: *Friday, January 26, 2024 1:35:17 PM
> *Subject: *[Evergreen-general] Claims Returned Item Status?
>
> Good afternoon,
>
>
>
> Currently NC Cardinal does not have a value set up at the consortium level
> for the Claim Return Copy Status, so a claims returned item remains in the
> Checked Out item status.  As a result, patrons are still able to view the
> item in the catalog and place holds on it.  We are looking at potentially
> transitioning this item status to Missing or otherwise creating an entirely
> new, separate item status.
>
>
>
> I wanted to see how other libraries might have handled a similar
> situation.  Do you set a specific value for Claim Return?
>
>
>
> Or if you created a completely separate item status, one library staff
> member posed these questions:
>
>
>
> Claims Returned item status:
>
> 1.Does the circulation remain open (still checked out to the patron)
>
> 2.If the circ remains open, where can staff find that information?
>
> 1.Right now, it appears in Items Out > Other/Special Circulations
>
> 3.If staff can see that information, can it be set up so that patrons
> can’t see it? If patrons can see it, they will be alarmed that they still
> see this checkout, even though it is technically been forgiven.
>
> 4.Staff will need to be able to retrieve that information because we
> give each patron one claim returned. There are often repeat offenders with
> this.
>
>
>
> We see Missing status as items that have been stolen or misplaced. We
> leave items in Missing status for one year and then we delete them from the
> catalog. Using Missing status for claims returned will eliminate any paper
> trail for claims returned items.
>
>
>
> Any ideas or suggestions would be greatly appreciated.
>
>
>
> Thank you.
>
>
>
> *William C. Szwagiel*
>
> NC Cardinal Project Manager
>
> State Library of North Carolina
>
> william.szwag...@dncr.nc.gov | 919.814.6721
>
> https://statelibrary.ncdcr.gov/services-libraries/nc-cardinal
>
> 109 East Jones Street  | 4640 Mail Service Center
>
> Raleigh, North Carolina 27699-4600
>
> The State Library is part of the NC Department of Natural & Cultural
> Resources.
>
> *Email correspondence to and from this address is subject to the North
> Carolina Public Rec

Re: [Evergreen-general] [External] Re: Claims Returned Item Status?

[Szwagiel, Will via Evergreen-general]

Thank you for this information!

William C. Szwagiel
NC Cardinal Project Manager
State Library of North Carolina
william.szwag...@dncr.nc.gov<mailto:william.szwag...@dncr.nc.gov> | 919.814.6721
https://statelibrary.ncdcr.gov/services-libraries/nc-cardinal
109 East Jones Street  | 4640 Mail Service Center
Raleigh, North Carolina 27699-4600
The State Library is part of the NC Department of Natural & Cultural Resources.
Email correspondence to and from this address is subject to the North Carolina 
Public Records Law and may be disclosed to third parties.

From: Evergreen-general  On 
Behalf Of Daniel Guarracino via Evergreen-general
Sent: Friday, January 26, 2024 2:15 PM
To: Evergreen-general 
Cc: Daniel Guarracino 
Subject: [External] Re: [Evergreen-general] Claims Returned Item Status?

CAUTION: 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.

Hi William,

We are in the process of potentially changing our approach to these items. 
Currently, our items marked as Claims Returned have their status set to 
Missing. We've done so for at least ten years.

We've received some feedback recently from some of our libraries that this can 
cause confusion because these items are sort of a "special" kind of Missing. 
Some of our libraries delete items marked Missing after a year or two but have 
found that deleting these items (marked Missing because they had been marked 
Claims Returned) causes some problems. For example, the circulation remains on 
the patron's Other/Special Circulations tab even after the item is deleted.

So, we've tested out using a new status for these items instead and are in the 
process of discussing the change with our member library directors. My 
understanding from testing a new status is that the status doesn't change the 
behavior of the circulation at all; the circ will still remain open and will 
still display on the Other/Special Circulations tab.

Dan

--
Daniel Guarracino
Automation Services Librarian
OWWL Library System
2557 State Route 21
Canandaigua, NY 14424
585.394.8260 x1104

____
From: "Evergreen-general" 
mailto:evergreen-general@list.evergreen-ils.org>>
To: "Evergreen-general" 
mailto:evergreen-general@list.evergreen-ils.org>>
Cc: "Szwagiel, Will" 
mailto:william.szwag...@dncr.nc.gov>>
Sent: Friday, January 26, 2024 1:35:17 PM
Subject: [Evergreen-general] Claims Returned Item Status?

Good afternoon,

Currently NC Cardinal does not have a value set up at the consortium level for 
the Claim Return Copy Status, so a claims returned item remains in the Checked 
Out item status.  As a result, patrons are still able to view the item in the 
catalog and place holds on it.  We are looking at potentially transitioning 
this item status to Missing or otherwise creating an entirely new, separate 
item status.

I wanted to see how other libraries might have handled a similar situation.  Do 
you set a specific value for Claim Return?

Or if you created a completely separate item status, one library staff member 
posed these questions:

Claims Returned item status:
1.Does the circulation remain open (still checked out to the patron)
2.If the circ remains open, where can staff find that information?
1.Right now, it appears in Items Out > Other/Special Circulations
3.If staff can see that information, can it be set up so that patrons can’t 
see it? If patrons can see it, they will be alarmed that they still see this 
checkout, even though it is technically been forgiven.
4.Staff will need to be able to retrieve that information because we give 
each patron one claim returned. There are often repeat offenders with this.

We see Missing status as items that have been stolen or misplaced. We leave 
items in Missing status for one year and then we delete them from the catalog. 
Using Missing status for claims returned will eliminate any paper trail for 
claims returned items.

Any ideas or suggestions would be greatly appreciated.

Thank you.

William C. Szwagiel
NC Cardinal Project Manager
State Library of North Carolina
william.szwag...@dncr.nc.gov<mailto:william.szwag...@dncr.nc.gov> | 919.814.6721
https://statelibrary.ncdcr.gov/services-libraries/nc-cardinal
109 East Jones Street  | 4640 Mail Service Center
Raleigh, North Carolina 27699-4600
The State Library is part of the NC Department of Natural & Cultural Resources.
Email correspondence to and from this address is subject to the North Carolina 
Public Records Law and may be disclosed to third parties.




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.

______

Re: [Evergreen-general] Claims Returned Item Status?

[Daniel Guarracino via Evergreen-general]

Hi William, 

We are in the process of potentially changing our approach to these items. 
Currently, our items marked as Claims Returned have their status set to 
Missing. We've done so for at least ten years. 

We've received some feedback recently from some of our libraries that this can 
cause confusion because these items are sort of a "special" kind of Missing. 
Some of our libraries delete items marked Missing after a year or two but have 
found that deleting these items (marked Missing because they had been marked 
Claims Returned) causes some problems. For example, the circulation remains on 
the patron's Other/Special Circulations tab even after the item is deleted. 

So, we've tested out using a new status for these items instead and are in the 
process of discussing the change with our member library directors. My 
understanding from testing a new status is that the status doesn't change the 
behavior of the circulation at all; the circ will still remain open and will 
still display on the Other/Special Circulations tab. 

Dan 

-- 
Daniel Guarracino 
Automation Services Librarian 
OWWL Library System 
2557 State Route 21 
Canandaigua, NY 14424 
585.394.8260 x1104 


From: "Evergreen-general"  
To: "Evergreen-general"  
Cc: "Szwagiel, Will"  
Sent: Friday, January 26, 2024 1:35:17 PM 
Subject: [Evergreen-general] Claims Returned Item Status? 



Good afternoon, 



Currently NC Cardinal does not have a value set up at the consortium level for 
the Claim Return Copy Status, so a claims returned item remains in the Checked 
Out item status. As a result, patrons are still able to view the item in the 
catalog and place holds on it. We are looking at potentially transitioning this 
item status to Missing or otherwise creating an entirely new, separate item 
status. 



I wanted to see how other libraries might have handled a similar situation. Do 
you set a specific value for Claim Return? 



Or if you created a completely separate item status, one library staff member 
posed these questions: 



Claims Returned item status: 

1. Does the circulation remain open (still checked out to the patron) 

2. If the circ remains open, where can staff find that information? 

1. Right now, it appears in Items Out > Other/Special Circulations 

3. If staff can see that information, can it be set up so that patrons can’t 
see it? If patrons can see it, they will be alarmed that they still see this 
checkout, even though it is technically been forgiven. 

4. Staff will need to be able to retrieve that information because we give each 
patron one claim returned. There are often repeat offenders with this. 



We see Missing status as items that have been stolen or misplaced. We leave 
items in Missing status for one year and then we delete them from the catalog. 
Using Missing status for claims returned will eliminate any paper trail for 
claims returned items. 



Any ideas or suggestions would be greatly appreciated. 



Thank you. 



William C. Szwagiel 

NC Cardinal Project Manager 

State Library of North Carolina 

[ mailto:william.szwag...@dncr.nc.gov | william.szwag...@dncr.nc.gov ] | 
919.814.6721 

[ https://statelibrary.ncdcr.gov/services-libraries/nc-cardinal | 
https://statelibrary.ncdcr.gov/services-libraries/nc-cardinal ] 

109 East Jones Street | 4640 Mail Service Center 

Raleigh, North Carolina 27699-4600 

The State Library is part of the NC Department of Natural & Cultural Resources. 

Email correspondence to and from this address is subject to the North Carolina 
Public Records Law and may be disclosed to third parties. 





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. 

_______ 
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] Chromebox for computer labs?

[Anne Savoie via Evergreen-general]

Hi Kevin,

In some of our libraries they utilize Google Workspace to manage their
Chromebook/Chromebox devices and we use the Envisionware CloudNine
Reservation service for managing use.  We use the Envisionware LPTOne
MobilePrint product for print management.

Thanks,
Anne

Anne Savoie (she/her/hers)
Systems/Networking Manager, C/W MARS, Inc.

--

[image: icon] asav...@cwmars.org | [image: icon]www.cwmars.org

[image: icon] 508-755-3323 x EXT 2


On Thu, Jan 25, 2024 at 7:59 PM Kevin Co via Evergreen-general <
evergreen-general@list.evergreen-ils.org> wrote:

> Greetings from Alaska!
>
>
>
> General library tech question: Anyone out there have any experience using
> chromebox machines in their public computer labs? What are folks using for
> printing and session management?
>
>
>
> We’re using PC’s + Cassie + Deepfreeze, but looking out for wisdom and
> future solutions.
>
>
>
> Thanks all,
>
>
>
> -Kevin, Homer Public Library
> ___
> 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] Claims Returned Item Status?

[Szwagiel, Will via Evergreen-general]

Good afternoon,

Currently NC Cardinal does not have a value set up at the consortium level for 
the Claim Return Copy Status, so a claims returned item remains in the Checked 
Out item status.  As a result, patrons are still able to view the item in the 
catalog and place holds on it.  We are looking at potentially transitioning 
this item status to Missing or otherwise creating an entirely new, separate 
item status.

I wanted to see how other libraries might have handled a similar situation.  Do 
you set a specific value for Claim Return?

Or if you created a completely separate item status, one library staff member 
posed these questions:

Claims Returned item status:
1.Does the circulation remain open (still checked out to the patron)
2.If the circ remains open, where can staff find that information?
1.Right now, it appears in Items Out > Other/Special Circulations
3.If staff can see that information, can it be set up so that patrons can't 
see it? If patrons can see it, they will be alarmed that they still see this 
checkout, even though it is technically been forgiven.
4.Staff will need to be able to retrieve that information because we give 
each patron one claim returned. There are often repeat offenders with this.

We see Missing status as items that have been stolen or misplaced. We leave 
items in Missing status for one year and then we delete them from the catalog. 
Using Missing status for claims returned will eliminate any paper trail for 
claims returned items.

Any ideas or suggestions would be greatly appreciated.

Thank you.

William C. Szwagiel
NC Cardinal Project Manager
State Library of North Carolina
william.szwag...@dncr.nc.gov<mailto:william.szwag...@dncr.nc.gov> | 919.814.6721
https://statelibrary.ncdcr.gov/services-libraries/nc-cardinal
109 East Jones Street  | 4640 Mail Service Center
Raleigh, North Carolina 27699-4600
The State Library is part of the NC Department of Natural & Cultural Resources.
Email correspondence to and from this address is subject to the North Carolina 
Public Records Law and may be disclosed to third parties.




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.
___
Evergreen-general mailing list
Evergreen-general@list.evergreen-ils.org
http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general

Re: [Evergreen-general] Chromebox for computer labs?

[Terran McCanna via Evergreen-general]

Hi Kevin!

I don't have direct experience, but I know most of our libraries are using
Chromeboxes for public computers and LibData for their print & session
management.

Best,
Terran


On Thu, Jan 25, 2024 at 7:59 PM Kevin Co via Evergreen-general <
evergreen-general@list.evergreen-ils.org> wrote:

> Greetings from Alaska!
>
>
>
> General library tech question: Anyone out there have any experience using
> chromebox machines in their public computer labs? What are folks using for
> printing and session management?
>
>
>
> We’re using PC’s + Cassie + Deepfreeze, but looking out for wisdom and
> future solutions.
>
>
>
> Thanks all,
>
>
>
> -Kevin, Homer Public Library
> _______
> 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] Chromebox for computer labs?

[Seth Erickson via Evergreen-general]

Hello Kevin,

We're using about 300 chrome devices (chromeboxes and chromebooks) across
multiple public libraries.  We run them in managed guest session mode, so
patron website history and downloads are wiped when they log out.  The
machines are very secure and easy to push changes out, add or edit
printers, etc.  We use Google Workspace to manage them, and it works
slick.  A couple of our larger libraries use Libdata for print & session
management, but most get along without it, being that they're mostly
smaller libraries.  We're exploring using the Chromeboxes as staff
terminals, as Evergreen works well on them.  Let me know if you need any
more info.

Thanks!

-Seth

 ---
Seth Erickson
Director of IT Systems
Traverse des Sioux Library System
833-837-5422  ext. 703
507-237-6085 (cell)
serick...@tds.lib.mn.us



On Thu, Jan 25, 2024 at 6:59 PM Kevin Co via Evergreen-general <
evergreen-general@list.evergreen-ils.org> wrote:

> Greetings from Alaska!
>
>
>
> General library tech question: Anyone out there have any experience using
> chromebox machines in their public computer labs? What are folks using for
> printing and session management?
>
>
>
> We’re using PC’s + Cassie + Deepfreeze, but looking out for wisdom and
> future solutions.
>
>
>
> Thanks all,
>
>
>
> -Kevin, Homer Public Library
> _______
> 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] Chromebox for computer labs?

[Kevin Co via Evergreen-general]

Greetings from Alaska!

General library tech question: Anyone out there have any experience using 
chromebox machines in their public computer labs? What are folks using for 
printing and session management?

We're using PC's + Cassie + Deepfreeze, but looking out for wisdom and future 
solutions.

Thanks all,

-Kevin, Homer Public Library
___
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

[Mike Rylander via Evergreen-general]

ot on the org
>> unit interface that are required in order to have descendants show up
>> (or not, depending on the local desire).
>>
>> I try not to deal in absolutes WRT "simpler" or "better" and the like,
>> but I will go out on a limb here: Custom org trees are /objectively/
>> conceptually simpler than the base org tree plus all the various
>> subtle adjustments to it.  The reason is simple: the custom org tree
>> is concrete.  It is "This is the OPAC search tree, which has this
>> specific order provided by the admin." vs "This is the org tree, some
>> of which may be visible in the OPAC for search depending on checkboxes
>> in one UI and settings in several others, and also local hacks put in
>> place to hide some orgs based on other criteria.  Oh, and you can't
>> decide on the order, which is probably sorted by name or short name,
>> without other local hacks."
>>
>> The frequency with which a central admin would need to add an org unit
>> is so low, and the rest of the configuration is so voluminous, that
>> surely they must have a checklist of all the /other/ things that may
>> need to happen when a new org unit is added -- working locations for
>> users, library settings, receipts and other various templates,
>> default/pinned workstation settings, 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 
>> >  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 mult

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

[Lussier, Kathy via Evergreen-general]

rch selector in the Angular catalog looking like the one we used in the
> tpac staff catalog is something our libraries have told us is necessary
> before they're willing to move to the Angular Catalog.
> >
>
> Sorry I wasn't clear.  There is a column on the custom org tree table
> literally called "purpose", and I was specifically referring to that.
> In the old dojo interface, that's what is shown in the dropdown next
> to the "Custom Unit Tree:" label.  Today, the only "purpose" value
> allowed is 'opac', but that's one line of SQL away from changing.
>
> >> 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.
> >
> >
> > I agree that the custom org tree is much more flexible, but we really
> don't need that flexibility. I'm not sure that I agree that it is
> conceptually simpler or more maintainable.  Although the Angular custom org
> tree admin interface is a huge improvement over the old dojo one, I find
> it's much simpler to just uncheck a visibility box when setting up or
> editing an org unit. The org tree admin is another place you have to
> remember to go after setting up the org unit to make sure it displays
> correctly in the catalog. But as I said to Galen, we'll reconsider it.
> >
>
> It is true that if you use a custom org tree then you have to adjust
> it when adding a new org, but I find it hard to believe that
> separately saying "ok, now show it in the OPAC (and/or staff catalog)
> at this position" is a massive, undue burden that is simply a waste of
> staff time.  And it would be trivial to add a link from the org unit
> admin UI to the custom tree UI, in order to reduce friction.
>
> Unfortunately, you can't simply uncheck the visibility box on an org
> and know for sure that you're done.  Setting aside the server-side
> script that you have to run in order to make sure that everyone sees
> the change, there are other configuration parameters not on the org
> unit interface that are required in order to have descendants show up
> (or not, depending on the local desire).
>
> I try not to deal in absolutes WRT "simpler" or "better" and the like,
> but I will go out on a limb here: Custom org trees are /objectively/
> conceptually simpler than the base org tree plus all the various
> subtle adjustments to it.  The reason is simple: the custom org tree
> is concrete.  It is "This is the OPAC search tree, which has this
> specific order provided by the admin." vs "This is the org tree, some
> of which may be visible in the OPAC for search depending on checkboxes
> in one UI and settings in several others, and also local hacks put in
> place to hide some orgs based on other criteria.  Oh, and you can't
> decide on the order, which is probably sorted by name or short name,
> without other local hacks."
>
> The frequency with which a central admin would need to add an org unit
> is so low, and the rest of the configuration is so voluminous, that
> surely they must have a checklist of all the /other/ things that may
> need to happen when a new org unit is added -- working locations for
> users, library settings, receipts and other various templates,
> default/pinned workstation settings, 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 ni

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

[Mike Rylander via Evergreen-general]

ojo one, I find it's much 
> simpler to just uncheck a visibility box when setting up or editing an org 
> unit. The org tree admin is another place you have to remember to go after 
> setting up the org unit to make sure it displays correctly in the catalog. 
> But as I said to Galen, we'll reconsider it.
>

It is true that if you use a custom org tree then you have to adjust
it when adding a new org, but I find it hard to believe that
separately saying "ok, now show it in the OPAC (and/or staff catalog)
at this position" is a massive, undue burden that is simply a waste of
staff time.  And it would be trivial to add a link from the org unit
admin UI to the custom tree UI, in order to reduce friction.

Unfortunately, you can't simply uncheck the visibility box on an org
and know for sure that you're done.  Setting aside the server-side
script that you have to run in order to make sure that everyone sees
the change, there are other configuration parameters not on the org
unit interface that are required in order to have descendants show up
(or not, depending on the local desire).

I try not to deal in absolutes WRT "simpler" or "better" and the like,
but I will go out on a limb here: Custom org trees are /objectively/
conceptually simpler than the base org tree plus all the various
subtle adjustments to it.  The reason is simple: the custom org tree
is concrete.  It is "This is the OPAC search tree, which has this
specific order provided by the admin." vs "This is the org tree, some
of which may be visible in the OPAC for search depending on checkboxes
in one UI and settings in several others, and also local hacks put in
place to hide some orgs based on other criteria.  Oh, and you can't
decide on the order, which is probably sorted by name or short name,
without other local hacks."

The frequency with which a central admin would need to add an org unit
is so low, and the rest of the configuration is so voluminous, that
surely they must have a checklist of all the /other/ things that may
need to happen when a new org unit is added -- working locations for
users, library settings, receipts and other various templates,
default/pinned workstation settings, 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 
>  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 purpo

[Evergreen-general] UI Interest Group meeting today @ 2pm Eastern

[Stephanie Leary via Evergreen-general]

Good morning, everyone! The UI Interest Group will meet today at 2pm
Eastern on Zoom:
https://us06web.zoom.us/j/87365620961?pwd=ekUrQnVZQk1YV1FsYlNrb1pjVWtOdz09

Here's our agenda:
https://docs.google.com/document/d/1riutXKb4fhJpiS8V1ijrMEiURm9e9ooCJk8PF16cuQM/edit?usp=sharing

See you there!

Stephanie Leary
Front End Developer
Equinox Open Library Initiative
stephanie.le...@equinoxoli.org
https://www.equinoxOLI.org
phone: 877-OPEN-ILS (673-6457)
___
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

[Andrea Buntz Neiman via Evergreen-general]

Correct - here's a screenshot from our test system:

[image: image.png]

On Wed, Jan 24, 2024 at 4:18 PM Lussier, Kathy 
wrote:

> 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
>  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 Ope

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

[Lussier, Kathy via Evergreen-general]

Hi Mike!

OP here, aka kmlussier. Thanks for adding your thoughts! My comments are
below.

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.


I can delve into our reasons for displaying the groups in the selector.
Most of our copy location groups are really departemental level groups
(children's, teen, adults), similar to the department levels that were
suggested at one time as possible child org units to branches. However, we
didn't want all of the other things that come with creating a new org unit:
a new pickup location, a message to send items into transit when items are
checked in at the branch, etc. We just wanted the department level for the
purposes of searching.

In the minds of our libraries and patrons, these shelving location groups
are "search scopes" in the same way that a branch or a system is a search
scope. On the public side, most patrons will not bother to go to the
advanced search page to see what's there, but they will easily see there is
a way to search the children's collection from the main search page. I get
what you're saying about large installations with many org units, but I
also know that CW MARS, which is far larger than us, is also interested in
seeing these restored to the library selector.

Out of curiosity, are there other libraries / consortia out there who are
using shelving location groups? If you are using them and do not want to
see them in the library search selector, it would be good to know. I guess
we shouldn't assume that restoring the traditional method is the approach
everyone wants to take.

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"),


To be clear, this isn't really a "new" purpose. The custom org trees always
worked in the tpac staff catalog.  For this year, NOBLE is prioritizing
development for features we previously funded, either individually or as
part of a larger development cooperative, that were inadvertently missed as
interfaces were replaced. Getting the library search selector in the
Angular catalog looking like the one we used in the tpac staff catalog is
something our libraries have told us is necessary before they're willing to
move to the Angular Catalog.

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.


I agree that the custom org tree is much more flexible, but we really don't
need that flexibility. I'm not sure that I agree that it is conceptually
simpler or more maintainable.  Although the Angular custom org tree admin
interface is a huge improvement over the old dojo one, I find it's much
simpler to just uncheck a visibility box when setting up or editing an org
unit. The org tree admin is another place you have to remember to go after
setting up the org unit to make sure it displays correctly in the catalog.
But as I said to Galen, we'll reconsider it.

Thanks 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

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 trus

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

[Lussier, Kathy via Evergreen-general]

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.
> [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.
> [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.
>
> As you can see, there's a wide range of effort among these options - and
> semantics.
>
> 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

[Evergreen-general] Job Posting: Executive Director - Bibliomation, Inc.

[Jessica Woolford via Evergreen-general]

*Executive Director – Bibliomation, Inc.*

Bibliomation, Inc <https://www.biblio.org/>.’s Board of Directors seeks a
creative, forward-thinking leader to serve as Executive Director to guide
this dynamic organization as it advances its vision for member libraries
and staff. The next Executive Director will exhibit exemplary communication
skills while providing leadership, management, and support for the new
initiatives and ongoing endeavors of member libraries through relevant
technology solutions, collaborative resource sharing, and thoughtful budget
development. The Executive Director serves under the general direction of
the 12-member Board of Directors, has overall responsibility for general
administration of operations. Bibliomation has a proud history and a strong
future helping member libraries and schools provide quality library service
to their users by providing state-of-the-art IT services effectively and
efficiently.

*Responsibilities:* The Executive Director implements the organization's
strategic plan and oversees financial and staff management
and development;. This position supervises key managers and has oversight
responsibility for program development and evaluation, operations, finance,
marketing, and public relations; Additional responsibilities include
coordinating, representing, and reporting on Board, Member Council, and
Finance Committee meetings; The Executive Director will prepare operating
budgets, investigate alternative revenue streams, negotiate contracts,
and establish effective communication with internal and external
stakeholders. A complete list of duties and responsibilities is listed in
the job description below.

*Qualifications:* A master’s degree in library science from an
ALA-accredited school and/or advanced management training (MPA, MBA, or
similar degree), proven experience reporting to a governing board, and
success in collaborating with multiple stakeholders are highly desirable.
This position requires a minimum of three years of progressively
responsible professional and administrative experience in a public library
or a nonprofit and a history of responsible senior-level
management/organizational leadership or an equivalent combination of
education and experience. Public library experience would
be advantageous in this role, and a strong commitment to customer service
is desired. Essential skills include: the ability to think strategically
and creatively to develop new programmatic opportunities; building and
developing diversified revenue streams; effectively serving as a
spokesperson with multiple stakeholders; and strong leadership skills
encouraging creativity, growth, collaboration, and accountability.

*Compensation*: The hiring salary range is *$90,000 – $105,000* (with
placement negotiable dependent on experience and qualifications) and an
exceptional benefit package that includes medical, dental, retirement plan,
vacation, life insurance, and more.

For further information, contact Bradbury Miller Associates
<https://bradburymiller.com/current-clients/>. This position closes on *Sunday,
March 3, 2024*.


-- 

Jessica Woolford (she/her)

Director of Member Services

jwoolf...@biblio.org | (203) 577-4070 <203-577-4070>x105

» Help Desk: Open or Check a Ticket <https://helpdesk.biblio.org>

[image: Stylized turquoise book with blue swirl around it, above text
reading Bibliomation: Libraries Sharing Computerized Services]
<https://biblio.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

[Mike Rylander via Evergreen-general]

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 
>  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.
>>
>>
>> 
>> From: Evergreen-general  
>> on behalf of Terran McCanna via Evergreen-general 
>> 
>> Sent: Tuesday, January 23, 2024 7:13 AM
>> To: Evergreen Discussion Group 
>> 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 
>>  wrote:
>>
>> Hi,
>>
>> 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
&

[Evergreen-general] Today's Business Solutions and Evergreen

[Jessica Woolford via Evergreen-general]

Hi everyone!

Does anyone work with or at a library that uses Today's Business Solutions
products, particularly their mobile printing and PC management systems? If
so, would you be willing to share your experiences?

Thank you!
Jessica

-- 

Jessica Woolford (she/her)

Director of Member Services

jwoolf...@biblio.org | (203) 577-4070 <203-577-4070>x105

» Help Desk: Open or Check a Ticket <https://helpdesk.biblio.org>

[image: Stylized turquoise book with blue swirl around it, above text
reading Bibliomation: Libraries Sharing Computerized Services]
<https://biblio.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

[Andrea Buntz Neiman via Evergreen-general]

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  >
> *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.
> ___
> Evergreen-general mailing list
> Evergreen-general@list.evergreen-ils.org
> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general
>


-- 
Andrea Buntz Neiman, MLS
Project Manager for Software Development | Product Specialist
Equinox Open Library Initiative
abnei...@equinoxoli.org 
1-877-OPEN-ILS (673-6457)
Direct: 770-709-5583
*https://www.equinoxOLI.org/ <https://www.equinoxOLI.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

[Tina Ji via Evergreen-general]

On Mon, Jan 22, 2024 at 12:09 PM Lussier, Kathy via Evergreen-general 
mailto: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  on 
behalf of Terran McCanna via Evergreen-general 

Sent: Tuesday, January 23, 2024 7:13 AM
To: Evergreen Discussion Group 
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 
mailto:evergreen-general@list.evergreen-ils.org>>
 wrote:
Hi,

On Mon, Jan 22, 2024 at 12:09 PM Lussier, Kathy via Evergreen-general 
mailto: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<mailto: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.
___
Evergreen-general mailing list
Evergreen-general@list.evergreen-ils.org
http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general

[Evergreen-general] Permissions Working Group Meeting Today

[Susan Morrison via Evergreen-general]

Good Morning,

The Permissions Working Group will be meeting at 3 p.m. EST this afternoon.

Agenda and connection info:
https://docs.google.com/document/d/1CFUZe0d7Mp_XAhHQhr_qkDpDV6MByQQAji_sAuruo44/edit?usp=sharing

Notes from the last meeting can be found here:
https://wiki.evergreen-ils.org/doku.php?id=community:permissions_working_group#past_meetings
 
<https://wiki.evergreen-ils.org/doku.php?id=community:permissions_working_group#next_meeting>

Thank you,

Susan
___
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

[Galen Charlton via Evergreen-general]

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 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.
[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.
[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.

As you can see, there's a wide range of effort among these options - and
semantics.

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

[Terran McCanna via Evergreen-general]

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
>
_______
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

[Jason Boyer via Evergreen-general]

I like the idea of bringing shelving location groups to the staff client, yay 
for feature parity!

I won't join in on the listing of potential reasons why #2 is necessary as 
there are already several, but I would like to lean hard toward adding a 
staff_visible flag to OUs or something similar because a global flag is too 
heavy a hammer for this.

If hiding "deleted" or unused / unwanted OUs from more of the staff client is a 
sub-goal that is a much bigger thing and should be dealt with directly, where 
just excluding some OUs from staff search should be manageable without too much 
fuss.

Jason

-- 
Jason Boyer
Senior System Administrator
Equinox Open Library Initiative
jbo...@equinoxoli.org
+1 (877) Open-ILS (673-6457)
https://equinoxOLI.org/

> On Jan 22, 2024, at 12:09 PM, Lussier, Kathy via Evergreen-general 
>  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:
> 
> We plan to restore shelving location groups in the selector, similar to the 
> way they appear in the public catalog.
> 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 <http://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

[Frasur, Ruth via Evergreen-general]

Adding another +1 for the staff visibility flag/check box in “org unit 
configuration.”

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  On 
Behalf Of Terran McCanna via Evergreen-general
Sent: Tuesday, January 23, 2024 10:06 AM
To: Evergreen Discussion Group 
Cc: Terran McCanna 
Subject: Re: [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. 

PINES is also in favor of a staff visibility flag that is separate from the 
OPAC-visibility flag.

On Mon, Jan 22, 2024 at 7:12 PM Jason Stephenson via Evergreen-general 
mailto:evergreen-general@list.evergreen-ils.org>>
 wrote:
Hi, all.

On 1/22/24 17:57, Lussier, Kathy via Evergreen-general wrote:
> 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.

We talked about this internally at C/W MARS and thought that a field for
staff catalog visibility on the org. unit would be appropriate.

HtH,
Jason

>
> 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<https://protect2.fireeye.com/v1/url?k=31323334-50bba2bf-31367a34-4544474f5631-7104298d45dbc571&q=1&e=b900b72f-fa15-4601-bdde-6a013f65f101&u=http%3A%2F%2Fwww.noblenet.org%2F>
>  
> <http://www.noblenet.org<https://protect2.fireeye.com/v1/url?k=31323334-50bba2bf-31367a34-4544474f5631-7104298d45dbc571&q=1&e=b900b72f-fa15-4601-bdde-6a013f65f101&u=http%3A%2F%2Fwww.noblenet.org%2F>>
>
>
>
>
> On Mon, Jan 22, 2024 at 5:46 PM Galen Charlton 
> mailto:g...@equinoxoli.org>
> <mailto:g...@equinoxoli.org<mailto:g...@equinoxoli.org>>> wrote:
>
> Hi,
>
> On Mon, Jan 22, 2024 at 12:09 PM Lussier, Kathy via
> Evergreen-general 
> mailto:evergreen-general@list.evergreen-ils.org>
> 
> <mailto:evergreen-general@list.evergreen-ils.org<mailto: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<mailto:g...@equinoxoli.org>
> 
> https://www.equinoxOLI.org<https://protect2.fireeye.com/v1/url?k=31323334-50bba2bf-31367a34-4544474f5631-58c7608fb94d6f45&q=1&e=b900b72f-fa15-4601-bdde-6a013f65f101&u=https%3A%2F%2Fwww.equinoxoli.org%2F>
>  
> <https://www.equinoxOLI.org<https://protect2.fireeye.com/v1/url?k=31323334-50bba2bf-31367a34-4544474f5631-58c7608fb94d6f45&q=1&e=b900b72f-fa15-4601-bdde-6a013f65f101&u=https%3A%2F%2Fwww.equinoxoli.or

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

[Terran McCanna via Evergreen-general]

PINES is also in favor of a staff visibility flag that is separate from the
OPAC-visibility flag.

On Mon, Jan 22, 2024 at 7:12 PM Jason Stephenson via Evergreen-general <
evergreen-general@list.evergreen-ils.org> wrote:

> Hi, all.
>
> On 1/22/24 17:57, Lussier, Kathy via Evergreen-general wrote:
> > 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.
>
> We talked about this internally at C/W MARS and thought that a field for
> staff catalog visibility on the org. unit would be appropriate.
>
> HtH,
> Jason
>
> >
> > 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 <http://www.noblenet.org>
> >
> >
> >
> >
> > On Mon, Jan 22, 2024 at 5:46 PM Galen Charlton  > <mailto:g...@equinoxoli.org>> wrote:
> >
> > Hi,
> >
> > On Mon, Jan 22, 2024 at 12:09 PM Lussier, Kathy via
> > Evergreen-general  > <mailto: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 <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
> ___
> 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]

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

[Josh Stompro via Evergreen-general]

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

[Jason Stephenson via Evergreen-general]

Hi, all.

On 1/22/24 17:57, Lussier, Kathy via Evergreen-general wrote:

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.


We talked about this internally at C/W MARS and thought that a field for 
staff catalog visibility on the org. unit would be appropriate.


HtH,
Jason



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 <http://www.noblenet.org>




On Mon, Jan 22, 2024 at 5:46 PM Galen Charlton <mailto:g...@equinoxoli.org>> wrote:


Hi,

On Mon, Jan 22, 2024 at 12:09 PM Lussier, Kathy via
Evergreen-general mailto: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 <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

___
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

[Miller, Jeremy via Evergreen-general]

Another…

A library building is undergoing remodeling or repairs, during which part of 
the collection has been stored in a way (or at a location) that is not readily 
accessible to the public.  But staff still needs to be able to see what is 
there.

Have actually done that twice here in our system.  Have also seen it done at 
others.



[cid:image001.png@01DA4D4C.7485A5E0]
Jeremy Miller
System Administrator
503-507-9258 cell
Information Technology
City of Albany, Oregon
333 Broadalbin St SW, Albany, Oregon 97321
www.cityofalbany.net<http://www.cityofalbany.net/>





From: Evergreen-general  On 
Behalf Of Galen Charlton via Evergreen-general
Sent: Monday, January 22, 2024 2:46 PM
To: Evergreen Discussion Group 
Cc: Galen Charlton 
Subject: Re: [Evergreen-general] Sharing plans for changing library selector in 
Angular staff catalog


[WARNING!  This email came from outside our organization. Do NOT click unknown 
attachments or links in email.]
Hi,

On Mon, Jan 22, 2024 at 12:09 PM Lussier, Kathy via Evergreen-general 
mailto: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<mailto:g...@equinoxoli.org>
https://www.equinoxOLI.org<https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fwww.equinoxOLI.org&c=E,1,le255JzTbR-I2rswZlvtdf-Ihysje6qvm5c6OPhO4cbbnYkzgzFGlvoLv4obC3_a1u1-SFLtayv_MtBAIdPGf7EKSpmjGWxtEObwGB31V51Q8wiWr1cluw,,&typo=1>
phone: 877-OPEN-ILS (673-6457)
direct: 770-709-5581

__
DISCLAIMER: This email may be considered a public record of the City of Albany 
and subject to the State of Oregon Retention Schedule. This email also may be 
subject to public disclosure under the Oregon Public Records Law. This email, 
including any attachments, is for the sole use of the intended recipient(s) and 
may contain confidential and privileged information. Any unauthorized review, 
use, disclosure or distribution is prohibited. If you have received this 
communication in error, please notify the sender immediately and destroy all 
copies of the original message.
_______
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

[Galen Charlton via Evergreen-general]

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

[Frasur, Ruth via Evergreen-general]

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  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.


[https://drive-thirdparty.googleusercontent.com/16/type/application/vnd.google-apps.document]
 Angular Staff Catalog: Library Selector 
Improve...<https://protect2.fireeye.com/v1/url?k=31323334-50bba2bf-31367a34-4544474f5631-72d20d3cf6093551&q=1&e=f1ee8472-6072-48e0-ab15-e15f80abd34b&u=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&q=1&e=f1ee8472-6072-48e0-ab15-e15f80abd34b&u=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

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

[Frasur, Ruth via Evergreen-general]

Great!  This is very intriguing and your use of shelving location groups is 
also pretty inspiring.

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: Lussier, Kathy 
Sent: Monday, January 22, 2024 12:34 PM
To: Frasur, Ruth 
Cc: Evergreen Discussion Group 
Subject: Re: [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 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<https://protect2.fireeye.com/v1/url?k=31323334-50bba2bf-31367a34-4544474f5631-7104298d45dbc571&q=1&e=4ba38e25-7e9d-4a5b-acb7-432497fb5929&u=http%3A%2F%2Fwww.noblenet.org%2F>




On Mon, Jan 22, 2024 at 12:30 PM Frasur, Ruth 
mailto:rfra...@library.in.gov>> 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 
mailto: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 
mailto:evergreen-general@list.evergreen-ils.org>>
Cc: Lussier, Kathy mailto:kluss...@noblenet.org>>
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.


[https://drive-thirdparty.googleusercontent.com/16/type/application/vnd.google-apps.document]
 Angular Staff Catalog: Library Selector 
Improve...<https://protect2.fireeye.com/v1/url?k=31323334-50bba2bf-31367a34-4544474f5631-72d20d3cf6093551&q=1&e=f1ee8472-6072-48e0-ab15-e15f80abd34b&u=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&q=1&e=f1ee8472-6072-48e0-ab15-e15f80abd34b&u=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

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&q=1&e=f1ee8472-6072-48e0-ab15-e15f80abd34b&u=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&q=1&e=f1ee8472-6072-48e0-ab15-e15f80abd34b&u=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...
<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

Re: Potential issues with the snippet to parse SOURCE_DATE_EPOCH in C

[Bernhard M. Wiedemann via rb-general]

On 19/01/2024 21.03, Chris Lamb wrote:

Was there any reason to reject >ULONG_MAX? I'm touching this code,
and don't see a reason for it; it looks very arbitrary; especially
since some systems can have 32-bit long, but 64-bit time_t. Should I
just drop that check, or keep it? And why?


There is another issue with the ULONG_MAX - that is it allows to 
represent timestamps up to 2106, but a 32-bit time_t is a signed int32, 
so will roll over in 2038 back to 1901.


At some (not too far) point in time, programs and libraries compiling 
with glibc should start to build with -D_TIME_BITS=64 
-D_FILE_OFFSET_BITS=64 to get 64-bit time_t everywhere. [1]


Ciao
Bernhard M.

[1] 
https://www.reddit.com/r/linux/comments/19a95cl/today_is_y2k38_commemoration_day_t14/


OpenPGP_signature.asc
Description: OpenPGP digital signature

Re: Problems with auto-roll and auto-play functions

[Bug reports for and general discussion about GNU Backgammon.]

Hi Murat,

Good luck with your project.

No, I'm not one of the developers. I can just about read C if I stare at it 
long enough. But I've never devoted time to learn it properly.

I've just been on the mailing list a long time, contributed bug reports and 
rollout time, and answered questions when I can to save the real devs the 
bother.

My coding skills are specific to industrial control systems. It's rather 
different to standard high level languages.


Regards,

Ian Shaw



From: MK 
Sent: Friday, January 19, 2024 11:25:10 PM
To: Ian Shaw ; bug-gnubg@gnu.org 
Subject: Re: Problems with auto-roll and auto-play functions

On 1/19/2024 2:37 AM, Ian Shaw wrote:

> I know nothing of Python, so I can’t help you with that. Good luck.

I just spent a couple hours on Python today, starting with this
post from Michael Petch in December 2013:

https://lists.gnu.org/archive/html/bug-gnubg/2013-12/msg00013.html

It briefly explain how to start using the GNUBG module. Then I
visited https://docs.python.org/3.10/tutorial/index.html and
selectively read from the Python tutorial some sections to get
a quick start.

If you know other programming languages, you'll pick it up very
fast. I really like it. I was able to quickly figure out the
individual parts of the script that I need already, using the
interactive interpreter. Hopefully I will be able to assemble
them into an actual script file and will share it freely when
I get it working. I would encourage you and anyone who wants
to experiment with GnuBG to take a look at it.

Are you one of the GnuBG development team? My other comments
about the auto-roll and auto-play functions, (unrelated to the
specific subject of the script making cube decisions for the
bot), are still valid and hopefully will be heeded by the GnuBG
team. In fact, they cause problems in the GUI also. If interested
you guys can look at this thread in RGB for example:

https://groups.google.com/g/rec.games.backgammon/c/ikCPgBiZHvs/m/SW66d7ZACAAJ

Thanks for your trying to help. You did at least motivate me.

MK

RE: Problems with auto-roll and auto-play functions

[Bug reports for and general discussion about GNU Backgammon.]

Hi MK, 

I know nothing of Python, so I can’t help you with that. Good luck.

-- Ian

-Original Message-
From: MK  
Sent: Friday, January 19, 2024 12:20 AM
To: Ian Shaw ; bug-gnubg@gnu.org
Subject: Re: Problems with auto-roll and auto-play functions

On 1/18/2024 2:22 PM, MK wrote:

> On 1/18/2024 6:31 AM, Ian Shaw wrote:

>> You can’t make the gnubg engine only be itself for some moves, and 
>> ask you to make the choices for other moves.

> There is no reason for this arbitrary, unnecessary limitation. Bot can 
> wait to roll and/or move until it's told to do so (i.e. "play" 
> command). If the user wants it to play automatically, he can just 
> select the auto-roll and auto-play setting. Simple logic and clean 
> implementation...

After looking at things some more, I realized that I had a misunderstanding how 
much can be done with a script. I thought you could intercept bot's play and 
inject a different play through the script. I see what you mean now that even 
though checker and cube settings are separate for players, you can't mix and 
match to have a half human half bot player.

So, the script has to parse the best checker hint and make the move also as you 
suggested. I guess we can continue to work towards a script with that in 
mind...?

MK

Re: org-->latex and beamer, avoid blocks

[General discussions about Org-mode.]

>>> "FE" == Fraga, Eric  writes:

> On Thursday, 18 Jan 2024 at 16:40, Uwe Brauer via "General discussions
> about Org-mode." wrote: 
>> Any suggestion how to tell the converter not convert
>> 
>> *** First step
>> 
>> To a block?

> Add the :B_ignoreheading: tag and the following property to the headline:

> :PROPERTIES:
> :BEAMER_env: ignoreheading
> :END:

> which you can do easily if you have

Ah, thanks very much.


> #+startup: beamer

> in your org file which allows you to then use "C-c C-b i" to add that
> information.

Aha also very useful (the allowframebreaks and shrink option that I use
often is unfortunately not among these property templates)

> Although the idea of a single document that exports to both beamer and
> LaTeX is attractive, I've always found it to be more effort than it's
> worth.  Just my 2¢.


Well, right. I just realized that for example 
when I export the document to LatReX article, then cosntructs like


*** Code
 :PROPERTIES:
 :BEAMER_env: ignoreheading
 :END:

Get converted in the sense that the properties are not simply ignored
but transformed to text, which is not what I want.



-- 
I strongly condemn Hamas heinous despicable pogroms/atrocities on Israel
I strongly condemn Putin's war of aggression against Ukraine.
I support to deliver weapons to Ukraine's military. 
I support the EU and NATO membership of Ukraine. 



smime.p7s
Description: S/MIME cryptographic signature

export to latex (article) but with multicolums

[General discussions about Org-mode.]

Hello

According to 

https://orgmode.org/worg/exporters/beamer/tutorial.html

It is possible to have multicolumns in beamer.

Now I am writing a bilingual text, and would have each language in a column.

Is there any similar configuration possible for exporting to LaTeX (article)?

Thanks and regards

Uwe Brauer 
-- 
I strongly condemn Hamas heinous despicable pogroms/atrocities on Israel
I strongly condemn Putin's war of aggression against Ukraine.
I support to deliver weapons to Ukraine's military. 
I support the EU and NATO membership of Ukraine. 

org-->latex and beamer, avoid blocks

[General discussions about Org-mode.]

Hi

I have a longer documents with a lot of graphics, and the following setting:

#+OPTIONS: H:2

So that 
** Introduction 

Will be converted to a frame, while if converted to LaTeX (article) it
will be converted to a subsection.

Now I also have  subsubsections like 

*** First step

Containing two graphics, 

This subsubsection will be converted to a block and then I cannot use
allowframebreaks and only one graphics is displayed.

Any suggestion how to tell the converter not convert 

*** First step 

To a block?

Thanks and regards

Uwe Brauer 


-- 
I strongly condemn Hamas heinous despicable pogroms/atrocities on Israel
I strongly condemn Putin's war of aggression against Ukraine.
I support to deliver weapons to Ukraine's military. 
I support the EU and NATO membership of Ukraine. 

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
<https://docs.google.com/document/d/1wkIIzS5gNW-EiZd8pIIh6P3ZXkX_phXkt7WJgaGSexc/edit?usp=drive_web>

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] LP 1948991: Administration Options - Mismatch with headers

[Diane Disbro via Evergreen-general]

Yes, please. +1

Diane Disbro
Pronouns: she/her
Circulation Coordinator
Scenic Regional Library
251 Union Plaza Drive
Union, MO 63084
(636) 583-0652 ext  110
ddis...@scenicregional.or 



On Wed, Jan 17, 2024 at 12:34 PM Jennifer Pringle via Evergreen-general <
evergreen-general@list.evergreen-ils.org> wrote:

> I actually think we should use the names from the menus rather than the
> current headings on the pages.  It sounds like it will be more work but, at
> least for us, those are the names library staff know the interfaces by and
> in most cases the names the interfaces have had for years. Changing them to
> match the headings will also change the order of the menu and in come cases
> split up interfaces that are currently nicely grouped together. (and
> will add the word Configuration to almost every menu item on the Server
> Admin menu)
>
>
>
> For example:
>
>
>
> Circulation Duration Rules -> Circulation Duration Rule Configuration
> Circulation Limit Groups -> Circulation Limit Group Configuration
> Circulation Matchpoint Weights -> Circ Matrix Weights Configuration
> Circulation Max Fine Rules -> Max Fine Rule Configuration
> Circulation Modifiers -> Circulation Modifier Configuration
> Circulation Recurring Fine Rules -> Recurring Fine Rule Configuration
>
>
>
> Jennifer
>
>
>
> --
>
> Jennifer Pringle (she/her)
>
> Co-op Support - Training Lead
>
> BC Libraries Cooperative
>
> Toll-free: 1-888-848-9250
>
> Email:jennifer.prin...@bc.libraries.coop
>
> Website: http://bc.libraries.coop
>
>
>
> Gratefully acknowledging that I live and work in the unceded Traditional
> Territory of the St'at'yemc Nations.
>
>
>
> *From:* Evergreen-general <
> evergreen-general-boun...@list.evergreen-ils.org> *On Behalf Of *Gina
> Monti via Evergreen-general
> *Sent:* Saturday, January 13, 2024 7:26 AM
> *To:* Evergreen Discussion Group  >
> *Cc:* Gina Monti 
> *Subject:* Re: [Evergreen-general] LP 1948991: Administration Options -
> Mismatch with headers
>
>
>
> +1 on fewer changes to make so I change my vote to the links
>
>
>
> On Sat, Jan 13, 2024 at 9:56 AM Jason Etheridge via Evergreen-general <
> evergreen-general@list.evergreen-ils.org> wrote:
>
> > Basically, the labels of the links within admin pages don't actually
> match the headers in the specific pages themselves.  I would like to work
> on part of the bug, but there needs to be a general agreement on if we
> should change the link or the headers.
>
> I'd vote for changing the links, as at least some of the UI titles are
> coming from the IDL, which means they may also get re-used with
> reporting. That also makes for fewer files to touch, overall. We
> shouldn't forget that we can also completely relabel things if the
> programmer-ese is too prominent.
>
> --
> Jason Etheridge
> Senior Developer
> Equinox Open Library Initiative
> ja...@equinoxoli.org
> https://equinoxOLI.org
> phone: 877-OPEN-ILS (673-6457)
> ___
> Evergreen-general mailing list
> Evergreen-general@list.evergreen-ils.org
> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general
>
>
>
>
> --
>
> Gina Monti (she/her)
>
> Evergreen Systems Manager
>
> Bibliomation, Inc.
>
> (203) 577-4070 ext. 109
>
> English, American Sign Language
>
> This message originated from outside the M365 organisation. Please be
> careful with links, and don't trust messages you don't recognise.
> ___
> 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