| Time |
Nick |
Message |
| 05:17 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
| 05:56 |
|
akilsdonk joined #evergreen |
| 07:07 |
|
DPearl joined #evergreen |
| 07:12 |
|
artunit joined #evergreen |
| 07:22 |
|
artunit_ joined #evergreen |
| 07:40 |
|
chatley joined #evergreen |
| 07:41 |
|
mmorgan1 joined #evergreen |
| 07:51 |
|
DPearl joined #evergreen |
| 08:00 |
|
jboyer-isl joined #evergreen |
| 08:04 |
|
mtate joined #evergreen |
| 08:04 |
|
eeevil joined #evergreen |
| 08:05 |
|
Callender joined #evergreen |
| 08:05 |
|
phasefx joined #evergreen |
| 08:06 |
|
graced joined #evergreen |
| 08:08 |
|
collum joined #evergreen |
| 08:26 |
|
ericar joined #evergreen |
| 08:28 |
|
kmlussier joined #evergreen |
| 08:31 |
|
mrpeters joined #evergreen |
| 08:35 |
|
mmorgan1 left #evergreen |
| 08:36 |
kmlussier |
bshum: dbs mentioned this last week, but it probably was missed in the midst of the hack-a-way. The google site search doesn't appear to be working at evergreen-ils.org anymore. Is that something you can fix? |
| 08:41 |
|
mmorgan1 joined #evergreen |
| 08:41 |
|
mmorgan1 left #evergreen |
| 08:52 |
|
jwoodard joined #evergreen |
| 08:53 |
|
mmorgan joined #evergreen |
| 09:34 |
bshum |
kmlussier: I see what happened. Someone updated the stock template without modifying it with the necessary changes for the footer and spot for search. |
| 09:35 |
bshum |
I'll try to fix it when I get a moment. |
| 09:35 |
kmlussier |
bshum: OK, thanks! :) |
| 09:35 |
kmlussier |
@dessert bshum |
| 09:35 |
* pinesol_green |
grabs some Red Velvet Cake for bshum |
| 09:35 |
kmlussier |
It's never too early for dessert. |
| 09:43 |
bshum |
Since the theme is broken anyways, I opted to update Wordpress to 4.0 (since that was pending) and also updated plugins and the theme again. |
| 09:43 |
kmlussier |
bshum++ |
| 09:43 |
bshum |
Now to actually fix the parts of the theme... |
| 09:48 |
|
yboston joined #evergreen |
| 10:09 |
bshum |
gmcharlt: I added a "customizr-child" theme and copied the key elements over there as far as I know. Hopefully this will cause slightly less disruption from now on as folks perform updates on the wordpress site. Though we'll have to track the changes made in the main theme vs. our custom child theme alterations. |
| 10:13 |
|
wlayton joined #evergreen |
| 10:18 |
kmlussier |
I feel like I'm missing something obvious. In patron search, there is a checkbox to "include inactive patrons." What exactly is an inactive patron? At first, I thought it was patrons whose accounts have expired, but they're retrieved regardless of whether that checkbox is selected. |
| 10:18 |
bshum |
gmcharlt: Also updated piwik to latest version for webstats.evergreen-ils.org |
| 10:19 |
bshum |
kmlussier: An "inactive" patron is defined as a patron who has their entry for active set to false in their patron record. |
| 10:19 |
bshum |
aka, no checkbox in the "active" area of their record. |
| 10:19 |
collum |
903502 |
| 10:19 |
kmlussier |
I was looking for someting like that, but didn't see it. I'm sure it was just staring me in the face. |
| 10:19 |
* kmlussier |
checks again |
| 10:19 |
collum |
995 |
| 10:19 |
bshum |
It doesn't have anything to do with expiration as far as I know. Expired patrons always show up in searches since they're still considered "active" till the patron record says otherwise. |
| 10:19 |
collum |
oops |
| 10:20 |
kmlussier |
Oh, I think I know what my problem is. |
| 10:21 |
kmlussier |
It helps if you show all fields in patron registration. Oops. |
| 10:21 |
* collum |
note to myself - don't click on irc when you have a script running |
| 10:26 |
|
jeff_ joined #evergreen |
| 10:30 |
bshum |
gmcharlt: Hmm, looks like piwik tracking on the main Evergreen-ILS website stopped around 8/20 or so |
| 10:30 |
bshum |
I guess that's when the site theme was updated and we lost the Google custom search, footer, and piwik tracker. |
| 10:31 |
* bshum |
disappears to his meetings |
| 10:32 |
* bshum |
will finish fully repairing the footer area later. |
| 10:32 |
|
sandbergja joined #evergreen |
| 10:37 |
|
julialima joined #evergreen |
| 10:40 |
|
julialima left #evergreen |
| 10:41 |
|
tito_ joined #evergreen |
| 10:43 |
|
julialima joined #evergreen |
| 10:43 |
|
titox joined #evergreen |
| 11:34 |
|
gargi joined #evergreen |
| 11:37 |
|
StephenGWills joined #evergreen |
| 11:52 |
|
gargi joined #evergreen |
| 11:54 |
|
StephenGWills left #evergreen |
| 12:08 |
|
cherri joined #evergreen |
| 12:24 |
|
buzzy joined #evergreen |
| 12:29 |
|
deepak joined #evergreen |
| 12:30 |
|
deepak left #evergreen |
| 12:30 |
|
deepak joined #evergreen |
| 12:36 |
|
tspindler joined #evergreen |
| 12:46 |
|
nhilton joined #evergreen |
| 13:00 |
kmlussier |
I've been doing all of my webby testing without registering a workstation. If I wanted to register a workstation, how would I do so? |
| 13:02 |
berick |
kmlussier: administration -> workstation |
| 13:02 |
berick |
3rd form down the page |
| 13:03 |
kmlussier |
berick: Ah, ok. I was looking for something right on the login screen since that's where we've always registered workstations in the past. |
| 13:05 |
jboyer-isl |
berick: was there any consideration given to making the username the “menu” for the change user and logout options? |
| 13:05 |
berick |
yeah, it's a little different since they're not required. a login-page reg. option could certainly be added, though. |
| 13:06 |
berick |
jboyer-isl: hadn't really thought about, but it makes perfect sense. |
| 13:06 |
|
nhilton_ joined #evergreen |
| 13:06 |
kmlussier |
berick: Yeah, I'm thinking that might be useful. Is it also possible for an Evergreen site to require workstation registration if they want all staff to be working from registered workstations? |
| 13:06 |
jboyer-isl |
I did try to click the username once or twice before I thought “oh hey, a menu.” |
| 13:07 |
kmlussier |
Sorry if you've answered these questions before in e-mails I may have not read carefully. |
| 13:07 |
|
jihpringle joined #evergreen |
| 13:07 |
jboyer-isl |
But it’s a toss up if there are other things planned for that menu |
| 13:08 |
* kmlussier |
likes jboyer-isl's idea. |
| 13:08 |
berick |
jboyer-isl: good point, if the menu expands beyond account-related stuff, it could get confusing. |
| 13:08 |
berick |
something to keep in mind |
| 13:09 |
berick |
kmlussier: in theory, yes, we could require a workstation via org/global setting |
| 13:09 |
berick |
but the pieces to enforce that are not in place |
| 13:09 |
kmlussier |
berick: OK, thanks! |
| 13:10 |
kmlussier |
I hadn't even noticed the logout/change operator menu until jboyer-isl made his suggestion. But my "Change Operator" is greyed out? |
| 13:10 |
berick |
kmlussier: you get 1 guess |
| 13:10 |
jboyer-isl |
kmlussier: may not be written yet |
| 13:10 |
berick |
jboyer-isl wins |
| 13:10 |
kmlussier |
LOL - what's his prize? |
| 13:11 |
kmlussier |
@praise jboyer-isl |
| 13:11 |
* pinesol_green |
Shall I compare jboyer-isl to a summer's day? jboyer-isl is more lovely and more temperate. |
| 13:11 |
jboyer-isl |
Volunteered to implement it! it’s the un-prize! |
| 13:11 |
|
Canepa joined #evergreen |
| 13:12 |
jboyer-isl |
:D |
| 13:12 |
berick |
pinesol_green++ |
| 13:12 |
kmlussier |
@karma pinesol_green |
| 13:12 |
pinesol_green |
kmlussier: Karma for "pinesol_green" has been increased 14 times and decreased 6 times for a total karma of 8. |
| 13:13 |
kmlussier |
What? Who would dare give negative karma points to pinesol_green? |
| 13:15 |
kmlussier |
I'm full of questions today. If you don't register a workstation, how does webby know what library you're in? |
| 13:15 |
berick |
kmlussier: it defaults to the user's home library |
| 13:15 |
sandbergja |
What permissions are needed to view/replace a user's barcodes in 2.5.2? I added UPDATE_PATRON_PRIMARY_CARD and UPDATE_PATRON_ACTIVE_CARD, but I am missing something. Thanks for your help! |
| 13:15 |
berick |
(which is why logging in w/ admin can get weird at times) |
| 13:21 |
jboyer-isl |
So embarrass, many disappoint. I assumed bug 1375907 had been reported before. We knew how to cause it but not how to fix it. |
| 13:21 |
pinesol_green |
Launchpad bug 1375907 in Evergreen "Offline receipt printing fails with alert" (affected: 1, heat: 6) [Undecided,New] https://launchpad.net/bugs/1375907 |
| 13:23 |
jboyer-isl |
I should follow up better on these things. |
| 13:34 |
|
Canepa joined #evergreen |
| 13:35 |
|
Dyrcona joined #evergreen |
| 13:45 |
Dyrcona |
Any laters for me? |
| 13:46 |
Dyrcona |
Nope. That's good. |
| 13:46 |
|
julialima joined #evergreen |
| 13:56 |
|
sarabee joined #evergreen |
| 14:00 |
* Dyrcona |
is using the third string laptop. |
| 14:00 |
jeff |
ouch |
| 14:00 |
jeff |
sounds... slow and painful. |
| 14:02 |
Dyrcona |
not so bad, but it can get uncomfortably warm in one spot, so I use a heat shift pad when it is on my lap. |
| 14:02 |
Dyrcona |
I used to use this as my principal laptop. |
| 14:02 |
jcamins |
jeff: the very day he purchased it, he christened his laptop, as his slow and painful computer third string door stop. |
| 14:03 |
Dyrcona |
jcamins: Not too far off. It was third string when it was bought, and spent a year or so sitting on a shelf. |
| 14:03 |
jcamins |
Okay, it was a bit of a stretch, but "guitar" and "orchestra" don't really rhyme or scan correctly either. |
| 14:03 |
Dyrcona |
It looked lonely, so I took it down, dusted it off, and used it. |
| 14:04 |
Dyrcona |
Now, my principal laptop is in rehab, so third string gets to play lead again. :) |
| 14:05 |
Dyrcona |
Anyway, back to collection reports.... |
| 14:05 |
jcamins |
And so you dream a mouse will join you, to reduce the carpal tunnel / and maybe now some... |
| 14:05 |
jcamins |
I've got nothing. |
| 14:05 |
Dyrcona |
;) |
| 14:12 |
jcamins |
Ooh, wait. "You sent your principle laptop in to be repaired / and found if you want it back no expenses can be spared. / And so for now you're stuck with your old laptop / it's you and your slow and painful computer third string door stop." |
| 14:32 |
|
Canepa joined #evergreen |
| 14:37 |
|
cherri joined #evergreen |
| 14:40 |
|
snigdha26 joined #evergreen |
| 14:40 |
Bmagic |
I'm beating my head against action_trigger's - I can manually create a row in action_trigger.event and it will fire the event email like I want it to. Getting the row into that table is not happening with the regular action_trigger_runner.pl --osrf-config /openils/conf/opensrf_core.xml --process-hooks --run-pending command. What am I missing? |
| 14:43 |
Bmagic |
hook="hold.available" validator="NOOP_True" reacton="SendEmail" delay="00:10:00" delay context="shelf_time" group="usr" *should create a row 10 minutes after a hold is captured? |
| 14:51 |
jboyer-isl |
Bmagic: The way I understand it the events are created at the time of the trigger. Any delay is added to the run_time field. |
| 14:51 |
mmorgan |
Bmagic: Our trigger has validator HoldIsAvailable rather than NOOP_True. Not sure if that is a problem. Do you have a granularity? |
| 14:52 |
Bmagic |
mmorgan: Ours started out as HoldIsAvailable but that wasn't working, so I tried what looked like to me to return "true" always |
| 14:53 |
Bmagic |
jboyer-isl: that would make sense. So, the row is inserted into the table when the Item is scanned, not during a cron? |
| 14:56 |
|
ericar joined #evergreen |
| 14:57 |
jboyer-isl |
Bmagic: yes, we’ve got 5760 events with a run_time in the future. mmorgan’s suggestion may help though, we’ve got HoldIsAvailable in for the Validator also. |
| 14:57 |
jboyer-isl |
And just to be certain, is enabled set to true? |
| 14:57 |
Bmagic |
jboyer-isl: that was it! I needed to understand that those rows are created during item checkin and not from the cron |
| 15:10 |
Bmagic |
On the other side of the coin passive=true for "shelf_expire_time" on "hold_request.shelf_expires_soon" will have rows created in action_trigger.event via cron |
| 15:13 |
bshum |
Hmm, does anyone think it might be good to add some sort of filter in TPAC to hide older payments made by patrons in their accounts? |
| 15:13 |
bshum |
I'm thinking maybe default to within a year, and then maybe a new YAOUS to specify different time limits. |
| 15:13 |
bshum |
Right now, it seems to show all payments made ever. |
| 15:14 |
jeff |
i kinda' thought that might have existed already, but i could be way off. |
| 15:21 |
berick |
bshum: jeff: opac.payment_history_age_limit |
| 15:33 |
|
snigdha26 joined #evergreen |
| 15:41 |
bshum |
berick: Aha! |
| 15:42 |
bshum |
I'll check that on our system, thanks man |
| 15:42 |
bshum |
jeff++ berick++ |
| 16:18 |
Bmagic |
So, I finally figured it out. Our passive event that needed the action_trigger_runner.pl script to create the rows was not getting included in the script's scope because we did not have /openils/conf/action_trigger_filters.json setup! |
| 16:19 |
jeff |
Bmagic++ |
| 16:19 |
Bmagic |
Which brings me to ask this question: Why does the *old* 2.4.1 example of action_trigger_filters.json contain this line [ { "stop_fines" : ["MAXFINES", "LONGOVERDUE"] }, and the current 2.6.1 example only has [ { "stop_fines" : ["MAXFINES"] }, |
| 16:21 |
Bmagic |
Knowing that "LONGOVERDUE" was introduced in 2.5, it seems that it would be in 2.5 and newer, not less than 2.5.... |
| 16:21 |
jeff |
LONGOVERDUE has existed before 2.5, but gained more/different support in 2.5, iirc. |
| 16:21 |
jeff |
and that may be the reason. |
| 16:21 |
bshum |
Correct. |
| 16:21 |
bshum |
I think |
| 16:22 |
berick |
correct |
| 16:22 |
berick |
the standard overdue processor now ignores longoverdue items, since they are handled separately |
| 16:22 |
jeff |
commit 18f672d4 |
| 16:22 |
pinesol_green |
[evergreen|Bill Erickson] LP 1169193 long-overdue automated processing - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=18f672d> |
| 16:22 |
Bmagic |
jeff: Support in such a way that the action_trigger_filters.json example no longer needs that array element? |
| 16:22 |
berick |
(and now actually have meaning) |
| 16:23 |
Bmagic |
That commit says it all |
| 16:23 |
Bmagic |
jeff++ |
| 16:24 |
mmorgan |
So prior to long-overdue automated processing, how did transactions get a stop_fines of LONGVERDUE? |
| 16:24 |
jeff |
git-blame++ |
| 16:24 |
berick |
if you wanted to keep sending overdue notices for an item which has been processed as longoverdue, you could, but presumably most people don't want that. |
| 16:24 |
berick |
mmorgan: they didn't ;) |
| 16:24 |
jeff |
mmorgan: i believe the only way was "manually" |
| 16:25 |
jeff |
"I'm not LONGOVERDUE, i was just migrated that way." |
| 16:27 |
mmorgan |
ok, just seems odd that it would be in an action trigger filter if it's not a value the system would assign. |
| 16:29 |
berick |
it was sort of unofficially supported. |
| 16:29 |
berick |
reserved for future use |
| 16:32 |
mmorgan |
gotcha. |
| 16:32 |
|
tspindler left #evergreen |
| 16:57 |
|
frank___ joined #evergreen |
| 17:04 |
frank___ |
hi all, could someone tell me the command/trigger to could see the pull list for hold request list? |
| 17:05 |
kmlussier |
frank___: Circulation -> Pull List for Hold Requests |
| 17:06 |
frank___ |
but I want to know if I have to execute a trigger to could update this list |
| 17:07 |
kmlussier |
frank___: Once a hold is targeted, it appears on the list. So I guess you would need to make sure your holds targeter is running. |
| 17:07 |
kmlussier |
frank___: But, IIRC, targeting automatically happens at the time the user places the hold. |
| 17:16 |
|
mmorgan left #evergreen |
| 17:28 |
|
vlewis joined #evergreen |
| 17:36 |
kmlussier |
Good night Evergreeners! |
| 17:49 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
| 19:25 |
|
stephsamson joined #evergreen |
| 19:44 |
|
wlayton joined #evergreen |
| 20:06 |
|
buzzy joined #evergreen |
| 21:34 |
|
gmcharlt joined #evergreen |
| 22:33 |
|
cherri_ joined #evergreen |
| 23:16 |
|
gmcharlt joined #evergreen |
