Time |
Nick |
Message |
06:31 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
07:02 |
|
JBoyer joined #evergreen |
07:28 |
|
rjackson_isl joined #evergreen |
08:21 |
|
_bott_ left #evergreen |
08:24 |
|
_bott_ joined #evergreen |
08:34 |
|
kmlussier joined #evergreen |
08:37 |
|
mmorgan joined #evergreen |
08:52 |
|
Dyrcona joined #evergreen |
09:08 |
|
dbwells joined #evergreen |
09:23 |
|
bos20k joined #evergreen |
10:07 |
|
csharp joined #evergreen |
10:39 |
|
dwgreen joined #evergreen |
10:41 |
* bshum |
has scrubbed that spam from the IRC logs yesterday |
10:42 |
Dyrcona |
bshum++ |
10:47 |
|
Christineb joined #evergreen |
10:49 |
|
littlet joined #evergreen |
10:54 |
|
afterl joined #evergreen |
11:21 |
|
khuckins joined #evergreen |
11:30 |
|
jvwoolf joined #evergreen |
11:52 |
|
_adb joined #evergreen |
11:55 |
|
mdriscoll joined #evergreen |
12:05 |
|
littlet joined #evergreen |
12:09 |
csharp |
bshum++ |
12:10 |
|
_adb joined #evergreen |
12:10 |
csharp |
anyone know whether a Biblioteca selfCheck 1000 can be configured to ignore copy notes? we have a library that wants us to blow those away to accommodate the selfcheck and I'm thinking that's just silly :-/ |
12:18 |
mmorgan |
csharp: Do you mean copy alerts? |
12:22 |
|
jvwoolf1 joined #evergreen |
12:25 |
|
abowling joined #evergreen |
12:27 |
csharp |
mmorgan: actually, yes - copy alerts |
12:34 |
mmorgan |
We actually had a similar request from a library to remove a certain flavor of copy alerts for the same reason, different vendor. |
12:34 |
jeff |
csharp: if their support confirms that it cannot be ignored, then i'd support a sipserver feature to omit them for certain clients. |
12:35 |
csharp |
jeff: good idea |
12:36 |
mmorgan |
This particular flavor of copy alerts may have been overkill anyway, so not necessarily a bad thing. |
12:40 |
csharp |
I just don't like a) workarounds in general or b) deleting data we don't have to, but sounds like the immediate answer is to go with the deletion as a workaround, then work on a feature addition for SIPServer to make it unnecessary the next time |
12:57 |
mmorgan |
fire-alarms-- |
12:58 |
mmorgan |
Especially when it's 2 degrees. |
13:04 |
bshum |
Maybe the alarms are good, but it's the drills are what we find terribly inconvenient. |
13:05 |
bshum |
Or if it's that one person that burned popcorn... doh, there's always someone that does that. |
13:05 |
mmorgan |
:-[ |
13:05 |
mmorgan |
Not this time, though. |
13:06 |
mmorgan |
No explanation. Just went on long enough to get us outside. |
13:07 |
Dyrcona |
mmorgan: You have my sympathies. |
13:08 |
kmlussier |
mmorgan: Brrrr! A bad day for a fire alarm. |
13:23 |
|
jwoodard joined #evergreen |
13:36 |
jeff |
csharp: it's similar to something we've been playing with -- turning on SIP client display of copy alert messages but not actually passing what's in asset.copy.alert_message, but instead using it for messaging regarding the checkout, such as when checking out an item that was on hold for someone else, when they've authorized you to do so, etc. |
13:48 |
|
abowling left #evergreen |
14:03 |
|
abowling joined #evergreen |
14:42 |
|
afterl joined #evergreen |
14:52 |
kmlussier |
I still haven't caught up on all the IRC logs, but did we set a new date for the next point release or did we decide to wait until the 17th when the January point release is scheduled? |
14:56 |
dbwells |
kmlussier: I don't think anything was decided. I tried to poke a few folks last week, but people were understandably not very available. |
14:57 |
dbwells |
kmlussier: I would really hope for some eyes on bug 1730470 before the next point release, whenever it happens. |
14:57 |
pinesol_green |
Launchpad bug 1730470 in Evergreen "Receive move/selected action fails for Serial Control Field" [High,Confirmed] https://launchpad.net/bugs/1730470 |
14:57 |
kmlussier |
dbwells: Sure. I added that to my mental to-test list when I was going through email this morning. |
14:59 |
dbwells |
kmlussier: that would be great, thank you. |
15:00 |
* dbwells |
just realized he forgot the pullrequest tag, adds it |
15:03 |
|
mmorgan1 joined #evergreen |
15:25 |
JBoyer |
kmlussier, dbwells: I don't have a lot of say in that regard but I'd say just wait until 1/15 for the next point release since it's only 2 weeks away. |
15:38 |
kmlussier |
JBoyer: Yeah, that's what I was thinking too. |
15:47 |
|
mmorgan joined #evergreen |
16:51 |
|
Jillianne joined #evergreen |
17:03 |
|
mmorgan left #evergreen |
17:04 |
|
afterl left #evergreen |
17:16 |
|
Jillianne joined #evergreen |
17:34 |
|
Dyrcona joined #evergreen |
18:30 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
19:02 |
|
abowling1 joined #evergreen |
22:04 |
|
abowling joined #evergreen |
22:08 |
|
abowling1 joined #evergreen |
22:19 |
|
abowling2 joined #evergreen |
22:21 |
|
abowling3 joined #evergreen |