Evergreen ILS Website

IRC log for #evergreen, 2014-08-21

| 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:04 mnsri joined #evergreen
00:10 dcook joined #evergreen
00:37 mnsri joined #evergreen
02:23 wsmoak joined #evergreen
03:12 bshum joined #evergreen
06:56 wsmoak joined #evergreen
06:56 wsmoak joined #evergreen
07:08 csharp @later tell bshum I just installed OpenSRF master on 14.04 and it started fine for me (with OpenSRF config, not Evergreen config in place)
07:08 pinesol_green csharp: The operation succeeded.
07:33 collum joined #evergreen
07:43 bshum csharp: Did you do any of the changes that gmcharlt linked to in a paste a few nights ago?
07:43 bshum For the apache 2.4 websockets config
07:44 mrpeters joined #evergreen
07:44 csharp bshum: nope - let me apply those too
07:44 bshum And srfsh passes the math test?
07:45 csharp actually... no
07:45 bshum I didn't get any errors on start, but I got no response error from srfsh
07:46 bshum I bet if you look at osrfsys.log you'll see some sort of 500 error
07:46 bshum I had to crank up my loglevel to 4 to get more details.
07:46 bshum It looks like it starts right, but it's actually dead.
07:49 jboyer-isl joined #evergreen
07:49 * bshum will wander back again a little later.
07:51 csharp ah - yeah, now I see it
07:51 csharp yes, confirmed
07:55 csharp and confirmed before adding gmcharlt's stuff, btw
08:07 csharp hmm the only perl mod with the text "OpenSRF::Application::Settings" at all is that module itself
08:08 * csharp wishes perl was less opaque to him :-/
08:09 rjackson-isl joined #evergreen
08:20 akilsdonk joined #evergreen
08:21 ericar joined #evergreen
08:42 mmorgan joined #evergreen
08:52 kmlussier joined #evergreen
08:53 kmlussier left #evergreen
09:05 jwoodard joined #evergreen
09:07 tspindler joined #evergreen
09:12 Shae joined #evergreen
09:28 yboston joined #evergreen
09:39 sarabee joined #evergreen
10:04 Dyrcona joined #evergreen
10:08 krvmga joined #evergreen
10:08 * tsbere spins up a trusty VM on masslnc's server to do a test of clean install of opensrf/evergreen master there
10:09 krvmga in browse search (eg 2.5) , is there a global option somewhere to tell the system to ignore initial articles?
10:09 krvmga (a, an, the)
10:09 krvmga for example
10:12 tsbere krvmga: Some of that is just reading from the marc
10:13 tsbere krvmga: Also, it isn't ignoring specific articles. It is ignoring however many characters the marc said to
10:13 krvmga tsbere: yes, i've seen that. unfortunately, it doesn't seem to be working :(
10:13 tsbere krvmga: Also, not all interfaces will ignore them, and not all places in marc have the ability to specify how many to ignore....
10:14 tsbere krvmga: Really, even on the marc side it is a crapshoot. Throw in "does this interface use, or even have the ability to see, the information for how many to ignore" and things get wonky.
10:15 krvmga *sigh*
10:26 mceraso joined #evergreen
10:39 Dyrcona Well, turns out you can bless a string ref into a Perl class. However it is not very useful.
10:46 mrpeters joined #evergreen
10:51 kmlussier joined #evergreen
10:51 kmlussier krvmga: Did you say the browse isn't honoring non-filing indicators?
10:52 kmlussier krvmga: I'm wondering if what you're seeing is a result of bug 1321780 where the browse search has listed the 740 field twice.
10:52 pinesol_green Launchpad bug 1321780 in Evergreen "Title browse isn't honoring non-filing characters in 740 field" (affected: 4, heat: 24) [Medium,Confirmed] https://launchpad.net/bugs/1321780
10:53 kmlussier Once with the non-filing indicators and once without.
10:53 krvmga kmlussier: that might be. the examples that were shown to me had 740s like that
10:54 kmlussier OK, then, also see the idea that has been suggested in my comment at https://bugs.launchpad.net/eve​rgreen/+bug/1321780/comments/2
10:54 pinesol_green Launchpad bug 1321780 in Evergreen "Title browse isn't honoring non-filing characters in 740 field" (affected: 4, heat: 24) [Medium,Confirmed]
10:55 kmlussier My current thinking is that this is a good thing for all title fields. Because, then, the title shows up whether or not the user knows to skip the initial article or not.
10:55 * dbs is with kmlussier
10:58 kmlussier NOBLE has just recently configured their production system to do this. I don't think their browse search is live yet, but it should be soon. We were talking yesterday about putting their changes into a working branch. That is, if we can get community consensus around it. :)
11:02 kmlussier left #evergreen
11:09 kmlussier joined #evergreen
11:10 gmcharlt bshum: I think I know what's going on... looking into it
11:10 kmlussier tsbere: Speaking of  the masslnc vm, I just received my first request for a Bug Squashing Sandbox, so it looks like at least one will be used. :)
11:10 bshum gmcharlt: Cool, let me know what I can do to help out.
11:10 mdriscoll joined #evergreen
11:10 mllewellyn joined #evergreen
11:11 Dyrcona tsbere is looking into it, too.
11:12 tsbere gmcharlt: I was just barking up the wrong tree, I think I just found the right tree. >_>
11:14 tsbere gmcharlt: Want to compare notes? Because I got to a point where I know the problem, but don't know how to best fix it.
11:14 gmcharlt tsbere: I've only just started looking at it, but thus far my assumption is that it's the patch for 1350457 that's triggering it
11:15 tsbere gmcharlt: Want file and line number?
11:15 gmcharlt yeah
11:16 tsbere gmcharlt: Application.pm line 562 (I search for "caller's" to grab the comment on the end of the line) - the $self->session looks to be the problem. My tests seem to show that $self isn't actually a ref at all, but I could have written that wrong.
11:16 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
11:17 * tsbere isn't sure how that ends up working
11:18 asimon joined #evergreen
11:18 gmcharlt tsbere: my plan is to poke at that for a bit, but just revert if necessary
11:18 tsbere gmcharlt: The part that confuses me is $self->session is apparently valid and calls the proper function, but said function dies because $self is a string and not a hashref
11:18 ericar joined #evergreen
11:19 * tsbere apparently doesn't know enough about perl to debug this
11:19 vlewis joined #evergreen
11:19 asimon * Is there any way to prevent the email autopopulate in reports?
11:19 tsbere asimon: Don't have an email on your user account?
11:20 asimon tsbere: Aside from that?
11:22 tsbere asimon: I got nothing else for ya right now
11:22 asimon tsbere:  Yeah, I was afraid of that.  TY.
11:22 mmorgan asimon: I don't think so, other than removing the email address when you are setting up the report before hitting submit.
11:26 tsbere gmcharlt: I am wondering if just adding "and ref $self" (or && or whatever) to the "if $meth" would work to fix that line.
11:30 Dyrcona Looks like method_lookup is being called as a class method somewhere, but line 562 expects it to be called as an instance method everywhere.
11:32 gmcharlt yeah
11:36 gmcharlt tsbere: tried tacking on a check on ref($self) per your suggestion; wasn't enough, as it triggered an apparent infinte recursion in perl2JSONObject
11:41 mrpeters morning all, is there a planned release date for the new OpenSRF?
11:42 gmcharlt mrpeters: alpha today
11:42 mrpeters 10-4...so probably a few weeks yet
11:43 mrpeters just trying to decide if i should roll with current opensrf on 14.04 for 2.7 or wait it out, thanks!
11:43 gmcharlt mrpeters: yeah, it will basically be out just before 2.7.0
11:43 gmcharlt as far as what version to use, 2.3.0 is fine *unless* you want to try out the web-based staff client bits that are targetedf for 2.7-beta2
11:43 mrpeters cool, its mostly for testing our GenaSYS stuff so I'll await the alpha, since we're using beta2 for Evergreen
11:44 phasefx_ joined #evergreen
11:44 bshum Hmm
11:45 bshum gmcharlt: So the changes in opensrf_core.xml for things like the loglength and msg_size_warn need to be reflected in the copy for Evergreen too I guess?
11:45 bshum (eventually)
11:45 gmcharlt bshum: yep, that would be good
11:45 bshum Okay
11:49 mrpeters joined #evergreen
11:51 bshum Wow
11:51 bshum msg_size_warn is super old
11:52 bshum From 2011
11:53 tsbere gmcharlt: Where are you getting that infinite recursion? I don't seem to be getting it.
11:54 gmcharlt tsbere: introspect opensrf.settings
11:55 tsbere gmcharlt: Ahhh. In that case I suspect that is more the fault of the session fallthrough in general, not the adding of the ref($self) check.
11:57 * eeevil looks to see if having ->session protect itself from string invocant is enough...
11:57 * tsbere sees things actually function, evergreen-wise, with the ref($self) check, but hadn't tried to introspect before that
11:59 mrpeters joined #evergreen
12:00 eeevil gmcharlt: http://pastebin.com/7470gS0A is what I'm thinking
12:02 gmcharlt eeevil: I just tried that in fact -- no dice
12:02 eeevil boo
12:02 eeevil meh, +1 to revert, then
12:03 eeevil have to find the session the hard way at time of need, it seems
12:05 gmcharlt yeah
12:05 * gmcharlt pushes a revert
12:06 eeevil or, remove all string-invocant calls to method_lookup and make that the rule
12:06 pinesol_green [opensrf|Galen Charlton] Revert "LP#1350457: Pass caller's session to subrequests called via method_lookup" - <http://git.evergreen-ils.org/?p​=OpenSRF.git;a=commit;h=6ed6f2b>
12:07 eeevil oh, but that's much easier said than done, a grep tells me
12:07 gmcharlt yep
12:09 gmcharlt moving on... my next steps for OpenSRF today are seeing if the CORS support patch works, then writing some release notes and releasing the alph
12:09 gmcharlt a
12:10 akilsdonk joined #evergreen
12:10 bshum I just finished getting the web client squash branch on my test server
12:11 bshum I'm trying to figure out what I missed to get it actually functional
12:11 bshum And I think whatever I missed is leaving me with broken hold placement / bookbags in the staff client's catalog view.
12:11 bshum The main client
12:11 bshum *XUL
12:11 gmcharlt bshum: I set up a web-based staff client demo server the other day (independent of berick), and I can compare notes if you want
12:12 bshum Those were two areas berick specifically mentioned to test and both are not functioning.
12:12 bshum gmcharlt: Thanks, I'm definitely in uncharted territory
12:12 bshum There's comments on the ticket about installing dependencies for the web client
12:13 bshum But I'm not seeing those reflected in the README or any associated files in the root level
12:13 bshum I'm checking around to see what I might have missed
12:14 gmcharlt bshum: ./Open-ILS/web/js/ui/default/staff/README.install
12:14 bshum gmcharlt: Ahh, there we are.
12:14 bshum Thanks!
12:14 bshum I'll try those :)
12:14 csharp <beavis>heh heh... $meth heh heh yeah</beavis>
12:15 gmcharlt csharp: for supporting the opensrf.explode service
12:15 csharp gmcharlt++
12:16 dbwells joined #evergreen
12:18 eeevil gmcharlt: I'll not push for immediate inclusion, but your LP update pointed me at a likely fix
12:18 gmcharlt eeevil: great
12:19 eeevil there's always next version :)
12:20 bshum Well it's only alpha for OpenSRF :)
12:21 bshum "set -j to number of CPU cores + 1"
12:21 bshum That sounds so harsh
12:21 bshum :)
12:22 bshum So, for record, what I got without installing the node stuff, etc. with the XUL client is that...
12:22 Dyrcona One of them is almost always idle. ;)
12:22 bshum Hold placement was in some sort of loop, where it kept taking me to another hold placement screen every time I tried to Submit
12:22 bshum Hitting Cancel eventually brought me back to the search results
12:22 bshum Equal number to the number of times I hit Submit
12:23 bshum And using the bookbag add to temp list took me to another tab, and then the XUL client told me that it couldn't complete due to too many redirects or something
12:23 bshum I'm hopeful that installing the web client bits will help resolve those issues...
12:24 bshum But I'm flying pretty blind in this :)
12:25 bshum Oh and unrelated
12:25 bshum I need to figure out why apache2-websockets never wants to start automatically after restarts
12:25 jeff oh bah. pre-cats prompt each time on checkout for title/author/etc.
12:26 jeff i suspected, but was secretly hoping i was wrong.
12:27 jihpringle joined #evergreen
12:27 csharp yeah, they can't be re-used - to the chagrin of our circ staff who try to avoid sending books to catalogers to process ;-)_
12:27 csharp and our database quality control staff
12:28 jeff yeah. we were hoping for a simple way to create temporary items that didn't re-prompt.
12:28 jeff might need to adjust my approach.
12:30 bshum gmcharlt: When it says in step 2 to go to the $EVERGREEN_ROOT is that referring to where I git cloned?  Or referring actually to where the live files are?
12:30 bshum If it's to where I cloned
12:30 bshum I assume that this is something I should have done before I make installed everything into place...
12:30 gmcharlt bshum: correct
12:30 bshum Great.
12:31 gmcharlt it's safe enough to run in the live directory
12:32 bshum Hmm
12:32 bshum Oh, as root, gotcha... for 2.1
12:32 Dyrcona jeff: There is, I believe, a patch for that in master. I'm not certain if it solves your particular problem.
12:33 Dyrcona Guess it is in 2.7 also.
12:33 bshum Well only for npm install apparently
12:33 bshum bower install doesn't like being run with root or sudo
12:34 gmcharlt right, running as opensrf is fine
12:35 bshum I'm just typing my observations here, but I expect to help put these to helping to improve the instructions at some point.  I don't mean to be rambly, just being lazy to take notes elsewhere. :)
12:38 bshum Well that's special
12:38 bshum "There are processes named 'apache2' running which do not match your pid file which are left untouched in the name of safety, Please review the situation by hand."
12:38 bshum Heh
12:39 bshum So if I start apache2-websockets before apache2, it doesn't like that.
12:40 csharp bshum: thanks for rambling ;-)
12:41 csharp I was running into the same issues
12:41 bshum Well
12:41 bshum I see the web client!
12:41 bshum But I can't log into it.
12:41 bshum :)
12:42 bshum Aha
12:42 bshum Websocket error
12:42 bshum Lovely
12:44 bshum Hmm
12:46 csharp yeah - that's as far as I got
12:46 csharp I think I was missing something in the config, but I didn't have time to dig deeply
12:47 csharp I'm also unclear on the relationship between apache2 and apache2-websockets?
12:47 bshum Well the main staff client works better for me right now
12:47 bshum Not encountering the issues I noted just a moment ago with holds and bookbags
12:47 bshum so that's good
12:47 csharp does one replace the other? does one start before the other? how does restarting apache work with websockets involved? etc.
12:48 bshum csharp: My guess has been that they work separately from each other.
12:48 bshum Since they operate on different ports and such
12:48 csharp feels messy
12:49 bshum I'm not quite sure why that is yet.
12:49 csharp from a sys admin perspective ;-)
12:49 csharp once I understand it, we can build init/upstart/systemd scripts to handle it, though
12:49 bshum I was going to call it "brittle"
12:49 Shae_ joined #evergreen
12:49 bshum :)
12:49 csharp right
12:50 csharp a little like the ruby pieces in acq
12:50 tsbere I would prefer we do everything we can to make everything work in a single apache, if possible. >_>
12:50 csharp tsbere: +1
12:51 eeevil tsbere: a single 300MB+ per backend apache :)
12:52 bshum Oh
12:52 bshum It's probably my load balancer
12:52 bshum Futzing in the way
12:52 bshum Sigh
12:53 * bshum tries again once adding the ports for websockets
12:54 bshum It lives!
12:54 bshum Sorta
12:55 buzzy joined #evergreen
12:59 buzzy joined #evergreen
13:00 gmcharlt so far the CORS patch is looking promising
13:02 bshum Hmm
13:02 bshum XUL patron search is giving undefined errors
13:03 bshum \npatron/search_form.xul\nSyntaxError: JSON.parse: unexpected character\n and such
13:05 bshum Yep, and we can't search there
13:05 dbs bshum: so that's the new native JSON methods maybe complaining about crappy JSON?
13:09 bshum dbs: Not sure really, I just started poking
13:10 * bshum pauses a moment to go eat his sandwich
13:11 dbs bshum: wild guess on my part, based on recent changes I saw in the commit mail
13:12 bshum dbs: Sometimes those turn out correct though :)
13:22 jboyer-isl Since lp is being lp, does anyone know if there's a bug about passing malformed xml to fancy_prompt.xul? (volume transfers explode on call numbers with '&' characters)
13:23 jboyer-isl I was hoping not to file a dup if there's already something floating around.
13:23 csharp that rings a bell, but I don't know about a bug :-/
13:29 jboyer-isl It's a 1-line fix (for volumes, anyway, more bugs may lurk at other access points) I suppose I could just throw a collab branch up and let the dupes fall where they may.
13:39 bbqben joined #evergreen
13:39 bshum dbs: This native JSON thing is in OpenSRF?  Thinking on 6c3b1001c6183b2f633d0f43ccd3d28071c0c48d
13:39 pinesol_green [opensrf|Bill Erickson] LP#1316245: JS now uses browser-native JSON routines - <http://git.evergreen-ils.org/?p​=OpenSRF.git;a=commit;h=6c3b100>
13:40 dbs bshum: that's what I was thinking
13:49 montgoc1 joined #evergreen
13:52 jboyer_isl joined #evergreen
13:53 jboyer_isl Eww. I underestimated how best to fix that encoding error. encodeURIComponent() is definitely not the correct choice.
13:54 jboyer_isl Looks like xml_encode() from server/serial/notes.xul is about to get a promotion.
13:55 tsbere jboyer_isl: What did you apply the encodeURIComponent to?
13:56 jboyer-isl tsbere, I was trying to make call numbers xml-safe in copy_browser.js, line 914. Currently if you try to transfer a volume with an ampersand you get an ugly XML error instead of a confirmation box.
13:58 jboyer-isl joined #evergreen
13:59 tsbere jboyer-isl: Have you tried using escape instead of encodeURIComponent?
13:59 jboyer-isl Not yet. I was thinking that it was deprecated, but that may be faulty memory on my part.
13:59 tsbere Not sure if it will work better or not (I dunno what your "Eww" means, actually...)
14:00 jboyer-isl I'm sure it'll work, I just didn't know if it was the best choice.
14:01 bbqben Hi all - EOB meeting starting here in just a few minutes
14:01 jboyer-isl Well, encodeURIComponent gives you "Transfer volumes J%20FIC%20CALL%20LABEL to library...
14:01 jboyer-isl So that's pretty "eww." :)
14:01 tsbere ok, then escape isn't gonna help. Nevermind my suggestion. :P
14:02 terran joined #evergreen
14:02 jboyer-isl :q
14:02 jeff Dyrcona: regarding pre-cats: is the patch you had in mind the same as or related to the one for permitting pre-cats to fill holds?
14:03 pinesol_green [opensrf|Bennett Goble] LP#1002028: Cross Origin Resource Sharing for OpenSRF - <http://git.evergreen-ils.org/?p​=OpenSRF.git;a=commit;h=d8dbf0c>
14:03 pinesol_green [opensrf|Galen Charlton] LP#1002028: support CORS for HTTPS - <http://git.evergreen-ils.org/?p​=OpenSRF.git;a=commit;h=bc914bf>
14:03 pinesol_green [opensrf|Galen Charlton] LP#1002028: set Access-Control-Expose-Headers - <http://git.evergreen-ils.org/?p​=OpenSRF.git;a=commit;h=e8f7863>
14:03 jeff Dyrcona: that was the first thing i thought to look into, good to have confirmation if that's what you had in mind also. :-)
14:03 bbqben #startmeeting Evergreen Oversight Board Meeting, 21.08.14
14:03 pinesol_green Meeting started Thu Aug 21 14:03:33 2014 US/Eastern.  The chair is bbqben. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:03 pinesol_green Useful Commands: #action #agreed #help #info #idea #link #topic.
14:03 pinesol_green The meeting name has been set to 'evergreen_oversight_board_meeting__21_08_14'
14:03 Dyrcona Well, yeah.
14:03 bbqben #topic introductions
14:03 bbqben EOB members, please introduce yourself with #info
14:04 bbqben #info bbqben = Ben Hyman, BC Libraries Co-op
14:04 bshum #info bshum = Ben Shum, Bibliomation
14:04 graced #info graced = Grace Dunbar, Equinox
14:04 montgoc1 #info montgoc1 = Chauncey Montgomery, Consortium of Ohio Libraries
14:04 yboston #info yboston is Yamil Suarez - Berklee College of Music
14:05 kmlussier #info kmlussier is Kathy Lussier, MassLNC
14:05 bbqben Hey everyone, happy Thursday!
14:05 csharp #info csharp is Chris Sharp, GPLS
14:05 bbqben #topic Minutes / Actions from last meeting
14:06 bbqben #info http://evergreen-ils.org/meetings/evergr​een/2014/evergreen.2014-06-19-14.09.html
14:06 bbqben I see 4 action items there - not 100% sure all are done
14:06 RoganH joined #evergreen
14:07 bbqben #4 will be addressed in this agenda... kmlussier, yboston - your bits?
14:07 kmlussier #info kmlussier did not put out a 2nd call for conference committee volunteers because shortly after the last meeting, jboyer-isl volunteered to serve as a community rep.
14:07 RoganH Apologies for being, late small crisis.
14:08 kmlussier jboyer-isl++
14:08 bbqben jboyer-isl++
14:08 jboyer-isl Let
14:08 jboyer-isl 's see how helpful I am before we get too carried away. ;D
14:08 bbqben Welcome, RoganH and hi csharp
14:09 csharp hi!
14:09 bbqben ok, will follow up with yboston later
14:09 yboston I am here
14:09 yboston I submitted some links and text to the board list to be sent to the SFC, but I can repackage in all inside a word doc if that would be better.
14:09 bbqben hey yboston - perrrfect!
14:10 bbqben #topic Evergreen vendor listing and related correspondence received
14:10 RoganH Related to this, kmlussier, what was the final status of the Edusys listing?
14:11 kmlussier RoganH: Ooh, I forgot about. They never responded to my e-mail, so I'll put out an e-mail to the general list today and remove their listing.
14:11 kmlussier Sorry, I got sidetracked after that discussion.
14:12 bbqben kmlussier ++
14:12 RoganH 'tis OK, you (we all) are busy.
14:12 bbqben so, that solves one bit.
14:12 RoganH I brought up the original point so I'll restate it a bit.
14:12 RoganH We implemented the vendor policy roughly a year ago.
14:13 RoganH We've had some community feedback from several vantage points since then and we've said we should live with it a year first before we entertain changes and we are now at that year.
14:13 RoganH Sometimes I've wanted to change since I think it would benefit those browsing the entries would be that if we linked directly to descriptions of services.
14:14 RoganH (imagine commas where I omitted them there)
14:14 kmlussier RoganH: I don't think that's a bad idea, but, in most cases, I also see that providers are listing their services on the support provider page.
14:15 kmlussier #link http://wiki.evergreen-ils.org/dok​u.php?id=faqs:evergreen_companies
14:15 RoganH Sometimes it's buried, I think for convenience we should have a direct link.  That might mean two links on a listing but I don't think that's a great hardship.
14:16 RoganH It also means that if they change information on their site users can easily see that since it might be more up to date than what they provide us with for their page listing.
14:16 graced That could be beneficial to people searching for information so long as the links are kept up to date.
14:17 RoganH graced: Agreed.  Of course as we saw with Edusys we should probably check occasionally since the whole vendor can disappear.
14:17 graced The web team could probably at least take on periodic link checking
14:18 kmlussier I try to check occasionally, but the timing varies.
14:18 RoganH graced: I would even volunteer to do it.  I wouldn't be checking validity of content or anything like that, just whether the links still went to sites and if their product page still had Evergreen services on it (if that part is agreed upon and becomes policy).
14:18 kmlussier Usually when I'm adding a new vendor to the page.
14:19 RoganH If I checked once a month or so and kmlussier checked when she adds someone that would probably cover it reasonably well I think.
14:19 graced Well, I see the value of linking directly to services in addition to a generic company link.  But do we want to require it?  Or should it be optional?
14:20 yboston We can consider adding a note for cumminty memebers to report bad links right from that page (I don't such a note right now)
14:20 montgoc1 yboston: good idea
14:20 yboston might help catch bad pages / compnaies on the earlier side
14:20 bbqben graced right, and anything required will take resources to monitor. Maybe start with suggested and give that a go for a year?
14:20 graced bbqben++  I can get behind that.
14:21 RoganH If we go with suggested I recommend we ask the vendors to supply us links to those services pages so that we can go ahead and add them.
14:21 kmlussier FWIW, I don't think requiring it will take any more resources to monitor than the link back to the page.
14:22 graced I'm happy to email current vendors and request the additional services link.
14:22 bbqben graced++
14:22 RoganH My preference would be to make it required as I think having them would be highly beneficial.
14:22 graced If they want to supply us with more than one for some reason will we accept that?
14:22 kmlussier +1 to required
14:23 RoganH But, if the consensus is to go with preferred I still think it's a good thing.
14:23 RoganH If they're each pages that link to service offerings I don't have an objection to that.
14:23 bbqben anyone strongly opposed to required?
14:23 graced I'm okay with required.
14:23 montgoc1 OK with me.
14:24 bbqben no scaly wags here
14:24 bbqben :)
14:24 bshum Hmm, required but do we want to offer a grace period for existing listed companies to provide us this information?
14:24 kmlussier We'll also need to update the policy at http://wiki.evergreen-ils.org/doku.php?id​=faqs:evergreen_companies:listing_policy
14:24 RoganH bshum: yes
14:24 bshum *the community (not just us specifically)
14:25 RoganH I think we should publish the idea to the list before we vote on it.
14:25 RoganH Gather feedback from community members and vote next meeting.
14:25 kmlussier RoganH: I agree. I was just thinking the same thing.
14:25 bshum +1 RoganH's idea
14:25 graced +1
14:25 graced I think Rogan just volunteered to write that email....
14:25 RoganH I will do so.
14:26 yboston I am always cocnerned about maintaining the same content in two location
14:26 graced RoganH++
14:26 bbqben RoganH - willing to dangle the idea on the list for us?
14:26 bbqben hah. reading too slow!
14:26 yboston so these companies need to maintain the wiki page updated with their services and their own services page?
14:26 yboston just playing devil's advocate
14:26 * kmlussier expects they're already updating their own services page.
14:26 bbqben #action Roganh will draft email to vendors re: service delineation etc
14:26 yboston would we want to ask them to only list their services in their own page and not on the wiki?
14:27 montgoc1 That may be more efficient for them.
14:27 montgoc1 Only one place to update services.
14:27 graced Well, I think people going to the wiki might want to know if a certain vendor is a "development only" vendor or a "support" vendor.
14:27 graced So I think it's valuable to have that on the wiki.
14:28 yboston graced: I agree with you, but just trying to see an alternitive viewpoint.
14:29 graced We could just have standard service categories, though.  And pare down the amount of info on the page.
14:29 bbqben the follow through on required is a concern for me, but lets see what the community input is
14:29 bshum Valuable, but perhaps not required.  If we require that we have a link to a services page/area, I'd say it's at discretion of company as to how complete their entry appears in the community listing.
14:29 bshum The ones who put more effort will naturally shine better in my eyes.  (But that's just my personal opinion)
14:30 kmlussier I agree with bshum. As it is, it really has been at their discretion as to how they want to describe their services.
14:30 RoganH I don't want to judge how complete an entry is, just have something that folks can look at and potential customers can judge themselves once they link through to it.
14:31 bbqben other thoughts on this thread before we move to replying to the correspondence received?
14:31 RoganH No more from me.
14:31 kmlussier bbqben: As far as following through, as it is, I always check the vendor page for their link back to the community. It's just one more step to visit their services page.
14:32 RoganH And you should be thanked for that effort.  kmlussier++
14:32 kmlussier The only problem I see is if a vendor were to take it down after they were listed. Which would be a bizarre thing to do.
14:33 RoganH Then I think it would fall under the same rule as the link back.
14:33 bbqben kmlussier++
14:33 kmlussier Do we need to have the larger discussion of how to handle complaints about a vendor?
14:34 graced I think that was the next issue up
14:35 bbqben yes and no; definitely we should follow up on the complaint with correspondence (compaint received)...
14:35 bbqben but I'm looking at our agenda and the time - think we'll need to take the chat away / revisit asap
14:36 RoganH Since it's not time critical can we follow up on that on list?
14:36 kmlussier +1`
14:36 bbqben RoganH totally
14:36 yboston +1
14:36 graced +1
14:36 montgoc1 +1
14:36 bbqben #action dealing with complaints about vendors
14:37 bbqben ok, moving on ...
14:37 bbqben #topic outreach Program for Women (Kathy)
14:37 kmlussier #link http://list.evergreen-ils.org/pipermail/e​g-oversight-board/2014-August/000850.html
14:38 bbqben Thanks kmlussier - care to walk us through?
14:39 kmlussier I would love to see the Evergreen community work with this project, but the big issue is whether we can allocate the funding and if we can find volunteers willing to mentor interns.
14:39 kmlussier Is there any interest in using community funds for this program?
14:41 graced I certainly have interest but I worry about having good entry points and mentorship - just like GSOC.
14:41 kmlussier Yes, I was concerned about the mentoring aspect too. I think we would need to make sure we had good projects and committed mentors before moving forward.
14:42 kmlussier But I didn't really want to put those questions out to the community if there wasn't a means for funding our participation either.
14:43 kmlussier I also would like to explore the idea of co-mentoring, which was done with GSoC too because committing something like 5 hours a week can be a lot of small organizations. But if mentors shared the responsibility, it might not be so much of a burden.
14:43 gmcharlt having multiple mentors would be good, based on GSoC experience
14:45 graced kmlussier: I think I'd feel better if we worked backwards - ID some projects that need doing and are accessible and get committed mentors who know that area and then ask for the funding?
14:45 bbqben kmlussier re: the $6250 ...
14:45 yboston For the record, I have used three seperate MLS students as interns. I ended up spending a huge amount of time training them for what I needed them to do (build test servers, AciiDoc, etc.). Luckily I have saved some of my trainign materials, and would be willing to help mentor
14:45 bbqben ...is there flexibility in how the funds are applied?
14:45 kmlussier Flexibility in what sense?
14:46 graced The sponsorship per intern includes $5,500 (USD) stipend, $500 travel allowance, and a $250-500 administrative fee for the GNOME Foundation.
14:46 yboston also, in my case Berklee did not have to pay, we went through a local college witn an MLS program, and two out of the three interns were female
14:46 bbqben graced - thanks, that explains it
14:46 graced :)
14:47 bbqben so, seems like general support. kmlussier - care to propose language for a vote?
14:47 kmlussier Also, I was told that if we ultimately had two solid projects with promising mentors, there *might* be funding for the project to pick up the expense of the other internship. A strong *might* based on the projects and applicants.
14:48 kmlussier Motion to allocate community funds to sponsor one intern through the Outreach Project for Women if we find strong projects and committed mentors?
14:49 kmlussier I think we would need to follow up via e-mail after we've had the community discussion just to confirm that everyone is on board with it.
14:49 kmlussier Since the deadline is before our next meeting.
14:49 bbqben #startvote Motion to allocate community funds to sponsor one intern through the Outreach Project for Women if we find strong projects and committed mentors? Yes, No, Abstain
14:49 pinesol_green Begin voting on: Motion to allocate community funds to sponsor one intern through the Outreach Project for Women if we find strong projects and committed mentors? Valid vote options are Yes, No, Abstain.
14:49 pinesol_green Vote using '#vote OPTION'. Only your last vote counts.
14:49 bshum #vote Yes
14:49 montgoc1 #vote Yes
14:49 graced #vote Yes
14:49 kmlussier #vote Yes
14:49 bbqben #vote Yes
14:49 RoganH #vote yes
14:49 yboston #vote yes
14:50 bbqben #endvote
14:50 pinesol_green Voted on "Motion to allocate community funds to sponsor one intern through the Outreach Project for Women if we find strong projects and committed mentors?" Results are
14:50 pinesol_green Yes (7): kmlussier, yboston, bbqben, graced, RoganH, montgoc1, bshum
14:50 bbqben #action kmlussier follow up with email to community, introducing topic
14:50 kmlussier Thanks all!
14:50 bbqben kmlussier ++
14:50 gmcharlt kmlussier++
14:51 bshum kmlussier++
14:51 bbqben #Topic SFC update (Emergency Fund & OCLC topics)
14:51 bbqben kmlussier and I spoke with Karen S this am briefly...
14:52 bbqben Broached the Emergency fund topic in broad strokes and will follow up in a little more detail shortly. Glad to have had the conversation as a start!
14:53 bbqben Also gave a heads up re: the OCLC topic. RoganH is going to get this ball rolling with a legal opinion, institutionally; we can determine if the issue scales nicely to"project level" from there, meriting more of SFC's attention, e.g.
14:53 collum joined #evergreen
14:54 bbqben kmlussier anything to add?
14:54 kmlussier Nope
14:54 bbqben ok, questions on these pieces?
14:55 bbqben #action bbqben update for next meeting on SFC topics
14:55 bbqben #Topic Election of a new Secretary
14:55 bbqben Any volunteers?
14:55 kmlussier Wait! Who's taking minutes? ;)
14:55 graced I volunteer csharp!
14:55 bbqben haha
14:55 RoganH Can we nominate csharp before he's inducted?
14:56 bshum Before we do that, should we formally affirm our newest member?
14:56 kmlussier We need to rearrange the agenda topics.
14:57 bbqben scaly waggery in action
14:57 csharp backroom deals are afoot
14:57 bbqben We have shamed csharp into dual duties
14:57 RoganH csharp: they're not very backroom really
14:58 bbqben so, a procedural adjustment here
14:58 csharp haha
14:58 csharp "the new secretary isn't even on the board!"
14:58 bbqben #Topic appointment of a new Board member
14:59 bbqben csharp was the runner up in the last STV vote for an EOB conducted by the community. Propose his appointment to replace sborger, given her resignation
14:59 jboyer-isl Gentlemen, you can't take notes in here, this is the Secretary's office!
14:59 bbqben any discussion?
15:00 * csharp fidgets uncomfortably
15:00 bbqben #startvote Motion to appoint csharp as an EOB member? Yes, No, Abstain
15:00 pinesol_green Begin voting on: Motion to appoint csharp as an EOB member? Valid vote options are Yes, No, Abstain.
15:00 pinesol_green Vote using '#vote OPTION'. Only your last vote counts.
15:00 kmlussier #vote Yes
15:00 bshum #vote NO
15:00 montgoc1 #vote Yes
15:00 RoganH #vote yes
15:00 bshum #vote Yes
15:00 bshum :)
15:00 csharp heh
15:00 bbqben #vote Yes
15:00 graced #vote Yes
15:00 yboston #vote yes
15:01 bbqben #endvote
15:01 pinesol_green Voted on "Motion to appoint csharp as an EOB member?" Results are
15:01 pinesol_green Yes (7): kmlussier, yboston, bbqben, graced, RoganH, montgoc1, bshum
15:01 kmlussier csharp++
15:01 csharp thanks!
15:01 csharp I'm honored, truly
15:01 graced congrats csharp!
15:01 gmcharlt csharp++
15:01 bshum Welcome aboard
15:01 bshum csharp++
15:01 bbqben csharp honored? In that case...
15:01 bbqben #startvote Motion to appoint csharp as EOB Secretary? Yes, No, Abstain
15:01 pinesol_green Begin voting on: Motion to appoint csharp as EOB Secretary? Valid vote options are Yes, No, Abstain.
15:01 pinesol_green Vote using '#vote OPTION'. Only your last vote counts.
15:02 kmlussier Did he accept the nomination?
15:02 csharp I accept your nomination - yes - thank you!
15:02 RoganH #vote yes
15:02 kmlussier #vote Yes
15:02 bbqben #vote Yes
15:02 montgoc1 #vote Yes
15:02 graced #vote Yes
15:02 yboston #vote yes
15:02 bshum #vote Yes
15:02 bbqben #endvote
15:02 pinesol_green Voted on "Motion to appoint csharp as EOB Secretary?" Results are
15:02 pinesol_green Yes (7): kmlussier, yboston, bbqben, graced, RoganH, montgoc1, bshum
15:02 bbqben csharp ++
15:02 graced csharp++
15:02 csharp I gladly accept that too ;-)
15:02 montgoc1 csharp++
15:03 bbqben Realize we're running late. Shall we continue?
15:03 kmlussier I'm not going anywhere.
15:03 bshum What's next?
15:03 montgoc1 I can continue.
15:03 yboston I can continue
15:03 csharp I'm good
15:03 graced continue
15:03 bbqben #Topic Evergreen community job postings
15:04 bbqben montgoc1 proposed a place for EG postings on the website, and there was some discussion on the list. Discussion?
15:04 RoganH The web team discussed this yesterday as well.
15:04 kmlussier We discussed it at yesterday's web team meeting.
15:05 kmlussier RoganH: I win!
15:05 bbqben poifect - update from the web team?
15:05 RoganH Some idiot offered to add job entries when they're posted.
15:05 kmlussier RoganH++
15:05 gmcharlt and we'll be trying out a couple ways to manage the listings
15:06 bbqben Excellent - glad to hear it. Will watch for updates
15:06 montgoc1 I can help if you need.
15:06 bbqben #Topic Evergreen 2.7 Release Manager's Report
15:06 RoganH montgoc1: great!
15:06 pmurray Any reason not to use an RSS feed from http://jobs.code4lib.org/jobs/Evergreen/
15:07 * pmurray goes back into lurking mode.
15:07 bshum #info Ben Shum wrote a blog post about 2.7.0-beta1 at http://evergreen-ils.org/eve​rgreen-2-7-0-beta1-released/
15:07 bshum Big thanks to everyone who participated in development, testing, writing release notes
15:07 bshum I think it's the first time we've had such comprehensive coverage of all new features in the notes on first pass.
15:08 bshum Later today/tomorrow, we'll make a final call on the web client preview going in (pending further testing)
15:08 csharp pmurray: nice - I didn't know about that
15:08 bbqben bshum ++
15:08 bshum I expect that we'll get some more work done during the Bug Squashing Day (see http://evergreen-ils.org/ev​ergreen-bug-squashing-day/)
15:08 kmlussier bshum++
15:08 csharp bshum++
15:08 bshum And that'll lead us to a better 2.7.0-RC1 if all goes according to timeline
15:09 graced As an aside, Equinox will have the public test/demo server for the web based client up by tomorrow.
15:09 yboston bshum++
15:09 RoganH graced: yay!
15:10 bbqben Wahoo, thanks for the update bshum and graced
15:10 bbqben #Topic Financial Report
15:10 bbqben gmcharlt ++
15:10 gmcharlt quick note on the numbers
15:11 kmlussier Can we reschedule that date for accessing the ledger sometime soon?
15:11 gmcharlt they reflect $312.19 for book sales via Lulu
15:11 gmcharlt which were mostly earned last year, but were added to the ledger this summer
15:12 gmcharlt as well as a $250 donation by graced
15:12 gmcharlt kmlussier: yes - I will send out a survey for dates in September
15:12 kmlussier gmcharlt: Thanks!
15:12 bbqben yboston ++ for the diff log on the financials too
15:13 bbqben #Topic Evergreen Conference Report
15:13 yboston I am storing the reports in a lcoal git repo, may push it to github at some point
15:13 kmlussier buzzy had to leave early, but left me some notes to report.
15:14 kmlussier #info the 2015 local conference team has been meeting with the site on details and and still seeking conference committee members.
15:14 kmlussier #info the website for the venue, if anyone wants to check it out, is http://www.hoodriverinn.com/
15:14 kmlussier That's all he gave me before he had to run off.
15:15 bbqben nice pool!
15:15 montgoc1 Nice view.
15:15 * csharp wants to go to there
15:15 yboston very nice
15:15 bbqben Thanks for the update kmlussier
15:16 graced kmlussier: do you know if he's seeking local committee members or general community?
15:16 kmlussier I don't know. I thought local, but I'll double check with him.
15:16 graced Thanks!
15:16 bbqben # Topic September teleconference call
15:17 bbqben oops #Topic September Teleconference call
15:17 bbqben So, basically proposing that our next scheduled meeting be via teleconference rather than IRC
15:17 kmlussier Will that work with the oops in there?
15:17 bbqben #Topic September Teleconference call
15:17 bbqben beats the horse
15:18 bbqben 18.09.14 @ 11 Pacific
15:18 bbqben The call will be recorded
15:18 csharp the new secretary can take old school minutes, too
15:19 bbqben csharp like, with a pen & paper? Too much!
15:19 csharp :-D
15:19 RoganH csharp: I think you can use a laptop though you'd get style points for clay tablets
15:20 bbqben #action bbqben to send out conference coordinates in advance
15:20 bbqben Before we wrap, any other items, thoughts, jokes?
15:20 RoganH No jokes shareable in a publicly logged forum.
15:21 bbqben Fair enough, thanks all for your time today!
15:21 bbqben #endmeeting
15:21 pinesol_green Meeting ended Thu Aug 21 15:21:24 2014 US/Eastern.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
15:21 pinesol_green Minutes:        http://evergreen-ils.org/meetings/evergr​een/2014/evergreen.2014-08-21-14.03.html
15:21 pinesol_green Minutes (text): http://evergreen-ils.org/meetings/evergr​een/2014/evergreen.2014-08-21-14.03.txt
15:21 pinesol_green Log:            http://evergreen-ils.org/meetings/evergree​n/2014/evergreen.2014-08-21-14.03.log.html
15:21 csharp bbqben++
15:21 graced bbqben++
15:21 montgoc1 bbqben++
15:21 RoganH bbqben++
15:21 csharp eob++
15:22 yboston bbqben++
15:22 kmlussier bbqben++
15:22 bshum bbqben++
15:22 gmcharlt bbqben++
15:22 bbqben stop already!
15:22 bbqben sheesh
15:22 kmlussier @karma bbqben
15:22 pinesol_green kmlussier: Karma for "bbqben" has been increased 24 times and decreased 0 times for a total karma of 24.
15:22 gmcharlt bshum: I have a lead on that error you were getting bringing up the patron search form
15:26 gmcharlt bshum: this both explains and solves the problem - http://paste.lisp.org/display/143457
15:26 bshum gmcharlt: Aha!
15:26 * bshum tests
15:26 gmcharlt upshot is that JSON2js in OpenSRF is now also stricter as a result of berick's change
15:27 Dyrcona bbqben++ :p
15:46 gmcharlt bshum: bug 1359934
15:46 pinesol_green Launchpad bug 1359934 in Evergreen "JavaScript error opening patron search form" (affected: 1, heat: 6) [High,New] https://launchpad.net/bugs/1359934
15:49 edoceo joined #evergreen
15:54 pmurray bbqben and all: Sorry about barging in on the meeting.  Galen's tweet distracted me, so I thought I'd come in and see what the community was doing...
15:55 bbqben pmurray no worries at all! gmcharlt can be distracting for all of us ;)
15:56 kmlussier pmurray: Ha ha. Maybe we can have gmcharlt tweet at every meeting to get more people to poke their heads in.
15:56 pmurray In case it was missed, the tweet was https://twitter.com/gmcharl​t/status/502524970052771840
16:00 bshum gmcharlt: Patch looks good and my test server's XUL patron search is happier now.
16:03 bshum I'll get it signed and into master as a bug fix
16:07 bshum So far, not encountering other errors in the XUL client
16:11 pinesol_green [evergreen|Galen Charlton] LP#1359934: prevent error opening patron search form - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=646d132>
16:29 tspindler left #evergreen
16:43 kmlussier Weeee! I just set up my first Sandbox with a working branch loaded.
16:43 kmlussier tsbere++ #Making things so easy!
16:43 bshum tsbere++
16:45 kmlussier Bmagic++ #Setting up Sandboxes from MOBIUS
16:46 kmlussier Now we just need more people to request them. :)
17:08 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
17:11 mmorgan left #evergreen
17:14 kmlussier Hmmm...is there an easy way to figure out what staff/user logins can be used with Concerto? It might be nice to provide that info on a wiki page somewhere.
17:17 mdriscoll left #evergreen
17:24 * kmlussier should stop testing bug fixes and save it for Bug Squashing Day.
17:24 kmlussier Have a nice night everyone!
18:08 remingtron_ joined #evergreen
18:08 dbwells_ joined #evergreen
18:21 ktomita Is the fact that a user is also an OverDrive user stored somewhere in the Evergreen database?
18:25 csharp ktomita: nope - it's checked via SIP2
18:26 ktomita csharp: thanks.  I didn't think it was in there.
18:36 dkyle joined #evergreen
19:25 wsmoak joined #evergreen
20:03 jboyer_isl joined #evergreen
20:11 bbqben joined #evergreen
21:40 kmlussier joined #evergreen
21:52 boxDbrand joined #evergreen
21:54 boxDbrand newbie setup question - the very last step #12 -srfsh login is failing with "Received no data from server" --any suggestions?
21:55 boxDbrand also setingstester.pl results with "libdbi postgresql driver not found in shared library path"
21:57 kmlussier ~troubleshoot
21:57 pinesol_green If you're having trouble getting Evergreen to work, please follow this guide for isolating the problem: http://evergreen-ils.org/dokuwiki/doku.ph​p?id=troubleshooting:checking_for_errors
21:58 kmlussier boxDbrand: I can't help with your question, but you might want to check that link.
21:59 kmlussier boxDbrand: The channel isn't very active at this hour, so if the link doesn't help or if nobody else is around to help out, you might want to try tomorrow. About 10 to 5 Eastern time is when it's the most active.
22:39 bshum boxDbrand: Which version of OpenSRF / Evergreen are you installing? And on which Linix distribution?
22:40 bshum *Linux

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