- Evergreen-dev - example.com

3.15 Feature Slush
by Andrea Buntz Neiman 18 Mar '25

18 Mar '25

Hi Community! (Belatedly) announcing the 3.15 Feature Slush. All wishlist items for 3.15-beta should have a pullrequest on them at this point. There are 37 wishlist items targeted for 3.15-beta, and 20 of them are still awaiting commit. Of those 20, 9 are signed off. https://docs.google.com/spreadsheets/d/1xodq5mLdU7Cjlw-gi8KYAyI6wmfGKRYUE7L… If you are a tester or core committer, please take some time this week and early next week to review outstanding wishlist items and commit them if you can! Feature freeze is currently scheduled for next Tuesday, March 18th. There's some great features both large and small lined up for 3.15 and it would be great to get as many of them in the 3.15 pipeline as possible. Thanks for your assistance, 3.15 Release Team Andrea Buntz Neiman Ruth Frasur Davis Martha Driscoll Jason Etheridge Llewellyn Marshall Gina Monti -- Andrea Buntz Neiman, MLS (she/her) Project Manager for Software Development | Product Specialist Equinox Open Library Initiative abneiman(a)equinoxOLI.org <abneiman(a)equinoxoli.org> 1-877-OPEN-ILS (673-6457) Direct: 770-709-5583 *https://www.equinoxOLI.org/ <https://www.equinoxOLI.org/>*

1 1

Re: Register to Vote in the Evergreen Project Board 2025 Election!
by Susan Morrison 18 Mar '25

18 Mar '25

Good Morning, This is the last day to register to vote for the Evergreen Project Board 2025 Election. Anyone who has contributed to Evergreen or is employed by an institution that runs Evergreen is eligible to vote. Please register to vote here: https://docs.google.com/forms/d/e/1FAIpQLScmJZ5m4VIwMUUqE21czKTAwnpM8RQKXTn… Information on the Evergreen Project Board and its function in the community can be found here: https://evergreen-ils.org/governance/. Feel free to contact me or any board member with questions about the board or the election process. Thank you! Susan, on behalf of the Evergreen Project Board On Tue, Feb 25, 2025 at 12:15 PM Susan Morrison < smorrison(a)georgialibraries.org> wrote: > Voter registration for the Evergreen Project Board 2025 Election is now > open. Anyone who has contributed to Evergreen or is employed by an > institution that runs Evergreen is eligible to vote. > > > Please register to vote here: https://forms.gle/BtofiUqeTpoCtRmm8 > > > Voter registration will end on March 18th. The election will begin on > March 25th and end on April 8th. If you are registered, you will receive an > email from Opavote.com with information on how to cast your vote. > Candidates will be announced before voting begins. > > > Information on the Evergreen Project board and its function in the > community can be found here: https://evergreen-ils.org/governance/ > > > Feel free to contact me or any board member with questions about the board > or the election process. > > > Susan, on behalf of the Evergreen Project Board > > -- > > [image: logo with link to Georgia Public Library Service website] > <https://georgialibraries.org/> > > Susan Morrison, PINES Operations Analyst > > ------------------------------ > > Georgia Public Library Service > > 2872 Woodcock Blvd, Suite 250 | Atlanta, GA 30341 > > (404) 235-7142 | smorrison(a)georgialibraries.org > > https://help.georgialibraries.org | help(a)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/> Susan Morrison, PINES Operations Analyst ------------------------------ Georgia Public Library Service 2872 Woodcock Blvd, Suite 250 | Atlanta, GA 30341 (404) 235-7142 | smorrison(a)georgialibraries.org https://help.georgialibraries.org | help(a)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.

1 0

Re: RFC: developer checklist for adding tables and columns to Evergreen
by Terran McCanna 17 Mar '25

17 Mar '25

Thank you for this, Galen! I have taken the liberty of copying it into the wiki here: https://wiki.evergreen-ils.org/doku.php?id=newdevs:checklist:tables-columns where it can be further edited / added to. On Mon, Feb 10, 2025 at 1:04 PM Galen Charlton via Evergreen-dev < evergreen-dev(a)list.evergreen-ils.org> wrote: > Hi, > > Inspired by a couple recent bugs, I've drafted a developer checklist for > adding tables and columns to the Evergreen database > <https://docs.google.com/document/d/1Wf3G3SrfkwvY0N3oqUrrZKBv-UbhsWX6S7okhDO…>. > When finalized, this is meant for the wiki or some other spot for > development writings. > > Please feel free to comment via this email thread or as comments in the > Google document. I note that the references to "thoughtfully" and > "appropriate" are meant to be supplemented over time with links providing > more details to guide judgement calls. > > Regards, > > Galen > -- > Galen Charlton > Implementation and IT Manager > Equinox Open Library Initiative > gmc(a)equinoxOLI.org > https://www.equinoxOLI.org > phone: 877-OPEN-ILS (673-6457) > direct: 770-709-5581 > <http://evergreen-ils.org> > _______________________________________________ > Evergreen-dev mailing list > Evergreen-dev(a)list.evergreen-ils.org > http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-dev >

1 0

Git server reboot tonight at 9:00 PM EDT
by Jason Stephenson 12 Mar '25

12 Mar '25

Hello, all. The community git server (git.evergreen-ils.org) will be rebooted at 9:00 PM EDT, 6:00 PM PDT today. This is 2025-03-13 01:00 UTC. This is being done as part of regular server maintenance and updates. Cheers, Jason Stephenson

1 0

Re: Register to Vote in the Evergreen Project Board 2025 Election!
by Susan Morrison 11 Mar '25

11 Mar '25

A friendly reminder that voter registration for the Evergreen Project Board 2025 Election is open. Anyone who has contributed to Evergreen or is employed by an institution that runs Evergreen is eligible to vote. Please register to vote here: https://forms.gle/BtofiUqeTpoCtRmm8 Voter registration will end on March 18th. Information on the Evergreen Project board and its function in the community can be found here: https://evergreen-ils.org/governance/ Feel free to contact me or any board member with questions about the board or the election process. Susan, on behalf of the Evergreen Project Board On Tue, Feb 25, 2025 at 12:15 PM Susan Morrison < smorrison(a)georgialibraries.org> wrote: > Voter registration for the Evergreen Project Board 2025 Election is now > open. Anyone who has contributed to Evergreen or is employed by an > institution that runs Evergreen is eligible to vote. > > > Please register to vote here: https://forms.gle/BtofiUqeTpoCtRmm8 > > > Voter registration will end on March 18th. The election will begin on > March 25th and end on April 8th. If you are registered, you will receive an > email from Opavote.com with information on how to cast your vote. > Candidates will be announced before voting begins. > > > Information on the Evergreen Project board and its function in the > community can be found here: https://evergreen-ils.org/governance/ > > > Feel free to contact me or any board member with questions about the board > or the election process. > > > Susan, on behalf of the Evergreen Project Board > > -- > > [image: logo with link to Georgia Public Library Service website] > <https://georgialibraries.org/> > > Susan Morrison, PINES Operations Analyst > > ------------------------------ > > Georgia Public Library Service > > 2872 Woodcock Blvd, Suite 250 | Atlanta, GA 30341 > > (404) 235-7142 | smorrison(a)georgialibraries.org > > https://help.georgialibraries.org | help(a)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/> Susan Morrison, PINES Operations Analyst ------------------------------ Georgia Public Library Service 2872 Woodcock Blvd, Suite 250 | Atlanta, GA 30341 (404) 235-7142 | smorrison(a)georgialibraries.org https://help.georgialibraries.org | help(a)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.

1 1

Developer Meeting Reminder -- Today, 3PM EDT
by Shula Link 11 Mar '25

11 Mar '25

Good morning! A reminder about the developer meeting *today*, 11 March 2025, at 3:00pm *EDT* in the #evergreen IRC chat. IRC Access is available through Libera via this link <https://web.libera.chat/#evergreen>. Agenda is available here <https://wiki.evergreen-ils.org/doku.php?id=dev:meetings>. Thanks! Shula Link (she/her) Systems Services Librarian Greater Clarks Hill Regional Library slink(a)columbiacountyga.gov | slink(a)gchrl.org 706-447-6702

1 0

3.15 Feature Slush - Wednesday March 12
by Andrea Buntz Neiman 10 Mar '25

10 Mar '25

Hello Evergreen, Apologies for the cross posting. Feature Slush for Evergreen 3.15 is this *Wednesday, March 12th*. Feature slush means "any features intended for this release should be finished & pullrequested." Bugfixes can still go in through 3.15-beta, which is still a couple weeks away. So, if you've got a feature close to completion, now's the time to get your branch out there! Next week *Tuesday, March 18th* is Feature Freeze / String Freeze / Translation String Slush. This means "no more feature merges after this date; minimize string [i.e. word/label] changes." So any of those pullrequested features must be merged before next Tuesday. There's a lot of good stuff pending for 3.15-beta already, so if you are a tester or a committer please take a look at this list and see what you can move along: Bugs currently tagged as "Wishlist" and targeted for 3.15-beta <https://bugs.launchpad.net/evergreen/+bugs?field.searchtext=&orderby=-impor…> Thanks on behalf of the release team, Andrea Buntz Neiman Ruth Frasur Davis Martha Driscoll Jason Etheridge Llewellyn Marshall Gina Monti -- Andrea Buntz Neiman, MLS (she/her) Project Manager for Software Development | Product Specialist Equinox Open Library Initiative abneiman(a)equinoxOLI.org <abneiman(a)equinoxoli.org> 1-877-OPEN-ILS (673-6457) Direct: 770-709-5583 *https://www.equinoxOLI.org/ <https://www.equinoxOLI.org/>*

1 0

Developer Meeting -- Tomorrow
by Shula Link 10 Mar '25

10 Mar '25

Good morning! A reminder about the developer meeting tomorrow, 11 March 2025, at 3:00pm EST in the #evergreen IRC chat. IRC Access is available through Libera via this link <https://web.libera.chat/#evergreen>. Agenda is available here <https://wiki.evergreen-ils.org/doku.php?id=dev:meetings>. Thanks! Shula Link (she/her) Systems Services Librarian Greater Clarks Hill Regional Library slink(a)columbiacountyga.gov | slink(a)gchrl.org 706-447-6702

1 0

Proposal for a Comprehensive Fix to Shared Address Issues in Evergreen
by Ian Skelskey 28 Feb '25

28 Feb '25

Dear Evergreen Developers, While executing a patron purge initiative at Bibliomation, I encountered an issue related to shared addresses that prevented some deletions from completing. I was able to work around the issue, but I believe a more permanent fix should be implemented to prevent similar problems in the future. I decided to share this as an email because it's a bit long and is easier to read with some shiny formatting that isn't possible on Launchpad. The root cause, as outlined in Bug #885270 <https://bugs.launchpad.net/evergreen/+bug/885270>, is that cloned patrons historically shared the same address row in the database. When attempting to delete a patron whose address is still referenced by another user, the process fails. Over the years, multiple solutions have been introduced to mitigate this issue, but they remain somewhat fragmented and the bug ticket remains open. *Summary of Fixes Implemented So Far* 1. *Library Setting: "Cloned patrons get address copy"* - When enabled, this setting ensures newly cloned patrons receive a separate address entry rather than sharing the original. - However, this only prevents new instances of the issue and does not fix pre-existing shared addresses. 2. *fix_addresses.sql <https://bugs.launchpad.net/evergreen/+bug/885270/+attachment/4112365/+files…> Script (shared by Jason Boyer)* - This script untangles shared addresses by duplicating them, ensuring each patron has a unique address entry. - It serves as a one-time fix for existing shared addresses but does not enforce consistent behavior moving forward. 3. *Address Deletion Failure* - The actor.usr_purge_data function currently attempts to delete all addresses linked to a user, which fails if the address is still referenced elsewhere. - A fail-safe could be added to prevent deletion if the address is still associated with another patron. *Proposed Next Steps**1. Make Cloning Behavior Consistent* - Remove the "Cloned patrons get address copy" setting and enforce the creation of separate address entries for all cloned patrons by default. - No use case seems to require shared addresses, and maintaining this setting prolongs potential inconsistencies. - Can anyone think of a use case where shared addresses would be helpful? - Does anyone have that setting set to *false*? *2. Database Migration Fix* - The fix_addresses.sql script should be incorporated into a future database upgrade process to automatically separate any remaining shared addresses. *3. Modify actor.usr_purge_data to Handle Shared Addresses Gracefully* - Instead of failing outright when trying to delete a shared address, modify the function to ensure the address is not deleted if still referenced. A log message can be added to report any cases where the issue persists. - SELECT COUNT(*) INTO shared_address_count FROM actor.usr u WHERE (u.mailing_address = actor.usr_address.id OR u.billing_address = actor.usr_address.id) AND u.id != src_usr; IF shared_address_count > 0 THEN RAISE NOTICE 'Address shared by another patron, not deleting address for user %', src_usr; ELSE DELETE FROM actor.usr_address WHERE usr = src_usr; END IF; - This adjustment ensures the deletion process continues rather than throwing an error while preserving shared addresses when necessary. *Next Steps & Feedback* Would the community support moving forward with this approach? If there’s consensus, I’d be happy to contribute toward implementing these updates. Looking forward to your thoughts! -- Best regards, *Ian Skelskey* *Evergreen Systems Specialist* *Bibliomation Inc.* 203-577-4070 <+12035774070> ext. 108

3 2

Re: [Eg-newdevs] Proposal: new angular components should be standalone
by Mike Rylander 28 Feb '25

28 Feb '25

I also agree with Galen's framing. Standalone components will definitely make the simple generic components easier to use, I think, but NgModules will still be useful for encapsulation in some important cases. Thanks, all! -- Mike Rylander Research and Development Manager Equinox Open Library Initiative 1-877-OPEN-ILS (673-6457) work: miker(a)equinoxOLI.org personal: mrylander(a)gmail.com https://equinoxOLI.org On Thu, Feb 27, 2025 at 5:26 PM Jane Sandberg via Eg-newdevs <eg-newdevs(a)list.evergreen-ils.org> wrote: > > +1 from me to Galen's formulation! Thanks for the discussion so far, Galen and Ruth! > > El jue, 27 feb 2025 a la(s) 1:02 p.m., Galen Charlton (gmc(a)equinoxoli.org) escribió: >> >> Hi, >> >> On Thu, Feb 27, 2025 at 9:10 AM Jane Sandberg via Eg-newdevs <eg-newdevs(a)list.evergreen-ils.org> wrote: >> > But my proposal is that after a certain date TBD, if you create a new component, please make it standalone. >> >> I think this is too strong at present until we collectively get more experience with standalone components. While the standalone model does look useful - and of course, in the long run it does not pay for us to try to buck what's a very clear trend in Angular's evolution - we do have several sets of closely-linked components where keeping them bundled in an NgModule may still make sense (e.g., eg-grid). I fear that - for now - setting an absolute requirement that new components be standalone may reduce flexibility and create an implicit expectation that we _must_ perform (and pay for in various ways) what would be a large refactoring of the existing NgModule-based app. >> >> Consequently, I would propose a different formulation in two parts: >> >> * Writing new Angular components as standalone is both permitted and encouraged >> * After more time has passed and we have more experience with wrestling with the management of dependencies for standalone components, we'll reevaluate whether a stricter mandate is warranted. >> >> By the way, I found this piece an interesting exploration of the opportunities and tradeoffs: https://borstch.com/blog/development/angulars-ngmodules-vs-standalone-compo… >> >> Regards, >> >> Galen >> -- >> Galen Charlton >> Implementation and IT Manager >> Equinox Open Library Initiative >> gmc(a)equinoxOLI.org >> https://www.equinoxOLI.org >> phone: 877-OPEN-ILS (673-6457) >> direct: 770-709-5581 > > _______________________________________________ > Eg-newdevs mailing list > Eg-newdevs(a)list.evergreen-ils.org > http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/eg-newdevs

1 0