Time |
Nick |
Message |
00:09 |
|
eady joined #evergreen |
04:20 |
|
bdljohn1 joined #evergreen |
05:02 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
07:37 |
|
bos20k joined #evergreen |
07:38 |
|
agoben joined #evergreen |
07:56 |
|
jvwoolf joined #evergreen |
08:26 |
|
stephengwills left #evergreen |
08:34 |
|
jvwoolf joined #evergreen |
08:35 |
miker |
gsams: we didn't do that because null is as good as false in most cases, and it would have meant rewrite the whole circulation table at upgrade (in currently supported versions of postgres) |
08:35 |
miker |
meant a* |
08:38 |
|
mmorgan joined #evergreen |
08:39 |
miker |
gsams: and we generally try not to ever fill in new fields on historical data where there wasn't functionality to produce the data before, if that makes sense |
08:53 |
mmorgan |
Speaking of auto renewal, I notice that the auto_renewal_remaining field can have a value > 0 even when renewal_remaining <= 0. |
08:54 |
mmorgan |
Doesn't seem to allow renewals inappropriately, but I'm just wondering if that may cause confusion when viewing a circulation. |
09:05 |
|
jvwoolf1 joined #evergreen |
09:06 |
|
stephengwills joined #evergreen |
09:09 |
|
Dyrcona joined #evergreen |
10:12 |
|
mmorgan joined #evergreen |
10:13 |
gsams |
miker++ #makes sense |
10:17 |
|
Christineb joined #evergreen |
10:18 |
miker |
mmorgan: renewal_remaining is the hard limit. we don't decrement auto_renewal_remaining on a non-auto renew because it's not an auto-renewal (we're preserving state information). While it doesn't exist yet, that leaves open the option for a YAOUS that allows use of all auto-renewals even if non-autos is 0 (for instance to be able to say, "only auto-renewals are allowed") |
10:22 |
|
beanjammin joined #evergreen |
10:27 |
gsams |
That's pretty nice, I hadn't thought about it becoming it's own factor when we were putting it to words, only how it would work within the current system. |
10:28 |
gsams |
Nice to know the possibility is there. |
10:31 |
Dyrcona |
While I appreciate the flexibility, I can see that leading to a lot of confusion on the part of front line staff. |
10:58 |
|
aabbee joined #evergreen |
11:35 |
|
sandbergja joined #evergreen |
11:37 |
|
jwoodard joined #evergreen |
11:41 |
|
khuckins joined #evergreen |
11:53 |
|
mcgriff joined #evergreen |
11:55 |
|
Stompro joined #evergreen |
11:55 |
|
agoben joined #evergreen |
12:00 |
|
beanjammin joined #evergreen |
12:28 |
|
jihpringle joined #evergreen |
12:47 |
Dyrcona |
Bmagic: I'm curious. Were you able to confirm that you max fines issue from the other day really is bug 1786312 |
12:47 |
pinesol |
Launchpad bug 1786312 in Evergreen "Extending circ due date can result in exceeding max fines" [Undecided,New] https://launchpad.net/bugs/1786312 |
12:48 |
Bmagic |
yeah, I believe my issue was that issue |
12:50 |
Dyrcona |
Mind confirming the bug? |
12:56 |
Bmagic |
oh! sure |
13:12 |
Dyrcona |
Bmagic++ |
13:12 |
Bmagic |
Dyrcona++ # bug hunting |
13:19 |
Dyrcona |
Bmagic: Do I remember correctly that you recently asked about sending HTML emails with a/t notices? |
13:26 |
csharp |
I recently asked about it |
13:26 |
csharp |
we were having a vendor presentation with slick email templates and I was wondering how feasible that is within EG - terran is looking into it |
13:27 |
Dyrcona |
OK. It might become easier in the future. I'm looking into using Email::Stuffer for bug 1801163 |
13:27 |
pinesol |
Launchpad bug 1801163 in Evergreen "SendEmail A/T reactor broken for recent version of Encode::MIME::Header" [High,In progress] https://launchpad.net/bugs/1801163 - Assigned to Jason Stephenson (jstephenson) |
13:28 |
Dyrcona |
Not sure, yet, how you'd get both HTML and plain text parts out of the reactor. |
13:40 |
|
derekz joined #evergreen |
13:51 |
|
nfBurton joined #evergreen |
13:54 |
nfBurton |
In response to the HTML emails. I did get them working and am currently testing (successfully) HTML emails for new patrons. Likely to be expanded after. |
13:54 |
Bmagic |
Dyrcona: We've got the plain and html working with the patch |
13:55 |
Dyrcona |
"The patch..." Which patch? |
13:55 |
Bmagic |
bug 1532236 |
13:55 |
pinesol |
Launchpad bug 1532236 in Evergreen "Evergreen should allow for HTML formatted action trigger emails" [Wishlist,Confirmed] https://launchpad.net/bugs/1532236 |
13:56 |
nfBurton |
I can confirm the same patch worked for me on 3.1.5 |
13:57 |
Bmagic |
The sample AT template on the bug shows how to do it |
13:59 |
Dyrcona |
Yes. That looks straightforward enough. We'll have to see if it still works with Email::Stuffer. |
14:06 |
csharp |
jeffdavis: testing privacy waiver branch - when I "purge" the patron via the UI, the actor.usr_privacy_waiver rows are retained - is that what you intended? |
14:06 |
csharp |
I realized that they would be deleted with an actual row deletion via cascade |
14:06 |
csharp |
s/realized/realize/ |
14:08 |
* csharp |
thinks we should add a DELETE to actor.usr_purge_data to handle it |
14:08 |
jeffdavis |
csharp: that's an oversight, the purge function should clear out that data |
14:08 |
csharp |
and I'm happy to do that |
14:08 |
jeffdavis |
yeah, that :) |
14:09 |
csharp |
do you want to do it? |
14:09 |
jeffdavis |
sure, will do |
14:09 |
csharp |
awesome |
14:09 |
csharp |
feature works great otherwise - tested from the staff and opac view |
14:09 |
csharp |
once we clear the policy hurdle (possibly in May) we'll probably implement it |
14:10 |
csharp |
it's a commonsense thing to be able to do with the software |
14:10 |
jeffdavis |
thanks for testing! |
14:13 |
Dyrcona |
Y'know, someone from CW MARS should open another bug on actor.user_delete, because the alternate names are not touched by that function, either. |
14:14 |
csharp |
jeffdavis: happy to do it |
14:20 |
* Dyrcona |
curses Lp and the infamous "Timeout Error." |
14:30 |
Dyrcona |
Hmm... Installed Jessie from the netinst image and got a GUI. |
14:30 |
Dyrcona |
Not exactly what I wanted. |
14:33 |
csharp |
heh |
14:33 |
csharp |
@blame Jessie |
14:33 |
pinesol |
csharp: I come to bury Jessie, not to praise them. |
14:34 |
Dyrcona |
Maybe I missed something in the installer options? |
14:34 |
csharp |
I haven't installed Debian in a while, but I have a faint memory of having to opt out of the desktop at the tasksel step |
14:40 |
jeffdavis |
csharp: I've pushed a commit to address the purge user data issue |
14:43 |
Dyrcona |
Yeah. First option at the top. Guess I missed it. |
14:52 |
csharp |
jeffdavis: rock on - I'll give it one last lookover and signoff/commit |
15:07 |
|
jvwoolf joined #evergreen |
16:55 |
csharp |
relevant: https://www.reddit.com/r/ProgrammerHumor/comments/ao4opn/10yearchallenge/ |
16:57 |
|
jvwoolf joined #evergreen |
17:02 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
17:09 |
|
mmorgan left #evergreen |
17:33 |
csharp |
calling 1144, 1145, & 1146 |
17:34 |
berick |
yeehaw |
17:41 |
csharp |
jeffdavis++ |
17:42 |
pinesol |
[evergreen|Jeff Davis] LP#1715767: Allow others to use my account (privacy waiver) - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=c7727d4> |
17:42 |
pinesol |
[evergreen|Jeff Davis] LP#1715767: remove privacy waiver entries when referenced actor.usr rows are deleted - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=be0e7e2> |
17:42 |
pinesol |
[evergreen|Jeff Davis] LP#1715767: remove privacy waiver entries when purging user data - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=c016af3> |
17:42 |
pinesol |
[evergreen|Chris Sharp] LP#1715767 - stamping upgrade scripts - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=6ae2427> |
17:44 |
csharp |
I guess the 10-year challenge meme is timely for our community since our first conference was in 2009 :-) |
17:59 |
|
bdljohn1 left #evergreen |
18:56 |
jeffdavis |
csharp++ # thanks for testing and commit! |
19:35 |
|
jamesrf joined #evergreen |
20:18 |
|
sandbergja joined #evergreen |
22:52 |
|
jamesrf joined #evergreen |