| Time |
Nick |
Message |
| 01:06 |
|
gmcharlt_ joined #evergreen |
| 01:06 |
|
Shae_ joined #evergreen |
| 04:44 |
|
ejk_ joined #evergreen |
| 04:45 |
|
bshum_ joined #evergreen |
| 04:46 |
|
mceraso joined #evergreen |
| 04:55 |
|
wsmoak joined #evergreen |
| 05:12 |
|
sard joined #evergreen |
| 06:47 |
|
TARA joined #evergreen |
| 07:17 |
|
rjackson_isl joined #evergreen |
| 07:53 |
|
mrpeters joined #evergreen |
| 08:05 |
|
ericar joined #evergreen |
| 08:36 |
|
rgagnon joined #evergreen |
| 08:36 |
|
mmorgan joined #evergreen |
| 08:41 |
|
JBoyer joined #evergreen |
| 08:43 |
|
kmlussier joined #evergreen |
| 08:49 |
|
Dyrcona joined #evergreen |
| 08:52 |
kmlussier |
Good morning #evergreen channel! I hope everyone has a great day today! |
| 08:52 |
kmlussier |
@coffee [someone] |
| 08:52 |
* pinesol_green |
brews and pours a cup of Nicaragua El Progresso COE Lot #1, and sends it sliding down the bar to rashma |
| 08:52 |
Dyrcona |
Traffic was nuts. Must have been an accident on 93 South. |
| 08:52 |
kmlussier |
@tea [someone] |
| 08:52 |
* pinesol_green |
brews and pours a pot of Top Leaf™ Green Tea, and sends it sliding down the bar to ldw (http://ratetea.com/tea/mellow-monk/top-leaf/1186/) |
| 08:52 |
mmorgan |
Good Morning! |
| 08:53 |
kmlussier |
Dyrcona: I normally don't need to deal with traffic on a telecommuting day, but I had to drive up from the Cape this morning and hit Providence traffic at the tail end. |
| 08:56 |
kmlussier |
Oh, it's point release day! |
| 08:57 |
Dyrcona |
It is, and given that Galen recently did 2.10.3, I assume 2.9 is the only thing getting released. |
| 08:58 |
kmlussier |
Looks like we have a few bug fixes. Shouldn't take long to work up some release notes. |
| 09:00 |
Dyrcona |
OK> |
| 09:02 |
kmlussier |
Dyrcona: Were you planning to look at any branches before cutting the release? If so, I'll hold off on the release notes. |
| 09:02 |
Dyrcona |
kmlussier: No, I'm not planning on looking at any branches today. |
| 09:14 |
|
bos20k joined #evergreen |
| 09:16 |
mmorgan |
Did I dream this? I seem to remember two ou settings for fees to add when a patron is billed for an item. A "processing fee" and "billing fee". Maybe I'm remembering this from a previous system... |
| 09:16 |
* mmorgan |
runs to get coffee |
| 09:17 |
Dyrcona |
mmorgan: Yeah, there are two fees for lost or long overdue items. One for a bill and one for a processing fee. |
| 09:17 |
Dyrcona |
There are more than two settings involved. |
| 09:20 |
mmorgan |
Dyrcona: Ok, I must have missed the bill one. I'll check again. It didn't come up in the filters I tried. |
| 09:22 |
kmlussier |
mmorgan: I usually find it by filtering by the word 'lost' |
| 09:23 |
Dyrcona |
Y'know what. I think it charges for lost items regardless. The processing fee gets added if it is set. |
| 09:24 |
kmlussier |
Yes, Dyrcona is right. |
| 09:24 |
kmlussier |
I was thinking of the setting to void the lost bill. |
| 09:25 |
Dyrcona |
Yes, there are settings for voiding lost bills on return. |
| 09:25 |
kmlussier |
It happens as part of the action trigger that sets the transaction to Lost |
| 09:25 |
mmorgan |
Dyrcona: Yes, it charges the price for lost items, and a processing fee if there is one set. Maybe I dreamed the additional "billing fee". I can't find such an option. |
| 09:25 |
mmorgan |
And I do find all the ones for voiding. Lots of those. |
| 09:25 |
Dyrcona |
mmorgan: By billing fee, I thought you meant charging the price of the lost item. |
| 09:25 |
kmlussier |
mmorgan: Could the additional billing fee be incorporated in the processing fee? |
| 09:27 |
mmorgan |
kmlussier: Lost Materials Procesing Fee adds a single amount when the item is billed (marked lost, or long overdue). |
| 09:27 |
kmlussier |
mmorgan: What is your use case? |
| 09:27 |
mmorgan |
I think I must be remembering an option from a previous system... |
| 09:28 |
JBoyer |
mmorgan, Also, is this something that you or someone else wants to enable, or are you just curious? Because as an option it sounds... extremely unpopular. |
| 09:28 |
Dyrcona |
I could see a use for a "collections fee," charged if a patron is sent to collections, or possibly one for sending a printed bill. |
| 09:28 |
Dyrcona |
Neither of those appear to exist, yet. |
| 09:29 |
mmorgan |
I was just looking for information to answer a question. A library wants to know what options exist. |
| 09:30 |
kmlussier |
mmorgan: There is also the minimum and maximum item price fees that can be used. Not sure if it fits in with your question at all. |
| 09:30 |
mmorgan |
The question was, is there a per billed item processing fee? (yes) Is there also a per user "billing fee"? So... |
| 09:31 |
mmorgan |
If a user is billed for three items, or 10 items, one billing fee would be charged. |
| 09:31 |
kmlussier |
Oh, I see. So it sounds similar to what Dyrcona was saying earlier. A fee for sending the printed bill, which would be set for one bill not matter how many items. |
| 09:31 |
mmorgan |
rather than a procesing fee per item. |
| 09:31 |
kmlussier |
No, that doesn't exist. :) |
| 09:32 |
Dyrcona |
You could do it by adding a grocery bill to the patron's account. |
| 09:32 |
mmorgan |
Yes, like an adminstrative fee for needing to do the work to bill the patron, and send the info to the bursar, etc. |
| 09:32 |
mmorgan |
Ok, so I did dream it ;-) |
| 09:32 |
Dyrcona |
It could be automated as part of a process to generate printed bills. |
| 09:32 |
kmlussier |
I dream all the time about functionality that doesn't exist. |
| 09:33 |
mmorgan |
kmlussier: Yes! It causes great confusion sometimes :-/ |
| 09:33 |
Dyrcona |
Generally, that's what the processing fee on lost and damaged items are about. |
| 09:34 |
Dyrcona |
Charging for the staff time to process the items. |
| 09:35 |
mmorgan |
I don't think the library in question necessarily wants to do this, they were looking for more info on the options that were available. |
| 09:38 |
mmorgan |
kmlussier: ok, thanks. They might be interested in that, too. Thanks for the input, all! |
| 09:38 |
mmorgan |
kmlussier++ Dyrcona++ |
| 09:39 |
|
jvwoolf joined #evergreen |
| 09:44 |
* kmlussier |
just realized she could steal...err...borrow language from gmcharlt's 2.10.3 release notes. :) |
| 09:44 |
kmlussier |
gmcharlt++ |
| 09:47 |
|
yboston joined #evergreen |
| 09:48 |
tsbere |
kmlussier: "Re-use"? ;) |
| 09:59 |
pinesol_green |
[evergreen|Kathy Lussier] Docs: Adding 2.9.5 Release Notes - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=6aeaffe> |
| 10:01 |
Dyrcona |
kmlussier++ |
| 10:05 |
Dyrcona |
So, looks like the db upgrade script will not really do anything but bump versions. But since I have a 2.9.4 concerto db hanging around, I'll test the upgrade first. |
| 10:23 |
Dyrcona |
Um. I thought the make_release script would make an upgrade script even if it did nothing. |
| 10:53 |
|
Christineb joined #evergreen |
| 10:55 |
|
ericar_ joined #evergreen |
| 11:04 |
|
kmlussier joined #evergreen |
| 11:17 |
|
TARA joined #evergreen |
| 11:18 |
|
collum joined #evergreen |
| 11:36 |
|
bmills joined #evergreen |
| 11:37 |
|
sandbergja joined #evergreen |
| 11:42 |
|
brahmina joined #evergreen |
| 11:43 |
|
rfrasur joined #evergreen |
| 12:10 |
|
edoceo joined #evergreen |
| 12:13 |
dbwells |
kmlussier: Do you have a moment to talk about bug #1315552? |
| 12:13 |
pinesol_green |
Launchpad bug 1315552 in Evergreen "Duplicate initial search results where copy circ lib/call number owning lib are different" [Medium,Confirmed] https://launchpad.net/bugs/1315552 |
| 12:14 |
kmlussier |
No, actually, I'm about to step away for a bit. But I'll be around later this afternoon. |
| 12:14 |
dbwells |
kmlussier: okay, I'll try to catch you later. |
| 12:19 |
* mmorgan |
was just catching up on that very bug :) |
| 12:43 |
|
ericar_ joined #evergreen |
| 12:44 |
dbwells |
kmlussier: mmorgan: I responded on the bug to help clarify what the proposed fix does and doesn't do, hope it helps. |
| 12:44 |
|
jihpringle joined #evergreen |
| 12:58 |
|
mdriscoll joined #evergreen |
| 13:18 |
|
TARA joined #evergreen |
| 13:20 |
Dyrcona |
Release 2.9.5 is published on the downloads page. |
| 13:22 |
jeff |
Dyrcona++ |
| 13:25 |
Dyrcona |
There's no db upgrade script, 'cause there wasn't anything to upgrade. |
| 13:25 |
|
geoffsams joined #evergreen |
| 13:27 |
miker |
that is, I think, the very best kind of upgrade |
| 13:27 |
miker |
Dyrcona++ |
| 13:33 |
|
agoben joined #evergreen |
| 13:33 |
* mmorgan |
just posted a brief comment to 1315552 and is now stepping out for a bit. |
| 13:53 |
* Dyrcona |
just published the 2.9.5 release announcement on the community blog. |
| 14:01 |
|
ericar_ joined #evergreen |
| 14:02 |
gmcharlt_ |
given the early release of 2.10.3 and that there have only been a couple patches in rel_2_10 since then, I'm thinking of doing the 2.10.4 release on Wednesday 5/25 |
| 14:02 |
gmcharlt_ |
then go back to the normal schedule in June (adjusted for my ALA attendance) |
| 14:03 |
|
gmcharlt joined #evergreen |
| 14:03 |
gmcharlt |
note: Wednesday, not Thursday, as Koha has a major release scheduled for the 26th |
| 14:05 |
|
TARA joined #evergreen |
| 14:08 |
* Dyrcona |
was considering postponing this release, and may have to make a new tarball anyway. :) |
| 14:25 |
Dyrcona |
I added a minimal db upgrade script and reuploaded the tarball. |
| 14:38 |
pinesol_green |
[evergreen|Jason Stephenson] Forward port 2.9.4 to 2.9.5 db upgrade script. - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=12164b7> |
| 14:46 |
|
ericar_ joined #evergreen |
| 15:58 |
|
jlitrell joined #evergreen |
| 17:02 |
|
mmorgan left #evergreen |
| 17:09 |
|
kmlussier joined #evergreen |
| 18:12 |
|
artunit_away joined #evergreen |
| 18:42 |
|
mrpeters joined #evergreen |
| 21:12 |
bshum |
Hmm, well Open-ILS/src/sql/Pg/t/regress/lp957466_update_date_and_source.pg is failing on live |
| 21:12 |
bshum |
http://testing.evergreen-ils.org/~live/test.21.html |
| 21:12 |
bshum |
I assume it's cause of some change to vandelay recently |
| 21:21 |
bshum |
https://bugs.launchpad.net/evergreen/+bug/1447746 |
| 21:21 |
pinesol_green |
Launchpad bug 1447746 in Evergreen "Do not update bib source on match-only merge" [Wishlist,Fix committed] |
| 21:21 |
bshum |
Probably that one |
| 21:22 |
bshum |
Maybe something else, but that seems likely to have shifted something |
| 21:25 |
bshum |
@decide bugs or naptime? |
| 21:25 |
pinesol_green |
bshum: go with bugs |
| 21:25 |
bshum |
No, that seems like a horrible idea, for shame pinesol_green |
| 23:43 |
|
book` joined #evergreen |
