Evergreen ILS Website

IRC log for #evergreen, 2014-11-12

| 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
05:08 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
06:36 wsmoak joined #evergreen
06:37 eeevil joined #evergreen
06:37 mtate joined #evergreen
07:09 mnsri_ joined #evergreen
07:17 Callender joined #evergreen
07:24 phasefx joined #evergreen
07:24 Callender joined #evergreen
07:26 eeevil joined #evergreen
07:31 remingtron_ joined #evergreen
07:40 kmlussier joined #evergreen
07:46 Huck5 joined #evergreen
07:52 Huck5 left #evergreen
07:53 jboyer-isl joined #evergreen
07:54 dreuther joined #evergreen
08:28 mdriscoll1 left #evergreen
08:28 mdriscoll1 joined #evergreen
08:30 graced joined #evergreen
08:35 Stompro joined #evergreen
08:37 bshum Stompro: I'm generally +1 to using the PostgreSQL apt repo and suggesting others to use newer PostgreSQL versions as long as the community users have had enough time to check things are working well.
08:37 bshum The trick is just getting enough testing done for all the combinations.
08:39 bshum That said, adding an extra repo might be more work than needed for some folks if the main repository for a given distribution already contains a reasonably new enough version of PostgreSQL.
08:39 * bshum is of many minds on much of this.
08:42 bshum Might be a good question to ask during the developer meeting this afternoon...
08:44 Stompro bshum: Thanks, I'll work on something for the upgrade/install docs.
08:44 artunit joined #evergreen
08:45 mmorgan1 left #evergreen
08:45 rjackson-isl joined #evergreen
08:45 bshum Stompro: Bear in mind though that the makefiles also point at installing specific PostgreSQL versions per distribution.
08:45 bshum So even if you set the apt source, the automated installer will choose PG 9.1 if you specify squeeze or precise
08:46 bshum So it's not just documentation that would need adjustment.
08:50 mmorgan joined #evergreen
08:51 Shae joined #evergreen
08:52 Stompro Thanks, I'll take a look at that also.  Maybe a check to see if 9.3 is available in the package cache, then fall back to 9.1.  Maybe this is getting to be too big of a change that will hold things up.  Maybe I'll focus on getting things updated for the staus quo, and then work on enhancements later.
08:54 bshum Sounds good.
08:54 bshum Perhaps this is something we can aim to standardize in the mext major Evergreen series for new installations.
08:55 bshum For existing point releases, it might be harder to tell folks to all upgrade to PG 9.3 right away.
08:56 * bshum wanders off for a bit.
09:00 RoganH joined #evergreen
09:06 Stompro Is Fedora supported?  It is mentioned in the install docs.  Anyone know what the minimum version of Fedora is?  The install docs just say "Fedora".  I'm not very familiar with red hat based distros.
09:07 maryj joined #evergreen
09:12 RoganH I know that someone(s) use Fedora and I've seen it discussed but I don't recall who off hand.  For some reason Dan Scott
09:12 RoganH 's name jumps to mind.
09:12 RoganH But that might be totally wrong.
09:13 kmlussier RoganH: Yes, it's db
09:13 kmlussier dbs even. :)
09:14 RoganH kmlussier: we both seem to have 's' issues today.
09:14 * kmlussier has issues everyday.
09:19 bshum csharp also seems to dabble in Fedora land.
09:19 bshum But indeed, mainly dbs
09:21 * bshum installed it once or twice for fun
09:27 RoganH bshum: I would say we need to talk about your definition of fun but people who live in glass houses and all that.
09:28 bshum RoganH: You're probably right.
09:28 RoganH bshum: Maybe we all need an intervention.
09:30 kmlussier Anyone who regularly posts in this channel probably has an interesting definition of fun. :)
09:31 RoganH I will conditionally agree with that if we amend it to say, sometimes.  I suspect most of us aren't complete deviants and find some mainstream fun things fun.
09:33 yboston joined #evergreen
09:34 kmlussier RoganH: Agreed
09:44 mtate joined #evergreen
09:47 kmlussier Hmmm...I remember thinking last thing there was something I wanted to be on the developers meeting agenda. I wonder what it was.
09:47 kmlussier That is, last week. Not doing too good of a job of typing this morning.
09:51 mmorgan @coffee kmlussier
09:51 * pinesol_green brews and pours a cup of Kenya Gethembwini, and sends it sliding down the bar to kmlussier
09:54 * bshum wants a cookie.
09:55 kmlussier @dessert bshum
09:55 * pinesol_green grabs some banana split for bshum
09:56 kmlussier bshum: Sorry, I tried.
09:56 RoganH bshum: I made chocolate chip cookies last night but I don't think they'd survive the trip to you.
09:56 kmlussier mmorgan: Thanks!
09:56 bshum @dessert get 1 bshum
09:57 pinesol_green bshum: (dessert get [<channel>] <id>) -- Gets the dessert with id <id> from the dessert database for <channel>. <channel> is only necessary if the message isn't sent in the channel itself.
09:57 bshum Aha!
09:57 kmlussier @dessert 1 bshum
09:57 * pinesol_green grabs some Chocolate Chip Cookies for bshum
09:57 bshum :d
09:57 bshum RoganH: Indeed.
09:58 RoganH I've been doing a lot of cooking this week come to think of it.
10:00 kmlussier @dessert add of jcamins' double-chocolate mint cookies
10:00 pinesol_green kmlussier: Error: You must be registered to use this command. If you are already registered, you must either identify (using the identify command) or add a hostmask matching your current hostmask (using the "hostmask add" command).
10:01 jcamins kmlussier: I made some amazing mint-wasabi chocolate chip cookies over the weekend.
10:02 jeff my brain wanted to add other green things to that, but probably not in a way that my mouth would appreciate.
10:02 jeff mint-wasabi-pistachio, etc.
10:02 kmlussier @dessert add of jcamins' amazing mint-wasabi chocolate chip cookies
10:02 pinesol_green kmlussier: The operation succeeded.  Dessert #28 added.
10:02 kmlussier @dessert 28 [someone]
10:02 * pinesol_green grabs some of jcamins' amazing mint-wasabi chocolate chip cookies for egbuilder
10:02 kmlussier pinesol_green: Stop feeding the bots!
10:03 pinesol_green kmlussier: You keep using that word. I do not think it means what you think it means.
10:03 pinesol_green kmlussier: I am only a bot, please don't think I'm intelligent :)
10:09 jcamins jeff: I was tempted to add green tea, but I fought the urge down.
10:09 dbs Stompro: we stopped saying which version of Fedora because it changes every six months (more or less)
10:10 dbs but go with the most recent stable and you should be good.
10:10 * dbs hasn't given Fedora 21 beta release a shot yet
10:18 mrpeters joined #evergreen
10:33 mrpeters can anyone clarify this notice from an attempt to convert A/T XML to FO?  http://pastie.org/9714575 -- I'm unclear on what position 2:55 is.  my <fo:root> block has layout-master-set, simple-page-master, region-body so I'm not sure what is missing from the XSL sheet
10:35 kmlussier The final tally from bug squashing day - bit.ly/144v9IV. If I missed anybody, let me know.
10:35 mrpeters everyone++ congrats on bug squashing!
10:41 jboyer-isl mrpeters, That message doesn't mean much without the contents of the fo file itself. The last time I was getting something like there wasn't much of anything actually inside the fo:root. It could be caused by lots of different XML validity issues.
10:41 mrpeters jboyer-isl: yeah, i know you and i talked about this recently
10:42 mrpeters i assume you mean the xsl, not the fo right?
10:42 jboyer-isl And I think 2:55 is the second line, 55th character. But I'm not 100% on that.
10:42 mrpeters ah, that would make sense if the .fo file and not the xsl
10:42 mrpeters line 2 in the xsl is the root line
10:43 jboyer-isl No, the fo. The xsl conversion outputs whatever it outputs, but your error message is from the .fo -> .pdf step.
10:43 mrpeters oh yeah, geez...the .fo is totally empty
10:43 jboyer-isl Which is what I was running into. :)
10:44 mrpeters i should talk to rjackson-isl -- im using variations of his stuff that it looks like lyrasis shared
10:44 jboyer-isl The cause of an empty .fo is probably xsl related in the end (or a recent A/T template change that confused the xsl you're using)
10:45 jboyer-isl There are a lot of layers in this stuff, which is why it's such a hassle to track down these kinds of things.
10:45 mrpeters yeah, helps to be looking in the right spot now though
10:45 mrpeters yeah, its a fun puzzle :)
10:45 mrpeters but rewarding when it works
10:47 jwoodard joined #evergreen
10:50 mrpeters helps if you are generating a logicial XML (like for the right date :P)
10:50 mrpeters its not yesterday anymore now is it!
10:51 jboyer-isl The date handling is the first thing I'll be changing when I update that stuff. (ETA: "Someday")
10:52 mrpeters i think rjackson-isl did a pretty good job of that, doesn't his scripting allow you to pass a "days back" number
10:56 jboyer-isl I'm told ESI built that system for us, Bob made some changes but either way it wasn't originally from here.
10:57 jboyer-isl And Days Back is my first issue. Someday we'll be able to just feed it a date directly.
11:09 * jeff yawns
11:09 jeff greetings.
11:10 * kmlussier waves to jeff
11:12 sarabee joined #evergreen
11:15 sbrylander joined #evergreen
11:26 mrpeters blah, xsltproc does not like call numbers with & chars -- need to do a sed to replace with &amp; -- if anyone else ever runs into this:  parser error : EntityRef: expecting ';' <td>CD 781.644 FIO R&B</td>
11:27 bshum Really...
11:27 mrpeters yep
11:27 * bshum checks his print overdues now...
11:28 mrpeters it would just fail to generate the .fo file for me...though i didnt check to see if i got a "partial" .fo file
11:30 mrpeters yeah, so i do think you get a partial .fo file
11:30 mrpeters it just stops when it runs into one of those & characters
11:31 bshum mrpeters: What version of xsltproc is on that server?
11:32 mrpeters good question
11:32 jboyer-isl Marvelous. That's something that should probably be done as part of the A/T template specifically to the call number field, otherwise you'll double-escape ampersands in the rest of the template.
11:32 bshum Hmm
11:32 bshum fwiw, it seems that my call numbers are generated into xml with "&amp;" for call numbers.
11:33 mrpeters 1.1.26-8ubuntu1.3 it appears
11:33 mrpeters intresting, bshum
11:33 bshum So I guess the legacy generate_circ_notices.pl generates the xml output properly.
11:33 bshum Maybe it's as you say an A/T issue?
11:33 mrpeters yeah, could be -- <td>[% circ.target_copy.call_number.label %]</td> is what im using to get the call number
11:33 bshum How are the outputs generated I guess.
11:34 mrpeters ProcessTemplate -- http://pastie.org/9714709
11:34 bshum Aha, okay
11:34 bshum So that's why we haven't noticed that issue yet.
11:34 bshum We're still doing it the old way
11:34 mrpeters yeah, they both work well, im just more comfortable with this method
11:35 mrpeters you can get some MONSTER xsl sheets when you're doing test's all throughout them
11:35 jboyer-isl Ah. mrpeters just wrap that circ.target_copy.call_number.label in helpers.escape_xml() and it will be fine. (but the old notices will stay busted.)
11:35 jboyer-isl In the A/T template, that is.
11:35 mrpeters jboyer-isl: oh, sweet...i can do that
11:35 sandbergja joined #evergreen
11:35 bshum jboyer-isl++
11:35 mrpeters and these are new, so i can just re-run them
11:36 mrpeters im also seeing a lot of empty title/author
11:36 mrpeters wonder if im using dated ways of getting at those too
11:36 jboyer-isl You'll have to reset all of the at.event entries to allow them to re-run. The data in the database is busted at the moment.
11:36 mrpeters yeah, i know how to reset them
11:36 jboyer-isl cool.
11:36 mrpeters have been doing it for a day and a half now :P
11:37 bshum mrpeters: Maybe they're pre-cats and you're asking for title data that doesn't exist
11:37 mrpeters yes, that is always possible
11:37 bshum Or again, maybe new helper functions
11:38 mrpeters they're all lower case, looks kind of tacky
11:38 jboyer-isl Oh, lucky us. Our templates already have that cleanup func sprinkled around. I was afraid I had another cleanup job to do.
11:38 mrpeters the helpers.escape_xml() jboyer-isl?
11:38 jboyer-isl Yeah.
11:39 mrpeters nice!
11:39 jboyer-isl At least in the ones I've checked. That's how I knew what to tell you.
11:39 mrpeters what are you guys using for the title/author these days?
11:39 mrpeters simple_record.title?
11:39 bshum No
11:39 mrpeters rather, circ.target_copy.call_number​.record.simple_record.title to be exact
11:39 bshum I think that's different now
11:40 vlewis joined #evergreen
11:40 jboyer-isl No, There's also a helpers.get_copy_bib_basics that appears to get things in a nicer format. I'll paste part of our 14 day notice real quick.
11:40 mrpeters this is a 2.3.5 server, fwiw
11:40 mrpeters so maybe those new helpers dont exist yet in this version
11:40 bshum Possible.
11:41 pastebot "jboyer-isl" at 64.57.241.14 pasted "Title Info from Copies" (16 lines) at http://paste.evergreen-ils.org/14
11:41 jboyer-isl I haven't touched these things since 2.2
11:42 mrpeters ok cool
11:43 mrpeters oh yeah this looks good, dont want to run into that same & issue anyways
11:43 jeff_ joined #evergreen
11:49 kmlussier berick++ #Throwing your hat into the ring
11:49 * kmlussier just looked at the dev meeting agenda. :)
11:49 bshum berick++
11:51 jboyer-isl agreed,
11:51 jboyer-isl berick++
11:52 * kmlussier notes that OPW announcements are scheduled to be made at 2 p.m. today, just in time for the dev meeting.
11:59 bshum GAHHH, parts--
12:00 * bshum curls up into the corner and weeps
12:05 kmlussier bshum: OK, I'll bite. What's happened?
12:10 chatley joined #evergreen
12:10 * mmorgan hands bshum a tissue
12:11 kmlussier And maybe some chocolate?
12:11 kmlussier @dessert bshum
12:11 * pinesol_green grabs some wild Alaskan rhubarb pie for bshum
12:11 bshum Sorry I moved on to my next topic.
12:11 bshum I'm in a circulation meeting with our libraries and staff.
12:14 kmlussier So maybe if we can identify what the specific problems are with parts, we can come up with potential solutions rather than throwing negative karma at them all the time. This is an open source system after all. :)
12:14 bshum kmlussier: Logic + parts does not compute for me today
12:16 krvmga joined #evergreen
12:17 krvmga i am puzzled by the results i'm getting in a search.
12:17 krvmga http://bark.cwmars.org/eg/opac/results?​query=frozen&amp;qtype=keyword&amp;fg%3​Aformat_filters=10&amp;locg=1&amp;sort=
12:17 bshum And I'll throw negative karma at parts whenever I feel like it
12:17 krvmga why is the 2010 DVD showing up first on the list?
12:17 * bshum grumbles
12:18 krvmga originally, i thought it was over record density. then the catalogers made the record less dense. it still shows up first.
12:18 krvmga any thoughts would be appreciated.
12:21 bshum krvmga: Since this is a keyword search, do you guys have any indexing for stuff.  I'm thinking of things like title weighting
12:21 kmlussier bshum: Sure, I know you will. And you know I'll throw positive karma whenever I feel like it. :) I'm just trying to think of a problem-solving approach that might make everyone's life better in the long run. But I'll leave you to your meeting now.
12:22 krvmga bshum: we do have title weighting.
12:22 kmlussier But the weighting would apply for both DVDs I would think.
12:23 bshum It should
12:23 krvmga kmlussier: yes, that's right. but, in addition, it doesn't change the result if you make the search a title search instead of a keyword search.
12:23 bshum But I'm wondering if there's more weighting for one or the other based on more factors.
12:23 bshum Or it's ordering by that, but given their relatively equal looking weight
12:23 krvmga bshum: i would have thought that the item with the latest active date would show up first
12:23 bshum Just based on "Frozen" being the only thing in 245a
12:23 bshum That's not always true.
12:25 kmlussier krvmga: Have you looked in your database tables to see what the title indexing looks like for those records?
12:25 bshum Maybe it's the rest of the title
12:25 bshum The subtitle, I mean
12:25 krvmga kmlussier: we're a little hindered from that atm
12:25 bshum C: Anchor Bay
12:25 bshum vs.
12:25 bshum c
12:25 bshum Walt Disney
12:26 kmlussier I was wondering if the presence of a 246 in the more recent record affected things.
12:26 bshum So with all else being equal, it's ordering like that
12:26 bshum Hmm
12:26 krvmga bshum: you mean, it's ordering alphabetically there?
12:26 bshum krvmga: I don't know, I'm just hypothesizing
12:27 bshum I'd be curious to know what the title entry was
12:27 bshum For the two bibs
12:27 mmorgan krvmga: same dvd shows up first in our catalog, too: http://evergreen.noblenet.org/eg/opa​c/results?query=frozen&amp;qtype=tit​le&amp;fg%3Aadvanced=12&amp;locg=1
12:27 kmlussier krvmga: It really helps to view those entries in the database. Because then you can see which words are being indexed.
12:28 krvmga mmorgan: thanks. that's good information.
12:29 bshum It just seems that all else being equal, the fact that the rest of the titles order by name as I would expect
12:30 kmlussier I didn't think there was any ordering by name. I thought pubdate was the tiebreaker in relevance ranking.
12:30 krvmga kmlussier: that's what i thought, too.
12:31 dbs It may be that one of the "Frozen" entries isn't indexed in your keywords (130?), and the 2014 film record has more indexed keywords, thus the 2010 film record is more relevant
12:32 jihpringle joined #evergreen
12:32 krvmga dbs: hmmmmm...that deserves looking into.
12:32 dbs as mmorgan says, SELECT * FROM metabib.keyword_field_entry WHERE source IN (2638564, 3254422) would probably help a lot
12:33 mmorgan so, mine was a title search...
12:33 mmorgan and I did a similar query
12:34 krvmga we had some database destruction over here on Friday and things aren't completely back to normal yet. i can look in the database when my access is restored.
12:34 mmorgan trying to find a pretty way to share the results
12:34 nhilton joined #evergreen
12:34 dbs mmorgan: pastebin.com ?
12:37 dbs SELECT * FROM metabib.record_attr WHERE id IN (2638564, 3254422); would be useful too, as the 260 $c has dates like [2010] / [2014] and maybe the square brackets are throwing off the date tie-breaker.
12:37 mmorgan using pgadmin, so the gui output doesn't paste well, here's the result: http://screencast.com/t/ISz7pTMto7
12:39 dbs yeah, "Disney Frozen" would be less relevant than just "Frozen", makes sense for the title search
12:40 krvmga dbs: you think that's the reason?
12:41 * kmlussier concurs
12:41 bshum Aha
12:41 krvmga if so, then fixing the 246 would/should fix the results
12:42 krvmga we'll give it a shot.
12:42 * kmlussier notes that an activity metric project should help with searches like that one.
12:43 Dyrcona joined #evergreen
12:44 * kmlussier also notes that the FedEx man just arrived with mint chips that she will be using in her own mint chocolate cookies.
12:44 kmlussier jcamins ^ ^
12:44 kmlussier krvmga: And then when somebody does a title search for Disney Frozen?
12:45 krvmga kmlussier: i'm guessing they might get nothing then
12:45 kmlussier I'm just thinking there was a reason the 246 field was entered that way.
12:46 krvmga kmlussier: i think it still might be worth experimenting just to see if that, in fact, is the cause.
12:49 krvmga kmlussier: because, if we determine that's it, then data could be put in a 246 for the 2010 DVD (say, "Anchor Bay Frozen" or something like that)
12:58 sarabee joined #evergreen
13:10 sandbergja joined #evergreen
13:18 jcamins kmlussier: yay!
13:31 DPearl joined #evergreen
13:47 nhilton_ joined #evergreen
13:59 berick now taking nominations for meeting Grand Poobah
13:59 * kmlussier would volunteer if she weren't in the middle of writing a blog post. :(
14:02 bshum I can do it.
14:02 bshum A little late but I can start us in a sec
14:02 berick bshum++
14:02 bshum #startmeeting 2014-11-12 - Developer Meeting
14:02 pinesol_green Meeting started Wed Nov 12 14:02:53 2014 US/Eastern.  The chair is bshum. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:02 pinesol_green Useful Commands: #action #agreed #help #info #idea #link #topic.
14:02 pinesol_green The meeting name has been set to '2014_11_12___developer_meeting'
14:02 bshum #topic Introductions
14:03 bshum #info bshum = Ben Shum, Bibliomation
14:03 phasefx_ #info phasefx_ = Jason Etheridge, ESI
14:03 DPearl #info DPearl = Dan Pearl, C/W MARS
14:03 kmlussier bshum++
14:03 bshum Please feel free to introduce yourselves, I'll dig up the agenda
14:03 bshum #link http://wiki.evergreen-ils.org/dok​u.php?id=dev:meetings:2014-11-12
14:03 kmlussier #info kmlussier is Kathy Lussier, MassLNC
14:03 berick #info berick Bill Erickson, KCLS
14:03 dbs #info dbs = Dan Scott, Laurentian University
14:04 bshum Bit slim looking at the moment, but I'm happy to take on any final discussion topics as we go
14:04 remingtron #info remingtron is Remington Steed, Hekman Library (Calvin College)
14:04 eeevil #info eeevil is Mike Rylander, Equinox
14:05 Stompro #info stompro is Josh Stompro, LARL
14:07 bshum Alrighty, as folks show up, please feel free to announce your presence.  We'll move on through the agenda...
14:07 remingtron bshum: I don't see past action items on the agenda
14:07 bshum Though of course
14:07 bshum Yeah I just noticed that :)
14:07 bshum Okay, based on the past meeting
14:07 bshum #topic Past action items
14:08 bshum #info dbwells to update Conditional Negative Balances bug 1198465 with links to new branches, etc.
14:08 pinesol_green Launchpad bug 1198465 in Evergreen "Support for Conditional Negative Balances" (affected: 14, heat: 62) [Wishlist,Confirmed] https://launchpad.net/bugs/1198465
14:08 bshum I saw that dbwells put some new comments on that bug
14:08 remingtron dbwells is out today, but I might be able to clarify any questions about his latest bug comment
14:09 gmcharlt #info gmcharlt is Galen Charlton, ESI
14:09 bshum I know I need more time to digest things on that
14:09 * dbs disappears to do some hardware stuff, grr
14:10 bshum Let's defer on that subject till we get some more time to read through and respond to the latest?
14:10 kmlussier I plan to test it soon, but I haven't had a chance look closely enough to come up with any questions yet.
14:10 bshum Though I think for the action item, it's settled since it looks like dbwells did update the bug with new details.
14:10 bshum Next past item
14:10 bshum #info gmcharlt to release OpenSRF 2.4 when ready
14:11 bshum Which actually links us to the OpenSRF release topic
14:11 gmcharlt #action gmcharlt will release OpenSRF 2.4.0 on 13 November
14:11 bshum gmcharlt++
14:11 bshum Okay, last item was
14:11 bshum #info kmlussier to schedule another Bug Squashing Day
14:12 bshum Which is done and was done
14:12 bshum Since we held that day earlier this week
14:12 kmlussier Yes indeed. I should have a wrap-up blog post written by the end of the week.
14:12 bshum kmlussier++
14:12 berick kmlussier++
14:12 DPearl kmlussier++
14:12 gmcharlt kmlussier++
14:12 bshum #action kmlussier to have results of second Bug Squashing Day posted to blog by end of week.
14:13 bshum okay
14:13 bshum Next topic
14:13 bshum #topic Release info
14:13 bshum We already covered OpenSRF latest.  Is there anything else we need to say about OpenSRF?
14:14 bshum ... and nope, everyone is just too excited about the next subject
14:14 bshum Quick info insert
14:15 bshum #info Security releases for Evergreen have been released, see http://evergreen-ils.org/security-rele​ases-evergreen-2-7-1-2-6-4-and-2-5-8/
14:15 bshum #topic Next Evergreen Release Manager
14:16 bshum So on the agenda, we see "berick throws his hat in the ring."
14:17 bshum Comments, thoughts?
14:17 bshum Other hats?
14:17 * berick confirms he in fact wrote that
14:17 gmcharlt berick: inquiring minds want to know... bowler, top hat, or fez?
14:18 berick gmcharlt: http://www.clownantics.com/​images/products/a2020r.jpg
14:18 gmcharlt berick++
14:18 phasefx_ 20 gallon?
14:18 berick phasefx_: heh, sounds about right
14:19 berick quick note, if I'm elected RM, my time for contributing to the OPW project will be diminished.
14:20 berick seems like we have that generally covered, though
14:20 gmcharlt I think we have enough devs who have previously expressed willingness to mentor to compensate
14:20 kmlussier berick: There are two other mentors for that project, so I think OPW will be fine.
14:20 * berick nods
14:21 bshum Okay, so next steps, do we want to go through a formal list vote (with some more info on what might be the vision of 2.next)?
14:21 bshum Or should we just vote berick in now ;)
14:22 kmlussier I'm okay with voting berick now, but I would still like to see a post to the list on objectives, vision, etc.
14:22 * gmcharlt agrees
14:23 bshum Alrighty
14:24 nhilton joined #evergreen
14:24 bshum #startvote Vote to show support of berick as our 2.next Release Manager
14:24 pinesol_green Unable to parse vote topic and options.
14:25 bshum Oh, gap
14:25 gmcharlt #startvote Foo? Option1, Option2
14:25 bshum #startvote Vote to show support of berick as our 2.next Release Manager? Yes, No
14:25 pinesol_green Begin voting on: Vote to show support of berick as our 2.next Release Manager? Valid vote options are Yes, No.
14:25 pinesol_green Vote using '#vote OPTION'. Only your last vote counts.
14:25 gmcharlt #vote Yes
14:25 bshum #vote Yes
14:25 Stompro #vote yes
14:25 phasefx_ #vote Yes
14:25 Dyrcona #vote Yes
14:25 jeff #vote Yes
14:25 jeff (hi)
14:25 kmlussier #vote Yes
14:25 eeevil #vote yes
14:26 DPearl #vote Yes
14:27 bshum Okay
14:27 bshum #endvote
14:27 pinesol_green Voted on "Vote to show support of berick as our 2.next Release Manager?" Results are
14:27 pinesol_green Yes (9): kmlussier, DPearl, jeff, Dyrcona, gmcharlt, Stompro, phasefx_, bshum, eeevil
14:27 bshum That's good enough for me.  Thanks berick for volunteering to steer the ship!
14:27 gmcharlt berick++
14:27 bshum #info berick is the next release manager for Evergreen 2.next
14:28 kmlussier Hooray!
14:28 DPearl berick++
14:28 bshum Your first action item is to write something up for the lists
14:28 Dyrcona berick++
14:28 berick thanks for the votes.  i'll send a note to the lists..
14:28 bshum #action berick to write about his ideas for 2.next to the lists
14:28 bshum And also, I affirm that I'll be helping out as always during the next cycle to help review and help with the release process.
14:29 berick bshum++
14:29 gmcharlt bshum++
14:29 bshum Also, 2.8 or 3.0?  (the eternal struggle)
14:29 bshum These are questions I'll be curious to see addressed as we move forward.
14:29 * gmcharlt settles on the absolutist position that I will be happy if it is called either 2.8 or 3.0
14:30 gmcharlt SO THERE!
14:30 bshum Heh
14:30 berick version 37 it is, then
14:30 gmcharlt :)
14:30 bshum Okay, if we're fine with this topic, let's move on then :)
14:31 bshum #topic New Business: Outreach Program for Women
14:31 * bshum passes the mic to kmlussier
14:31 kmlussier OPW just made the announcement about 30 minutes ago, and I just made an announcement to the community blog.
14:31 kmlussier #link http://evergreen-ils.org/welcome-julia-t​o-the-evergreen-opw-internship-program/
14:31 kmlussier Julia Lima will be working as the intern for Evergreen. She'll be working on the UI style guide project.
14:32 kmlussier berick, dbwells, and graced will be the mentors. But, as berick mentioned above, a lot of that might fall to graced and dbwells and to others in the community.
14:33 kmlussier Julia shared some great suggestions for UI improvement at http://wiki.evergreen-ils.org/dok​u.php?id=opw:ui_suggest:julialima
14:33 kmlussier I'm really excited about the project.
14:34 bshum Cool, cool
14:35 kmlussier Also, many thanks to everyone who helped out with the project during the application period, especially everyone who volunteered to be mentors.
14:35 bshum Any questions or comments for kmlussier?
14:35 bshum berick++ dbwells++ graced++ kmlussier++
14:35 bshum And everyone++
14:35 bshum :)
14:35 kmlussier I also added something to the agenda that came up in conversation during the application review when we talked about ways to improve the application period if we decide to do a similar project again.
14:36 phasefx_ Julia++
14:36 kmlussier It really was better as a developer community discussion than an OPW discussion. Basically, it would be easier to encourage new people to contribute to Evergreen if the installation process were easier.
14:37 bshum "easier" in the sense of fewer steps, less manual from source building?
14:38 bshum Or what else do we mean
14:38 kmlussier Well, seeing as how I've never installed Evergreen, I throw that question out for others.
14:38 * gmcharlt tosses out a couple thoughts
14:39 kmlussier I do think that installing Evergreen presents a big hurdle for somebody trying to get their first code contribution in. I don't know what we can do to make it easier.
14:39 Stompro The install docs could include various methods, such as the install script that I've heard about, and the Pines repo method.  How would you all feel to having multiple install methods.
14:39 * kmlussier also notes that none of the coding applicants for OPW successfully made a code contribution to the project.
14:39 gmcharlt 1. being able to run through the installer is kinda necessary for doing dev -- maybe we could throw people at the problem -- i.e., an informal system for partnering with folks tackling it
14:40 kmlussier Stompro: I added the install script to the OPW wiki page at one point, but I know dbs had suggested adding it to the readme.
14:40 gmcharlt 2. as a more techie route, the Koha ecosystem has tools for converting a package install to a variant that can grab code from a Git checkout
14:40 gmcharlt kinda a best of both worlds setup
14:40 gmcharlt that might be worth spending cycles on replicating
14:41 remingtron #link http://wiki.evergreen-ils.org/doku.php​?id=server_installation:semi_automated
14:41 remingtron that's a wiki page of all the installer scripts I'd heard of in the community
14:42 kmlussier I don't think berick's script is there.
14:42 Dyrcona When we're talking packages, what distro(s)?
14:43 Dyrcona We could always share the scripts that tsbere developed for the MassLNC sandboxes. Those might prove helpful.
14:43 * tsbere thought those were already out there
14:43 kmlussier tsbere: I added those to the OPW wiki too.
14:44 Dyrcona OK. I didn't know.
14:44 Christineb joined #evergreen
14:44 kmlussier I had forgotten about the page that remingtron just linked to. Is that fairly up to date?
14:44 Dyrcona It points at something of mine that no longer exists.
14:44 kmlussier The OPW wiki isn't an ideal place to share these scripts. If we think they might be useful to people, then maybe adding them to the install docs or the readme, as dbs previously suggested, is a good idea.
14:45 * Dyrcona puts curmudgeon hat on.
14:45 Dyrcona I think the current installation procedure is a good test for potential developers.
14:46 Dyrcona If you can't follow a README, do a manuals installation, and troubleshoot issues, you're going to have a very hard time later figuring out why your code broke something.
14:46 kmlussier Dyrcona: The curmudgeon hat suits you. :)
14:47 Stompro Dyrcona: I understand your view, but if people give up during the install phase, then there is never the possibility of them contributing at all.
14:47 kmlussier Like I've said, I've never done an installation, so I feel out of my depth in this discussion. But when you look at a project like the responsive design one, it seems like you shouldn't have to be able to do a manual install to make a valuable contribution.
14:48 remingtron kmlussier: you haven't had to do a manual install to make a valuable contribution!
14:48 gmcharlt one nuance is that "developer" does not refer to just single, unitary skillset that could make useful code-level contributions to Evergreen
14:48 berick remingtron++
14:49 Dyrcona All good points, and I've maybe limited my view to the backend too much.
14:49 gmcharlt so it should be possible for (say) a JavaScript person or a web develoepr to be able to jump in without having to care about the backend
14:50 gmcharlt that said, I don't entirely disagree with Dyrcona either; being able to follow install instructions is a useful skill
14:50 kmlussier Going beyond contributions, another question is does the install process impeded adoption of Evergreen?
14:50 * Stompro just added phasefx's wheezy_installer to the "semi_automated" page.  And removed Dyrcona's 404 link.
14:50 kmlussier s/impeded/impede
14:51 kmlussier It was a light agenda, so I figured it was a good time to raise weighty questions. :)
14:51 phasefx_ Stompro: more berick's than mine, but cool deal
14:51 Dyrcona Going beyond Evergreen, installation impedes the adoption of anything.
14:51 gmcharlt I think separating the question of installation for code-level contributors vs. production use would be a good idea, though
14:51 * Dyrcona agrees with gmcharlt.
14:51 kmlussier OK, I withdraw the question then.
14:52 krvmga just a note back to the list on the "Frozen" search issue from early today: fiddling with the 246 did nothing to change the display order; the older DVD still appears first in returns.
14:52 Dyrcona Developers of any project typically have to follow different installation methods from regular users.
14:52 bshum krvmga: We're in the midst of a dev meeting, give us say another 8 minutes.
14:52 * krvmga says sorry and slinks off.
14:53 bshum Okay
14:54 bshum So since we're coming up on good time chatting on this, I'd like to ask for some actionable items to help move us in new directions.
14:54 bshum From the discussion, I think we can summarize that installation could be "easier" (for lack of a more precise term)
14:54 bshum Does anyone want to take some action items to investigate or help poke on this topic further?
14:54 sarabee joined #evergreen
14:55 * gmcharlt is interest, but cannot promise any cycles before 2015
14:55 gmcharlt *interested
14:56 bshum I can define it more generically if we're not ready to commit to anything.
14:56 bshum Just adding something in the notes for now
14:56 Dyrcona I know! Let's form a committee!
14:56 bshum #help Looking for input and ideas to make the installation process easier on future developers and contributors.
14:56 kmlussier I can see it being a long-term action item. :)
14:56 Dyrcona Oh wait.... librarian hat slipped on there for a moment.
14:57 gmcharlt kmlussier: that wouldn't be any different ... and to be fair to the project, it actually has gotten TONS better by many accounts
14:57 kmlussier Dyrcona: Put the curmudgeon hat back on!
14:57 bshum I'm curious to see if there's more we can learn from our Koha neighbors, i.e. tools that gmcharlt alluded to.
14:57 kmlussier gmcharlt: That's good to hear.
14:57 kmlussier FWIW, I've been planning for a while to try a manual install over the weekend. Just for "fun." :)
14:58 bshum How about this, then, so that we don't forget about it
14:58 gmcharlt kmlussier++ # please take good notes!
14:58 bshum If berick is fine with it, I think maybe we can consider this to be a potential goal for our next release.
14:58 bshum To look at finding ways of making the process "easier"
14:58 * berick likes it
14:58 gmcharlt especially since once somebody has done their first install, they start to stop perceiving the rough points
14:59 bshum Gives us a soft target (through next year) and we can keep working on it then.
14:59 gmcharlt +1
14:59 kmlussier gmcharlt: I think Stompro has been helpful in that respect.
15:00 bshum Okay
15:00 bshum We're at the one hour mark (more or less) so I'd like to leave this topic for now and finish with one little detail before we close.
15:01 bshum #info Look at ways of improving installation process during the next release cycle as a potential 2.next goal.
15:01 bshum #topic Release Maintainers
15:01 bshum gmcharlt asked about this and so I just wanted to make a note on the release maintaining.
15:01 bshum For 2.7, I'm happy to continue to help coordinate and cut new maintenance releases for that series.
15:02 gmcharlt bshum++
15:02 bshum For 2.6, dbwells can speak on that later, but presumably he's still on board there.
15:03 bshum And 2.5 has ended maintenance releases unless there are further security backports needed.
15:03 bshum #info 2.7 series release maintainer will be bshum
15:04 bshum Okay
15:04 bshum Any other topics for discussion before we adjourn today?
15:04 gmcharlt #info 2.5 series will receive security updates only
15:04 bshum gmcharlt: Thanks :)
15:04 gmcharlt :)
15:05 bshum Okay, thanks to berick for keeping us on track with organizing the meetings.  We okay with setting up the next meeting before the holidays?
15:05 bshum (and also for being our next intrepid leader)
15:05 kmlussier Okay with me
15:05 gmcharlt +1
15:06 remingtron +1
15:06 bshum Alrighty then.  Thanks for your attention and participation.  Enjoy the rest of the week.  And thus this meeting ends, but the discussion goes on!
15:06 bshum #endmeeting
15:06 pinesol_green Meeting ended Wed Nov 12 15:06:56 2014 US/Eastern.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
15:06 pinesol_green Minutes:        http://evergreen-ils.org/meetings/evergr​een/2014/evergreen.2014-11-12-14.02.html
15:06 pinesol_green Minutes (text): http://evergreen-ils.org/meetings/evergr​een/2014/evergreen.2014-11-12-14.02.txt
15:06 pinesol_green Log:            http://evergreen-ils.org/meetings/evergree​n/2014/evergreen.2014-11-12-14.02.log.html
15:07 kmlussier bshum++
15:07 berick bshum++
15:07 gmcharlt bshum++
15:10 Christineb left #evergreen
15:15 kmlussier krvmga: When I look at http://bark.cwmars.org/eg/opac/record/3254422?qu​ery=frozen%20-kjklfjdkaljfd;qtype=title;fg%3Afor​mat_filters=10;locg=1;expand=marchtml#marchtml, I still see a 246 with Disney Frozen
15:16 krvmga kmlussier: yes, jschrader added other 246 fields without "Disney" in them
15:17 kmlussier I would leave one 246 there that just says Frozen as a better test.
15:18 bshum parts++
15:18 kmlussier Heh...I was going to wait until you were on the road to do that.
15:18 krvmga kmlussier: she's not in the office today. when i see her next, we'll try and see.
15:19 bshum Or remove all 246 entirely and see that too
15:19 krvmga bshum: another good thought
15:20 bshum "Parameter 'Value | ISBN | UPC' not specified"
15:20 bshum krvmga: It looks like you've got an added content problem...
15:21 bshum ?
15:21 kmlussier bshum: That's a bug that was already reported in LP
15:21 bshum Aha
15:21 krvmga bshum: yes, we have added content problems. i'm trying to work with EBSCO and see if there's anything either they or we need to do.
15:21 kmlussier https://bugs.launchpad.net/evergreen/+bug/1318029
15:21 pinesol_green Launchpad bug 1318029 in Evergreen "Content Cafe can no longer retrieve cover images by UPC" (affected: 1, heat: 10) [Medium,New] - Assigned to Jeff Godin (jgodin)
15:22 kmlussier krvmga: NOBLE reverted the changes in the commit I referenced in my original report. IIRC, it fixed the problem
15:22 kmlussier krvmga: But there's also a patch from berick on that bug you might want to try.
15:22 krvmga kmlussier: am i remembering right that tsbere wrote some code to fix this?
15:22 kmlussier krvmga: that's in 2.7. I don't think you want to wait that long.
15:22 krvmga ah, no, i must have been thinking of berick.
15:23 krvmga kmlussier: so tsbere's code is in (or will be in) master?
15:23 dbs #vote yes -- albeit super late
15:23 * berick chuckles
15:23 krvmga kmlussier: if berick's code will not be in master, there is reluctance to use it.
15:24 krvmga not on my part but we have a policy here now
15:24 kmlussier OK, but reverting that change that I mentioned in the first description is a simple tpac change.
15:24 krvmga kmlussier; hmmmm, i thought i did that. i might be misremembering
15:26 kmlussier krvmga: The fix from tsbere is at https://bugs.launchpad.net/evergreen/+bug/1347805
15:26 pinesol_green Launchpad bug 1347805 in Evergreen "Content Cafe module should use an XML lookup method" (affected: 2, heat: 10) [Wishlist,Fix released]
15:26 kmlussier I have no idea how easy/hard it is to backport.
15:26 krvmga kmlussier: i'll look at it.
15:26 krvmga thx
15:26 Dyrcona tsbere's code for ContentCafe are in master.
15:27 * Dyrcona should put on his grammar hat. :)
15:27 kmlussier Dyrcona has many hats
15:27 Dyrcona kmlussier: Don't we all?
15:27 krvmga we have been wondering if ContentCafe is the best solution for us.
15:27 tsbere backporting should be fairly easy. If you run into conflicts in ContentCafe.pm overwrite it with the new version entirely. ;)
15:28 krvmga tsbere: i'll run it up the flagpole and see if i can get anyone to salute
15:28 kmlussier krvmga: I think it's hard to make a decision like that until you fix the existing problems.
15:29 krvmga kmlussier: i've been pounding on EBSCO's door for weeks and all i get is "we've referred it to our developers"
15:29 Dyrcona lp 1302207 might be relevant.
15:29 pinesol_green Launchpad bug 1302207 in Evergreen "Syndetics broken cover image retrieval" (affected: 3, heat: 18) [Medium,Fix released] https://launchpad.net/bugs/1302207
15:29 Dyrcona It doesn't just affect Syndetics, though that is how it was reported.
15:30 krvmga ok, gotta run. see all tomorrow.
15:46 buzzy joined #evergreen
16:04 nhilton joined #evergreen
16:34 nhilton_ joined #evergreen
16:50 nhilton joined #evergreen
16:51 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
17:00 mdriscoll1 left #evergreen
17:02 mtcarlson joined #evergreen
17:17 mmorgan left #evergreen
17:27 kmlussier @karma parts
17:27 pinesol_green kmlussier: Karma for "parts" has been increased 27 times and decreased 27 times for a total karma of 0.
17:28 kmlussier parts++
17:28 berick heh
17:28 kmlussier Shhhh...
18:58 buzzy joined #evergreen
20:13 dcook joined #evergreen
20:29 buzzy joined #evergreen
20:47 sbrylander joined #evergreen
21:04 tsbere parts-- # Don't tell Kathy. ;)
21:18 jeff :-)
23:05 sarabee joined #evergreen
23:07 artunit_ joined #evergreen

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