Time |
Nick |
Message |
04:54 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
07:02 |
|
akilsdonk joined #evergreen |
07:13 |
|
TaraC joined #evergreen |
07:50 |
|
collum joined #evergreen |
08:23 |
|
mrpeters joined #evergreen |
08:28 |
|
mmorgan joined #evergreen |
08:31 |
|
graced joined #evergreen |
08:34 |
|
Shae joined #evergreen |
08:52 |
|
ericar joined #evergreen |
08:54 |
|
akilsdonk joined #evergreen |
08:57 |
|
maryj joined #evergreen |
09:05 |
|
Newziky joined #evergreen |
09:12 |
kmlussier |
Is there a reason why, on the downloads page, we link to release notes at http://evergreen-ils.org/documentation/release/RELEASE_NOTES_2_8.html instead of linking to the ones in the official docs? |
09:13 |
kmlussier |
Well, I guess it looks nicer to have the entirety of the release notes listed on one page. I withdraw my question. |
09:15 |
kmlussier |
berick: I made some additions to the release notes yesterday that will need to be incorporated in the notes we link to from the downloads page. But I expect more tweaking to happen early next week. so you may want to hold off until then. |
09:16 |
|
RoganH joined #evergreen |
09:21 |
|
yboston joined #evergreen |
09:40 |
|
akilsdonk joined #evergreen |
09:42 |
|
Dyrcona joined #evergreen |
09:53 |
berick |
kmlussier: OK. I'm happy to update them when you're done |
10:24 |
kmlussier |
Either I was wrong when I reported bug 1438362 or a fix for the bug has already been loaded on webby. |
10:24 |
pinesol_green |
Launchpad bug 1438362 in Evergreen "Web staff client: secondary permission groups missing from patron registration screen" (affected: 1, heat: 6) [Undecided,New] https://launchpad.net/bugs/1438362 |
10:24 |
kmlussier |
If I was wrong, I should mark it invalid. If it was indeed a bug that has been fixed on webby, then I should leave it open so the patch can be added there. |
10:25 |
kmlussier |
I suspect I was wrong because I didn't realize the secondary permission group button never appears with new registrations. |
10:31 |
Dyrcona |
Oh no! We're four cents over budget on our new servers. |
10:32 |
mmorgan |
Quick! Check under the couch cushions! |
10:33 |
Dyrcona |
It looks really odd on the quote: $30,000.04. :) |
10:33 |
jeff |
@blame floating point math |
10:33 |
pinesol_green |
jeff: floating point math musta been an Apple employee. |
10:37 |
jeff |
Dyrcona: this is what came to mind first: http://dilbert.com/strip/1995-06-24 |
10:40 |
Dyrcona |
jeff: I liked that one. |
10:41 |
Dyrcona |
One of my favorite quotes: UNIX is user friendly. It's just picky about who its friends are. |
10:45 |
RoganH |
Dyrcona++ |
10:49 |
Dyrcona |
Heh. I like today's Dilbert. |
10:49 |
Dyrcona |
I stopped reading Dilbert regularly around 2002. |
10:50 |
Dyrcona |
Someone should put this on badges: "Hi! I'm Dick from the Internet." |
10:59 |
berick |
wow, that site is hard to look at |
10:59 |
berick |
is there an rss feed i'm not seeing? |
11:00 |
RoganH |
Dyrcona: reminds me of the Penny Arcade internet theory. https://cdn.shopify.com/s/files/1/0042/9942/products/dickwad2_det_1024x1024.jpg?v=1305060896 |
11:00 |
Dyrcona |
RoganH: Ah, but the cartoon version is more profane and funnier. |
11:01 |
RoganH |
Dyrcona: I was trying to keep it relatively clean for IRC :) |
11:01 |
Dyrcona |
heh. |
11:05 |
|
taterr joined #evergreen |
11:06 |
|
taterr left #evergreen |
11:27 |
|
sarabee joined #evergreen |
11:49 |
|
sandbergja joined #evergreen |
11:49 |
kmlussier |
@weather 02771 |
11:49 |
pinesol_green |
kmlussier: The current temperature in Rumford, East Providence, Rhode Island is 56.1°F (11:40 AM EDT on April 03, 2015). Conditions: Overcast. Humidity: 73%. Dew Point: 48.2°F. Pressure: 29.84 in 1010 hPa (Steady). Wind Advisory in effect from 10 am to 9 PM EDT Saturday... |
11:50 |
RoganH |
@weather 29732 |
11:50 |
pinesol_green |
RoganH: The current temperature in Winthrop University, Rock Hill, South Carolina is 72.9°F (11:50 AM EDT on April 03, 2015). Conditions: Clear. Humidity: 56%. Dew Point: 55.4°F. Pressure: 30.07 in 1018 hPa (Steady). |
11:50 |
kmlussier |
RoganH: I'll trade weather reports with you |
11:51 |
RoganH |
kmlussier: I appreciate the offer but I'll live with the burden of living in the south for now. |
11:51 |
kmlussier |
RoganH: You'll be sorry when July/August rolls around. :) |
11:52 |
* kmlussier |
is actually quite pleased with today's temps. |
11:52 |
kmlussier |
Now, if I could just go outside to enjoy them. |
11:52 |
RoganH |
kmlussier: it's not always so bad, last year the summer was actually pretty mild but yeah, July and August can be like in a sauna in Hell |
11:53 |
RoganH |
kmlussier: But now that gmcharlt has moved back I'm expecting it to be pretty bad because the universe knows how much he prefers the heat to the cold |
11:53 |
mmorgan |
\me is pleased with the current temp, too. The melting continues...:) |
11:54 |
gmcharlt |
RoganH: refrigerate the entire neighborhood? |
11:54 |
gmcharlt |
DON'T MIND IF I DO!!!! |
11:54 |
gmcharlt |
;) |
11:54 |
RoganH |
:) |
11:55 |
kmlussier |
mmorgan: Do you still have snow? I think yesterday cleared out the rest of ours. Now I'm just waiting for the crocuses to begin appearing. |
11:56 |
mmorgan |
kmlussier: Oh yes, we do! Still small mountains in places, but some actual grass (such as it is) is beginning to appear. |
11:56 |
mmorgan |
Not much sign of plant life yet. |
11:58 |
kmlussier |
The example text on the patron registration form typically only displays if there is a regex supplied in the OU settings. |
11:58 |
kmlussier |
But the DOB example text displays even if the "Format Dates with this pattern" setting is null. |
11:59 |
kmlussier |
How does the system decide what to show as an example, in that case? Is it hardcoded to mm/dd/yyyy. Or is it looking at some other setting? |
12:03 |
jeffdavis |
Last I checked, the example was hardcoded. |
12:03 |
kmlussier |
jeffdavis: Thanks! |
12:05 |
jeffdavis |
kmlussier: hang on a sec while I double-check my memory though ;) |
12:09 |
|
graced joined #evergreen |
12:15 |
jeffdavis |
kmlussier: my mistake, looks like there's a line in register.js that checks the format.date org setting |
12:15 |
Dyrcona |
@weather 01845 |
12:15 |
pinesol_green |
Dyrcona: The current temperature in WB1CHU, Lawrence, Massachusetts is 61.0°F (12:15 PM EDT on April 03, 2015). Conditions: Clear. Humidity: 53%. Dew Point: 44.6°F. Pressure: 29.80 in 1009 hPa (Steady). Wind Advisory in effect from 10 am to 9 PM EDT Saturday... |
12:15 |
kmlussier |
jeffdavis: Yes, but if that org setting is null, it still displays an example here m/dd/yyyy |
12:16 |
Dyrcona |
kmlussier: It is common to have a hard coded fall back for when a setting is not set. |
12:17 |
kmlussier |
OK, then. That's what I was trying to verify. If that fall back was hardcoded or coming from somewhere else. |
12:17 |
kmlussier |
jeffdavis++ Dyrcona++ |
12:18 |
jeffdavis |
ftd.appendChild(document.createTextNode(localeStrings.EXAMPLE + dojo.date.locale.format(new Date(1970,0,31),{selector: "date", fullYear: true, datePattern: (orgSettings['format.date'] ? orgSettings['format.date'] : null)}))); |
12:20 |
kmlussier |
jeffdavis: That actually makes sense to me. Thanks! :) |
12:21 |
Dyrcona |
Glad that makes sense to someone. :) |
12:25 |
* csharp |
just read the title of bug 1440114 and wondered what a "support blanket" is |
12:25 |
pinesol_green |
Launchpad bug 1440114 in Evergreen "Support blanket orders in acquisitions via direct charges" (affected: 1, heat: 6) [Wishlist,New] https://launchpad.net/bugs/1440114 |
12:25 |
csharp |
@who needs a support blanket? |
12:25 |
pinesol_green |
csharp needs a support blanket. |
12:26 |
csharp |
pinesol_green: well played, my friend. well played |
12:26 |
pinesol_green |
csharp: I am only a bot, please don't think I'm intelligent :) |
12:26 |
pinesol_green |
csharp: Sorry, that command is only available to Evergreen Premium™ Subscribers. Please upgrade your subscription ASAP! |
12:26 |
mmorgan |
:) |
12:26 |
kmlussier |
Ha ha. I read it the same way. |
12:35 |
Dyrcona |
Where's Linus when you need him? |
12:41 |
Dyrcona |
Trivia of the day: I tried to learn Linus and Lucy on the piano, but the left hand proved too difficult for me. |
12:53 |
|
ericar_ joined #evergreen |
12:59 |
* berick |
chuckles at 'support blanket' |
12:59 |
berick |
the Evergreen Binky module |
13:05 |
kmlussier |
@love clam chowdah |
13:05 |
pinesol_green |
kmlussier: The operation succeeded. kmlussier loves clam chowdah. |
13:20 |
Bmagic |
When a patron has a long overdue item, and they use the OPAC, their account summary will have a one in parenthesis (1) indicating that have 1 item checked out. When you click on it, the resulting page says "You have no items checked out" |
13:21 |
Bmagic |
Would this be because the code that sifts the items from action.circulation does not include the long overdue status? |
13:23 |
Bmagic |
Another way to phrase it: Should "special" circulations be considered at all in this context? |
13:25 |
bshum |
Hmm, that seems like a good thing to look at. |
13:25 |
bshum |
Depends on what long overdue means? |
13:26 |
bshum |
For me, I would think to show those circs to the user and count them. |
13:26 |
bshum |
But maybe this is a case for YAOUS? :\ |
13:27 |
kmlussier |
I would consider long overdues to still be checked out. |
13:27 |
berick |
i think they should show, too. |
13:27 |
Bmagic |
What does the TPAC do for Lost? |
13:27 |
Bmagic |
I think we have a bug here |
13:27 |
kmlussier |
Which is a distinct difference from what it should do for lost. |
13:27 |
Bmagic |
the TPAC says that they have 1 item checked out, but when you view the items that they have checked out, it shows none |
13:28 |
kmlussier |
We have an OU setting that says whether lost items should be included in the staff client count. I would think you would want the tpac count to be the same as the staff client count. |
13:29 |
berick |
for LO, the fix is simple. Account.pm:1385, remove 'LONGOVERDUE' from the array |
13:29 |
berick |
for tpac display |
13:30 |
Bmagic |
so, the count is different than the list of check outs? |
13:30 |
Bmagic |
and there is a setting for this? |
13:30 |
kmlussier |
Bmagic: There is a setting just for lost. Not long overdue. And it's for the patron summary only, not tpac. |
13:31 |
Bmagic |
kmlussier: I am speaking about the OPAC/TPAC only |
13:32 |
kmlussier |
Yes, I know. I was just musing that it would make sense for it to handle both counts. |
13:32 |
* kmlussier |
will stop musing now. |
13:32 |
Bmagic |
kmlussier: I see the setting "Items Out Long-Overdue display setting" "1 = top list, bottom list. 2 = bottom list" |
13:32 |
Bmagic |
Is that the setting you are talking about? |
13:33 |
kmlussier |
Include lost circulation in lump sum tallies in Patron Display |
13:33 |
Bmagic |
oh I see |
13:33 |
Bmagic |
So, did I uncover a bug in the OPAC/TPAC ? |
13:35 |
kmlussier |
For the long overdues? Yes, I would say it's a bug. |
13:36 |
kmlussier |
Given that there seemed to be initial consensus here that they should display as items out, I don't think a YAOUS is required. But that's just me. |
13:36 |
bshum |
I'd wait for csharp and his folks to weigh in. Since longoverdue was their feature, right? |
13:36 |
bshum |
:) |
13:36 |
kmlussier |
yeah |
13:38 |
* mmorgan |
thinks that "long overdue" implies that they are still checked out. But maybe that's just me :) |
13:39 |
Bmagic |
Here is a screen shot |
13:39 |
Bmagic |
https://drive.google.com/file/d/0B8kJTfmejGJ1TU1CLTNzRTl1N2s/view?usp=sharing |
13:42 |
kmlussier |
Whatever the desired behavior is, I think the fact that the count displays and then no titles display is a bug. It's just a matter of nailing down whether it should be part of the count and listed or whether it shouldn't. We can work that out on the bug report. |
13:45 |
Bmagic |
I took a quick peek at a patron who has the same scenario but instead of long overdue, it was lost, and it didn't show (1) for the lost circ |
13:45 |
Bmagic |
Is there a bug report? |
13:45 |
kmlussier |
Yes |
13:48 |
Bmagic |
Which bug? |
13:49 |
|
buzzy joined #evergreen |
13:49 |
kmlussier |
What I said in [13:42:08] |
13:51 |
Bmagic |
I dont see a bug number mentioned |
13:52 |
kmlussier |
Bmagic: Sorry, I thought you were asking if there was a bug there that was worthy of reporting. AFAIK, there isn't one. |
13:52 |
kmlussier |
But I haven't looked |
13:52 |
Bmagic |
Oh ok, I just made one then https://bugs.launchpad.net/evergreen/+bug/1440148 |
13:52 |
pinesol_green |
Launchpad bug 1440148 in Evergreen "Long overdue Items out TPAC OPAC display My Account" (affected: 1, heat: 6) [Undecided,New] |
13:58 |
|
ericar joined #evergreen |
14:21 |
* csharp |
appears |
14:22 |
kmlussier |
poof! |
14:24 |
csharp |
so, our issue is one of terminology, I think, and "longoverdue" has been fraught with misunderstanding and ambiguity since its inception |
14:24 |
csharp |
what we *wanted* was "auto-lost but use the term 'longoverdue' to show that it was system set" |
14:25 |
csharp |
some of our specifications were vague on some of the finer points, so there are some differences |
14:25 |
csharp |
the main one being whether longoverdue and paid for items should show on a patron account |
14:26 |
kmlussier |
Oh, but in this case are they paid for or are they just long overdue? |
14:26 |
csharp |
s/items/circs/ - even the terminology can get confusing just talking about it ;-) |
14:27 |
csharp |
we probably want them to act like Lost items and *not* show |
14:27 |
csharp |
but I can understand the thought behind the "longoverdue means still checked out" that led to the fact that they *do* continue to show after payment |
14:27 |
kmlussier |
csharp: OK, in that case then, it probably would be worthwhile to have a YAOUS. |
14:28 |
csharp |
I haven't seen Bmagic's issue yet, though |
14:28 |
csharp |
kmlussier: I agree, since there are different expectations |
14:28 |
kmlussier |
And I hadn't considered the after payment question. I think my opinion is different for longoverdues that have been paid. |
14:28 |
Dyrcona |
Well, for that you have lostandpaid. |
14:28 |
Dyrcona |
At least, you do now. ;) |
14:28 |
kmlussier |
But not all sites use lostandpaid. |
14:29 |
csharp |
yeah, we're not using lostandpaid |
14:29 |
* csharp |
makes note to investigate that later |
14:29 |
Dyrcona |
Too many options, choices, and knobs. It's as simple as that. :) |
14:29 |
csharp |
Dyrcona: true dat |
14:30 |
jeff |
relevant: bug 1424646 |
14:30 |
* csharp |
wishes our libraries had just gone with automatic lost and not gone down the longoverdue path |
14:30 |
pinesol_green |
Launchpad bug 1424646 in Evergreen "Paid-For Long Overdue Items Still Appear in "Other/Special Circulations" Window" (affected: 3, heat: 16) [Undecided,New] https://launchpad.net/bugs/1424646 |
14:30 |
kmlussier |
csharp: FWIW, I find that's it's difficult to outline every piece of behavior you need to outline when writing up specs for a project like this. Finer points always get missed. :) |
14:30 |
csharp |
jeff++ # thanks - I was pretty sure I'd done a bug on it |
14:30 |
csharp |
kmlussier: yup |
14:31 |
kmlussier |
csharp: We also have a couple of sites that are very happy the longoverdue functionality is there. |
14:31 |
csharp |
overall, we're really happy with it |
14:31 |
Dyrcona |
It's the same as lost, just a different name. |
14:31 |
kmlussier |
Although, even here, there are differences in the way our sites are implementing it. |
14:31 |
csharp |
if the paid-for longoverdues didn't show on the list of items out, we'd be cool |
14:31 |
Dyrcona |
We don't use it or lostand paid. We'd figured it would cause too much confusion. :) |
14:32 |
csharp |
and obviously, if Bmagic's OPAC-side issue affects us, we'll want that fix too |
14:32 |
Dyrcona |
csharp: That is a bug, IMO. |
14:32 |
csharp |
Dyrcona: the irony is that "longoverdue" was chosen so that it would be immediately clear to staff what had happened |
14:33 |
Dyrcona |
csharp: Yes, that seems like it would be simpler to explain than "lost" which could have different meanings. |
14:33 |
csharp |
after we implemented it, though, we got lots of "what is this?" tickets |
14:33 |
Dyrcona |
But, having a committee vote to change a numeric limit from 10 to 20 is enough to confuse some people. |
14:33 |
csharp |
Dyrcona: heh - we've got lots of examples like that |
14:34 |
Dyrcona |
In our case, all of the limits were 20 but this one, so the Executive committee decided it would be less confusing to make this one 20 also. :) |
14:34 |
Dyrcona |
Confusion over the change ensues.... |
14:34 |
csharp |
"and now we have X+1 problems..." |
14:35 |
Dyrcona |
In general, I think librarians, and circ staff in particular, do not like change. |
14:35 |
* Dyrcona |
has a MSLS, so is technically a librarian. |
14:37 |
Dyrcona |
csharp: And tomorrow it will be X+2. :) |
14:55 |
Bmagic |
csharp: we adpoted it with the thought that long overdue would happen first, then eventually the trigger to make them lost would come later. We didn't want the same functionality as lost in the mean time |
14:56 |
Bmagic |
csharp: So we introduced the library setting "Assess Billing When Marked Long-Overdue" from this bug https://bugs.launchpad.net/evergreen/+bug/1331174 |
14:56 |
pinesol_green |
Launchpad bug 1331174 in Evergreen "Long Overdue processing needs org unit settings separate from Lost Processing" (affected: 3, heat: 14) [Wishlist,Confirmed] |
15:01 |
mmorgan |
Bmagic: Have you implemented this? |
15:02 |
Bmagic |
mmorgan: We were sort of waiting for it to be tested, now that it has, we are feeling good about merging it |
15:06 |
mmorgan |
gotcha. How were you thinking of using the Long Overdue vs. Lost? |
15:35 |
Bmagic |
mmorgan: So the trigger would turn something into long overdue and fire an alert to the patron at 20 days overdue and not bill. Then at 40 days overdue, the trigger would mark them lost and bill them accordingly. For example. |
15:37 |
|
gsams joined #evergreen |
15:40 |
mmorgan |
Ok, thanks. We were thinking similarly. Probably longer intervals, though. We would also use the long overdue status to help staff identify the items better, and block the patron appropriately. |
15:48 |
|
mrpeters left #evergreen |
16:19 |
Bmagic |
mmorgan: exactly |
16:26 |
jonadab |
Just one more data point, the phrase "long overdue" to our staff means something different from "lost". "lost" means the patron's account has been charged for the item, "long overdue" merely means they can't check other items out until they deal with the item (either bring it back or declare it lost), IIRC. Something like that. |
16:52 |
mmorgan |
jonadab: Yes, that's what this option is meant to allow. A way to identify the items as seriously overdue, and provide a condition that can apply a block to the patron. |
16:53 |
jonadab |
Sounds good. |
17:05 |
|
mmorgan left #evergreen |
17:17 |
Bmagic |
What does a "-1" mean in the context of hold status? Inside a patron xul UI? |
17:18 |
Bmagic |
Another example of a status would be "Waiting for Copy" |
17:18 |
berick |
Bmagic: it means there's something inconsistent with with the hold |
17:19 |
berick |
"something ain't right" |
17:19 |
Bmagic |
berick: so it won't be filled? In this example, there is a current copy |
17:20 |
berick |
what's the copy status? |
17:20 |
phasefx |
Bmagic: happens most often with data migrations, say, a hold thinks it has something on the hold shelf but the item status doesn't agree |
17:20 |
Bmagic |
available |
17:20 |
berick |
that's it |
17:20 |
berick |
it should be on-holds-shelf or in-transit |
17:20 |
Bmagic |
could be the reshelver? |
17:21 |
|
Newziky left #evergreen |
17:21 |
berick |
if it was captured while reshelver was running, maybe |
17:22 |
Bmagic |
Thanks, I think that will get me to the answer |
17:40 |
csharp |
bmills: just sent you an email re: the shuttle |
17:40 |
csharp |
my flight is scheduled to arrive at 4:51 p.m. Tuesday and I'm hoping it will wait for me (understanding if not, though ;-)) |
18:10 |
Bmagic |
have a good weekend everyone! |
19:18 |
jeff |
oh, that's right. there's a conference coming up. |