Time |
Nick |
Message |
05:11 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
06:06 |
|
ktomita joined #evergreen |
06:06 |
|
dreuther joined #evergreen |
06:10 |
|
sseng joined #evergreen |
06:20 |
|
IAm_thor joined #evergreen |
06:20 |
|
IAm_thor left #evergreen |
07:35 |
|
wsmoak joined #evergreen |
07:35 |
|
wsmoak joined #evergreen |
07:42 |
|
jboyer-isl joined #evergreen |
07:42 |
|
mtate joined #evergreen |
07:45 |
|
kmlussier joined #evergreen |
07:56 |
|
rjackson-isl joined #evergreen |
08:02 |
|
collum joined #evergreen |
08:11 |
|
eeevil joined #evergreen |
08:13 |
|
Shae joined #evergreen |
08:21 |
|
mtate joined #evergreen |
08:29 |
|
akilsdonk joined #evergreen |
08:34 |
|
mdriscoll joined #evergreen |
08:37 |
|
tspindler joined #evergreen |
08:44 |
|
jwoodard joined #evergreen |
08:50 |
|
ericar joined #evergreen |
09:24 |
|
jeff joined #evergreen |
09:24 |
|
jeff joined #evergreen |
09:34 |
|
yboston joined #evergreen |
09:42 |
|
berick joined #evergreen |
10:05 |
|
berick joined #evergreen |
10:21 |
|
ericar_ joined #evergreen |
10:28 |
|
ericar_ joined #evergreen |
10:45 |
|
phasefx joined #evergreen |
10:57 |
|
BigRig joined #evergreen |
11:02 |
|
Dyrcona joined #evergreen |
11:04 |
|
ericar_ joined #evergreen |
11:14 |
|
pmurray joined #evergreen |
11:30 |
|
ericar left #evergreen |
11:33 |
|
BigRig_ joined #evergreen |
11:51 |
|
IAm_thor joined #evergreen |
11:51 |
|
IAm_thor left #evergreen |
12:11 |
|
buzzy joined #evergreen |
12:28 |
bshum |
jeff: What is this "vacation" you speak of? It sounds like a mystical event that shall never pass for me :) |
12:29 |
* kmlussier |
thinks bshum needs to learn to take a vacation. :) |
12:30 |
bshum |
Vacation is for winners who don't have broken utility servers. |
12:31 |
bshum |
:( |
12:31 |
* bshum |
hates on action/triggers |
12:33 |
bshum |
I think it's our preoverdues |
12:33 |
bshum |
Too many running at once, even with granularity |
12:33 |
bshum |
We need to be even more granular |
12:33 |
bshum |
And start breaking up all the preoverdues into even smaller chunks |
12:33 |
tsbere |
That sounds less than fun |
12:34 |
* tsbere |
isn't sure we have even had a need to worry about that from an A/T standpoint |
12:34 |
bshum |
People must be terrible in our consortium :D |
12:35 |
tsbere |
Or you just have a lot more circs to generate notices for. <_< |
12:35 |
bshum |
Well, attempt and fail most of them I would imagine. |
12:35 |
tsbere |
Or perhaps there is benefit to our "one template for the entire system" layout. |
12:35 |
bshum |
Not everyone will hae an email address |
12:35 |
bshum |
Maybe there's something wonky with how the preoverdues are configured. |
12:36 |
bshum |
Granularity only exists on the event_definition table I think |
12:36 |
bshum |
So if I want to alter this, I'll have to poke there |
12:37 |
berick |
bshum: and the a_t_runner crontab entries |
12:37 |
bshum |
berick: Right, that too :) |
12:37 |
berick |
just making sure :) |
12:38 |
|
jihpringle joined #evergreen |
12:38 |
* bshum |
only has 56 A/T event definitions with granularity of "daily-preoverdues" |
12:38 |
bshum |
I guess I'll split them half and half with "daily-preoverdues-1" and "daily-preoverdues-2" :D |
12:38 |
* tsbere |
has one preoverdue template configured at MVLC. Total. So he can't split them. |
12:38 |
bshum |
And try to pick the crazy big libraries so that they're not all in one or the other |
12:39 |
bshum |
Everybody wanted slightly different wording. Or enough of them did anyways :( |
12:39 |
tsbere |
bshum: Go back to one template, and make the text that varies a library setting? |
12:39 |
bshum |
tsbere: Yeah............................ maybe. |
12:39 |
bshum |
:) |
12:39 |
tsbere |
Though that can get wonky if someone has circs at more than one library... |
12:40 |
* tsbere |
bases all library-specific information (mainly name and email for the library) on the patron's home library in MVLC templates |
12:42 |
Bmagic |
Has anyone encountered a setting/feature request that would set the system to automatically "unbar" a patron on a preset date? |
12:43 |
* dbs |
is with tsbere. we even have French and English within the same template, controlled by a variable. |
12:44 |
tsbere |
Bmagic: I think standing penalties can have a "stop date" - That isn't really "unbar" but comes close on a "block everything" penalty type |
12:45 |
Bmagic |
tsbere: I saw that the database had a date but I don't see that in the staff client |
12:46 |
* tsbere |
hasn't looked into it, just recalled the field existing |
12:46 |
Bmagic |
Yeah, I looked into it a little bit and realized that there wasn't a way to set the date from the staff client (at least from what I could tell) |
12:48 |
jeff |
actor.usr_standing_penalty.stop_date being set means "this penalty is archived, not currently active" -- i don't believe there is any present logic for having it set in the future and meaning it's "not archived yet". |
12:51 |
tsbere |
jeff: Huh. Looking at code, most of the stop date code is "stop date is null or in the future" type checks, except for "do I put this in the archive category in the staff client?" which just looks for a stop date. I may be missing other points, though. |
12:52 |
jeff |
or i'm just wrong. |
12:54 |
tsbere |
Looks like bad contact penalties doesn't seem to check that stop date is in the future, but that is about it beyond the staff client |
12:54 |
tsbere |
Everything else, at a quick glance anyway, actually checks for the stop date being null or in the future |
12:55 |
tsbere |
jeff: Of course, that could have just been planning ahead. We don't have many ways to set a stop date right now iether. <_< |
12:56 |
* tsbere |
can't actually find one other than archiving in an obvious sense |
13:01 |
Bmagic |
Thanks for checking |
13:01 |
Bmagic |
And another question that I am fuzzy about: A library gets a copy from another library. Lends it out. It goes lost. Then returned, it seems that the system wants the item to go back to the original library before it can be "unlost" |
13:03 |
jeff |
there is a "lost items immediately available on check-in" (paraphrased) org unit setting that might help you there. |
13:03 |
jeff |
first place i'd look, at least |
13:03 |
Bmagic |
jeff: awesome, I wasn't aware of such a setting |
13:03 |
Bmagic |
I will relay that |
13:09 |
jeff |
i can't guarantee that it does what you want -- we don't use it one way or the other. |
13:11 |
eeevil |
tsbere: the "or in the future" check was, indeed, planning ahead. or, more correctly, "check reality" with a happy (intended) side effect of one day being able to set an "expiration date" on penalties |
13:12 |
eeevil |
the lack of that when filtering for display in the SC is, IMO, an oversight |
13:14 |
eeevil |
Bmagic: that "lost goes home" was intended ... logic being, lost is an exceptional status, and the owner should have a shot at touching the copy first |
13:15 |
eeevil |
I don't recall the details of the setting jeff points at, but it's probably exactly what he's intimating |
13:29 |
kmlussier |
I'm wondering if you all have any ideas for potential coding projects for the Outreach Project for Women. http://markmail.org/message/5smotqzxpiqhewm5 |
13:30 |
kmlussier |
Things that may be easy entry points for coders new to Evergreen. They suggest possibly having interns start on bugs that revolve around one theme and then move on to a small enhancement. |
13:30 |
eeevil |
kmlussier: would looking at bitesize-tagged LP entries be a good place to start? |
13:30 |
* eeevil |
looks |
13:31 |
kmlussier |
One suggestion I received a little earlier was possibly moving self-check to Angular. There are a few selfcheck related bugs, so I though we might be able to group them together somehow. |
13:38 |
dbs |
kmlussier: Mobile-first catalogue, round two? (Taking our current fonts.tt2 / styles.tt2 / CSS + HTML and making it better suited for customization to avoid those "white text on white background" surprises) |
13:39 |
kmlussier |
I also was looking at some of the old GSoC ideas, but some probably are no longer relevant, like updating Dojo. I don't know if others really are easy entry points. |
13:39 |
kmlussier |
dbs: I was wondering if we could possibly do more work around mobile. Sounds like something that would be doable during the internship period. |
13:40 |
eeevil |
the bitesize buts are kinda all over the place, so either of those makes sense if you want to keep them in the same area to encourage collaboration and possibly speed time-to-fix |
13:40 |
dbs |
kmlussier: Yeah, and if that goes really well, then maybe there could be some involvement in the web-based client as well. |
13:40 |
kmlussier |
And maybe expanding more mobile functionality for client functions. Like the mobile-friendly holds pull list I've always wanted to see. |
13:40 |
dbs |
kmlussier++ # BRILLIANT IDEA :) |
13:42 |
jeff |
and it's one, two, three attempts to find that copy and it's marked - miss - ING! |
13:42 |
kmlussier |
Great minds think alike dbs. :) |
13:42 |
jeff |
(to be sung to the tune of "take me out to the ballgame", as if that wasn't completely obvious) |
13:42 |
|
mtcarlson_away joined #evergreen |
13:43 |
kmlussier |
I wonder if there are further improvements that could be made to selfcheck to make the project a little more interesting. |
13:44 |
eeevil |
while on the subject, I ran across a post on G+ about long-list infini-scrolling in angular that might let us get away from paging (and its attendant issues of sorting and refetching data and such) where most of the pain comes from rendering the rows (which is, I suspect, most of the time) |
13:45 |
eeevil |
http://ionicframework.com/blog/collection-repeat/ (just to add to the collective memory) |
13:45 |
kmlussier |
eeevil: I saw that post. I can't recall if I +1'ed it or not, but I think we have a lot of users who would love to get rid of paging. Especially in acq. |
13:45 |
jeff |
eeevil: under phonegap on recent(ish) (Galaxy S3) hardware it turned out to be disappointingly slow. Further poking might be done, but I was sad. |
13:45 |
eeevil |
kmlussier: I, for one, hate all forms of paging |
13:45 |
eeevil |
jeff: the iconic framework thing? that's no fun :( |
13:46 |
jeff |
eeevil: specifically collection-repeat |
13:47 |
jeff |
just throwing out a data point. i don't know if it was due to what phonegap presents these days as a javascript engine (dunno if it's using webview or chrome or what), etc. |
13:52 |
dbs |
One must always be wary of memory consumption with infini-scrolls too. |
13:52 |
* jeff |
nods |
13:52 |
jeff |
as i understand it, collection-repeat recycles dom objects in an attempt to avoid that. |
13:54 |
eeevil |
jeff: an important data point, though. we should avoid any dead ends early, going forward ... do you have link for a test? I can point my N4 at it (and I'm curious) |
13:54 |
berick |
eeevil: re: scrolling, it would be fairly easy to give infinite scrolling to the grid using angular's ui-scroll (http://angular-ui.github.io/ui-utils/) |
13:54 |
berick |
there's a brief mention here http://wiki.evergreen-ils.org/doku.php?id=dev:browser_staff:dev_notes#section20140411 |
13:55 |
jboyer-isl |
I'm curious what phonegap has to do with it? I thought that was a library to build an "app" out of a webpage, giving it access to the camera and other hardware bits. |
13:55 |
berick |
but it's mostly a question applying a small bit of wrapper code |
13:55 |
jboyer-isl |
Unless I've missed some context. |
13:55 |
berick |
(and loadin the ui-scroll js bits) |
13:58 |
eeevil |
berick: ah, indeed. thanks! |
14:00 |
jboyer-isl |
Notification question: What uses the opensrf/default/email_notify/template setting? (i.e. hold_notification_template.example in opensrf.xml) |
14:06 |
tsbere |
jboyer-isl: Non-AT notice generation, I think |
14:07 |
|
jihpringle_ joined #evergreen |
14:07 |
jboyer-isl |
tsbere: I wondered if that might be the only thing. (I'm currently going through our git repo looking for things to keep custom vs. ignore) |
14:09 |
* tsbere |
hasn't actually looked for the setting in anything so can't be 100% sure |
14:14 |
jboyer-isl |
I've tried looking around and I haven't been able to find anything else either. |
14:15 |
jboyer-isl |
I just placed an available item on hold though, and once my email arrives I should be able to narrow things down. :) |
14:17 |
|
jihpringle joined #evergreen |
14:32 |
dbs |
email. just received a phone call from someone upset they didn't get their pre-overdue notice. Could be related to our server move, could be our IT Services tightening up their inbound filter rules. |
14:32 |
dbs |
I hate debugging "email not received" :/ |
14:33 |
* dbs |
does know that IT Services added a straight-up block for emails from outside our domain that contain more than a certain number of links, as I ran into it last night trying to send an email filled with links. |
14:34 |
dbs |
The error that the other server returned was: |
14:34 |
dbs |
554 rejected due to spam content |
14:34 |
tsbere |
dbs: I also hate debugging that. Especially when the report is "this patron didn't get their email" without any information as to the patron. >_> |
14:35 |
dbs |
(I had 5 links and 5 email addresses in that email, all very informative and very much non-phishy!) |
14:35 |
dbs |
Well, at least in this case it was the patron that contacted me directly |
14:36 |
tsbere |
That is a better situation than I usually get. Though the last few I researched hit one of two blocks. Either the hold wasn't set to notify by email, or the remote mail server accepted the message. Obviously not much to be done in the latter case. :/ |
14:42 |
dbs |
grr. reports are sending email just fine. |
14:42 |
dbs |
(and I'm receiving them) |
15:01 |
kmlussier |
Back to the OPW projects, if we were to add Angular selfcheck and mobilizing the catalog/client part 2, are there any devs who would be able to commit the time to serve as mentors? My hope is to get two mentors for each project listed so that the burden doesn't fall all on one person. |
15:22 |
|
bmills joined #evergreen |
15:27 |
* dbs |
could put in some time on a mobilization effort, but definitely needs at least one other mentor with solid amounts of time available |
15:28 |
dbs |
I'm very s-t-r-e-t-c-h-e-d |
15:28 |
kmlussier |
dbs++ Thanks! |
15:29 |
kmlussier |
dbs: If we don't have two mentors for a project by the end of the week, I most likely will remove it from the page. I think co-mentors is the only way to go because we're all very stretched. |
15:30 |
csharp |
we have our postfix logs from our dedicated EG mail server alongside our opensrf/apache/PG logs to ease "email not received" complaints |
15:31 |
csharp |
in nearly all cases, the end user's email provider's server has silently accepted our mail and that's the last we know of it |
15:32 |
bradl |
csharp: speaking of not getting email, was that you I saw on the backhoe outside Century Place? |
15:33 |
csharp |
heh - yeah, it's been a bumpy week |
15:33 |
csharp |
network was mostly up over the weekend, now totally down |
15:34 |
csharp |
I'm at home now, basking in the Internet's warm, glowing warming glow |
15:34 |
bradl |
sorry, I mean Clarmont Place, which is on Century Place. Not confusing at all. ;) |
15:35 |
dbs |
Turns out our server was running through some fairly severe mail config problems up until Aug 20th, as evidenced by looking through the mail logs. |
15:36 |
csharp |
bradl: always confusing, even to veterans ;-) |
15:36 |
csharp |
dbs: yowza |
15:36 |
* dbs |
once again reminds self to get added to munin so we can hopefully catch this stuff when it actually occurs, rather than much later |
15:36 |
csharp |
munin++ |
15:37 |
csharp |
monitoring++ |
15:37 |
eeevil |
munin-graphs-- |
15:37 |
eeevil |
(I mean, graphs are great. but it wants ALL THE I/O'S to draw them) |
15:37 |
dbs |
pictures, bah, who needs pictures |
15:38 |
csharp |
@who needs pictures? |
15:38 |
pinesol_green |
pinesol_green needs pictures. |
15:38 |
csharp |
@dessert [someone] |
15:38 |
* pinesol_green |
grabs some Apple Crisp for ktomita |
15:38 |
* dbs |
sends pinesol_green all the picturezzz |
15:41 |
* dbs |
was so *happy* to have the prof on the other end of the phone say "have you ever used <other library system>? It works really well!" |
15:42 |
dbs |
I don't _think_ said prof was being passive-aggressive |
15:42 |
csharp |
haha |
15:42 |
jcamins |
dbs: ouch. |
15:43 |
* dbs |
heads off to a union meeting for a strike mandate vote for another possible ouch. |
15:43 |
csharp |
we had a library director who was pretty anxious for us to adopt another (any other) library system for a while - haven't heard anything like that lately |
15:44 |
csharp |
at&t-- |
15:44 |
csharp |
old_school_telecom-- |
15:50 |
bradl |
csharp: funny how people forget so easily (I guess the grass looks so tasty just over... there...) |
15:54 |
csharp |
yep |
15:55 |
|
hbrennan joined #evergreen |
15:57 |
hbrennan |
Is there a way to verify that an Overdue Courtesy email was sent to a specific patron? Not that they received it, just that EG sent one? |
16:01 |
|
hbrennan_ joined #evergreen |
16:01 |
hbrennan_ |
Oops, I was booted. Let's try that again... |
16:01 |
hbrennan_ |
Is there a way to verify that an Overdue Courtesy email was sent to a specific patron? Not that they received it, just that EG sent one? |
16:08 |
csharp |
@later tell hbrennan yes, but where you look depends on whether you're using A/T or legacy scripts for email notifications... you should be able to see the generated email in Other -> Triggered Events if it was A/T *and* your data set is small enough for that to load (see bug 1207533) |
16:08 |
pinesol_green |
csharp: The operation succeeded. |
16:08 |
|
hbrennan joined #evergreen |
16:09 |
csharp |
hbrennan: just answered you with a @later |
16:11 |
* csharp |
confirms that bug 1207533 still applies to PINES after a move to DBs with SSDs |
16:11 |
pinesol_green |
Launchpad bug 1207533 in Evergreen 2.5 "Triggered event log times out for large-data sites" (affected: 14, heat: 74) [Medium,Confirmed] https://launchpad.net/bugs/1207533 |
16:13 |
hbrennan |
Ah, thanks. Don't know where the conductivity problem is... I just keep getting booted |
16:13 |
hbrennan |
csharp++ Thanks |
16:17 |
csharp |
hbrennan: if you have access to your email server's logs too, that can provide the proof that the patron's email provider's server received (or didn't receive) the email |
16:20 |
hbrennan |
bmills++ as well |
16:35 |
|
tspindler left #evergreen |
16:53 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
16:55 |
Dyrcona |
1 file changed, 613 insertions(+), 1 file changed, 476 insertions(+), 7 deletions(-), 1 file changed, 9 insertions(+), 10 deletions(-): I call that a productive day. |
16:56 |
|
mdriscoll left #evergreen |
17:18 |
|
jwoodard joined #evergreen |
17:56 |
bmills |
hello, is there a way to sort patrons in a case-insensitive manner in the staff client (browse holds shelf, especially) ? we have a few libraries that enter their patron names in all caps. after searching for a patron and sorting by last name, "SMITH" currently sorts above "Samuel", for instance. |
18:25 |
|
wsmoak joined #evergreen |
18:25 |
|
wsmoak joined #evergreen |
19:03 |
|
sarabee_ joined #evergreen |
21:00 |
|
buzzy joined #evergreen |
22:09 |
|
b_bonner joined #evergreen |
22:54 |
|
sarabee joined #evergreen |
23:00 |
|
sarabee_ joined #evergreen |
23:13 |
|
RBecker joined #evergreen |