| Time |
Nick |
Message |
| 00:49 |
|
jeff_ joined #evergreen |
| 04:03 |
|
_bott_ joined #evergreen |
| 04:12 |
|
eby joined #evergreen |
| 04:12 |
|
mtate joined #evergreen |
| 04:21 |
|
eby joined #evergreen |
| 04:21 |
|
mtate joined #evergreen |
| 04:43 |
* bshum |
apologizes to csharp if there are lots of noise from lupin over memory usage. |
| 04:43 |
bshum |
Upgrading piwik is apparently taking its toll. |
| 04:43 |
bshum |
(and fixing crashed mysql tables apparently) |
| 07:56 |
* csharp |
hasn't seen any warnings |
| 07:58 |
|
rjackson-isl joined #evergreen |
| 08:27 |
|
akilsdonk joined #evergreen |
| 08:28 |
|
Shae joined #evergreen |
| 08:34 |
|
ningalls joined #evergreen |
| 08:34 |
|
RoganH joined #evergreen |
| 08:35 |
|
timf joined #evergreen |
| 08:46 |
* jeff |
yawns |
| 08:46 |
jeff |
morning. |
| 08:46 |
* RoganH |
needs more coffee. |
| 08:47 |
|
kbeswick joined #evergreen |
| 08:53 |
|
Dyrcona joined #evergreen |
| 08:56 |
csharp |
@whocares coffee |
| 08:56 |
pinesol_green |
kmlussier loves coffee |
| 09:00 |
|
ericar joined #evergreen |
| 09:05 |
csharp |
@whocares autoupdate |
| 09:05 |
pinesol_green |
csharp: I can't find anyone who loves or hates autoupdate. |
| 09:05 |
csharp |
@love autoupdate |
| 09:05 |
pinesol_green |
csharp: The operation succeeded. csharp loves autoupdate. |
| 09:07 |
|
akilsdonk_ joined #evergreen |
| 09:10 |
|
mmorgan joined #evergreen |
| 09:30 |
kmlussier |
I can't be the only person in here who loves coffee. |
| 09:36 |
csharp |
@love coffee |
| 09:36 |
pinesol_green |
csharp: The operation succeeded. csharp loves coffee. |
| 09:39 |
ningalls |
I love coffee beer |
| 09:53 |
kmlussier |
ningalls: That is something I would be open to trying. :) |
| 09:58 |
csharp |
I'm interested... has anyone other than dbs implemented GIN indexes in their databases? |
| 09:58 |
csharp |
wondering about the process and whether the performance gains are worth the effort |
| 10:03 |
eeevil |
csharp: several sites. easiest thing to do is CREATE INDEX CONCURRENTLY and then, after hours because of locking, drop the gist indexes. |
| 10:03 |
|
mllewellyn joined #evergreen |
| 10:04 |
dbs |
csharp: 'cause let's face it, yo, dbs is CRAZZZZZY |
| 10:04 |
|
Dyrcona joined #evergreen |
| 10:04 |
eeevil |
perhaps even CRAY CRAY, as the kids say these days |
| 10:09 |
bshum |
csharp: I've thought about making the switch but been concerned about space requirements and us not having enough room on our server for them. |
| 10:10 |
bshum |
But that's mostly because I like keeping our DB small enough to fit in RAM. |
| 10:11 |
|
yboston joined #evergreen |
| 10:12 |
|
mrpeters joined #evergreen |
| 10:16 |
bshum |
@love autoupdate |
| 10:16 |
pinesol_green |
bshum: The operation succeeded. bshum loves autoupdate. |
| 10:17 |
* bshum |
can't believe that he wasn't on that yet. |
| 10:18 |
bshum |
csharp: If you do experiment with GIN, I'd be curious to learn how much space it took to switch up. |
| 10:21 |
dbs |
Don't forget the OLIVE. |
| 10:24 |
dbs |
But stay away from the Aleph. |
| 10:29 |
jboyer-isl |
bshum: I noticed I missed an "Around?" yesterday. Anything I can help with? |
| 10:30 |
bshum |
jboyer-isl: Oh I just saw a comment in the Evergreen website that seemed like an Indiana patron trying to give feedback (or complain?) about the catalog. |
| 10:30 |
bshum |
I'll type it up and send you (or someone else) the copy. |
| 10:30 |
bshum |
It was lodged against the OpenSRF release blog post. Not sure why exactly. |
| 10:31 |
* bshum |
doesn't know if other web team members regularly watch the moderated blog comments. |
| 10:31 |
dbs |
W/win 17 |
| 10:31 |
dbs |
win win!@ |
| 10:31 |
jboyer-isl |
cool. Thanks for letting me know. |
| 10:33 |
kmlussier |
bshum: I try to. |
| 10:34 |
bshum |
kmlussier++ # I'm bad at checking myself, but happened upon it this time when I was updating Wordpress. |
| 10:45 |
|
mllewellyn left #evergreen |
| 11:02 |
Dyrcona |
pcregrep++ |
| 11:03 |
Dyrcona |
Why did it take me 15 years to "discover" it? |
| 11:05 |
csharp |
eeevil sold me on ack a while back |
| 11:06 |
csharp |
"ack-grep" in mainline distro repos |
| 11:07 |
csharp |
I think I'll play with GIN on a couple of test instances and report back |
| 11:07 |
csharp |
@whocares gin |
| 11:07 |
pinesol_green |
csharp: I can't find anyone who loves or hates gin. |
| 11:07 |
* csharp |
loved gin martinis before becoming a teetotaler |
| 11:08 |
Dyrcona |
What I find amusing is that a community called "Mother's Ruin Gin Lovers" showed up my suggested G+ communities this morning. |
| 11:08 |
csharp |
haha |
| 11:08 |
Dyrcona |
I think it has something to do with having eby in my circles. ;) |
| 11:15 |
csharp |
@love db02 |
| 11:15 |
pinesol_green |
csharp: The operation succeeded. csharp loves db02. |
| 11:18 |
csharp |
eeevil or dbs: are there particular indexes I should focus on using GIN on, or is it best to convert them all? |
| 11:58 |
jeffdavis |
csharp: our metabib.*_field_entry tables are mostly using GIN indexes |
| 11:58 |
eby |
Dyrcona: it does ;) |
| 12:00 |
|
dMiller_ joined #evergreen |
| 12:00 |
jeffdavis |
csharp: we were doing some relevancy ranking adjustments at the same time, but overall we saw roughly a 40% improvement in response times |
| 12:01 |
jeffdavis |
(according to the internal wiki page documented someone else's testing :) |
| 12:01 |
jeffdavis |
.. on broad searches |
| 12:06 |
csharp |
oh wow |
| 12:06 |
csharp |
jeffdavis: thanks for that information |
| 12:18 |
linuxhiker |
pinesol_green: I love Gin. I good Gin Martini with Hendricks... and 4 large olives, oh heck yes |
| 12:18 |
pinesol_green |
linuxhiker: You probably want hard-boiled eggs. |
| 12:18 |
pinesol_green |
linuxhiker: I am only a bot, please don't think I'm intelligent :) |
| 12:18 |
linuxhiker |
well that was entertaining |
| 12:18 |
csharp |
linuxhiker++ |
| 12:19 |
linuxhiker |
csharp: also with a really good tonic water such as Fever Tree |
| 12:27 |
|
smyers_ joined #evergreen |
| 12:51 |
|
dMiller___ joined #evergreen |
| 12:59 |
|
stevenyvr2 joined #evergreen |
| 13:13 |
|
eby joined #evergreen |
| 13:13 |
|
mtate joined #evergreen |
| 13:15 |
sseng |
just wondering, in evergreen, is there a purge old action trigger events? am not sure whether the purge old holds / circulation took care of that or not |
| 13:17 |
gmcharlt |
sseng: nothing built in |
| 13:19 |
sseng |
gmcharlt: oh I see, since this table can get very large fast. any known external script to run? similar to script to purge holds / circulation? or this not available yet (built in or script wise). thanks! |
| 13:20 |
bshum |
senator++ # asking for logs :) |
| 13:22 |
csharp |
sseng: there's not such a script that I've seen |
| 13:22 |
gmcharlt |
sseng: can't speak to what might be floating around, but the principle of such a script would be easy enough to articulate -- delete/move to another table rows in action_trigger.event, event_output, and friends based on date criteria and event type criteria |
| 13:23 |
gmcharlt |
event type matters because one might, for example, want to keep atev rows related to EDI messages indefinitely but prune events related to patron activity after X number of months |
| 13:23 |
* csharp |
would probably advise not bothering deleting the data unless there's a disk space concern |
| 13:24 |
* eeevil |
agrees heartily with csharp. the output can get big-ish relative to the event table itself, but the event table is really very skinny |
| 13:25 |
sseng |
csharp: eeevil: gmcharlt: ah I see. just that this bug here (https://bugs.launchpad.net/evergreen/+bug/1207533) is causing some trouble, and maybe a purge script might help while that gets resolved. |
| 13:25 |
pinesol_green |
Launchpad bug 1207533 in Evergreen 2.5 "Triggered event log times out for large-data sites" (affected: 6, heat: 34) [Medium,Confirmed] |
| 13:32 |
eeevil |
sseng: that's going to continue to be a problem, unfortunately ... I think there's no way around restructuring that. the main problem I would have with purging A/T events is that they serve as markers for other, later events in many cases ... you only want one "you lost this book" event, etc. Config can help make sure that doesn't happen, but you still have to retain the data for some period of time (the alerting window between delay and |
| 13:32 |
eeevil |
max_delay, IIRC) |
| 13:33 |
eeevil |
that said, if you were careful to purge only active events, and only of some types, it could be done as gmcharlt says pretty easily with SQL and cron |
| 13:34 |
bshum |
Calling 0850 |
| 13:36 |
sseng |
eeevil: gmcharlt: csharp: oh i see, could get very tricky. thanks again though for insight! going to rethink that |
| 13:38 |
gmcharlt |
yeah, it's almost a general principle -- unless you're literally running out of disk, a query problem that is related to "too much data" is best solved by first looking at the query structure, then the structure of the tables |
| 13:38 |
gmcharlt |
pruning data, unless it truly never will be needed, should be a last step |
| 13:39 |
pinesol_green |
[evergreen|Thomas Berezansky] Translate the icon labels in TPAC - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=f337381> |
| 13:39 |
pinesol_green |
[evergreen|Ben Shum] Stamping 0850 - translate icon labels - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=5e373d3> |
| 13:39 |
sseng |
gmcharlt: got it, thanks! |
| 13:41 |
|
collum joined #evergreen |
| 14:00 |
|
remingtron joined #evergreen |
| 14:13 |
bshum |
sseng: Regarding "assigned to" and bugs. That's sometimes loosely used to show whether or not someone is working on a bug. If there isn't anybody assigned, there's a good chance nobody has claimed to be working on it. |
| 14:13 |
bshum |
Though not everybody marks themselves as assigned to a bug while they poke at it either. |
| 14:13 |
sseng |
bshum: ah I see. thanks! |
| 14:13 |
bshum |
It's sort of on your own initiative. Though if you were to assign yourself to a bug and claim to be working on it, I'm sure the others would be pleased to have the extra hand in the mix ;) |
| 14:30 |
|
phasefx joined #evergreen |
| 14:37 |
jeff |
whee. no syntactically improbable email addresses in the database, and regex prevents new invalid entries. |
| 14:37 |
csharp |
jeff++ |
| 14:44 |
|
smyers__ joined #evergreen |
| 15:08 |
|
phasefx joined #evergreen |
| 15:12 |
|
mllewellyn joined #evergreen |
| 15:35 |
Dyrcona |
One problem with autoupdates is if you build a lot of development versions over time, it takes longer and longer to build the incremental updates, unless you wipe out the archive files. |
| 15:39 |
|
berick joined #evergreen |
| 15:39 |
bshum |
Wiping out the archives made me happy last time. |
| 15:47 |
|
kupo_ joined #evergreen |
| 15:51 |
kupochu |
Hi, are chromebooks / chromeboxes going to be usable on evergreen's library client one day? Curious on whether or not they'll be of use to us.. |
| 15:54 |
bshum |
kupochu: Presently, with the existing Evergreen client, that seems unlikely to run on a Chromebook. But if the web-based staff client stuff takes off, I could see that working on a Chromebook. Since it'll be browser based at that point. |
| 15:56 |
kupochu |
I see, so should we simply wait and see on that? |
| 15:56 |
Dyrcona |
I don't expect the browser based staff client to be ready for a year or more. |
| 15:56 |
bshum |
Pretty much that's the best I can suggest at this time. |
| 15:56 |
Dyrcona |
I could be wrong, but.... |
| 15:57 |
kupochu |
Alright, thanks. |
| 15:59 |
Dyrcona |
With browsers becoming operating systems, I think I should create the EMACSBook! |
| 16:00 |
bshum |
Huh |
| 16:00 |
bshum |
bug 1262359 - I'm not sure it ever worked the way described for pre-cats. |
| 16:00 |
pinesol_green |
Launchpad bug 1262359 in Evergreen "pre-cat creates permanent item" (affected: 1, heat: 6) [Undecided,New] https://launchpad.net/bugs/1262359 |
| 16:01 |
bshum |
At least not without deleting the copy that's created. Or transferring the volume to the real bib. |
| 16:01 |
tsbere |
I was under the impression it has pretty much always worked as it currently does, and catalogers had to decide to delete the item. |
| 16:01 |
bshum |
The pre-cat is always an entry in asset.copy |
| 16:01 |
bshum |
Yeah |
| 16:01 |
senator |
ha! emacsbook |
| 16:02 |
* senator |
pictures oversize control keys |
| 16:02 |
senator |
Dyrcona++ |
| 16:03 |
Dyrcona |
And a Meta key that is labeled "Meta" instead of Alt or Esc. |
| 16:04 |
jeff |
kupochu: with some effort, you can run Evergreen on a chromebook using Citrix |
| 16:04 |
tsbere |
Why not split the spacebar in two and slip an extra control key in the middle too. Can never have enough of them with emacs, right? ;) |
| 16:04 |
jeff |
kupochu: but in that case, you're really just "viewing" the staff client on the chromebook. :-) |
| 16:04 |
jeff |
and you have limitations such as rfid readers and printers being not-possible or trickier. |
| 16:05 |
kupochu |
I suppose I could simply put linux on the chromebook and install evergreen that way. |
| 16:07 |
kupochu |
Btw, we don't have any yet, but they're becoming a viable alternative for web browsing right now. |
| 16:07 |
kupochu |
I'm just more cirious about the client side of things.. |
| 16:07 |
kupochu |
curious * |
| 16:10 |
* jeff |
nods |
| 16:10 |
bshum |
Could always use the selfcheck interface |
| 16:10 |
bshum |
On a chromebook |
| 16:11 |
bshum |
Doesn't let you deal with as many exceptions per say |
| 16:11 |
bshum |
But I could see it getting you something |
| 16:12 |
kupochu |
Yeah, future project for me I guess, if we get some. |
| 16:14 |
|
Guest8614 joined #evergreen |
| 16:23 |
bshum |
akilsdonk_: I marked that bug as "invalid" for now, since none of us recall that behavior. But that said, I could see it evolving as a potential wishlist feature if you can find someone to champion for different handling options for pre-cats |
| 16:24 |
akilsdonk_ |
bshum: thanks! it can be ignored if no one else expects this behavior. |
| 16:43 |
jeff |
** Changed in: evergreen |
| 16:43 |
jeff |
Status: New => Spanish Inquisition |
| 16:46 |
bshum |
jeff: That should go on a t-shirt |
| 17:00 |
|
jboyer-isl joined #evergreen |
| 17:10 |
|
mllewellyn joined #evergreen |
| 17:14 |
|
mrpeters left #evergreen |
| 17:16 |
|
mmorgan left #evergreen |
| 17:19 |
Bmagic |
I just installed Evergreen 2.5 on Fedora 19! |
| 17:20 |
Bmagic |
The staff client logged in however it looks like apache doesnt have a directive for index.xhtml because it gives me a directory listing of /xul/server in the staff client - Where should the index directive go? |
| 17:29 |
|
dcook joined #evergreen |
| 19:27 |
gsams |
had a question: do non-cataloged items adhere to circulation policies for the local library that checks them out, or do they default to the highest level? |
| 19:29 |
jeff |
non- or pre-cataloged items? |
| 20:14 |
gsams |
sorry, pre-cataloged items |
| 20:14 |
gsams |
having to go back and forth from the front desk and haven't had a chance to pull up irc up there |
| 20:18 |
bshum |
Precats generally follow the most generic rule that applies. |
| 20:18 |
bshum |
I think if you choose the circ mod, it will attempt to use any matching rules. |
| 20:23 |
bshum |
In our setup, most precats will follow the circ library's default rule, i.e. circ mod as NULL. |
| 21:05 |
jeff |
thinking some more about SIP modifications to support vendor auth and only auth |
| 21:12 |
gsams |
bshum: Thanks! |
| 21:12 |
gsams |
bshum++ |
| 22:39 |
|
smyers_ joined #evergreen |
