Evergreen ILS Website

IRC log for #evergreen, 2025-01-14

| Channels | #evergreen index | Today | | Search | Google Search | Plain-Text | summary | Join Webchat

All times shown according to the server's local time.

Time Nick Message
00:50 Bmagic joined #evergreen
00:50 dluch joined #evergreen
00:50 Jaysal joined #evergreen
00:50 scottangel joined #evergreen
01:50 jonadab joined #evergreen
03:12 dluch joined #evergreen
07:23 collum joined #evergreen
08:43 mmorgan joined #evergreen
08:46 dguarrac joined #evergreen
09:05 mantis1 joined #evergreen
09:40 Dyrcona joined #evergreen
09:42 csharp_ @band add Vanilla Server
09:42 pinesol csharp_: Band 'Vanilla Server' added to list
09:53 mantis1 Does anyone use Long Overdue?
10:02 * csharp_ raises hand on behalf of PINES
10:03 csharp_ mantis1: I'm in a meeting, but ask your question and I'll see if I can help
10:06 mantis1 I'm trying to do some testing with it.  We never tried it before.  I just wanted to see if anyone has an example of their AT for it.
10:06 mantis1 I guess that isn't really a question
10:08 Christineb joined #evergreen
10:17 Bmagic mantis1: the first thing to know about Long Overdues is that it's the exact same thing as LOST. It just results in a different status for the item. Some people like the word "Long Overdue" instead of LOST. In it's current implementation, it's not possible to also have LOST AT setup.
10:18 mantis1 ok so it's either one or the other is what you're saying Bmagic?
10:18 Bmagic A LOST AT trigger won't react to a circulation that was previously marked Long Overdue
10:18 mantis1 that probably explains why I'm not returning anything
10:18 mantis1 ok thank you so much
10:18 mantis1 Bmagic++
10:20 Bmagic I created a branch that allows the LOST AT to react to a previously-marked Long Overdue. It's a bit crusty, and none of our libraries are using it at this time: bug 1331174
10:20 pinesol Launchpad bug 1331174 in Evergreen "Long Overdue processing needs org unit settings separate from Lost Processing" [Wishlist,Confirmed] https://launchpad.net/bugs/1331174
10:21 mantis1 Bmagic: I can look at it since we're testing now
10:21 mantis1 thank you though!
10:21 Bmagic mantis1++
10:29 mantis1 Should the docs be changed to reflect this?  There just isn't anything in there right now.
10:29 mantis1 *that at least explains the situation with the bug
10:32 Bmagic I think it was a difference of view. When Long Overdue was introduced into Evergreen, the feature was described and written from a certain point of view. And it was clear to all parties. I think once it became public, it was easy to misunderstand the feature. A lot of people saw it as a way to alert the patron as well as change the status, but not bill them. Then, at a later time, mark it LOST. That's not what it's for (today).
10:33 Bmagic Unless I'm living in the past, and it's changed since then? Does the docs say that LOST reactors will react to long overdue?
10:34 mantis1 https://docs.evergreen-ils.org/docs/​latest/circulation/circulating_items​_web_client.html#_long_overdue_items
10:35 mantis1 I don't think I see anything about it
10:41 mmorgan mantis1 we use Long Overdue and Lost, but have to cheat with database updates to convert LOD to Lost.
10:41 mmorgan Long overdue at 42 days, Lost at 1 year.
10:43 * mmorgan should dust the cobwebs off of bug 1562061
10:43 pinesol Launchpad bug 1562061 in Evergreen "Marking a Long Overdue transaction Lost adds a second bill to the patron record" [Medium,Confirmed] https://launchpad.net/bugs/1562061
10:52 sandbergja joined #evergreen
10:57 mantis1 I'll bring the Long Overdue question to DIG
10:57 mantis1 in regards to the docs
10:57 mantis1 and mmorgan that's a great workaround
10:57 mantis1 mmorgan++
10:57 Bmagic I think that's a good move. The docs should make that clear
10:59 jihpringle joined #evergreen
11:20 Dyrcona Well, it depends on your configuration, and I don't think you're generally expected to use both Lost and Long Overdue.
11:36 mantis1 right now, we have interest in having a 'purgatory' status for items in between overdue and lost just because there's an influx of libraries wanting to go fine free with aggressive overdues
11:36 mantis1 at least I think some of the overdues they want to implement are pretty aggressive rules
11:42 csharp_ @band add Becord Ruckets
11:42 pinesol csharp_: Band 'Becord Ruckets' added to list
11:42 Dyrcona Yes, I can see an argument for using the two as distinct "statuses," but the circulation table isn't really set up that way as far as stop_fines goes. They always seemed like near synonyms to me.
11:43 Bmagic That bug I linked had a branch that made evergreen work that way.
11:43 Dyrcona Well, you can always push it. :)
11:44 Dyrcona IIRC, Long Overdue was something from III that a migrating library wanted to bring over, but I could be mistaken.
11:44 Bmagic It's like 5 years old now. Probably doesn't merge, and would need to be updated to play nice with some of the new YOUS probably
11:44 mantis1 that's a III thing?
11:44 mantis1 interesting
11:52 Dyrcona Bmagic: It definitely needs a rebase. The "first" commit conflicts with fm_IDL.xml, items.adoc, andOpenILS/Const.pm.
11:53 Dyrcona Most of the code still applies, so that's nice.
12:04 jihpringle26 joined #evergreen
12:17 Bmagic I'm having fun asking Evergreen to export a 32k bib file via the staff client. It's working, but I'm noticing that Firefox is taking huge amounts of memory while the Javascript is capturing the server's data. No file is being downloaded yet, it seems it's coded to store it in the browser cache until the stream is complete. In this case, 32k bibs, is taking over 20GB of memory on my computer. Windows, sometimes, decides to kill the
12:17 Bmagic browser when it's had enough, and sometimes, it finishes and the browser delivers a file
12:18 Bmagic the filesize is only 65megs if it completes. What's up with 20+GB of memory getting used during the process?
12:20 JBoyer What ui are you using? Short of preparing and sendnig the request, "JavaScript" shouldn't be involved in a file download in any way.
12:21 Bmagic marc import/export
12:25 Bmagic fed it a csv on the interface, with 32k lines of bib ID's
12:28 Dyrcona Bmagic: Have you tried it with Chrome? Maybe V8 is more efficient than Spider Monkey? But honestly, I'd just export it on the server with marc_export.
12:28 Bmagic I was thinking that too. I'll see if Chrome makes a difference
12:33 JBoyer Though now that I look at it, I expect something like this: saveAs(new Blobl([evt.body as Blob]...) to require ram at least 2x the size of the file, and that's ideal; I suspect it's more. (not multiple thousands of times though)
14:04 mdriscoll joined #evergreen
14:10 eby Dyrcona: yeah we are one that uses both status as distinct. Lost means a patron told us they lost it/take responsibility and Long Overdue means we automatically billed them for it. Helps with some interactions, ordering, notice wording, etc. Long overdue are more likely to show up after billing than lost.
14:11 redavis joined #evergreen
14:13 mmorgan We have our Lost status set as not OPAC visible, but Long Overdue is OPAC visible. So Long Overdue items (due 42 days to 1 year ago) are visible to patrons, but Lost (due more than 1 year ago) are not visible to patrons.
14:13 mmorgan Lots of Long Overdue items come back. Lost, not nearly as many.
14:14 mdriscoll joined #evergreen
14:15 Dyrcona eby: The way you describe it being used makes a lot of sense.
14:15 mdriscoll87 joined #evergreen
14:18 mdriscoll joined #evergreen
14:20 eby holds aren't as hopeless with long overdue
14:22 mmorgan eby: Indeed! We have Long Overdue as a holdable status.
14:31 shulabramble joined #evergreen
14:31 shulabramble 29 minutes to the hottest ticket in town; the first developers meeting of 2025!
14:47 redavis shulabramble++
14:50 Stompro joined #evergreen
14:56 shulabramble Five minutes to dev meeting; this is your bathroom break reminder.
14:56 berick shulabramble++
14:56 * berick makes tea
14:57 tslittle joined #evergreen
14:57 jvwoolf joined #evergreen
14:57 terranm joined #evergreen
14:57 collum joined #evergreen
14:59 shulabramble ~60 seconds to meeting
14:59 mdriscoll joined #evergreen
15:00 shulabramble #startmeeting 2025-01-14 - Developer Meeting
15:00 pinesol Meeting started Tue Jan 14 15:00:03 2025 US/Eastern.  The chair is shulabramble. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00 pinesol Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00 pinesol The meeting name has been set to '2025_01_14___developer_meeting'
15:00 shulabramble #topic Introductions
15:00 shulabramble #info shulabramble = Shula Link, GCHRL
15:00 redavis #info redavis = Ruth Frasur Davis, ECDI
15:00 phasefx @info phasefx = Jason Etheridge, EOLI
15:00 pinesol phasefx: (info <url|feed>) -- Returns information from the given RSS feed, namely the title, URL, description, and last update date, if available.
15:00 terranm #info terranm = Terran McCanna, PINES
15:01 collum #info collum = Garry Collum,  KCPL
15:01 mmorgan #info mmorgan = Michele Morgan, NOBLE
15:01 phasefx #info phasefx = Jason Etheridge, EOLI :-)
15:01 sleary #info sleary = Stephanie Leary, EOLI
15:01 eeevil #info eeevil = Mike Rylander, EOLI
15:02 Bmagic #info Bmagic = Blake GH, MOBIUS
15:02 berick #info berick Bill Erickson, KCLS
15:02 sandbergja #info sandbergja = Jane Sandberg, PUL
15:02 Dyrcona #info Dyrcona = Jason Stephenson, C/W MARS
15:02 abneiman #info abneiman = Andrea Buntz Neiman, EOLI
15:03 shulabramble People can continue to introduce themselves as they file in. :)
15:04 shulabramble #topic Action Items from Last Meeting
15:04 shulabramble #topic eeevil will open a bug for cross-column stats targets
15:04 eeevil I'm sure he will ... one day!
15:04 eeevil but today is not that day
15:04 jeff #info jeff = Jeff Godin, Traverse Area District Library (TADL)
15:04 shulabramble can kicked!
15:04 shulabramble #action eeevil will open a bug for cross-column stats targets
15:04 jeff (missed it by THAT much)
15:04 shulabramble #topic gmcharlt - create a Git commit message type and update bug 2051946
15:04 pinesol Launchpad bug 2051946 in Evergreen "institute a Git commit message template" [Wishlist,New] https://launchpad.net/bugs/2051946 - Assigned to Galen Charlton (gmc)
15:05 shulabramble is gmcharlt around, or should we just put both of his action items off for another month?
15:05 abneiman I don't think he's around for this meeting
15:06 shulabramble does anyone want to reach out to him about this or POEditor access?
15:07 Dyrcona The thing about POEditor is gmcharlt is apparently the only one who can do it. According to POEditor, it has to be the project owner who sets up git integration.
15:07 shulabramble dyrcona++
15:07 abneiman I will reach out to him
15:07 shulabramble abneiman++
15:07 mmorgan abneiman++
15:07 abneiman he has been poked
15:08 shulabramble #action abneiman will reach out to gmcharlt concerning bug 2051946 and POEditor git integration
15:08 pinesol Launchpad bug 2051946 in Evergreen "institute a Git commit message template" [Wishlist,New] https://launchpad.net/bugs/2051946 - Assigned to Galen Charlton (gmc)
15:08 shulabramble #action sleary and sandbergja will report progress on test writing wiki pages next month
15:08 sleary carry over, please! sorry to keep kicking this down the road
15:08 shulabramble that's fine! I mistyped so it's already kicked :)
15:09 sleary :)
15:09 shulabramble #topic sleary will make a new LP tag denoting bugs that involve string changes
15:09 sleary whoops, that slipped my mind. Will do it this afternoon
15:09 shulabramble #action sleary will make a new LP tag denoting bugs that involve string changes
15:09 shulabramble sleary++
15:09 shulabramble #topic sandbergja and sleary will revisit feasibility of automated testing for string changes
15:10 sandbergja also please carry over!
15:10 sleary second verse, same as the first
15:10 shulabramble #action sandbergja and sleary will revisit feasibility of automated testing for string changes
15:10 shulabramble #topic abneiman will poll concerning moving the developer's meeting from IRC to a different platform
15:10 abneiman ask not for whom the can kicks
15:10 abneiman it kicks for thee!
15:10 terranm lol
15:11 Dyrcona Heh
15:11 berick heh
15:11 redavis lol!
15:11 sandbergja hahaha
15:11 shulabramble abneiman++
15:11 shulabramble world class can punter
15:12 shulabramble #action abneiman will poll concerning moving the developer's meeting from IRC to a different platform
15:12 shulabramble #topic Updates
15:12 redavis Evergreen - Monthly maintenance releases for 3.13.8 and 3.14.3 are in process right now. They're due out tomorrow, but it will likely be Thursday, January 16 before they're announced.
15:12 shulabramble redavis++
15:12 terranm maintenance_release_team++
15:13 abneiman and 3.15 has a schedule up and team meetings have commenced! https://wiki.evergreen-ils.org/do​ku.php?id=faqs:evergreen_roadmap
15:13 redavis abneiman++
15:13 shulabramble abneiman++ 3.15_release_team++
15:13 abneiman please populate roadmap if you have features: https://wiki.evergreen-ils.org/doku​.php?id=faqs:evergreen_roadmap:3.15
15:13 Dyrcona redavis++
15:13 abneiman redavis++
15:14 shulabramble Anything for docs?
15:14 redavis Not sure if this is the place for it, but there will be a bugsquash week at the end of the month for 3.15 facilitated by the intrepid terranm
15:15 shulabramble #info Evergreen - Monthly maintenance releases for 3.13.8 and 3.14.3 are in process right now. They're due out tomorrow, but it will likely be Thursday, January 16 before they're announced.
15:15 mmorgan terranm++
15:15 shulabramble #info 3.15 has a schedule up and team meetings have commenced!
15:15 redavis (sorry...typed too slow to get it into the 3.15 release update
15:15 shulabramble terranm++
15:15 redavis terranm++
15:15 shulabramble #info 3.15 -- please populate roadmap if you have features
15:15 abneiman terranm++ # hooray for BSW
15:15 terranm bugsquash for all the things Jan 27-31, feedback fest for 3.15 March 31-April 4
15:17 shulabramble #info BSW at the end of the month
15:17 shulabramble #info BSW Jan 27-31
15:17 shulabramble #info Feedback Fest for 3.15 March 31 - April 4
15:17 shulabramble If that's it for updates, then prepare thyself for Wall O' Text
15:17 shulabramble #topic Launchpad Status (as of noon Eastern)
15:17 shulabramble #topic Snapshot
15:17 shulabramble #info Open Bugs - 3198
15:17 shulabramble #info Pullrequests - 99
15:17 shulabramble #info Signedoff - 5
15:17 shulabramble #info Needswork - 85
15:17 shulabramble #info Needstestplan - 2
15:17 shulabramble #info Needsrebase - 24
15:17 shulabramble #topic Updates Since Last Meeting
15:17 shulabramble #info Bugs Added - 66
15:17 shulabramble #info Pullrequest tag Added - 18
15:17 shulabramble #info Signedoff tag Added - 13
15:17 shulabramble #info Needswork tag Added - 1
15:17 shulabramble #info Needstestplan tag Added - 0
15:17 shulabramble #info Needsrebase tag Added - 1
15:17 shulabramble #info Fix Committed - 20
15:18 shulabramble #topic New Business
15:18 shulabramble There's nothing on the agenda, but is there anything that needs discussion?
15:19 shulabramble Are we about to have a meeting clock in at under 25 minutes?
15:19 jeff berick++ for a successful and uneventful update to the Hatch Chrome Extension
15:19 redavis daaaaaahhhng
15:19 terranm berick++
15:19 sleary berick++
15:19 mmorgan berick++
15:19 shulabramble berick++ yes, that was so painless I don't think anyone noticed.
15:19 mmorgan jeff++
15:19 collum berick++
15:20 shulabramble jeff++
15:20 collum jeff++
15:20 redavis berick++
15:20 abneiman berick++
15:20 shulabramble And if that's all...
15:20 redavis Ooooohhhh...one more thing. Conference stuff
15:21 shulabramble !!!! redavis++
15:21 shulabramble the floor is yours
15:21 redavis The call for session proposals is live. The "deadline" is January 31. https://evergreen-ils.org/2025-evergr​een-international-online-conference/
15:21 redavis The theme is Emerging Technologies...and we're looking for pre-conference and regular conference session proposals.
15:22 redavis I know everyone here is an extrovert who loves expounding on things...
15:22 shulabramble #topic Evergreen Online Conference 2025 -- Emerging Technologies
15:22 * redavis has completed her pitch.
15:22 shulabramble #info Call for session proposals is live. Deadline is January 31 -- https://evergreen-ils.org/2025-evergr​een-international-online-conference/
15:22 mmorgan redavis: Are there many submissions yet?
15:23 redavis Uhhhh...I don't think so. Let me check.
15:23 redavis newp
15:24 mmorgan Plenty of opportunities!
15:24 redavis So, please...submit. Fun fact.  My first conference in 2012, I still remember berick, eeevil, and phasefx having things to say about git.
15:24 csharp_ buncha gits
15:24 redavis (In the Indianapolis Hyatt)
15:24 shulabramble All positive, I assume?
15:24 abneiman left #evergreen
15:25 redavis I mean, I was a library director without much context...so git was still a little over my technological head.
15:25 redavis positive is relative
15:25 redavis but MEMORABLE and now positive
15:25 abneiman joined #evergreen
15:25 shulabramble redavis++
15:26 shulabramble Okay, anyone have any other last minute business?
15:27 shulabramble In that case...
15:27 shulabramble #endmeeting
15:27 pinesol Meeting ended Tue Jan 14 15:27:07 2025 US/Eastern.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
15:27 pinesol Minutes:        http://evergreen-ils.org/meetings/evergr​een/2025/evergreen.2025-01-14-15.00.html
15:27 pinesol Minutes (text): http://evergreen-ils.org/meetings/evergr​een/2025/evergreen.2025-01-14-15.00.txt
15:27 pinesol Log:            http://evergreen-ils.org/meetings/evergree​n/2025/evergreen.2025-01-14-15.00.log.html
15:27 eeevil shulabramble++
15:27 sleary shulabramble++
15:27 eeevil redavis++
15:27 jeff shulabramble++
15:27 sandbergja shulabramble++
15:27 terranm shulabramble++
15:27 redavis shulabramble++
15:27 mmorgan shulabramble++
15:27 collum shulabramble++
15:27 abneiman shulabramble++
15:28 eeevil (I'm pretty sure I was not being positive about git in 2012, fwiw)
15:28 redavis lol, I don't think you were. I just thought "whoa...smart people...."
15:29 terranm lol
15:29 Dyrcona shulabramble++
15:29 redavis And I remember the room seemed dark and the screen was big. Also, I don't trust my memory.
15:30 mmorgan It was a dark, dark room, with a big, big screen...
15:31 redavis lol, EXACTLY.
15:32 abneiman the screen was dark and full of terror
15:33 phasefx The glow of green phosphorus emanates from the dark dungeon monitor
15:35 redavis lol, I don't know what it actually was. My mind's eye says the whole wall was a screen and y'all were a little mst2king it.
15:37 redavis mmorgan++
15:43 mantis1 left #evergreen
15:46 Bmagic shulabramble++
15:49 smayo joined #evergreen
15:52 pinesol News from commits: Docs: 3.14.3 release notes <https://git.evergreen-ils.org/?p=E​vergreen.git;a=commitdiff;h=6f84b8​02b390630eaabf57c53b6bbab584eea810>
16:22 pinesol News from commits: Docs: 3.13.8 release notes <https://git.evergreen-ils.org/?p=E​vergreen.git;a=commitdiff;h=5b2e38​9fb11a94ca877cec11f7369ede47b783a6>
16:24 frank_g joined #evergreen
16:26 frank_g Hi all, Does someone know where I have to modify the URL sended by email when a report finishes?
16:26 frank_g I mean the base url
16:33 jvwoolf left #evergreen
16:34 jeff frank_g: I think that's still going to be in opensrf.xml, the reporter / setup / base_uri value
16:34 jeff frank_g: in the example config, it's set to "https://localhost/reporter/"
16:37 frank_g great, It works, thanks jeff
16:38 jeff You're welcome!
16:45 mmorgan jeff++
17:01 mmorgan left #evergreen

| Channels | #evergreen index | Today | | Search | Google Search | Plain-Text | summary | Join Webchat