Re: [Evergreen-general] Dealing with significant traffic increase caused by AI bots

[Jane Sandberg via Evergreen-general]

Hi Linda,

It's not for Evergreen, but my colleague recently blocked claudebot using
fail2ban on our load balancer
.
Essentially, fail2ban is configured to watch Nginx's access log, and if
more than 10 claudebot requests appear within the past minute from a
particular IP, it automatically blocks all requests from that IP for the
next 24 hours.  I would think that something similar could work for
Apache's access log.

Good luck with the bots!

  -Jane

El vie, 19 abr 2024 a la(s) 3:42 a.m., Linda Jansová via Evergreen-general (
evergreen-general@list.evergreen-ils.org) escribió:

> Dear all,
>
> Have any of you encountered an extensive crawling by Bytespider and
> Bytedance (see e.g.,
>
> https://wordpress.org/support/topic/psa-bytedance-and-bytespider-bots-recommend-blocking/),
>
> Claudebot or other AI bots?
>
> If so, do you have any secret recipe how to disable the crawler from
> accessing the site?
>
> Thank you very much for sharing your experience!
>
> Linda
>
> ___
> 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

[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
 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
>
> 
>- Release Notes - 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

[Evergreen-general] Reminder: collaborative code review call today

[Jane Sandberg via Evergreen-general]

Hi Evergreeners,

Friendly reminder that we'll be meeting to review Evergreen pull requests*
at 11am Pacific / 2pm Eastern today.  We'll be at
https://princeton.zoom.us/my/sandbergja.  If you can't make it today, we'll
be meeting every Monday until 3.12 is released, so we can hopefully see you
at a future session!

Everybody is welcome, no matter your experience with Evergreen or its code.

See you there,

  -Evergreen 3.12 release team

* = Pull requests are proposed improvements to Evergreen's code and
documentation
___
Evergreen-general mailing list
Evergreen-general@list.evergreen-ils.org
http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general

[Evergreen-general] Collaborative code review session: next Monday

[Jane Sandberg via Evergreen-general]

Hi Evergreen Community,

With the goal of creating an amazing Evergreen 3.12.0 release, you are
cordially invited to weekly collaborative code review sessions.  In these,
we'll meet for an hour to review recent pull requests
,
read code, run automated tests, try patches out, provide feedback, merge
code that is ready... all the best stuff!

It'll be 11am Pacific / 2pm Eastern on Mondays, starting next Monday,
September 25.  We can meet at https://princeton.zoom.us/my/sandbergja.

All skill levels welcome!  You can join for as many or as few sessions as
you'd like.  If you have submitted a pull request that has been languishing
and needs some review, please bring that along too.  We're going for a fun,
positive, and social tone. :-D

This is not to take the place of any of the other great ways that
developers can get feedback on their work (e.g. bug squashing week, the new
developers working group, typical review process), just a fun supplement.

Hope to see you there,

  -Evergreen 3.12 release team
___
Evergreen-general mailing list
Evergreen-general@list.evergreen-ils.org
http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general

Re: [Evergreen-general] How to make changes to eg_vhost.conf in the Docker container?

[Jane Sandberg via Evergreen-general]

That is very mysterious!

These steps worked for me to add the 950 db seed in French within a docker
container:

docker exec -it [container_name] bash
cd /home/opensrf/repos/Evergreen
make -f Open-ILS/src/extras/Makefile.install ubuntu-focal-translator
su opensrf
cd build/i18n
mkdir locale
make newpot
make LOCALE=fr-CA updatepo
exit # go back to root user
cd /home/opensrf/repos/Evergreen/build/i18n && make LOCALE=fr-CA install
su evergreen
psql -f Open-ILS/src/sql/Pg/950.data.seed-values-fr-CA.sql

El vie, 11 ago 2023 a la(s) 05:51, Linda Jansová (linda.jans...@gmail.com)
escribió:

> Thank you very much, Jane!
>
> We currently use the dev tag (but we may also try some other non-dev tags
> as you have suggested :-); actually, it seems that the language selector in
> the OPAC correctly appears after a couple of reloads, then - for a couple
> of other reloads - it disappears only to appear again after some more
> reloads ;-).
>
> It definitely works in mysterious ways so far; we would probably also need
> to add the 950 db seed with French (and Czech) translations. Any ideas how
> to do this correctly?
>
> Linda
> On 8/11/23 14:25, Jane Sandberg wrote:
>
> Hi Linda,
>
> What tag of the Evergreen container are you using?  I believe that the
> instructions under "Restarting Evergreen services" are only applicable to
> the "dev" tag (i.e. if you ran `docker run
> [...] mobiusoffice/evergreen-ils:dev`).  If you don't specify a tag, it
> defaults to the "latest" tag, which doesn't contain the file-based
> restart/recompile methods.
>
> I typically use the non-dev tags, using the following steps to restart
> apache.  Theoretically, they should work if you are using the dev tag too,
> but I haven't tried them:
>
> 1. docker ps # this will show the name of the running container
> 2. docker exec -it [container_name] bash # this will provide a shell
> within the running container.  For example, if step 1 had mentioned that
> the running Evergreen container is named "peaceful_spence", it would be
> `docker exec -it peaceful_spence bash`
> 3. apache2ctl restart # simply restarts apache. When I need to restart all
> services, I use `ansible-playbook /egconfigs/evergreen_restart_services.yml
> -e hosts="127.0.0.1"` instead.
>
> Hope this helps,
>
>-Jane
>
> El vie, 11 ago 2023 a la(s) 04:28, Linda Jansová via Evergreen-general (
> evergreen-general@list.evergreen-ils.org) escribió:
>
>> Dear all,
>>
>> We have just started experimenting with a Docker container (
>> https://hub.docker.com/r/mobiusoffice/evergreen-ils), mainly to see
>> whether it could help us identify what causes i18n issues reported in a
>> separate thread (with a subject "Evergreen 3.11.0a not properly switching
>> into Czech in the staff client").
>>
>> At this point we are a bit stuck as we would like to make appropriate
>> i18n changes to the eg_vhost.conf file and then make them visible both in
>> the OPAC and in the staff client.
>>
>> We have uncommented lines related to French translation (just to see if
>> it works before we would make a deep dive into Czech) and restarted
>> Evergreen as described at
>> https://hub.docker.com/r/mobiusoffice/evergreen-ils (under the heading
>> "Restarting Evergreen services") but it doesn’t seem to change anything in
>> the OPAC.
>>
>> How exactly should we proceed?
>>
>> (Maybe a more specific piece of documentation that would answer our
>> question is available somewhere; in that case, sharing a URL would be great
>> :-).)
>>
>> Thank you in advance!
>>
>> Linda
>>
>> ___
>> 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] How to make changes to eg_vhost.conf in the Docker container?

[Jane Sandberg via Evergreen-general]

Hi Linda,

What tag of the Evergreen container are you using?  I believe that the
instructions under "Restarting Evergreen services" are only applicable to
the "dev" tag (i.e. if you ran `docker run
[...] mobiusoffice/evergreen-ils:dev`).  If you don't specify a tag, it
defaults to the "latest" tag, which doesn't contain the file-based
restart/recompile methods.

I typically use the non-dev tags, using the following steps to restart
apache.  Theoretically, they should work if you are using the dev tag too,
but I haven't tried them:

1. docker ps # this will show the name of the running container
2. docker exec -it [container_name] bash # this will provide a shell within
the running container.  For example, if step 1 had mentioned that the
running Evergreen container is named "peaceful_spence", it would be `docker
exec -it peaceful_spence bash`
3. apache2ctl restart # simply restarts apache. When I need to restart all
services, I use `ansible-playbook /egconfigs/evergreen_restart_services.yml
-e hosts="127.0.0.1"` instead.

Hope this helps,

   -Jane

El vie, 11 ago 2023 a la(s) 04:28, Linda Jansová via Evergreen-general (
evergreen-general@list.evergreen-ils.org) escribió:

> Dear all,
>
> We have just started experimenting with a Docker container (
> https://hub.docker.com/r/mobiusoffice/evergreen-ils), mainly to see
> whether it could help us identify what causes i18n issues reported in a
> separate thread (with a subject "Evergreen 3.11.0a not properly switching
> into Czech in the staff client").
>
> At this point we are a bit stuck as we would like to make appropriate i18n
> changes to the eg_vhost.conf file and then make them visible both in the
> OPAC and in the staff client.
>
> We have uncommented lines related to French translation (just to see if it
> works before we would make a deep dive into Czech) and restarted Evergreen
> as described at https://hub.docker.com/r/mobiusoffice/evergreen-ils
> (under the heading "Restarting Evergreen services") but it doesn’t seem to
> change anything in the OPAC.
>
> How exactly should we proceed?
>
> (Maybe a more specific piece of documentation that would answer our
> question is available somewhere; in that case, sharing a URL would be great
> :-).)
>
> Thank you in advance!
>
> Linda
>
> ___
> 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] Voluntary Product Accessibility Template (VPAT)

[Jane Sandberg via Evergreen-general]

I agree with Benjamin's overview 100%.  Also, I do think that a formal VPAT
would be a helpful thing for the community to have -- it's an industry
standard for sure.  This has come up in other open source communities
I'm in as well.

I'd gladly participate in a group, or convene one, to create a VPAT and
document the process so that it is repeatable.  Another approach would be
to contract out to a respected accessibility vendor for a VPAT -- I think
this could be valuable to get additional expertise from outside the
community, especially if we could repeat this process on a regular basis
(for example, every other feature release).

El sáb, 10 jun 2023 a la(s) 12:24, Benjamin Kalish via Evergreen-general (
evergreen-general@list.evergreen-ils.org) escribió:

> It's several years out of date, but it looks like the Georgia Center for
> Inclusive Design and Innovation did an Accessibility Evaluation
> 
> of Evergreen in June 2019.
>
> Accessibility has not always been a focus in the community but has been
> getting a lot more love lately and I know some of the problems identified
> in that report have been fixed while others remain.
>
> I'm hoping someone else will chime in if there are more current resources
> we can point you towards.
>
> Benjamin Kalish
> Cataloger / Technology Librarian
> Forbes Library Technical Services
>
> bkal...@forbeslibrary.org
> 413-587-1011
>
> Support Forbes Library:
>
>- Consider giving a gift
> to Forbes Library
>- Vote for the Friends of Forbes in the Florence Bank Community Grant
>Program .
>- Join the Friends of Forbes today 
>!
>
> Currently reading: *Divergence *by C. J. Cherryh
> Just Finished: *Word Nerd: Dispatches from the Games, Grammar, and Geek
> Underground by John D. Williams*
>
> For information about accessibility at the library, please see:
> http://forbeslibrary.org/accessibility/
>
>
> On Tue, Jun 6, 2023 at 8:36 AM PYF HTMLCSS via Evergreen-general <
> evergreen-general@list.evergreen-ils.org> wrote:
>
>> Hi There,
>>
>> I am looking to get evergreen installed in our organization but our IT
>> department requires a VPAT. I was wondering if Evergreen has one?
>>
>> Thanks,
>>
>> - Phil
>> ___
>> 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] [Eg-newdevs] Bug Squashing Week Starts Now!

[Jane Sandberg via Evergreen-general]

Hi all,

Apologies to all testers, and especially to Blake, for that bad patch!
Thanks for tracking down the issue!


   -Jane


On Wed, Mar 1, 2023, 6:54 AM Blake Henderson via Evergreen-general <
evergreen-general@list.evergreen-ils.org> wrote:

> All,
>
> There is something amiss with our bugsquashing server. It's unable to
> create new rows in the database. Which is giving the wrong impression on
> some of these bug tests. I'm investigating.
>
> -Blake-
> Conducting Magic
> Will consume any data format
> MOBIUS
>
> On 2/28/2023 11:49 AM, Mary Llewellyn wrote:
>
> Thanks, Blake! I noticed new records there this morning, very nice.
>
> I'm still unable to add a new fund for my branch, WAKA-LTL. (Wakanda?)
> Can't add a new provider, either.  I'm in with the admin log-in, so this
> was unexpected.
>
> Mary
>
>
> On Tue, Feb 28, 2023 at 12:22 PM Blake Henderson via Evergreen-general <
> evergreen-general@list.evergreen-ils.org> wrote:
>
>> All,
>>
>> Our (MOBIUS) server is ready now. It didn't get finished until later in
>> the day yesterday. For you eager testers that looked yesterday, I want to
>> invite you back to the spreadsheet. It's got the new "Enhanced" Concerto
>> dataset on it as well. (https://bugs.launchpad.net/evergreen/+bug/1901932)
>> Which might help with some of the ACQ stuff.
>>
>> -Blake-
>> Conducting Magic
>> Will consume any data format
>> MOBIUS
>>
>>
>> On 2/27/2023 8:14 AM, Terran McCanna via Eg-newdevs wrote:
>>
>> Hi everyone, and welcome to the first Bug Squashing Week of 2023.
>>
>> There is one test server running current master (3.10+) with a number of
>> proposed bug fixes and features installed on it that are ready for testing,
>> and another test server is currently being built. These test servers have
>> the Concerto data set installed. Details at:
>>
>>
>> https://docs.google.com/spreadsheets/d/1i7CeyfgmlLgWk_3yyqQhK7PR0kMvGVUM5-nEL9BvTNU/edit?usp=sharing
>>
>> Also, please take a look at the links at the top of that page that go to
>> lists of new bugs and wish list requests that have been reported but not
>> yet reviewed and confirmed, and also old bugs that need to be checked to
>> see if they are still valid in the current version or if they have already
>> been resolved (for instance, some of the newer interfaces may have fixed
>> old bugs as part of their development).
>>
>> More general info about adding tags, signing off on fixes, and other bug
>> squashing activities that you can contribute a little of your time to this
>> week are available at:
>> https://wiki.evergreen-ils.org/doku.php?id=dev:bug_squashing
>>
>> Please feel free to contact me directly at tmcca...@georgialibraries.org
>> if you have any questions.
>>
>> Happy Squashing!
>> Terran
>>
>> Terran McCanna, PINES Program Manager
>> --
>>
>> Georgia Public Library Service | University System of Georgia
>>
>> 2872 Woodcock Blvd, Suite 250 l Atlanta, GA 30341
>>
>> (404) 235-7138 | tmcca...@georgialibraries.org
>>
>> http://help.georgialibraries.org | h...@georgialibraries.org
>>
>> 
>> 
>> 
>> 
>>
>> Join our email list  for stories of Georgia
>> libraries making an impact in our communities.
>>
>>
>> ___
>> Eg-newdevs mailing 
>> listEg-newdevs@list.evergreen-ils.orghttp://list.evergreen-ils.org/cgi-bin/mailman/listinfo/eg-newdevs
>>
>>
>> ___
>> Evergreen-general mailing list
>> Evergreen-general@list.evergreen-ils.org
>> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general
>>
>
>
> --
> 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 mailing list
Evergreen-general@list.evergreen-ils.org
http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general

[Evergreen-general] Evergreen 3.10 release candidate available

[Jane Sandberg via Evergreen-general]

Hi colleagues,

The Evergreen Community is pleased to announce the release candidate for
Evergreen 3.10.  This pre-release marks one more step towards the release
of 3.10.0, a major release with numerous new features.  Everyone is
encouraged to test the release candidate and report any issues on the
launchpad bug tracker , so that we
can make 3.10.0 the best that it can be!

A full list of new features can be found in the release notes
.

The Evergreen Community wishes to thank all those who contributed code,
testing, documentation and their time to this release. Thanks to all
members of the community for their hard work to improve Evergreen.

Full information is available on the Evergreen downloads
 page.

Warm regards from the 3.10 release team,

   - Galen Charlton, Michele Morgan, Terran McCanna and Jane Sandberg
___
Evergreen-general mailing list
Evergreen-general@list.evergreen-ils.org
http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general

[Evergreen-general] Reviewing new Evergreen features together

[Jane Sandberg via Evergreen-general]

Hi Evergreen friends,

In anticipation of Evergreen 3.10, I'll be hosting weekly code review
swarms, where we can meet together to review open pull requests in a
collaborative setting!

The first one will be 1pm Pacific/4pm Eastern on Wednesday, October 5 at
https://princeton.zoom.us/my/sandbergja.  I'd like to take a look at Mike
Rylander's new Queued Ingest
 functionality.  It's a
proposed fix for some long-standing performance issues
, and uses some
cool Postgres features that are new to me!

If this intrigues you, please join!  All skill levels welcome; I'm hoping
we can set a fun, positive, and social tone. :-D

If you have other pull requests that you'd like to be reviewed by a swarm
of Evergreeners, let me know, and I can add them to the docket for future
weeks.

  -Jane
___
Evergreen-general mailing list
Evergreen-general@list.evergreen-ils.org
http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general

[Evergreen-general] Moving to a new job

[Jane Sandberg via Evergreen-general]

Hi Evergreeners,

I wanted to let you know that I will be leaving my current position at the
end of the month, for a job as a Ruby programmer at Princeton University
Library.

It has been such a joy to be part of the Evergreen community for the past 8
years.  I'd really like to stay connected -- you can reach me at
sandber...@gmail.com.  Also, I'll still be a patron at an Evergreen
library, so I will still get to use the software a bit, even if it's no
longer my job. :-)

Please let me know if there's anything I can do to help in the next few
weeks, or beyond.  I'm wishing y'all all the best.  Please enjoy this
awesome community and software just a little bit extra on my behalf.

Warmly,

  -Jane

-- 
Jane Sandberg
Electronic Resources Librarian
Library Department Chair
Linn-Benton Community College
sand...@linnbenton.edu / 541-917-4655
Pronouns: she/her/hers

Library instagram: @lbcc_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] [Evergreen-documentation] Automating Antora documentation builds on GitLab

[Jane Sandberg via Evergreen-general]

For what it is worth, I have a pull request to do something similar for
Github, using the existing generate_docs script:
https://bugs.launchpad.net/evergreen/+bug/1903476

Whether on Github or Gitlab, I am very supportive of using these CI tools
to simplify our workflows.

On Thu, Dec 30, 2021 at 10:06 AM Floyd, Angelia Lynn via
Evergreen-documentation 
wrote:

> As I like this concept and the lowering of the bar for edits, my main
> concern is that we currently have people adding docs two different ways.
>
>1. Straight to the working Git Repo
>2. Via GitHub
>
>
>
> Will the use of GitLab incorporate both of these methods for adding docs?
>
>
>
> I think definitely a further discussion on this process and how to best
> use it at the next DIG meeting is a must.
>
>
>
> -
> Lynn Floyd
> MIS Supervisor
>
> Indiana State Library
> 317-232-3290
> lflo...@library.in.gov
>
>
>
> *From:* Evergreen-general <
> evergreen-general-boun...@list.evergreen-ils.org> *On Behalf Of *Dan
> Scott via Evergreen-general
> *Sent:* Thursday, December 30, 2021 11:45 AM
> *To:* evergreen-general@list.evergreen-ils.org
> *Subject:* Re: [Evergreen-general] Automating Antora documentation builds
> on GitLab
>
>
>
>  This is an EXTERNAL email. Exercise caution. DO NOT open attachments
> or click links from unknown senders or unexpected email. 
> --
>
> I took things a little further today.
>
>
>
> The GitLab docs build now includes the Evergreen CSS, header, and footer.
> The UI bundle is currently sourced from a pinned job from an automated
> build of the "evergreen" branch of the Antora default UI (
> https://gitlab.com/denials/antora-ui-default/-/tree/evergreen [1]) I set
> up.
>
>
>
> The UI bundle is currently in my GitLab namespace for testing purposes but
> it would be easy to move the repository to GitLab's
> evergreen-library-system group. I suggest mirroring the
> Antora/antora-ui-default main branch (GitLab makes mirroring trivial) and
> keeping our customizations in an "evergreen" branch to avoid merge hassles,
> etc.
>
>
>
> If we were willing to rely on GitLab's automated builds, we could remove
> docs/generate_docs.pl
> 
> and replace docs/site.yml. We wouldn't need to maintain a special server to
> build and serve the Evergreen documentation. We could even have GitLab
> serve up the docs.evergreen-ils.org
> 
> domain, given that Evergreen 3.6 marks the first Antora-based documentation
> and is currently in "only security fix mode". Or we could continue to serve
> up docs.evergreen-ils.org
> 
> on our own server along with the legacy docs by automating the downloading
> & unzipping of the artifacts bundle (all the HTML/CSS/JS/media) GitLab
> creates with each build.
>
>
>
> Depending on how far we wanted to go with GitLab integration, we could
> also unhide the "Edit this page" link on every page of the Evergreen
> documentation that leads to the corresponding file in the GitLab repository
> and the web IDE. That might be a lower bar for basic documentation
> contributions (e.g. fixing typos or adding a clarification) than our
> current footer's suggestion to email the DIG list (which, based on the list
> archives, doesn't seem to be attracting many contributions). Edits made via
> the Web IDE create a merge request (& potentially a branch) per
> https://docs.gitlab.com/ee/user/project/web_ide/#commit-changes so
> contributors wouldn't have to learn git mechanics to edit existing files.
>
>
>
> On Wed, 29 Dec 2021 at 14:30, Dan Scott  wrote:
>
> I was exploring GitLab's CI/CD (continuous integration / delivery)
> functionality last night/this morning and decided to try building our
> Antora-based documentation this way with the output hosted on GitLab Pages.
>
>
>
> It works quite nicely. I've posted a rough implementation branch at
> https://gitlab.com/evergreen-library-system/evergreen-library-system/-/commits/gitlab-antora-build
>
>
>
> As you can see, it's just a couple of YAML files; .gitlab-cy.yml defines
> the "pages" step, and .gitlab-antora.yml defines a custom Antora playbook
> for the Docker environment. The CI/CD piece means that a new build would be
> triggered by every commit.
>
>
>
> The output is visible at
> https://evergreen-library-system.gitlab.io/evergreen-library-system/docs/latest/index.html
> 

[Evergreen-general] "Default phone" required field in the patron edit screen

[Jane Sandberg via Evergreen-general]

Hi Evergreeners,

We just upgraded from 3.4 to 3.7, and are running into bug 1901726
.  Basically, when we go
to edit any of our patrons, there is a field called "Default phone number",
which is now required.  It's almost always empty, meaning we can't save the
form until we fiddle with it.

It's frustrating that we have to fiddle with this field before making any
changes to patron records.  Are there any workarounds that your libraries
are using to reduce this frustration?

  -Jane

-- 
Jane Sandberg
Electronic Resources Librarian
Linn-Benton Community College
sand...@linnbenton.edu / 541-917-4655
Pronouns: she/her/hers

Library instagram: @lbcc_library 
___
Evergreen-general mailing list
Evergreen-general@list.evergreen-ils.org
http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general