| Time |
Nick |
Message |
| 07:21 |
|
Callender joined #evergreen |
| 07:26 |
|
rjackson_isl joined #evergreen |
| 08:05 |
|
ericar joined #evergreen |
| 08:07 |
|
mdriscoll joined #evergreen |
| 08:07 |
|
Stompro joined #evergreen |
| 08:17 |
krvmga |
@librarian |
| 08:17 |
pinesol_green |
krvmga: Management:17, Cataloging:14, Acquisitions:13, Reference:10, Circulation:16, Systems:11, Research:16, Custodial:12 |
| 08:17 |
krvmga |
@developer |
| 08:17 |
pinesol_green |
krvmga: Communication:13, BigPicture:14, DetailOriented:17, KungFu:12, GetsStuffDone:11, FlakeFactor:17, JavaAvoidance:16 |
| 08:17 |
krvmga |
lol |
| 08:44 |
|
mmorgan joined #evergreen |
| 08:45 |
|
Dyrcona joined #evergreen |
| 08:48 |
kmlussier |
@coffee [someone] |
| 08:48 |
* pinesol_green |
brews and pours a cup of Ka'u Bourbon, and sends it sliding down the bar to bwicksall |
| 08:48 |
kmlussier |
@tea [someone] |
| 08:48 |
* pinesol_green |
brews and pours a pot of Bao Zhong Oolong Tea, and sends it sliding down the bar to jeff_ (http://ratetea.com/tea/rishi/bao-zhong-oolong/768/) |
| 08:49 |
Dyrcona |
@pain_reliever |
| 08:49 |
pinesol_green |
Dyrcona: I see nothing, I know nothing! |
| 08:52 |
Dyrcona |
@swill |
| 08:52 |
* pinesol_green |
grabs a bottle of Smirnoff Ice Wild Grape and sends it sliding down the bar to Dyrcona |
| 08:52 |
kmlussier |
Dyrcona: Isn't it a little early in the morning for that? |
| 08:52 |
* Dyrcona |
slides it back down the bar to pinesol_green. |
| 08:52 |
Dyrcona |
Not if you're a frat bro, which I am not. |
| 08:53 |
Dyrcona |
That really is "swill," imho. |
| 08:56 |
* jeff |
steals jeff_'s tea, per usual |
| 09:00 |
Dyrcona |
kmlussier: I just updated my dev vm with the latest sprint2-sprint3 updates. |
| 09:00 |
kmlussier |
Dyrcona++ |
| 09:01 |
Dyrcona |
My hunch is that it will resolve lp 1538702 for you. |
| 09:01 |
pinesol_green |
Launchpad bug 1538702 in Evergreen "webclient: Double-clicking copy from holdings view doesn't always select copy" [Undecided,Invalid] https://launchpad.net/bugs/1538702 |
| 09:02 |
kmlussier |
Dyrcona: Yup. |
| 09:03 |
* kmlussier |
goes off to test the most recent fixes before proceeding with her day. |
| 09:06 |
|
kmlussier left #evergreen |
| 09:06 |
|
kmlussier joined #evergreen |
| 09:11 |
|
maryj joined #evergreen |
| 09:41 |
|
yboston joined #evergreen |
| 10:56 |
tsbere |
Just throwing this out here: If anyone has looked at CT-20 bluetooth barcode scanners and found that Codabar always outputs start/stop characters I am willing to share the "Turn that off" codes I figured out that aren't in the manual. |
| 10:57 |
* tsbere |
is also willing to share said manual, for that matter, as all he could find posted online was the CT-10 manual (which uses the same codes, BTW) |
| 11:01 |
* mmorgan |
would be interested in tsbere's codes to turn those off. |
| 11:01 |
|
Christineb joined #evergreen |
| 11:03 |
tsbere |
mmorgan: http://tomtrunk.mvlcstaff.org/Codabar%20Start%20Stop%20Chars%20On.png http://tomtrunk.mvlcstaff.org/Codabar%20Start%20Stop%20Chars%20Off.png |
| 11:04 |
tsbere |
You need to enter setup mode to use them and don't forget to exit with save |
| 11:10 |
* mmorgan |
needs to dig out that scanner to give it a try |
| 11:10 |
mmorgan |
tsbere++ |
| 11:11 |
tsbere |
mmorgan: I also made up a libreoffice "Pairing, configuration, and inventory mode" document. The configuration is basically just the codabar pieces. |
| 11:12 |
* tsbere |
kindof went nuts with figuring that out a few nights ago because he was bored, his internet was acting flaky, and there was nothing good on TV |
| 11:48 |
|
RoganH joined #evergreen |
| 12:15 |
|
bmills joined #evergreen |
| 12:30 |
csharp |
@swill [tea [bartender]] |
| 12:30 |
* pinesol_green |
grabs a bottle of Pink Champale and sends it sliding down the bar to brews and pours a pot of Keemun Full Leaf Tea, and sends it sliding down the bar to fills a pint glass with Blanche De Brooklyn, and sends it sliding down the bar to csharp (http://beeradvocate.com/beer/profile/45/2160) (http://ratetea.com/tea/foojoy/keemun-full-leaf/6686/) |
| 12:41 |
|
bmills joined #evergreen |
| 12:42 |
csharp |
so on miker's advice, we moved from an every 15 minute hold targeter cron to a once-per-night cron, and it has been running for unreasonably long times (about 14h last night) |
| 12:43 |
csharp |
I can see from pgbadger that some of the queries to deleted from the hold_copy_map were subject to lock waits |
| 12:43 |
csharp |
we have 5 concurrent processes running, which worked well for us before, but I'm wondering if we should lower it - any thoughts? |
| 12:43 |
miker |
csharp: do you have any parallelism enabled? |
| 12:43 |
csharp |
miker: yessir |
| 12:43 |
miker |
how much? |
| 12:43 |
csharp |
5 |
| 12:45 |
csharp |
I'm thinking that the lock waits may be part of the delay and was wondering if it makes sense to lower rather than raise that number |
| 12:45 |
miker |
IMHO, you have the cpu time for a lot more than 5 for an overnight run... perhaps that will help |
| 12:45 |
csharp |
ok - that works too |
| 12:45 |
csharp |
I'll up it to 8 and see what happens |
| 12:47 |
tsbere |
csharp: MVLC runs 6 every 15 minutes. |
| 12:47 |
miker |
fwiw, I was thinking 20 or so, but 8 should help |
| 12:47 |
csharp |
miker: ok - I'll see what 20 does ;-) |
| 13:04 |
|
edoceo joined #evergreen |
| 13:27 |
|
jihpringle joined #evergreen |
| 13:38 |
* kmlussier |
chuckles at the 1 minute age hold protection somebody put into webby. |
| 13:39 |
kmlussier |
It doesn't take much to amuse me. |
| 13:40 |
JBoyer |
Me first! The rest, whenever. |
| 13:49 |
tsbere |
kmlussier: Not the most useless one I have seen.... |
| 13:49 |
* tsbere |
found out on accident that those intervals don't have to be *positive* |
| 13:50 |
kmlussier |
Ha ha. No, that doesn't sound terribly useful. |
| 13:53 |
tsbere |
"We are going to protect it from non-local holds up until 3 weeks before we create the item" is a fun sounding one, isn't it? >_> |
| 14:20 |
mceraso |
Just curious if there is anyone out there who runs their entire Evergreen system with VMs using a cloud-based service? |
| 14:20 |
mceraso |
Or if anyone knows of someone that does... |
| 14:23 |
RoganH |
I'm sure someone has at least experimented with it. I think I recall someone on open-ils talking about doing a trial with it not that long ago. But I don't know of anyone actually doing it at any significant scale, much less in production. |
| 14:28 |
mceraso |
RoganH: Thanks! I had a vague memory of something out there on the open-ils list. |
| 14:29 |
RoganH |
mceraso: and I think they were a new library exploring evergreen, probably just looking at a single vm install |
| 14:29 |
mceraso |
Ahhh, okay. |
| 14:31 |
RoganH |
mceraso: with that said, go for it! What could go wrong? <--- note this is not legally actionable advice if you actually take it |
| 14:35 |
Dyrcona |
We run ours on VMs, but not using a "cloud" service. (There is no cloud. There is only someone else's computers.) |
| 14:36 |
Dyrcona |
The cloud is all the "wibbly wobbly, timey wimey stuff" in between you and them. |
| 14:36 |
mceraso |
RoganH: haha! It's something that we are potentially considering. |
| 14:37 |
mceraso |
Dyrcona: Very, very true |
| 14:37 |
Dyrcona |
That said, I've toyed with the notion of setting up OpenStack to run VMs for Evergreen, but not enough hours in the day. |
| 14:38 |
krvmga |
i've looked at clouds from both sides now... |
| 14:38 |
Dyrcona |
I would also imagine that ESI's Sequoia might be in the same ball park. |
| 14:38 |
Dyrcona |
krvmga++ |
| 14:49 |
RoganH |
Dyrcona: I always assumed that they mean insubstantial with moisture when they said clouds :) |
| 14:51 |
RoganH |
When people say VMs I usually assume they're renting some somewhere they don't have local access. Not a local dedicated infrastructure. |
| 14:53 |
miker |
mceraso: our Sequoia platform is a private automated cloud, like Dyrcona says |
| 14:53 |
Dyrcona |
RoganH: We run our own VMs and can build some in an automated way, but don't really have a "cloud" infrastructure. |
| 14:54 |
RoganH |
Dyrcona: Yeah, that's what I assumed. Local VMs are so common now I assume people are using them. |
| 14:54 |
miker |
and, agreed re <airquotes>cloud</> |
| 14:55 |
miker |
though the VM part of Sequoia is by far the least interesting bit |
| 14:55 |
Dyrcona |
RoganH: Ah, I misunderstood part of what you meant. |
| 14:59 |
mceraso |
Thanks all! At this point, we are trying to figure out what the potential logistics could be |
| 15:00 |
RoganH |
Dyrcona: It's become part of the evolution of the terms where they mean one thing but people (imho) are gradually using it slightly differently. Sounds like we're using it the same way. |
| 15:03 |
Dyrcona |
yep |
| 15:04 |
|
afterl joined #evergreen |
| 15:55 |
|
afterl left #evergreen |
| 16:04 |
|
jlitrell joined #evergreen |
| 16:05 |
csharp |
reports++ |
| 16:06 |
csharp |
I know it's rare for me to increment reports karma, but when they keep me from creating another server-side thing that connects to a third-party on behalf of a library, I love 'em |
| 16:18 |
dbwells |
csharp: Just FYI, http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/dbwells/lp1528627_masterkey_poc |
| 16:21 |
csharp |
dbwells: ooooh - cool - I'll play with that when I get a chance! |
| 16:24 |
csharp |
dbwells++ |
| 16:24 |
RoganH |
I feel like I should be decrementing reports on general principle. |
| 16:24 |
RoganH |
dbwells++ |
| 16:24 |
RoganH |
That will be awesome to have. |
| 16:27 |
berick |
reports++ |
| 16:28 |
berick |
if you know what you're doing, reports are great |
| 16:28 |
berick |
(not to imply that i always know what i'm doing, but sometimes I do) |
| 16:29 |
berick |
dbwells++ (password stuff) |
| 16:32 |
RoganH |
berick: that's exactly the problem, the learning curve is high enough and most staff use it so rarely that very few ever know what they're doing. For those few that use it regularly, it's fine. |
| 16:33 |
miker |
RoganH: but we have a plan, eh? ;) |
| 16:33 |
RoganH |
miker: it resembles a plan anyway. :) |
| 16:34 |
miker |
it has plan-ish outlines |
| 16:34 |
RoganH |
miker: agreed |
| 16:34 |
kmlussier |
There's a plan? Is it a secret plan? |
| 16:34 |
miker |
kmlussier: RoganH and I have tossed "direct SQL for reports" around for ... a long time |
| 16:35 |
kmlussier |
Ah, ok. That would be good. |
| 16:35 |
RoganH |
kmlussier: I think it would serve a different audience than the current reporter but be useful. |
| 16:36 |
kmlussier |
I'm not a big user of reports, but I hear high praise about reports from our people who are good at using them. |
| 16:37 |
kmlussier |
In our case, it's the consortium staff who creates the templates, so the frontline staff don't need to worry about the high learning curve. |
| 16:37 |
RoganH |
kmlussier: same. Unfortunately they're the minority in my consortium because they're the few at systems big enough that they stay in regular practice. |
| 16:38 |
RoganH |
kmlussier: at least in SC the line between front line staff and systems staff is awfully thin at a lot of libraries. |
| 16:39 |
kmlussier |
RoganH: Yeah, I think we have more centralized staff up in these parts. It helps. |
| 16:40 |
RoganH |
kmlussier: that's been my impression as well |
| 16:40 |
RoganH |
gotta run, sick staff at a branch so I have to help them close, have a good weekend all! |
| 17:01 |
Stompro |
Saving notification preferences in the catalog doesn't update current holds, right? I think that would be a good enhancement, unless it already happens. |
| 17:02 |
jeff |
yeah, we've hacked that in place here. |
| 17:02 |
jeff |
i've argued for it a few times, perhaps arguing with code might be a good place to start. :-) |
| 17:02 |
jeff |
but i know lots of people have different opinions on how that "should work" |
| 17:02 |
jeff |
and what should be possible. |
| 17:04 |
jeff |
i tend to favor "notification settings are per patron, not per hold" -- with maybe the ability to override per hold, but that might take some convincing :-) |
| 17:04 |
Stompro |
jeff, I would agree with you on that. I'm just seeing way too many mistakes made. |
| 17:05 |
jeff |
most common is: patron has a new phone number, staff does not manually review and set phone notification on existing outstanding holds. |
| 17:05 |
Stompro |
If someone changes ISP's and gets a new email, I don't really get how they are currently supposed to update all their holds. |
| 17:05 |
jeff |
email is the exception. |
| 17:05 |
Stompro |
Wait... bad example. |
| 17:05 |
jeff |
because that's just a boolean on the hold. |
| 17:05 |
Stompro |
Sorry, just remembered that. |
| 17:06 |
jeff |
but even there: patron with a landline and no email transitions to a no-landline email user. :-) |
| 17:07 |
|
mmorgan left #evergreen |
| 17:08 |
Stompro |
Thanks Jeff. |
| 17:11 |
Stompro |
Maybe a library settings "Update holds when notification preferences are changed" so each org can choose if they want that behavior. |
| 17:11 |
kmlussier |
jeff: I think it would be useful to send out a message to the general list to see if people really are using it on a per-hold basis. When the question has been raised here before, I think most people agreed with you on the per-patron. |
| 17:12 |
jeff |
Stompro: which holds do you update, then? only the ones that had the previous default? :-) |
| 17:12 |
kmlussier |
But we're just a small piece of the community in here. :) |
| 17:12 |
Stompro |
I don't see that it is even possible for users to see what the notification settings are on their current holds, or change them. |
| 17:12 |
jeff |
Stompro: it is not, last i looked. |
| 17:12 |
Stompro |
I would update all the holds with the new defaults. |
| 17:13 |
kmlussier |
I like the idea of a dialog asking "Do you want to update the contact information on these holds too?" |
| 17:14 |
* kmlussier |
wanders off to dinner while pondering the two competing branches that affect patron's circulation history. |
| 17:14 |
Stompro |
I just cannot picture someone saying... Well, I want to get an email about this one, and a text message for this one, but this one I need to hide, so don't want any notification. |
| 17:15 |
Stompro |
But our old system never had that capability so I'm just not used to that. |
| 17:16 |
|
mdriscoll left #evergreen |
| 17:53 |
|
bmills joined #evergreen |
| 18:46 |
|
jlitrell joined #evergreen |
| 18:59 |
|
dbwells_ joined #evergreen |
| 19:57 |
|
Bmagic_ joined #evergreen |
| 19:57 |
|
hopkinsju_ joined #evergreen |
| 19:57 |
|
dluch_ joined #evergreen |
| 20:01 |
|
eby__ joined #evergreen |
| 20:03 |
|
sandbergja2 joined #evergreen |
| 20:05 |
|
eady joined #evergreen |
