Evergreen ILS Website

IRC log for #evergreen, 2015-10-29

| Channels | #evergreen index | Today | | Search | Google Search | Plain-Text | summary | Join Webchat

All times shown according to the server's local time.

Time Nick Message
00:09 jlitrell joined #evergreen
02:24 jihpringle joined #evergreen
05:21 miker joined #evergreen
07:30 ericar joined #evergreen
07:50 kmlussier gmcharlt: is better-webstaff-hotkeys loaded on webby?
07:59 mrpeters joined #evergreen
08:01 kmlussier I've never been able to figure out how to add questions to a survey. I must be missing something very basic.
08:11 _bott_ left #evergreen
08:14 phasefx kmlussier: make sure the survey date is set for the future?
08:14 kmlussier phasefx: Really? OK, I'll try that.
08:14 phasefx surveys become read-only if they're in effect
08:15 phasefx in the admin interface, that is
08:18 kmlussier phasefx: Yup! That was it.
08:18 phasefx I've tripped over that before
08:18 kmlussier It makes sense in reality. But when you're doing a survey for testing, you want it to appear right away. :)
08:18 phasefx :)
08:30 mdriscoll joined #evergreen
08:35 kmlussier And if you set the option to display in user summary, where should it be displaying?
08:38 rjackson_isl joined #evergreen
08:38 kmlussier Never mind. I see it now. I had to restart the client.
08:47 mmorgan joined #evergreen
08:47 * kmlussier notes what a pleasant experience it is to use berick's angular patron editor in the web client.
08:49 kmlussier Actually, the same can be said for many of the web client interfaces. :)
09:02 collum joined #evergreen
09:02 jwoodard joined #evergreen
09:03 gmcharlt kmlussier: it is, though I'm working on a follow-up to make it function in more places
09:04 kmlussier gmcharlt: OK, thanks! I'll try to take a look at it later today. Or, maybe next week. Today is filling up already. :(
09:04 gmcharlt the attack of the Creeping Meeting Monster?
09:05 sarabee joined #evergreen
09:05 kmlussier Alas, no, I don't even have meetings to blame. Just a long to-do list.
09:23 maryj joined #evergreen
09:54 yboston joined #evergreen
09:55 _bott_ joined #evergreen
09:58 Stompro Good morning, I'm trying to write a report and I was going to use the substring transform to limit the length of title and author data, but I cannot figure out how to enter the substring parameters.  Can someone clue me in.
10:16 mmorgan Stompro: Sorry, I'm no help.  I have never used that transform in reports. And I can't see where to enter the parameters either.
10:33 tsbere Stompro: I think I can see how it is supposed to work in the backend, but can't find how to make it actually function from the frontend
10:34 * tsbere has given up on several aspects of the current template builder entirely due to being unable to figure out what was going wrong with them
10:35 Stompro I couldn't find a bug report, probably something that just was never implemented.  I can file a bug report, just so it is documented.  I can live without it.
10:36 * jeff tries to remember if we ever used that before abandoning the reporter ourselves
10:36 jeff I can't recall if we used it, if it was there but we didn't have need for it, or if it wasn't present at the time.
10:37 jeff I suppose git history can answer one of those questions, and our old templates could answer the other.
10:38 jeff answer the first: we never used it (or any templates that did use it were long ago deleted).
10:40 jeff heh. the last comit to Open-ILS/web/reports/xul/transforms.js was from miker in 2009, and the one before that was a patch from me.
10:44 kmlussier Stompro: You also might want to try sending the question to the reports list. Many of the expert reports people I know don't spend time in IRC.
11:04 sandbergja joined #evergreen
11:06 Christineb joined #evergreen
11:10 csharp Stompro: the substring transform has never worked for me - I usually use the "Contains matching substring" filter when that sort of thing is needed
11:10 csharp csharp-- # not filing a bug report
11:10 pinesol_green csharp: Error: You're not allowed to adjust your own karma.
11:10 csharp pinesol_green--
11:10 csharp tranferrence++
11:10 jeff csharp: Unfortunately that doesn't help Stompro's use case of wanting to trim output to a certain max length... :-)
11:10 csharp transferrence, even
11:11 csharp jeff: yeah, you're right :-/
11:11 bshum That's interesting...
11:11 bshum Must be a setting on the karma
11:11 jeff But since adding that transform to an output or base filter column breaks the template, I think it's just broken. :-)
11:11 csharp jeff: yep
11:14 berick good times, libperl segfaults when inserting a bib record into my new 2.7 dev DB.  this is going to be fun...
11:14 * berick turns his hat around backwards, gets serious
11:16 jboyer-isl berick: Is the marc particularly busted or is it really srs bzness?
11:17 RoganH joined #evergreen
11:17 berick jboyer-isl: simplest possible record. acq brief record w/ 1 field :)
11:20 csharp Stompro: some historical discussion about your issue: http://irc.evergreen-ils.org/​evergreen/2013-08-28#i_25534
11:21 Stompro Thanks csharp.
11:21 csharp Stompro: also the bug referenced: https://bugs.launchpad.net/evergreen/+bug/1100262
11:21 pinesol_green Launchpad bug 1100262 in Evergreen 2.4 "Report editor uses translated string internally and crashes" [Medium,Confirmed]
11:22 csharp so looks like I was too hard on myself earlier ;-)
11:23 jboyer-isl berick: Ouch.
11:24 berick i have a feeling i'll be learning a lot about ingest today
11:28 jboyer-isl In the interest of accelerated learning, does it also crash on more full-figured marc records? Maybe there are some unfortunate assumptions made in the ingest code, knowing that it works with this record and not that one may help suss that out.
11:29 csharp @blame in[di]gest[ion]
11:29 pinesol_green csharp: in You keep using that word. I do not think it means what you think it means. gest What we have here is a failure to communicate. must eat cottage cheese!
11:30 csharp @blame braces
11:30 pinesol_green csharp: braces musta been an Apple employee.
11:30 jboyer-isl csharp: Something fascinating happened.
11:32 berick jboyer-isl: we have local modifications to some of these ingest functions.  i'm willing to bet this is not an issue w/ the community code.
11:34 jboyer-isl I see.
11:34 kmlussier Wow. pinesol_green's blame was quite special.
11:40 dbwells indeed
11:41 dbwells Took me five tries, but I finally parsed it :)
11:42 kmlussier Yeah, it took me a while too. :)
12:34 berick jboyer-isl: mismatched config.metabib_field xpath and format caused oils_xpath to croak.  oddly, when run by hand, it just prints a namespace error.  ¯\_(ツ)_/¯ -- fixing the data fixed the problem.
12:35 jboyer-isl berick: good to hear that it should be simple, but that is a weird reason to segfault.
12:36 jboyer-isl (and now, to away for real)
12:36 berick indeed
12:54 mmorgan kmlussier++ # Hackaway wrangling
12:57 RoganH gmcharlt++ #SSLing the website
12:59 RoganH kmlussier++ #all the hackaway stuff :)
13:35 jlitrell joined #evergreen
13:41 jihpringle joined #evergreen
13:46 kmlussier yboston has the best excuses for running late to a meeting.
13:47 csharp @excuse
13:47 pinesol_green csharp: I see nothing, I know nothing!
13:49 jlitrell I knew a guy whose power went out, so he led a call entirely on his cellphone, from his front lawn.  Knew where code was within about 5 lines, for hundreds of files.  Pretty amazing mind.
13:49 jlitrell But he indented with three spaces, so there's that.
13:49 kdemey joined #evergreen
13:49 jeff jlitrell++
13:50 jeff though i should not have taken a large sip of coffee between reading those two lines.
13:51 jlundgren joined #evergreen
13:51 jlitrell That's why I still use a Model M.  Drain holes.  :-D
13:54 kmlussier See? So what you're saying, jlitrell, is that yboston could really run a meeting even if there was a fire in his building. He just needs to show a little more commitment. ;)
13:54 bshum I think he could do it better if he wasn't using Apple devices.
13:55 kmlussier bshum: Yes, the fire isn't the problem. It's the Apple devices.
13:55 jlitrell Somebody was holding something wrong...
13:55 * kmlussier wonders if there's a backup to run the meeting.
14:03 kmlussier I'm guessing that's a 'no.'
14:04 kmlussier #startmeeting 2015-10-29 Evergreen for academics meeting
14:04 pinesol_green Meeting started Thu Oct 29 14:04:42 2015 US/Eastern.  The chair is kmlussier. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:04 pinesol_green Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:04 pinesol_green The meeting name has been set to '2015_10_29_evergreen_for_academics_meeting'
14:05 kmlussier It's been a while since I've been involved in a meeting, so it may take me a few minutes to get up to speed. Please bear with me.
14:05 kmlussier #topic Introductions
14:05 kmlussier Please introduce yourselves with the #info command.
14:05 kmlussier #info kmlussier is Kathy Lussier, MassLNC
14:05 mdriscoll #info mdriscoll is Martha Driscoll, NOBLE
14:05 jihpringle #info jihpringle is Jennifer Pringle, BC Libraries Cooperative (Sitka)
14:06 jlundgren #info jlundgren is Jeanette Lundgren, CWMARS
14:06 jlitrell #info jlitrell is Jake Litrell, MassLNC
14:06 kdemey #info kdemey is kathy demey from Calvin College
14:07 kmlussier Since the action items were all in yboston's hands, I want to skip to updates from subgroup leaders. Do we have a list of subgroup leaders somewhere?
14:08 kmlussier #info Agenda is available at http://wiki.evergreen-ils.org/doku.php​?id=evergreen_for_academics:2015-10-29
14:11 kmlussier OK, I'll wait for yboston on that one. I think I can, at least, handle the agenda items on meeting times.
14:11 kmlussier #topic Best use of Academic Interest Group meeting time
14:12 kmlussier It looks like the group has already moved from monthly to quarterly, but one of the ideas yboston posted on the agenda was to perhaps pick a specific topic to discuss at each meeting.
14:13 kdemey i like that idea
14:13 yboston buenas tardes
14:13 mdriscoll I think that would be useful
14:13 kmlussier yboston: Yay! I've been floundering in your absence. We're talking about your idea to pick a topic to discuss at each meeting.
14:13 yboston let me get y bearings, keep going a bit longer without me
14:14 yboston OK, I am ready
14:14 kmlussier yboston: Do you remember how I can hand meeting controls over to you?
14:14 yboston I read what I missed
14:15 yboston lets stay on the topic of picking a meeting topic in the future
14:15 kmlussier I also give a general +1 to specific topics. I haven't been involved in the meetings in a while, but I think it would help give us some focus.
14:15 yboston kmlussier: I don't know how to pass control
14:15 jlitrell2 joined #evergreen
14:16 yboston do thers have interest in having meeting topics?
14:17 kmlussier The folks from MassLNC have recently been having some local discussions regarding academic reserves. I would be up for a meeting on that topic at some point in the future.
14:17 kmlussier #chair yboston
14:17 pinesol_green Current chairs: kmlussier yboston
14:17 yboston also for a future meeting, I would ask poeple on the general mailing list to weigh in on picking a topic, so we geet more feedback
14:17 yboston kmlussier: thanks
14:18 kmlussier yboston: So maybe an email could go out after today's meeting to see what topics people are interested in?
14:19 yboston kmlussier: I like that idea, but we may also want to ask about how often to meet on the list
14:20 kdemey kmlussier: good idea. give us time to think and get feedback from our colleagues
14:20 yboston not sure it if should be two seprate emails to ask feednack for topics AND to ask for feedback on how oftten to meet/when shoudl our next meeting be?
14:20 kmlussier I'm inclined to go with one email.
14:20 yboston thanks
14:21 jihpringle I vote for one email too
14:21 yboston thanks
14:21 kdemey how do we make sure our email is known?
14:21 yboston here a draft action item:  send out an email to the general list to solicit topics to focus on for next group meeting; and also ask how often to meet (monthly/querterly/ect)
14:22 kmlussier kdemey: The email should probably go out on the open-ils-general list.
14:22 yboston kdemey: are you signed up to the EG general mailing list? if so, you would get a copy of the email
14:23 kdemey yboston: i don't believe i'm signed up. i can ask for particulars from the evergreen team here
14:25 yboston kdemey: as an alternative you can send me your email, others too, and I will try to remember to BCC you academics related emails to you too
14:25 jeff #link https://evergreen-ils.org/​communicate/mailing-lists/ More info on the various Evergreen mailing lists can be found here.
14:26 kmlussier kdemey: But I would still recommend signing up for the general list because it might send other useful emails your way. :)
14:26 yboston I do strongly recommend that folks sing up at list for the general list digest; and just keep a look out for subjects that deal with acadmics stuff
14:26 yboston or other topics that may interest you
14:26 yboston in theory those that do not want to sign up could list their emails on the academics wiki page, which any can edit
14:27 kdemey yboston: i'm sure dan wells and remington steed here at calvin can help me with that. i'm brand new to evergreen for academics!
14:27 yboston this reminds me of the concern of the dozens of folks that are interested in EG acedmics issues, but are not on the general list
14:28 yboston kdemey: we are big fans of both of them
14:28 kmlussier kdemey: Welcome!
14:28 kdemey yes, remy and dan are great guys!!
14:29 kmlussier yboston: Do you need somebody to take that action item?
14:29 yboston no, I'll send out the letter
14:30 yboston #action yboston will send out an email to the general list to solicit topics to focus on for next group meeting; and also ask how often to meet (monthly/querterly/ect)
14:30 yboston what I could use now is 1) feedback on what topisc to suggest in that email (I could just use the ones listed on our wiki page http://wiki.evergreen-ils.org/dok​u.php?id=evergreen_for_academics)
14:31 yboston 2) suggetsions for how long to wait for the next meeting
14:31 kmlussier 1) reserves & authorities are the first that come to mind for me.
14:31 mdriscoll Topic suggestions: inventory functionality, improving in-house use functionality, course reserves, patron loading, exporting citations in the catalog
14:31 yboston for today's agenda I had these example topics:  EG reserves, authorities, batch patron loading
14:32 kmlussier 2) I like quarterly
14:32 yboston BTW, in theory we could try a primary topic for a meeting, and a back up topic if time permits
14:32 kmlussier Though, if we're doing specific topics, we may be able to do the meetings more frequently.
14:32 yboston kmlussier: excelent point
14:33 mdriscoll I like the idea of monthly meetings, expecially if sending out an agenda spurs interest
14:33 kmlussier yboston: It might also be good for an interested person to take charge of the planning for a particular meeting. So that it's not all on you.
14:33 yboston kmlussier: good idea
14:34 yboston I would be interested in goign back to monthly or every other month when we have topics lined up
14:34 kmlussier mdriscoll: Exporting citations. That's a good one!
14:34 mdriscoll Someone asked the other day
14:35 yboston what we can do is leave the meetings occuring monthly, but every month one of us can email the list to solicit a topic and a helper on top of me
14:36 kdemey i would vote for monthly, also
14:36 yboston or a variaiton on that
14:36 jihpringle I like the ideas of having an interested person do the planning and lead the topic and holding the meetings every other month
14:37 HoloIRCUser3 joined #evergreen
14:37 mdriscoll I volunteer to help plan a meeting to talk about patron loading
14:37 yboston mdriscoll: thanks
14:38 mdriscoll I'll also add some stuff on the wiki regarding citations, inventory, and in-house use improvements
14:38 yboston so for now monthly and every other month have supporters, at least more than quarterly
14:39 yboston though, I got some feedback that we should meet less int he summer, since a lot of people tend to eb un avialable
14:39 kdemey less often in the summer seems to make sense
14:39 jihpringle agreed
14:40 kmlussier I can volunteer to help plan a meeting on course reserves
14:40 yboston can I get a quick vote to see if we should try to meet in November or if we should wait for December?
14:41 yboston I personally am interested in November
14:41 mdriscoll I'm good with November too
14:43 kdemey November
14:45 kmlussier yboston: +1 to November
14:45 yboston thanks
14:46 yboston if we stuck to our usual schedule of the second week of the month, we would meet on Thursday, November 12 - 2 PM EST
14:46 yboston BTW, I am open to pickign a differnt day or time, though it should be at 2 PM EST or later for the sake of west coast folks
14:47 yboston should I go ahead and add the meeting for that date? then we can turn to the list for topic ideas?
14:47 kdemey nov. 12 works for me!
14:47 jlundgren Nov 12th 2pm works for me
14:48 kmlussier yboston: It doesn't work for me, but that's okay. I don't need to be here as long as the topic isn't reserves.
14:48 kdemey kmlussier: nov. 19 better for you?
14:49 yboston kmlussier: that is too bad, but I can't guarantee just yet what the topic will be yut, but I feel the meeting organizer reserves soem rights :)
14:50 mdriscoll Some of us will be talking about Syrup at the Hackaway so will have some momentum.  It might be good to tackle that topic soonish
14:50 yboston we can agree to make reserves the second meeting topic, and we can pick a differnt topic for November
14:50 yboston mdriscoll: that is a good point
14:50 yboston lets flip this around
14:50 kmlussier November 19 is better at the moment, but I have another meeting I'm scheduling right now via Doodle that might land on that date.
14:51 yboston lets shoot to tlak about reserves sometime in November, with a date to be determined. we can ask on the list
14:51 jihpringle Acq interest group is meeting November 12th
14:52 kmlussier jihpringle: Nice catch!
14:52 yboston we can send a separet email to the list to pick a topic and time for the Decmeber/January meetng
14:52 mdriscoll The community calendar says there is a Evergreen Oversite board meeting on the 19th
14:52 yboston all of those meeting shoudl end at 3 PM
14:52 kmlussier Sounds like a Doodle poll is in order.
14:52 yboston specially if they see there is a meeting right after theirs
14:52 yboston kmlussier: yes
14:53 yboston though, I would like to give defference to those here to decide the first topic, which sounds like it might be reserves from the comments of those that are here
14:54 yboston BTW, I don't see anything wrong with talking about reserves in November and again a couple of months later
14:54 yboston assuming we put it to a vote
14:54 mdriscoll I'm ok with leaving reserves for December if that's better for kmlussier.
14:55 kmlussier Yeah, I keep thinking about that. December might actually be better, not just because of my schedule, but we may have more solid ideas at that time.
14:55 kmlussier If others are interested in the topic, that is.
14:57 yboston I don't ahve a preference for when to cover resreves, but would liek to accomodate kmlussier
14:58 kmlussier yboston: I can plan on talking about it in December if you put the email out and find there is interest in it. That will give you the flexibility to schedule a November meeting that works well for everyone else.
14:59 kmlussier It looks like the 12th is out anyway due to the acq interest group meeting.
14:59 kmlussier jihpringle: Do you know what time that meeting is? I can put it on the community calendar.
15:00 kmlussier I saw the email go out, but I must have deleted it.
15:00 jihpringle 1pm EST
15:01 yboston in theory we could still meet at 2 PM, but they might want more than an hour, which is fine
15:01 jihpringle Christineb added it to the calendar yesterday
15:02 yboston which calendar?
15:03 jihpringle http://wiki.evergreen-ils.or​g/doku.php?id=calendar:start
15:03 yboston for some reason it was not showing up in my calendar, I see it now
15:03 kmlussier jihpringle: You're right. I was looking for it on the community calendar. I'll have to remember to follow  that calendar.
15:04 yboston it is 3 Pm, so we should probably start wrapping up
15:04 HoloIRCUser2 joined #evergreen
15:04 yboston to recap, as far as I can remember
15:04 yboston we want to try to meet in November
15:05 yboston I need to step away from my desk for a minute
15:07 yboston my apoliges, it was not a fire related issue
15:07 yboston like I was saying… we want to meeet in November and December (monthly), but we need to decide a date.time and a topic for each meeting
15:08 yboston I wil send out an email to the list
15:08 yboston any final comments or quesitons?
15:08 kdemey yboston: thank-you. signing off
15:09 yboston OK, thank you all for coming
15:10 yboston #endmeeting
15:10 pinesol_green Meeting ended Thu Oct 29 15:10:03 2015 US/Eastern.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
15:10 pinesol_green Minutes:        http://evergreen-ils.org/meetings/evergr​een/2015/evergreen.2015-10-29-14.04.html
15:10 pinesol_green Minutes (text): http://evergreen-ils.org/meetings/evergr​een/2015/evergreen.2015-10-29-14.04.txt
15:10 pinesol_green Log:            http://evergreen-ils.org/meetings/evergree​n/2015/evergreen.2015-10-29-14.04.log.html
15:10 kmlussier yboston++
15:11 kmlussier jihpringle: Do you have the URL for the Google calendar that's being used for the acq interest group? I usually track the eg calendars directly in Google rather than going to the page on the wiki.
15:13 jihpringle kmlussier: https://calendar.google.com/calendar/embed?​src=k75m6gidbikb0ne4kh8u3elg34%40group.cale​ndar.google.com&ctz=America/Vancouver
15:13 jihpringle let me know if that's not what you need
15:13 kmlussier jihpringle: Great! Thanks! It's exactly what I needed. :)
15:13 kmlussier jihpringle++
15:26 Stompro Sigh, a seperate hold notification preference per hold request is really a pain.  I wish it was just for the usr.
15:31 berick Stompro: you are not the first to feel this way
15:32 jeff Yep.
15:33 jeff We've (mostly) implemented it that way locally, but I'd love to have it built-in.
15:33 kmlussier I understand the 'feature' that allows people to have different hold contact information depending on the hold, but I've heard that comment so many times I start to wonder if we should just switch.
15:33 jeff Especially when I run into a corner case where the local hack breaks. :-)
15:35 kmlussier Or, if we keep it the way it is, have a nice prompt to update all holds when a user's phone number is updated.
15:47 kmlussier @dessert
15:47 * pinesol_green grabs some Boston Cream doughnuts for kmlussier
16:36 mmorgan We get lots of email replies to our sms hold notifications. Is there a way to change the action trigger template to prevent replies?
16:55 jeffdavis mmorgan: not sure about SMS specifically, but in our email notice templates, the From header is set to a noreply address (emails to that address are silently discarded). The actual sending address is specified by an org setting (org.bounced_emails), so we can direct bounce notifications to specific libraries to indicate that a patron has an invalid email or whatever.
16:57 jeffdavis not sure that made sense, perhaps I should go get that coffee
16:59 mmorgan jeffdavis: A lot of it did make sense :)
17:01 mmorgan We use the bounced emails setting to send the undeliverable emails and patron responses directly to the libraries.
17:02 mmorgan But for the sms, there's not enough information in the replies for anyone to act on. So we'd rather prevent replies.
17:05 mmorgan I'll look into the no reply email address. I wonder if that is enough to inform patrons know that their replies won't be seen.
17:05 mmorgan jeffdavis++
17:06 mdriscoll left #evergreen
17:09 mmorgan left #evergreen
19:59 geoffsams joined #evergreen
20:35 jihpringle joined #evergreen
23:09 eby joined #evergreen

| Channels | #evergreen index | Today | | Search | Google Search | Plain-Text | summary | Join Webchat