| Time |
Nick |
Message |
| 01:49 |
|
bmills1 joined #evergreen |
| 01:54 |
|
BigRig joined #evergreen |
| 02:49 |
|
bshum joined #evergreen |
| 04:58 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
| 07:22 |
|
collum joined #evergreen |
| 07:44 |
|
graced joined #evergreen |
| 07:48 |
|
rjackson_isl joined #evergreen |
| 07:56 |
kmlussier |
Good morning #evergreen |
| 07:56 |
kmlussier |
@tea |
| 07:56 |
* pinesol_green |
brews and pours a pot of Home, and sends it sliding down the bar to kmlussier (http://ratetea.com/) |
| 07:57 |
kmlussier |
A pot of Home? |
| 07:58 |
kmlussier |
@coffee [someone] |
| 07:58 |
* pinesol_green |
brews and pours a cup of Resiprocate Verita Espresso, and sends it sliding down the bar to ldw |
| 08:00 |
|
mrpeters joined #evergreen |
| 08:04 |
rjackson_isl |
Happy Friday kmlussier! |
| 08:10 |
|
_bott_ joined #evergreen |
| 08:21 |
|
akilsdonk joined #evergreen |
| 08:22 |
|
Newziky joined #evergreen |
| 08:25 |
kmlussier |
rjackson_isl: Happy Friday! :) |
| 08:26 |
rjackson_isl |
Best work day of week - especially around 4:30 PM - with added bonus of 67 for a high tomorrow and sunshine |
| 08:36 |
|
mmorgan joined #evergreen |
| 08:40 |
kmlussier |
@weather 02771 |
| 08:40 |
pinesol_green |
kmlussier: The current temperature in Rumford, East Providence, Rhode Island is 39.7°F (8:35 AM EDT on April 10, 2015). Conditions: Light Rain. Humidity: 97%. Dew Point: 39.2°F. Windchill: 39.2°F. Pressure: 30.06 in 1018 hPa (Falling). |
| 08:40 |
kmlussier |
The weekend holds much more promise. |
| 08:41 |
mmorgan |
Maybe by Monday all the snow will finally be gone :) |
| 08:46 |
|
ericar joined #evergreen |
| 08:47 |
|
Shae joined #evergreen |
| 08:56 |
|
sarabee joined #evergreen |
| 09:01 |
gmcharlt |
csharp: Mailman 3 is looking quite interesting |
| 09:02 |
|
Dyrcona joined #evergreen |
| 09:03 |
|
mrpeters joined #evergreen |
| 09:03 |
|
maryj joined #evergreen |
| 09:17 |
|
akilsdonk joined #evergreen |
| 09:36 |
Bmagic |
Is there any setting in Evergreen to remove items from the items out screen? Lost for example? Never checked in. |
| 09:36 |
Dyrcona |
Don't think so. |
| 09:36 |
Bmagic |
So, they need to be checked in to be removed |
| 09:36 |
Dyrcona |
They only disappear when the transaction is closed, i.e. xact_finish set. |
| 09:37 |
Dyrcona |
They need to be checked in and paid up. |
| 09:37 |
Bmagic |
Checking in Lost items would be a lie |
| 09:37 |
Bmagic |
and it messes with the billing, which we dont want |
| 09:37 |
Dyrcona |
Then why do you want them to go away? |
| 09:38 |
Dyrcona |
If they are lost and the patrons owes, I think you'd want to see the transactions. |
| 09:38 |
Bmagic |
The patron doesnt owe |
| 09:38 |
Bmagic |
they paid |
| 09:38 |
Bmagic |
then you check it in, and it voids the original fine |
| 09:38 |
Bmagic |
but the item is technically checked out, and therefore, still shows in the items out screen (on the bottom) |
| 09:39 |
Dyrcona |
Right. So, you have to add a fee to balance it out. |
| 09:39 |
mmorgan |
Bmagic: There's an org unit setting to control the display of Lost items, "Items Out Lost Display Setting" |
| 09:39 |
Bmagic |
mmorgan: I discovered that setting |
| 09:39 |
Bmagic |
mmorgan: it doesn't work the way we want it to |
| 09:39 |
Bmagic |
mmorgan: it would appear that the item still needs to be checked in for it to get totally off the screen |
| 09:40 |
Dyrcona |
There's code being worked on to take care of situations like this, but two people have worked on it for over two years, so I wouldn't hold my breath. |
| 09:40 |
mmorgan |
Did you say they have paid for the item? |
| 09:40 |
Bmagic |
yep, paid |
| 09:40 |
mmorgan |
Hmm. Ours disappear at that point. |
| 09:40 |
jeff |
Bmagic: are you aware of the new "lost and paid" support? |
| 09:41 |
Bmagic |
jeff: I am aware, but it's not implemented, Would this impact our situation if we were to implement it? |
| 09:41 |
mmorgan |
What about the org unit setting "Leave transaction open when lost balance equals zero"? How is that set for you? |
| 09:44 |
* mmorgan |
thinks that if the transaction is closing, the item should disappear from items out. |
| 09:44 |
Bmagic |
mmorgan: Set to false |
| 09:44 |
Bmagic |
mmorgan: I think the code looks for the column checkin_time and not xact_finish |
| 09:44 |
Dyrcona |
Bmagic: It might look for both. |
| 09:44 |
|
yboston joined #evergreen |
| 09:45 |
mmorgan |
In our experience, patron loses item, patron pays for item, item no longer shows on items out. |
| 09:45 |
Bmagic |
well, even both, means that checkin_time is required |
| 09:45 |
Bmagic |
and we are not checking it in (or don't think that's correct) |
| 09:46 |
Bmagic |
I'm going to run some more expierements |
| 09:47 |
mmorgan |
Just marked an item Lost on my test patron. Paid the bill and the item is gone from items out. |
| 09:48 |
mmorgan |
Item never got checked in. |
| 09:49 |
Bmagic |
mmorgan: that is good news, let me see what is going on here |
| 09:51 |
kmlussier |
I thought the setting mmorgan referred to above is the one that removed it from Items Out if it was fully paid. Strange that it isn't working for you that way. |
| 09:51 |
|
RoganH joined #evergreen |
| 09:53 |
mmorgan |
"Leave transaction open when lost balance equals zero" is unset for us, and my understanding is that would default to FALSE |
| 09:53 |
mmorgan |
Could be that the transactions aren't closing for some reason. |
| 09:54 |
bshum |
Well it might be a bad setting. Meaning it's bugged and false doesn't do what we expect, while unset is better... |
| 10:02 |
Dyrcona |
Bmagic: Is that setting set to true or false or not set? |
| 10:02 |
Dyrcona |
If it is true, it will leave the transactions open on the patron account. |
| 10:03 |
Dyrcona |
At least, that is my understanding of how it is supposed to work. |
| 10:03 |
Bmagic |
it's false |
| 10:04 |
Bmagic |
I think that long overdue is part of the equation here. I am going to ask the library for some details |
| 10:04 |
kmlussier |
Bmagic: That could be. I think csharp has reported a bug on that. |
| 10:04 |
Dyrcona |
Ah, long overude.... The code may not be checking that status correctly. |
| 10:04 |
Bmagic |
oh? |
| 10:04 |
Dyrcona |
over-rude? :) |
| 10:05 |
kmlussier |
bug 1424646 |
| 10:05 |
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 |
| 10:05 |
Bmagic |
I think perhaps, since long overdue assess bills just like lost, our libraries are voiding those bills |
| 10:05 |
bshum |
berick: gmcharlt asked about backporting https://bugs.launchpad.net/evergreen/+bug/1435494 to 2.8. To me, I read it as new feature meaning closed to backport, but will defer this to your decision on how to include it. |
| 10:05 |
pinesol_green |
Launchpad bug 1435494 in Evergreen "Clark Kent can over-consume system resources" (affected: 1, heat: 6) [Wishlist,Fix committed] |
| 10:07 |
Bmagic |
This code should stop long overdue from creating bills LP1331174 |
| 10:07 |
gmcharlt |
bshum: yeah, it straddles the line; I entered the bug as the wishlist, but it could also be viewed as a bugfix mitigated the bug "reporter allows users to write reports that can cause server indigestion" |
| 10:07 |
jeff |
bug 1331174 |
| 10:07 |
pinesol_green |
Launchpad bug 1331174 in Evergreen "Long Overdue processing needs org unit settings separate from Lost Processing" (affected: 3, heat: 14) [Wishlist,Confirmed] https://launchpad.net/bugs/1331174 |
| 10:09 |
berick |
bshum: i'd call that a bug fix |
| 10:10 |
berick |
bshum++ kmlussier++ ACQ merging/tseting |
| 10:11 |
kmlussier |
berick: We're always happy to test acq improvements in these parts. :) |
| 10:11 |
kmlussier |
berick++ |
| 10:11 |
* berick |
rebases bug 1380803 |
| 10:11 |
pinesol_green |
Launchpad bug 1380803 in Evergreen "PO totals do not include all amounts" (affected: 1, heat: 8) [Medium,Confirmed] https://launchpad.net/bugs/1380803 |
| 10:12 |
bshum |
berick: Alrighty, up to you. Since it has a release note, we probably should move that into the mainline notes for 2.8 so that it doesn't get lost in the darkness. |
| 10:13 |
kmlussier |
That reminds me. I have to merge another release note change. |
| 10:14 |
* kmlussier |
does it right now before she forgets again. |
| 10:18 |
* bshum |
decides to remove the 2.next milestones from all the bugs he merged yesterday. If they're fixes for 2.8.1, then it'd be good to have them closed and not lurking in 2.next (or moved to 2.9, since they'll likely be fix released and can be closed once 2.8.1 is cut) |
| 10:20 |
* berick |
wonders why bug fixes would ever target 2.next |
| 10:20 |
bshum |
berick: Pretty much. |
| 10:20 |
bshum |
:) |
| 10:21 |
berick |
;) |
| 10:26 |
jeff |
@eightball will this be the upgrade that drives us away from our 2.1-era opac templates? |
| 10:26 |
pinesol_green |
jeff: No clue. |
| 10:28 |
berick |
heh |
| 10:29 |
Dyrcona |
I sometimes target 2.next just to target something. |
| 10:29 |
pinesol_blue |
jeff: It is certain. |
| 10:30 |
berick |
soylent_green: why don't you have nutritional labels? |
| 10:30 |
soylent_green |
It would only confuse the consumer. |
| 10:31 |
berick |
true |
| 10:31 |
soylent_green |
It's good for you. Stop asking questions. |
| 10:32 |
* Dyrcona |
is surprised soylent_green isn't a registered nick. |
| 10:34 |
bshum |
Alright, in lieu of a future decision at the next dev meeting over how to handle release notes for maintenance .x releases of Evergreen series, I'm going to start a new heading for stuff like this for 2.7 |
| 10:34 |
pinesol_green |
[evergreen|Remington Steed] DOCS: Simplify release notes entry for AccessHandler - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=21a5a96> |
| 10:34 |
|
soylent_green joined #evergreen |
| 10:35 |
bshum |
I'm not sure what I'm going to name it quite yet... "Bug Fixes for Maintenance Releases" sounded wordy and annoying. |
| 10:36 |
Dyrcona |
Just Bug Fixes works for me. |
| 10:37 |
* bshum |
goes with the simple answer |
| 10:37 |
bshum |
Dyrcona++ |
| 10:37 |
kmlussier |
bshum: For 2.7? Awesome! |
| 10:38 |
kmlussier |
BTW, is that on the dev meeting agenda already? |
| 10:38 |
|
sandbergja joined #evergreen |
| 10:38 |
bshum |
kmlussier: It merged cleanly, and basically I'm running it on a 2.7-ish system right now. |
| 10:38 |
bshum |
If it's a bug fix, push it, push it real good. |
| 10:39 |
berick |
bshum++ |
| 10:40 |
|
collum joined #evergreen |
| 10:47 |
|
Shae_ joined #evergreen |
| 10:52 |
pinesol_green |
[evergreen|Ben Shum] Docs: Start a new section for bug fixes for 2.7 series - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=55555b7> |
| 10:52 |
pinesol_green |
[evergreen|Ben Shum] Docs: Move security bug fix note into the Bug Fixes area of 2.7 RELEASE NOTES - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=9cc10e9> |
| 10:52 |
pinesol_green |
[evergreen|Ben Shum] Docs: Update 2.8 RELEASE NOTES to include new Bug Fixes section - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=6c8a070> |
| 10:52 |
* bshum |
thinks in hindsight, he should have started with the backport to rel_2_6 first, and worked forward. Darn. |
| 10:53 |
* bshum |
learns his lesson and tries to fix everything anyways |
| 10:58 |
pinesol_green |
[evergreen|Ben Shum] Docs: Update 2.6 RELEASE NOTES to include new section on Bug Fixes - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=612ea94> |
| 11:25 |
|
bmills joined #evergreen |
| 11:26 |
|
krvmga joined #evergreen |
| 11:27 |
|
bmills joined #evergreen |
| 11:28 |
gmcharlt |
bshum: berick: I suppose I ought to send an EOL message to open-ils-general for 2.5? |
| 11:28 |
krvmga |
i don't recall seeing a resolution for reported 2.7 search slowness with format filters that was talked about on one of the mailing lists. was there? |
| 11:30 |
berick |
gmcharlt: that would be super. maybe include a note that 2.6 will also be EOL (technically, anyway) in a few months. |
| 11:30 |
berick |
hm, do we need to update the downloads page to show 2.6 as security only? |
| 11:31 |
gmcharlt |
berick: indeed - are we all in agreement that 2.6 is now security-only? |
| 11:31 |
Dyrcona |
krvmga: There has been discussion on Bug 1438136 |
| 11:31 |
pinesol_green |
Launchpad bug 1438136 in Evergreen "OPAC searching significantly slowed by adding format filters" (affected: 1, heat: 6) [Undecided,New] https://launchpad.net/bugs/1438136 |
| 11:31 |
berick |
gmcharlt: good question. (The déjà vu is overwhelming) |
| 11:32 |
krvmga |
Dyrcona: thanks |
| 11:33 |
kmlussier |
krvmga: One thing to remember is that C/W MARS is currently using search filter groups for format filters. The bug in question isn't related to search filter groups. |
| 11:33 |
kmlussier |
When you do your upgrade, you should probably move to MVF for your format limiting. |
| 11:33 |
krvmga |
kmlussier: thanks |
| 11:37 |
bshum |
berick: gmcharlt: I think that we decided that because 2.6 was released on 2014-04-16, we should keep it in regular release to get the full 12 months support, then move it to security-only next month. |
| 11:37 |
bshum |
But 2.5 is definitely done and over. |
| 11:38 |
bshum |
So more than likely, 2.6.8 will be the last regular bug fix 2.6 milestone. |
| 11:38 |
berick |
bshum: that's right, thanks for the reminder |
| 11:41 |
gmcharlt |
ok, then I think we can defer saying anything about 2.6 until after 2.6.8 is cut |
| 11:43 |
kmlussier |
Was dbwells part of that discussion on 2.6 when we had it earlier? Just want to make sure he is okay with/aware of it since he's the release maintainer. |
| 11:44 |
|
bbqben joined #evergreen |
| 11:49 |
Bmagic |
mmorgan jeff Dyrcona kmlussier This turned out to be this bug https://bugs.launchpad.net/evergreen/+bug/1424646 |
| 11:49 |
pinesol_green |
Launchpad bug 1424646 in Evergreen "Paid-For Long Overdue Items Still Appear in "Other/Special Circulations" Window" (affected: 4, heat: 20) [Undecided,New] |
| 11:49 |
jeff |
Bmagic: ah! |
| 11:50 |
Bmagic |
yep! |
| 11:50 |
jeff |
Bmagic: and yes, now that you link that i should have remembered that bug. |
| 11:51 |
Bmagic |
Here is a related question. We are finding that Lost triggers do not run on circulations that have already been turned to long overdue. Is that correct? |
| 11:51 |
* mmorgan |
nudges the heat on that bug. |
| 11:54 |
berick |
Bmagic: http://evergreen-ils.org/documentation/release/RELEASE_NOTES_2_5.html -- section 1.2.1 might be what you need |
| 11:54 |
Bmagic |
berick: hmmm, I messed with this file awhile back |
| 11:54 |
berick |
basically.. http://git.evergreen-ils.org/?p=Evergreen.git;a=blobdiff;f=Open-ILS/examples/action_trigger_filters.json.example;h=31d713d79bccb275866866ed26d03737323d2e21;hp=d599d7bd42a7a0026eb2ff8ce642f2cb5495d3d5;hb=18f672d40658964f85657713c743acafe22f3633;hpb=feb1c3f2044add1cf6a262824f7e2082a372253c |
| 11:54 |
pinesol_green |
[evergreen|Bill Erickson] LP 1169193 long-overdue automated processing - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=18f672d> |
| 11:54 |
pinesol_green |
[evergreen|Bill Erickson] LP 1169193 long-overdue SQL seed data - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=feb1c3f> |
| 11:56 |
berick |
i'm shooting from the hip, but I think that's probably the issue |
| 11:56 |
Bmagic |
berick: My config has this code merged |
| 11:56 |
Bmagic |
my line looks like this [ { "stop_fines" : ["MAXFINES"] }, |
| 11:57 |
berick |
hmm, actually |
| 11:57 |
berick |
for this, you would want the list to include LONGOVERDUE |
| 11:57 |
Bmagic |
oh, i see |
| 11:57 |
berick |
you might need to use a separate filters file for auto lost processing |
| 11:58 |
berick |
which you can specify via a_t_runner.pl command line option |
| 11:58 |
berick |
--custom-filters=/path/to/custom.json |
| 11:59 |
Bmagic |
oh, pass the perl file an overrided action_trigger_filters.json file ? |
| 11:59 |
berick |
yeah |
| 11:59 |
Bmagic |
I am ok with changing the default file though |
| 11:59 |
berick |
well, but you may not want to |
| 11:59 |
Bmagic |
explain |
| 12:00 |
berick |
if you add LONGOVERDUE back, then longoverdue items might get marked as longoverdue again. or, more likely, you'll re-process (and evetually ignore) a bunch of circs you don't need to |
| 12:00 |
Bmagic |
oh jees |
| 12:01 |
berick |
the validators should prevent anything from getting the full treatment twice. |
| 12:01 |
berick |
but they'd have to be loaded and tested |
| 12:01 |
berick |
over and over again |
| 12:01 |
Bmagic |
so, I need to setup an AT with a grainularity, and pass that cron the special config |
| 12:01 |
berick |
yes |
| 12:02 |
Bmagic |
sounds doable |
| 12:02 |
berick |
the mark-lost event def probably already has a granularity |
| 12:02 |
berick |
oh, you mean the cron job |
| 12:02 |
Bmagic |
both, the cron and the AT need to match grainularity |
| 12:02 |
Bmagic |
so that only the Lost trigger will include LONGOVERDUE |
| 12:02 |
berick |
yes, it needs its own cron job w/ the mark lost granularity, and --granularity-only applied, and --custom-filters applied |
| 12:02 |
berick |
right |
| 12:03 |
Bmagic |
berick++ |
| 12:39 |
|
jihpringle joined #evergreen |
| 12:57 |
|
ericar_ joined #evergreen |
| 13:50 |
|
ericar_ joined #evergreen |
| 14:07 |
kmlussier |
Ooh! I missed bug 1429317 when it was first posted. |
| 14:07 |
pinesol_green |
Launchpad bug 1429317 in Evergreen "Serials in holdings view should be able to sort in ascending and descending order as well as by call number" (affected: 2, heat: 14) [Wishlist,New] https://launchpad.net/bugs/1429317 |
| 14:12 |
|
krvmga joined #evergreen |
| 14:22 |
Dyrcona |
Bug 1442752 seems to ring a bell, but when I searched for something related, I naturally couldn't find anything. |
| 14:22 |
pinesol_green |
Launchpad bug 1442752 in Evergreen "oils_xpath invalid xpath expression in acquisitions record upload" (affected: 1, heat: 6) [Undecided,New] https://launchpad.net/bugs/1442752 |
| 14:28 |
|
tsbere joined #evergreen |
| 14:33 |
kmlussier |
Dyrcona: That's interesting. I have the order records in question. Your report is showing a different value in one of the subfield u's than is in the actual record. |
| 14:33 |
kmlussier |
I think I've seen that happen before. |
| 14:34 |
Dyrcona |
IDK. I copied directly from the postgres log on the server. |
| 14:34 |
kmlussier |
Dyrcona: Never mind. I'm looking at the wrong thing. |
| 14:43 |
kmlussier |
@dessert Dyrcona |
| 14:43 |
* pinesol_green |
grabs some Banana Puddin' for Dyrcona |
| 14:43 |
kmlussier |
Pudding is such a disappointing dessert when it comes down to it. |
| 14:43 |
Dyrcona |
It's not coconut cream pie, but it'll do. |
| 14:43 |
Dyrcona |
;) |
| 14:43 |
kmlussier |
@dessert [someone] |
| 14:43 |
* pinesol_green |
grabs some Mint Chocolate Chip Ice Cream for ningalls |
| 14:52 |
|
tsbere joined #evergreen |
| 15:07 |
|
dreuther joined #evergreen |
| 16:52 |
gmcharlt |
@coffee |
| 16:52 |
* pinesol_green |
brews and pours a cup of Belle Espresso, and sends it sliding down the bar to gmcharlt |
| 16:52 |
kmlussier |
It's a little late in the day for that, isn't it gmcharlt? |
| 16:52 |
mmorgan |
Especially Espresso! |
| 16:52 |
kmlussier |
@bartendar |
| 16:52 |
pinesol_green |
kmlussier: As great as you are man, you'll never be greater than yourself. |
| 16:52 |
* gmcharlt |
is a little bee, buzzing around today |
| 16:52 |
gmcharlt |
emphasis on the buzzing |
| 16:53 |
* kmlussier |
does know to spell FWIW |
| 16:53 |
kmlussier |
@bartender |
| 16:53 |
* pinesol_green |
fills a pint glass with Icehouse, and sends it sliding down the bar to kmlussier (http://beeradvocate.com/beer/profile/105/1299/) |
| 16:53 |
kmlussier |
And I know how to type too. Just not in IRC |
| 16:55 |
berick |
ouch, Icehouse |
| 16:56 |
berick |
@bartender |
| 16:56 |
* pinesol_green |
fills a pint glass with Full Sail Rip Curl, and sends it sliding down the bar to berick (http://beeradvocate.com/beer/profile/5316/2893/) |
| 16:56 |
kmlussier |
Bmagic++ #Long Overdue fixes |
| 16:56 |
kmlussier |
berick: Is Icehouse a bad thing? |
| 16:56 |
kmlussier |
Oh, it gets terrible ratings on beeradvocate |
| 16:58 |
berick |
:) |
| 17:12 |
|
mmorgan left #evergreen |
| 17:30 |
kmlussier |
@sortinghat |
| 17:30 |
pinesol_green |
Hmm... kmlussier... Let me see now... SLYTHERIN! |
| 17:31 |
kmlussier |
bwahahaha |
| 17:43 |
|
gsams joined #evergreen |
| 17:49 |
|
Newziky left #evergreen |
| 17:57 |
* kmlussier |
decides to remove the webstafclient tag from bugs that aren't specifically related to the web client. |
| 19:41 |
|
akilsdonk joined #evergreen |
