Evergreen ILS Website

IRC log for #evergreen, 2013-09-26

| 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
01:05 Dyrcona joined #evergreen
01:05 Dyrcona Insomnia is a many splintered thing.
01:06 Dyrcona @later tell bshum It works. The missing 4 records had no copies. If I don't use the --items option I get the full 8,755 bibs in my test.
01:06 pinesol_green Dyrcona: The operation succeeded.
01:07 Dyrcona @later tell bshum It might work for immediate purposes, but I don't like it. I'm going to redesign it as a real module, probably under OpenILS::Utils.
01:07 pinesol_green Dyrcona: The operation succeeded.
01:12 Dyrcona @later tell tsbere Building an array from the Fieldmapper's properties method doesn't work because properties isn't guaranteed to return the field names in the proper order, so you have to create a new, empty object and fill in the field from the hash.
01:12 pinesol_green Dyrcona: The operation succeeded.
01:12 Dyrcona @later tell MyBoss I'm taking off the month of November. :p
01:12 pinesol_green Dyrcona: The operation succeeded.
01:15 paxed braaargh
01:16 paxed Open-ILS/src/templates/opac/​parts/myopac/prefs_base.tt2:       <select name="acct_prefs_url" aria-label="Select a preference page" Open-ILS/src/templates/opac/parts/myopac/base.tt2:         <select name="acct_url" aria-label="Select an account page"
01:16 paxed i18n i18n i18n i18n
01:24 Dyrcona Question is: Will anything break if properties is made to return the field names in the proper order?
01:25 Dyrcona Answer: Not bloody likely.
01:36 Mark__T joined #evergreen
01:50 paxed @later tell kmlussier i18n in Open-ILS/src/templates/opac/​parts/myopac/prefs_base.tt2 and base.tt2 - aria-label and select box text are hard-coded...
01:50 pinesol_green paxed: The operation succeeded.
02:01 Dyrcona Heh. The rent is too damned high, and the export is too damned slow.
02:13 Dyrcona And the i18n is too damned hardcoded?
02:14 zxiiro joined #evergreen
04:44 RBecker joined #evergreen
04:58 RBecker joined #evergreen
07:21 Bmagic joined #evergreen
07:33 timlaptop joined #evergreen
07:50 jboyer-isl joined #evergreen
08:11 kmlussier joined #evergreen
08:12 jboyer-isl Is there a timeline for point releases, or are they still "as needed?" I know the majors are on a schedule but I couldn't see a yay or nay anywhere about the minors.
08:13 kmlussier jboyer-isl: My recollection is once a month.
08:14 kmlussier According to the developer's calendar, it's supposed to happen on the 18th of the month.
08:17 kmlussier paxed: I'll take a look at fixing the select menus later in the day.
08:17 kmlussier I probably should write up a release notes entry for the responsive tpac work too.
08:26 akilsdonk_ joined #evergreen
08:35 Dyrcona joined #evergreen
08:36 Dyrcona Any laters for me?
08:36 berick jboyer-isl: what kmlussier said. 2.3.11 was delayed by the hackaway.  going to cut it today
08:37 Dyrcona kmlussier: Do you need my dev vm today?
08:39 kmlussier Dyrcona: That's right. You're rebuilding the VM today. To be honest, I'm really busy today. Do you think it will be ready tomorrow?
08:40 Shae joined #evergreen
08:42 Dyrcona kmlussier: Not tomorrow. I want to load our production branch for a final migration test.
08:45 kmlussier Dyrcona: OK, don't worry about it then. I'm good. :)
08:46 Dyrcona All righty, then....
08:46 Dyrcona :)
08:56 pinesol_green [evergreen|Ben Shum] TPAC: Add format icon back to record details - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=64e888e>
08:58 mmorgan joined #evergreen
09:00 mrpeters joined #evergreen
09:03 ericar joined #evergreen
09:10 hopkinsju joined #evergreen
09:14 kmlussier dbwells: Just as a point of information for bug 1211473. I tested it yesterday and it looked pretty good to me. I was going to add a sign-off to csharp's sign-off, but I ran out of time.
09:14 pinesol_green Launchpad bug 1211473 in Evergreen "Setting to disable payment by patron credit" (affected: 1, heat: 6) [Wishlist,New] https://launchpad.net/bugs/1211473 - Assigned to Dan Wells (dbw2)
09:15 dbwells kmlussier: thanks for the verbal sign-off, will push shortly
09:15 dbwells kmlussier++
09:23 jboyer-isl joined #evergreen
09:32 yboston joined #evergreen
09:50 dbwells grabbing 0835
09:52 mllewellyn joined #evergreen
09:55 jbfink joined #evergreen
09:56 pinesol_green [evergreen|Bill Erickson] LP1211473 YAOUS : disable patron credit payments - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=46629e2>
09:56 pinesol_green [evergreen|Dan Wells] Stamping 'patron credit disable' setting - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=a64be32>
09:58 zxiiro joined #evergreen
10:08 berick we should call the web printing shim the Spinals Tap
10:08 bshum +1
10:08 senator *rim shot*
10:10 _bott_ does it go to 11?
10:12 jeff running old xulrunner over an ssh x forwarding from ec2 gives a whole new meaning to slow.
10:12 jeff the slow goes to 11.
10:12 Dyrcona jeff++
10:13 * Dyrcona LOL'd all over himself.
10:15 * jeff attempts to make things worse by introducing vnc to the equation
10:15 jeff into the equation, perhaps.
10:15 jeff "vnc, meet equation. equation, this is vnc."
10:19 hopkinsju @ircquote berick: we should call the web printing shim the Spinals Tap
10:19 pinesol_green hopkinsju: Error: You don't have the owner capability. If you think that you should have this capability, be sure that you are identified before trying again. The 'whoami' command can tell you if you're identified.
10:20 phasefx isn't there a known bug with supercat returning deleted items?  I can't find it.  I assume that would affect simple2zoom with Evergreen
10:20 jeff i believe there was one and it may have been fixed.
10:20 jeff could still be lingering similar bugs.
10:21 * phasefx can't stand launchpad search :)
10:21 * phasefx digs in gmail
10:22 * phasefx digs in commit log
10:26 * Dyrcona thinks digging through commits would be easier if we used merges instead of cherry-picks with individual signoffs.
10:27 Dyrcona It would certainly make it easier to check if a given commit was applied to a given branch.
10:27 phasefx for reference, re: deleted holdings, 37b1dfec9a1fcdf20a9192f41abb207625b1ce0a
10:27 pinesol_green [evergreen|Dan Scott] Hide OPAC-invisible holdings from SRU/Z39.50 - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=37b1dfe>
10:32 mcooper joined #evergreen
10:33 krvmga joined #evergreen
10:45 akilsdonk_ joined #evergreen
10:49 kbutler joined #evergreen
10:58 kmlussier joined #evergreen
11:04 jeff Dyrcona: I know that we discussed that briefly at the hackaway. I'd like to see some more discussion either here or on-list. I don't know that I remember all of the original reasons for the approach we've been using.
11:05 Dyrcona I suggest you jump into #git here on freenode and say "We use cherry-picks. Why is that bad?"
11:05 * jeff grins
11:06 Dyrcona You are basically rewriting history. You can't back out a series of commits easily if there is a problem.
11:06 Dyrcona You can't tell if a single commit exists in multiple branches because every time you signoff and cherry-pick the hash changes.
11:07 Dyrcona The best practice according to all the documentation and consensus in #git is use merges. If you want to signoff, then sign off the merge commit.
11:09 gmcharlt we do want a signal that the seris has been merged
11:10 gmcharlt so signn-offs (or perhaps Reviewed-By:) for the merge commits
11:10 gmcharlt and sign-offs on the individual patches when submitted to signify the DCO?
11:10 Dyrcona gmcharlt: My suggestion is the original author signs off each commit in their branch.
11:10 jeff single sign-off on individual commits (typically by the Author) indicates DCO, as I understand it.
11:11 Dyrcona then a reviewer/committer signs off the merge commit.
11:11 gmcharlt I do have a reservation in that if we start using merges commits more, we should encourage folks to squash stream-of-conciousness patch series into a more sensible state before a branch gets merged
11:11 Dyrcona gmcharlt: Isn't that more or less what koha does?
11:12 Dyrcona I agree with squashing stream-of-consciousness commits. I've been doing that in my own branches before sharing lately.
11:12 gmcharlt not really -- our workflow in Koha-land is heavily based on the integration of patches with Bugzilla
11:12 gmcharlt essentially, patches get reviewed as attaches in BZ with the aid of git-bz
11:12 gmcharlt once a serious has reached a stable state, they get (in effect) cherry-picked into master
11:13 gmcharlt then cherry-picked into the release branches for the maintenance versions, as decided by the RMaints
11:13 gmcharlt *occassionally* I'll create and merge topic branches
11:13 Dyrcona I see, so it is similar to our workflow.
11:13 gmcharlt but I tend to do that only if I have reason to think that a patch series has more than the usual risk of having to get reverted
11:14 gmcharlt yeah, similar, just with (IMO) slightly better tool support
11:14 Dyrcona I got a slightly different impression in the #koha channel a few weeks ago, but maybe the people in the conversation didn't understand each other.
11:15 gmcharlt well, jcamins tended to create a topic branch for every single bug, no matter how small -- overkill IMO, but that's also definitely a case where tastes very
11:16 gmcharlt a happier medium for the RMaints would indeed be more use of topic branches, perhaps, but I am hesitant to risk breaking the patch review process that's heavily dependent on the git-bz workflow
11:17 Dyrcona Well, I'm just throwing out ideas of something that might work better for us in Evergreen-land.
11:17 Dyrcona And it might not, too.
11:18 gmcharlt our use of the working repos does lend itself to a merge commit being the default merge-to-master action
11:18 gmcharlt s/being/becoming/
11:19 gmcharlt but as I've implied, if we do that, my preference would be for the branches to be cliean and recently rebased before they get merged
11:19 senator i've long had a vague sense that merges were more "correct" and i know they'd make  git branch --contains  smarter
11:21 senator i could also go for that preference. even as a soft requirement. more than trivial conflict resolution, no merge branch is rebased and clean
11:21 senator s/no merge branch/no merge until the branch/
11:21 Dyrcona I can agree with that preference as well.
11:25 csharp is there not a 'rel_2_5' branch?
11:25 ericar joined #evergreen
11:25 dbwells not yet
11:25 csharp ok - so that comes with rel_2_5_0?
11:26 dbwells right
11:26 * phasefx likes the cut more often from master thing
11:26 csharp okay so today's master is later today's beta1?
11:26 dbwells that's the plan
11:26 csharp okay cool ;-)
11:31 gsams joined #evergreen
11:35 csharp hmm - no 2.4.1-2.4.2-upgrade-db.sql file in master
11:35 Dyrcona Might not have been any db changes?
11:35 csharp no, it's in tags/rel_2_4_2
11:36 bshum It's not in rel_2_4 either.  Probably just forgot to port it around
11:36 pinesol_green [evergreen|Lebbeous Fogle-Weekley] Serials: Support reader address information in routing slip template - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=15d0943>
11:37 csharp also, we can probably be rid of 2.3-2.4.alpha1 and 2.3-2.4.0RC upgrades scripts right? ;-)
11:41 eeevil I'll push 2.4.1-2.4.2 into master asap
11:43 eeevil sorry about that ... fall out of the lingering 2.4.2 release process.
11:44 senator csharp: how goes it on 1214464 ?
11:44 phasefx once we get bug 1206531 merged, I'd like to subscribe pinesol_green to http://testing.evergreen-ils.org/~live/   A run from yesterday is here: http://testing.evergreen-ils.org/~live​/archive/2013-09-26_17:25:56/test.html
11:44 pinesol_green Launchpad bug 1206531 in Evergreen "perl-based tests against stock test data on running system" (affected: 1, heat: 6) [Undecided,New] https://launchpad.net/bugs/1206531
11:44 pinesol_green [evergreen|Mike Rylander] Push the 2.4.2 inter-version upgrade script forward - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=2d7c6d4>
11:45 senator csharp: just let me know if i can be helpful on that
11:46 fparks joined #evergreen
11:46 csharp senator: I got stuck in the weeds of creating a good example of "see also" data - mainly because I'm not actually familiar with the format of authorities data
11:47 fparks joined #evergreen
11:48 csharp my hope was to export a couple of records from PINES prod and import them, but that became a rabbit hole, then I tried creating an authority record from right-clicking the controlled field, but it wasn't complete enough :-/
11:48 yboston csharp: what is missing?
11:48 senator 500 tag?
11:49 csharp I'll have to get there just a sec ;-)
11:49 yboston OK
11:51 dbwells Okay, 10 minutes till beta freeze, and I know of three branches I'd like to see in, two on the beta-blockers list, and also bug #1065378
11:51 pinesol_green Launchpad bug 1065378 in Evergreen "Added content by record ID" (affected: 2, heat: 16) [Wishlist,In progress] https://launchpad.net/bugs/1065378 - Assigned to Jeff Godin (jgodin)
11:52 Dyrcona dbwells: If you want them in, then commit them. You Have The Power.
11:52 dbwells is anyone actively reviewing them?
11:53 bshum I'm going to be checking out the last changes jeff made for ac by record ID
11:53 jeff bshum stated his intent a few minutes ago to put eyes on -- yeah, what he said.
11:53 dbwells bug #1214464 already has two signoffs
11:53 pinesol_green Launchpad bug 1214464 in Evergreen "Bi-directional authority enhanced bib browse" (affected: 1, heat: 8) [Undecided,New] https://launchpad.net/bugs/1214464
11:53 dbwells It's just way over my head.
11:54 yboston concerning 1065378  (UPC added content) I am about to load some bibs to my test branch VM. I may need 30 more minutes tops
11:55 dbwells I'll probably push it in even without another party giving it a thumbs up, but I'd rather not if someone is still looking at it.
11:55 dbwells ^^ authority enhancements that is
11:55 csharp dbwells: I'm looking at it right now
11:55 kmlussier csharp: I sent a sample authority record that may or may not help. It's one I used when testing the original bib browse work.
11:55 kmlussier That is, I sent it via e-mail.
11:56 dbwells csharp: ok, thanks, that's what I wanted to know.  I know you were poking it earlier.
11:56 csharp kmlussier: thanks!
11:56 * Dyrcona goes to lunch, and yes, I'm actually going out of the office for a change.
11:56 jeff Dyrcona: enjoy!
11:57 dbwells remingtron is actively attempting to test #1071423, but it's a pretty complex.  Anybody have any opinion on that, good or bad?
11:57 bshum lp 1071423
11:57 pinesol_green Launchpad bug 1071423 in Evergreen "Floating should be more flexible than an on/off" (affected: 6, heat: 30) [Wishlist,Confirmed] https://launchpad.net/bugs/1071423
11:57 * bshum is lazy
11:57 bshum Ah
11:59 dbwells okay, as long as all three branches are being actively tested as we speak, they can go in after noon.  Thanks, everybody!  Are there any other lonely branches needing last minute attention?
12:00 csharp posting here for later investigation: 'TypeError: obj.active_services is undefined' alert box appears when entering z39.50
12:00 bshum dbwells: Before I hit up ac-by-record-id I'm just sneaking in lp 1231523 for senator
12:00 pinesol_green Launchpad bug 1231523 in Evergreen "Fix a small floating issue on the OPAC login page" (affected: 1, heat: 6) [Low,New] https://launchpad.net/bugs/1231523
12:00 bshum It's a small tweak
12:00 jdouma joined #evergreen
12:01 smyers_ joined #evergreen
12:01 dbwells bshum: bug fixes can always come later, no problem
12:01 hopkinsju joined #evergreen
12:01 phasefx dbwells: how about "tests", can they go in later?
12:01 kmlussier dbwells: I did some limited testing of 1071423 a few weeks ago. What I saw look good, but have to admit my testing wasn't as thorough as I would have liked.
12:02 kmlussier I agree. It is fairly complext.
12:02 * kmlussier can't type.
12:03 gmcharlt actually, that looks like a useful new word -- just need to set on its precise meaning
12:03 graced heh, I was just about to say the same thing
12:04 dbwells phasefx: I don't see why not, unless they require some kind of fundamental changes.
12:04 phasefx dbwells: an extra make target is the riskiest change I can think of (not risky at all)
12:05 dbwells phasefx: that is, new tests are fine, new test hooks or infrastructure, depends.  That's probably just common sense.
12:05 phasefx dbwells: oh, also maybe a pre-req addition
12:06 dbwells phasefx: then forget it! ;)
12:06 * phasefx is thinking about lp 1206531   durn :)
12:06 pinesol_green Launchpad bug 1206531 in Evergreen "perl-based tests against stock test data on running system" (affected: 1, heat: 6) [Undecided,New] https://launchpad.net/bugs/1206531
12:07 phasefx no pre-reqs
12:07 phasefx an extra-sub in an existing perl module
12:08 dbwells kmlussier: regarding 1071423, are you fairly confident it at least doesn't break anything?
12:08 csharp kmlussier: eeevil: so I've added kmlussier's example authority record: http://pastebin.com/yuizvy2T and then added How to Cook Everything by Mark Bittman (subj of "cooking")
12:09 afterl joined #evergreen
12:09 csharp when I search "cooking" it appears, but a search for "cookery" fails
12:09 csharp is that because "cookery" needs a separate auth record?
12:09 eeevil it does
12:09 csharp ok
12:09 eeevil that points at the cooking one
12:10 csharp gotcha
12:12 kmlussier dbwells: I was able to do checkouts and checkins. I tested checkins on non-floating items as well as floating ones, and they went to the branch that they were supposed to go. So, in that sense, it didn't break anything.
12:12 dbwells kmlussier: thank you
12:12 kmlussier I guess I would say where I lacked thoroughness was in testing more floating use cases.
12:12 kmlussier I only tested one.
12:13 pinesol_green [evergreen|Lebbeous Fogle-Weekley] OPAC: on the login page, Make "Questions?"/"FAQs" areas not float weird - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=42e8c33>
12:13 kmlussier eeevil: What should happen if csharp searched for Cuisine? I just want to make sure I'm understanding the functionality correctly.
12:15 eeevil kmlussier: sorry, I was digging into something else ... lemme look.
12:15 eeevil csharp: is the system externally visible?
12:21 csharp eeevil: sadly no :-(
12:21 csharp I added this auth record for cookery: http://pastebin.com/st9UcryJ
12:22 csharp but only "cooking" shows up
12:23 csharp "shows up" = in the browse list/autosuggest - also when typing "cookery" in the search bar as keyword or subject search gets no results
12:24 eeevil csharp: there's no $0 linking the records
12:25 eeevil (pardon brevity... :) )
12:25 csharp no problem
12:27 csharp ah - that did it
12:27 csharp I see now
12:28 kmlussier csharp++
12:28 yboston csharp++
12:28 eeevil whee!
12:28 csharp okay - I'll go create a signoff branch
12:28 eeevil csharp++
12:31 jcamins gmcharlt: yeah, I think if I were to RM now that I've seen your techniques I would not do topic branches for bugs with only one patch.
12:32 csharp bug 1214464 updated with signoff branch location
12:32 pinesol_green Launchpad bug 1214464 in Evergreen "Bi-directional authority enhanced bib browse" (affected: 1, heat: 8) [Undecided,New] https://launchpad.net/bugs/1214464
12:33 senator csharp++
12:33 kmlussier csharp++
12:34 dbwells csharp++ eeevil++
12:35 kmlussier I hate to interrupt all the dev discussion on a beta release day, but just a heads up that the web team wll be meeting in about 25 minutes.
12:35 gmcharlt and in 1 hour and 25 minutes, the EOB meeting
12:35 csharp webteam_v2.0++
12:39 RoganH joined #evergreen
12:41 * yboston needs like 15 more minutes before sign off
12:42 dbwells yboston: no worries, I don't believe in daylight savings time, so you still have 20 minute or so
12:44 * RoganH says that daylight savings is for dirty hippies.
12:45 kmlussier RoganH's here! I was looking for you earlier.
12:46 RoganH I'm off today so I just logged on for meetings.  What's up?
12:46 kmlussier I didn't know if you wanted me to add something to http://www.evergreen-ils.org/dokuwiki/doku​.php?id=webteam:meetings:agenda:2013-09-26 for the work you've been doing on the web site. Or are you just going to cover it under the status for your action item.
12:46 csharp dbwells: would you consider pulling in this cleanup commit?  It removes old 2.3-2.4 alpha/RC version db upgrade scripts
12:46 csharp http://git.evergreen-ils.org/?p=wor​king/Evergreen.git;a=commit;h=38f8c​ff8276152381afab4f897fd990d51b5a45f
12:47 RoganH I'll cover the current work being done under one item.
12:47 book` joined #evergreen
12:47 RoganH And separately I'd like to see if anyone has any comments on the doc I sent out about possible roles.
12:48 RoganH And finally in relation to the other doc I sent out if anyone has any projects they find particularly compelling to work on.
12:48 dbwells csharp: I guess that is something eeevil should look at, not sure if he wants those around for any reason.
12:48 csharp works for me
12:50 dbwells grabbing 0836
12:55 pinesol_green [evergreen|Thomas Berezansky] Floating Groups - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=2307d45>
12:55 pinesol_green [evergreen|Dan Wells] Stamping upgrade for floating groups - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=c3a805e>
12:57 * senator sets out to merge that bib auth thing with all the signoffs :-)  grabbing 0837 and getting out of the way for the web meeting starting soon here
12:59 StephenGWills joined #evergreen
13:00 RoganH updating agenda now
13:01 kmlussier RoganH++
13:02 eeevil dbwells: I don't care about those scripts ... if folks are mistakenly running them, sure, we can remove them
13:02 kmlussier Meeting time.
13:02 RoganH ok, it was at 1:01 but technically the meeting hadn't started :)
13:02 kmlussier #startmeeting Evergreen Web Team meeting, 2013-09-26
13:02 pinesol_green Meeting started Thu Sep 26 13:02:58 2013 US/Eastern.  The chair is kmlussier. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:02 pinesol_green Useful Commands: #action #agreed #help #info #idea #link #topic.
13:02 pinesol_green The meeting name has been set to 'evergreen_web_team_meeting__2013_09_26'
13:03 kmlussier #info agenda is at http://www.evergreen-ils.org/dokuwiki/doku​.php?id=webteam:meetings:agenda:2013-09-26
13:03 kmlussier #topic Introductions
13:03 bshum #info bshum = Benjamin Shum, Bibliomation
13:03 kmlussier Everyone can introduce themselves with the #info command.
13:03 gmcharlt #info gmcharlt = Galen Charlton, Equinox
13:03 kmlussier #info kmlussier is Kathy Lussier, MassLNC
13:03 RoganH #info RoganH = Rogan Hamby, SCLENDS
13:03 StephenGWills #info Steve Wills, Paine (i mean Maine) Balsam Consortium.
13:04 * RoganH thinks he meant Paine
13:04 * StephenGWills looks skyward
13:04 ericar #info ericar is Erica Rohlfs, Equinox
13:05 kbutler #info kbutler is Kate Butler, Rodgers Memorial
13:05 kmlussier OK, moving on. Late arrivals can introduce themselves as they come in.
13:05 kmlussier #topic Action items from last meeting
13:05 kmlussier #info The one action item was RoganH will break down the web site into editorial categories and send it out to the mailing list.
13:05 kmlussier RoganH: Status?
13:05 RoganH I sent it.
13:05 RoganH No one replied.
13:06 RoganH I've relinked it in the agenda for today's meeting.
13:06 kmlussier OK, we'll discuss it later in the agenda.
13:06 kmlussier #topic Wordpress conversion
13:06 RoganH I'll chat about it some more then and we can mull over it.
13:07 bshum Well, the wordpress conversion happened
13:07 kmlussier bshum++ for the conversion to Wordpress!
13:07 bshum We're still cleaning things up and arranging things.  But kudos to everyone who's helped step into it already.
13:07 bshum And thanks to those who helped notice tiny corners we had missed.
13:07 ktomita #info ktomita = Kyle Tomita, Catalyst IT
13:08 kmlussier Are there any particular areas where others can help with cleanup?
13:08 kmlussier #info Wordpress conversion is done.
13:08 kmlussier #info bshum and others are doing cleanup.
13:08 bshum Well I think the big things for me is redesigning the "get involved" stuff so that it's not just a leftover from the old "communicate" page
13:08 bshum And dealing with the downloads page
13:09 bshum phasefx helped forward me a request to add back a "search" button to the website that looks up all the various page contents.  So that's something too.
13:09 kmlussier On the "get involved'" section, I was thinking it would be good to link to the committees page, since that's a great way to get involved. But should it be converted to a WordPress page first?
13:09 RoganH I think it should be, yes.
13:09 RoganH And reflect different ways for people to get involved rather than channels.
13:09 RoganH That means that some channels will be duplicated but that's OK.
13:10 bshum kmlussier: I would agree with that.  Getting us off the wiki pages and into Wordpress would be the most ideal.
13:10 kmlussier I can take that as an action item. That is, converting the committees page to a WordPress page
13:11 kmlussier #action kmlussier to convert committes page to a WordPress page so that it can be included in the "get involved" section.
13:11 pinesol_green [evergreen|Mike Rylander] Bi-directional authority enhanced bib browse - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=d3b6548>
13:11 pinesol_green [evergreen|Mike Rylander] Some release notes for browse enhancements - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=96e1a74>
13:11 pinesol_green [evergreen|Lebbeous Fogle-Weekley] Numbering upgrade script for auth-only-bib-auth-browse-signoff - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=e1e4198>
13:12 kmlussier Anything else on the conversion before we discuss the downloads page further?
13:12 kmlussier #topic Evergreen downloads page
13:13 kmlussier This was an action item I took on at a previous meeting with hbrennan, but then neglected to follow up on. :(
13:13 kmlussier bshum: Do you want to talk about this?
13:13 bshum Sure, so
13:14 bshum For the downloads page, there'd been some talk about reorganizing the content there.  Specifically, I think we're thinking to move away from the weird table structure we'd been using up till now.
13:14 bshum By that I mean having three columns (from left to right, new to old versions)
13:14 kmlussier #link http://evergreen-ils.org/egdownloads/
13:14 bshum And changing that to be more accessible and/or relevant.
13:15 RoganH Are you talking about moving each version to it's own table, maybe newest at the top so they're less crowded together?
13:16 bshum RoganH: Well that's certainly an approach we could use
13:16 bshum I think the open question has been what's the best way of presenting the information in a meaningful way to end users.
13:16 bshum (and also cleaning up old links along the way, like the Mac stuff and Linux stuff, which are severely outdated)
13:17 RoganH I think we can get cleaner but better is going to be very subjective.  I've already betrayed my preference to move each version to it's own table.
13:17 kmlussier I think the structure RoganH suggests might be good.
13:17 RoganH I think it would be easier for people quickly trying to find what they're looking for.
13:17 kmlussier What I also think would be helpful is some color coding for the releases. Maybe green for stable releases.
13:18 graced #info graced is Grace Dunbar, Equinox
13:18 RoganH Red for beta or release candidates?
13:18 kmlussier graced: We already volunteered you for everything. :)
13:18 graced excellent!
13:18 RoganH graced: really, the Parsi translations were a step above and beyond on your part.
13:19 kmlussier RoganH: Yeah, I was thinking red or maybe yellow for use with caution.
13:19 graced well, I like to be thorough...
13:19 RoganH yellow might be too faint I tink
13:19 * kmlussier nods.
13:19 RoganH think.  <--- engrish good
13:19 bshum kmlussier: RoganH:  To be honest, I've never been a fan of color coding the releases too much.
13:19 bshum But that's just been my personal opinion.
13:19 bshum Happy to continue trying it.
13:19 gmcharlt color coding isn't accessible by itself
13:19 RoganH I have no strong feelings there, just bouncing of kathy's thought.
13:19 gmcharlt it can be used, but should be supplemented by text
13:19 graced Good point
13:19 bshum We used to use green for stable, red for unstable, yellow for RC, I think.
13:20 kmlussier Well, no, I wouldn't be used on its own. Definitely supplemented by text.
13:20 RoganH gmcharlt: I'm thinking more of the casual low vision user who needs strong contrast.
13:20 bshum And gray for deprecated.  Though in a recent conversation with gmcharlt, I think we shouldn't advertise old versions on the main downloads pages.
13:20 RoganH I agree with gmcharlt on that.
13:20 gmcharlt RoganH: yep, but there's colorblind users to consider as well
13:21 gmcharlt and while I'm spitballing -- I think the relevant OpenSRF installation instructions should be linked directly from the EG downloads page
13:21 RoganH gmcharlt: I agree.  And Red might be a bad choice for that reason, green too.
13:21 bshum +1 to gmcharlt's suggestion to put the OpenSRF stuff up front.
13:21 RoganH +1
13:21 graced +1
13:22 RoganH What we could do is do everything in black for all users and then put red or green blinking signs for those who aren't colorblind for "stable" and "test"
13:22 RoganH Then we will wish we couldn't see them.
13:23 * graced thinks Rogan misses Geocities
13:23 kmlussier bshum: So what do you need from us? Direction on layout for the page or would you like somebody to dive in to try reformatting the page?
13:23 * gmcharlt is glad that Mozilla has removed the blink tag, suddenly
13:23 RoganH Can I propose we try a stable arrangement separating out the versions and putting the opensrf content in?
13:23 * kmlussier is ignoring RoganH's suggestion.
13:23 graced Would mockups be helpful?
13:24 bshum kmlussier: Any outside assistance would be welcome as for both direction on layout and help diving in.
13:24 kmlussier graced: Are you volunteering to do mockups?
13:24 graced I am, I am also volunteering to give others access to our mockup software if they want
13:24 bshum If someone has a strong urge to help change it, I expect that'll just help get it done faster :)
13:24 bshum *faster than waiting for me to do it
13:25 graced bshum: I think you're doing a bang-up job considering the salary...
13:26 RoganH Ben has done a spectacular job.
13:26 kmlussier I want to move on to the next topic, so why don't we take graced up on her offer to do mockups. I'm familiar with the mock-up software, so I'm willing to pitch in as time allows.
13:26 StephenGWills Ben++
13:26 RoganH So, action item, graced will do mockups?
13:26 kmlussier #action graced to do mockups for downloads page.
13:27 bshum Sounds good to start with mockups and then move from there as it develops.
13:27 kmlussier graced: And if you're able to do them before the next meeting, don't hesitate to share them on the list. We can give feedback via e-mail as well.
13:27 kmlussier Anything else on the downloads page?
13:27 kmlussier #topic Accessibility color change
13:27 kmlussier RoganH?
13:27 RoganH Just a quick FYI really.
13:28 RoganH Galen and I did some tweaking so it's accessibility friendly.
13:28 RoganH a very dark green
13:28 csharp graced: re: geocities http://wonder-tonic.com/geocitiesizer/content.ph​p?theme=2&amp;music=6&amp;url=evergreen-ils.org
13:28 * csharp is sorry to distract :-/
13:28 RoganH but he found a bug with the besting where it doesn't see the css added in the header
13:28 graced csharp++
13:28 RoganH so if we make css changes that way (rather than changing the underlying css files) we will need to test manually so to speak
13:28 gmcharlt csharp: my eyes!
13:29 RoganH this is so that updates don't break changes we make
13:29 RoganH that's all
13:29 RoganH #info csharp is going to heck for posting that link
13:29 csharp RoganH++
13:30 kmlussier OK, anything else on the color changes/css before moving on to the next topic?
13:30 RoganH nope
13:30 kmlussier #topic Merchandising page
13:30 kmlussier RoganH again.
13:30 RoganH very quick again - I added a section for links on the top banner
13:31 RoganH Right now it only has Evergreen in Action.
13:31 RoganH It will in the future have links to our Amazon and Zazzle content assuming that all survives it's own process.
13:31 kmlussier RoganH++
13:31 RoganH I wanted to give folks time to voice any questions or concerns.
13:31 kmlussier I hadn't noticed the new menu item.
13:31 RoganH It's been there about a week.  :)
13:32 bshum I saw it.  I should mention a quirk with the theme is that the actual listed top level doesn't link properly
13:32 RoganH I added it Friday while waiting for my plane last week (6 days).
13:32 kmlussier #info RoganH added merchandising to the top-level links of the Evergreen web site.
13:32 bshum So I've cheated by making a sub link go to the landing pages occasionally
13:32 bshum Like the "Overview" does for the "About Us" pointing back to the main page
13:32 RoganH I saw that but quickly found those workarounds too.
13:33 bshum But yes, RoganH++
13:33 kmlussier Does anyone have any concerns about the new link.
13:33 kmlussier I like it and am excited to see the new stuff that will be posted there. :)
13:33 RoganH We will talk about that more at the next meeting.
13:34 kmlussier #topic Discussion of roles / sections looking at papers for inspiration
13:34 RoganH OK.  I emailed out the link to a google doc for collaboration because I suspect not everyone has WIKI accounts.
13:34 RoganH And I've reposted it on the agenda.
13:34 kmlussier #link https://docs.google.com/document/d/1GJXaUJU4M_ol​IDH1KHLXCe9bNJIU0PzL8J5gVeXrDM4/edit?usp=sharing
13:35 RoganH We've had this talk for a while about should the web team be kind of anarchist where each person raises their hand to do as they like or should there be defined roles.
13:35 RoganH I'm a bit anarchist at heart but in the interest of exploring the other path I looked at how papers organize.
13:35 RoganH Newspapers have similar needs - they have regular sections, news, highlights, support communities, etc...
13:36 RoganH So that document is based off that.  And to be fair we have sections of the site and wiki that probably have been neglected by the 'do as thou will' approach.
13:37 RoganH And maybe we want the WIKI to be a more hands off thing from the web site and be more wild west.
13:37 RoganH I'm more comfortable now with that, now that the site and WIKI aren't so easy to confuse with each other.
13:38 RoganH I will put some more comments into the header of that document for context and put it on the agenda for the next meeting again.
13:38 RoganH And hopefully we can discuss it on list inbetween.
13:38 kmlussier My only comment with the document is that there are a lot of roles there. I know we had an issue with DIG for a while where we had more roles than volunteers to fill them. I'm concerned that might happen here too.
13:38 RoganH I think that's a very valid concern.
13:39 kmlussier Perhaps merging the managing editor with editor in chief might be a good place to start.
13:39 gmcharlt +1 # had exactly the same thought
13:39 kmlussier Oh, but you did mention that a bit in the document.
13:39 RoganH I did.
13:39 kbutler I think it's a good idea to have a range of smaller and larger roles for people with varying amounts of time.
13:40 RoganH Part depends on scope.  I also think about the web team's role in relationship to the wiki is critical because it changes the scope of duties quite a bit.
13:40 kbutler If someone has a lot of time they can combine some smaller roles or just do a bigger one.
13:40 RoganH And it impacts number of roles
13:41 RoganH Frankly, if the wiki is part of the web team's duties is quite a bit more complicated though at the same time it would be good to have at least one or two roles associated with flagging out of date content.
13:41 gmcharlt could define a separate wiki curator position
13:42 gmcharlt editor, janitor, etc.
13:42 graced I think that's a good suggestion - but we run into the same problem of not having enough people to fill the roles.
13:42 StephenGWills The wiki really should be an open space and perhaps, to some degree a place to draft info that is not vetted for the website yet?
13:42 RoganH gmcharlt: that's the direction I'm leaning in preference
13:43 kmlussier In looking at specific sections, I think DIG has traditionally taken on the role of mainining all the doc pages, and I think it would be appropriate to keep it there.
13:43 RoganH I think the wiki person's role would be to just flag out of date content and maybe keep up a wishlist of pages that need updating as they have time.
13:43 RoganH I think it has to be treated different from the website itself.
13:43 RoganH kmlussier: I agree and those are actively maintained.
13:44 RoganH If we change the scope of the wiki to be a different beast then the web site proper I think becomes easier to define roles for.
13:44 kmlussier We have about 15 minutes until the EOB needs our meeting space.
13:44 RoganH I'm happy to carry this thread onto email and doc editing.
13:45 kmlussier RoganH: Sure. I think you got some good suggestions on specific roles. Continuing on e-mail would be good.
13:45 kmlussier And then getting to the point of seeking volunteers for the specific roles. :)
13:45 RoganH We may need to put that off a little as this discussion develops but I'm OK with that.
13:46 RoganH And everyone, please jump in!
13:46 kmlussier #action RoganH to continue roles discussion via e-mail on the web team list.
13:46 kmlussier #topic Some ongoing tasks
13:46 StephenGWills the reasons I don't say much is because I am already volunteering for several things I have no time to deliver…  :(
13:47 kmlussier link: https://docs.google.com/document/d/1AvGW1NTJVM7y​5MeokT6um3OjapOCUDqdDDTqpsQ03F0/edit?usp=sharing
13:47 RoganH not a lot to say here, just a list of discrete tasks that need to be done.
13:47 RoganH I've done a few already and as I have spare moments will do more but others can as well of course.
13:47 RoganH Trying to take some of the load off Ben here so he doesn't have to do every little thing :)
13:47 gmcharlt one thing I need to do and have mentioned is to get a couple pages arising from the EOB put up
13:48 gmcharlt the trademark policy to start, most notably
13:48 RoganH in the About Evergreen section?
13:48 bshum That sounds like a good place
13:48 gmcharlt yeah, I think that's a good place
13:48 elizabethm_ joined #evergreen
13:48 RoganH I'll volunteer to do that and link to some good hi res and eps graphics there
13:49 gmcharlt actually, I was intended to do that
13:49 gmcharlt there are a couple technical changes to the wording of the policy that I have to dig through first
13:49 gmcharlt *intending
13:49 kmlussier I think this list of tasks is a great idea! I think it's hard for potential volunteers to know where to start, and this gives them a nice list to start with.
13:49 kmlussier RoganH++
13:49 graced RoganH++
13:50 kmlussier Should we ask people to add their names to a specific task? So that two people aren't working on the same thing.
13:50 gmcharlt kmlussier: +1
13:50 RoganH I think so.  And as Galen did, if you need to take over a task just edit it to show.
13:50 RoganH In this case I know why Galen is but otherwise adding a note about why would be good.
13:52 RoganH So, that's all for this.  I was hoping to have bite size items on here that anyone could start with.
13:52 kmlussier #info Volunteers who want to help with web site should add their name to the task they are planning to work on.
13:52 ericar Sorry, this is my first meeting. I'm not seeing this on the tasks, but do you need someone to identify out dated content on wiki page or do you want to hold off on that?
13:52 RoganH yes we do!
13:52 RoganH Do you want to volunteer to be a wiki janitor?
13:52 kmlussier IIRC, there was a convention for identifying outstated content on the wiki. I can't recall the details now.
13:52 ericar Awesome job title, yes.
13:52 graced It sounds so glamorous...
13:53 gmcharlt wiki librarian?
13:53 RoganH We can call it Editor if you like.  Curator?
13:53 kbutler weeder
13:53 RoganH Curator implies controlling what's published though, so does editor.
13:53 RoganH Wrangler?
13:53 kmlussier #info web team membes can also add new tasks to the list RoganH started.
13:54 kmlussier Terrible. My typo will show up in the minutes. :(
13:54 RoganH What ever it is Erica has volunteered so I'll add her to the roles page.  She has the duty of deciding what the position is called.
13:54 kmlussier ericar++
13:54 gmcharlt RoganH++
13:54 gmcharlt ericar++
13:54 RoganH ericar++
13:54 montgoc1 joined #evergreen
13:54 bshum ericar++
13:54 kbutler ericar++
13:55 jeff win 32
13:55 jeff er.
13:55 kmlussier We have 5 minutes during which web team/EOB members can take a rest between meetings. Anything else for today?
13:55 pinesol_green [evergreen|Dan Scott] Include auth browse docs in OPAC section - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=639d435>
13:55 jboyer-isl jeff: no swearing during the meeting.
13:55 pinesol_green [evergreen|Dan Scott] Clean up minor doc problems - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=a833b34>
13:55 pinesol_green [evergreen|Dan Scott] Fix doc typo in public interface setup section - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=323b185>
13:55 bshum webteam_v2.0++
13:56 kmlussier OK. Next meeting is scheduled for October 17 then. Thanks all!
13:56 kmlussier #endmeeting
13:56 jeff jboyer-isl: missed a slash on my attempt to switch to window 32. :-)
13:56 pinesol_green Meeting ended Thu Sep 26 13:56:12 2013 US/Eastern.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
13:56 pinesol_green Minutes:        http://evergreen-ils.org/meetings/evergr​een/2013/evergreen.2013-09-26-13.02.html
13:56 pinesol_green Minutes (text): http://evergreen-ils.org/meetings/evergr​een/2013/evergreen.2013-09-26-13.02.txt
13:56 pinesol_green Log:            http://evergreen-ils.org/meetings/evergree​n/2013/evergreen.2013-09-26-13.02.log.html
13:56 bshum Thanks!
13:57 Shauna_ joined #evergreen
13:59 pinesol_green Showing latest 5 of 11 commits to Evergreen...
13:59 pinesol_green [evergreen|Jeff Godin] Add method to permit AC handler to expect keyhash - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=83d198a>
13:59 jboyer-isl jeff: Read Charles Petzold's Programming Windows and you'll think Win32 is a 4-letter word. :D
13:59 pinesol_green [evergreen|Jeff Godin] Add ISSN support to Syndetic AC handler - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=9c0ea8a>
13:59 pinesol_green [evergreen|Jeff Godin] Show jacket on record page even when no isbn/upc - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=07e6490>
13:59 pinesol_green [evergreen|Jeff Godin] Add release notes for AC by record id - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=cc905f4>
13:59 pinesol_green [evergreen|Jeff Godin] Add apache config examples for AC by record id - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=e5eccfe>
13:59 jeff my irc clients just went a bit nuts.
14:00 bshum jeff++ # it's finally in!
14:00 jeff bshum++ thanks!
14:00 jeff yboston++ for testing and for test data
14:00 bshum yboston++ #for helping me test cause my syndetics subscription level sucks
14:00 berick jeff++
14:00 abneiman joined #evergreen
14:01 gmcharlt show time
14:01 Dyrcona Another meeting is supposed to be starting isn't it?
14:01 gmcharlt #startmeeting Evergreen Oversight Board Meeting, 26 September 2013
14:01 pinesol_green Meeting started Thu Sep 26 14:01:15 2013 US/Eastern.  The chair is gmcharlt. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:01 pinesol_green Useful Commands: #action #agreed #help #info #idea #link #topic.
14:01 pinesol_green The meeting name has been set to 'evergreen_oversight_board_​meeting__26_september_2013'
14:01 kmlussier Dyrcona: Yup!
14:01 gmcharlt #topic Introductions
14:01 b_bonner left #evergreen
14:01 gmcharlt EOB members, please itnroduce yourself with #info
14:01 gmcharlt #info gmcharlt = Galen Charlton, Equinox Software
14:01 Shauna_ #info Shauna=Shauna Borger, Indiana State Library
14:02 RoganH #info RoganH = Rogan Hamby, SCLENDS
14:02 George_ joined #evergreen
14:02 elizabethm_ #info elizabethm = Elizabeth McKinney
14:02 StephenGWills #info Steve Wills, Maine Balsam Consortium
14:02 abneiman #info abneiman = Andrea Neiman, Kent County Public Library
14:02 dbwells #info dbwells = Dan Wells, Hekman Library, Calvin College
14:02 montgoc1 #info montgoc1 = Chauncey Montgomery, Consortium of Ohio Libraries
14:02 kmlussier #info kmlussier is Kathy Lussier, MassLNC
14:02 George_ #info George = George Rodgers-Clark, La Conner, WA (public library)
14:03 gmcharlt OK, we have a quorum.  There's a lot to talk about, so I'm moving on, but latecomers please introduce yourselves
14:03 gmcharlt #topic Action items from previous meeting
14:03 gmcharlt #info Status of tax rebate for 2013 conference: the conference did not in the end qualify for one
14:03 gmcharlt #info Net gain from the 2013 conference is about $5,900
14:04 gmcharlt #info For future conferences outside the U.S., tax implications can be considered when deciding whether to have Conservancy subcontract the conference to the host institution that year.
14:04 yboston #info ysboston - Yamil Suarez - Berklee College of Music
14:04 gmcharlt any questions about that?
14:05 gmcharlt ok
14:05 gmcharlt #info Conservancy confirmed that an open Amazon referral link is acceptable http://list.evergreen-ils.org/pipermail/eg-​oversight-board/2013-September/000573.html
14:05 gmcharlt #info RoganH has surveyed community about options for merchandise
14:05 gmcharlt that leaves one more
14:05 gmcharlt yboston: an update on the documentation back-filling proposal?
14:05 RoganH We've gotten about a dozen items recommended, some duplicates like the Jono Bacon book.
14:06 * afterl is Amy Terlaga, Bibliomation (guest)
14:06 RoganH All are about systems librarianship or Evergreen related technologies so I think they are appropriate.
14:06 yboston gmcharlt: I am preparing a link to share the draft that I have, need a couple of minutes
14:06 gmcharlt yboston: OK, we'll come back to you later
14:07 gmcharlt #topic Financial summary
14:07 gmcharlt #info Current summary is at http://list.evergreen-ils.org/pipermail/eg-​oversight-board/2013-September/000604.html
14:07 gmcharlt #info Net gain of $5,850.02 from last month, arising from 2014 conference sponsorships
14:07 gmcharlt any questions about the bottom line?
14:07 RoganH nope
14:07 montgoc1 Nope.
14:08 gmcharlt ok
14:08 gmcharlt #topic 2.5 Release Manager's report
14:08 gmcharlt dbwells: you have the floor
14:08 dbwells thanks
14:08 dbwells #info A few days ago, I finally accepted the fact that 2.5 will be at least a few weeks late.
14:08 dbwells Current plans are for an Oct. 14 release, but even that counts on no more bumps and/or
14:08 dbwells bruises.
14:09 dbwells #info Looking back, I think a combination a vacation season ending, plus Hack-a-Way activity, plus general procrastination in a few areas, all conspired together to create a brief but intense whirlwind.
14:10 dbwells #info We ended up with 49 total bugs/features committed for the beta phase, so considering the other phases all had 30-40, it wasn't a /huge/ rush by comparison, but it was noticeable.
14:10 Dyrcona k
14:10 dbwells #info The page hasn't been cleaned up yet, but you can see these as "Fix Committed" here: https://launchpad.net/everg​reen/+milestone/2.5.0-beta1
14:10 dbwells #info I am still hopeful that some of the more methodical activity we accomplished over the summer will result in a better overall release.
14:10 dbwells Any questions?
14:11 gmcharlt dbwells++ # making the tough decisions
14:11 yboston dbwells++
14:11 RoganH dbwells++
14:11 kmlussier dbwells++
14:11 jeff dbwells++
14:12 yboston dbwells I really applaud the approach you took and the time to report back metrics to the community at large
14:12 Dyrcona dbwells++
14:12 egbuilder build #400 of evergreen-master-debian-6.00-x86_64 is complete: Failure [failed test]  Build details are at http://testing.evergreen-ils.org/buildbot/builder​s/evergreen-master-debian-6.00-x86_64/builds/400  blamelist: Bill Erickson <berick@esilibrary.com>, Jeff Godin <jgodin@tadl.org>
14:12 egbuilder build #376 of evergreen-master-ubuntu-12.04-x86 is complete: Failure [failed test]  Build details are at http://testing.evergreen-ils.org/buildbot/builde​rs/evergreen-master-ubuntu-12.04-x86/builds/376  blamelist: Bill Erickson <berick@esilibrary.com>, Jeff Godin <jgodin@tadl.org>
14:12 egbuilder build #343 of evergreen-master-fedora-18 is complete: Failure [failed test]  Build details are at http://testing.evergreen-ils.org/buildbot/bu​ilders/evergreen-master-fedora-18/builds/343  blamelist: Bill Erickson <berick@esilibrary.com>, Jeff Godin <jgodin@tadl.org>
14:12 yboston also, you guys were an excellent host
14:12 yboston for the hack-a-way
14:12 jeff buildbot likely needs a new dependency installed: Business::ISSN
14:12 bshum Sorry for the chatter, that's just the buildbots being unhappy.  Yeah.
14:12 RoganH I had a request that the next hack-a-way have a soft serve ice cream machine because Calvin College had one.
14:13 yboston its timing is impeccable
14:13 dbwells yboston: thanks, it was our pleasure
14:13 kmlussier RoganH++
14:13 gmcharlt looks like no questions for dbwells; thanks for the update!
14:13 gmcharlt #topic Evergreen 2014 Conference Committee Report
14:14 kmlussier We reached the 6 month mark until conference time last week.
14:14 kmlussier We've opened up registration, but just a few have come in so far.
14:14 kmlussier Don't forget to get your registrations in before the Early Bird Deadline: http://evergreen-ils.org/conferen​ce/eg14/conference-registration/
14:14 afterl I'll be sending out monthly reminders
14:15 kmlussier Thanks to the great work of bshum to move the Evergreen site over to Wordpress, we also have a conference web page integrated in with the community web site.
14:15 kmlussier http://evergreen-ils.org/conference/eg14/
14:15 kmlussier And the Program Committee is looking for program proposals.
14:15 kmlussier afterl: Do you want to talk about sponsorships?
14:15 afterl A word on sponsorships so far:  it appears to be who you know.  If you don't have an in, you don't get a reply back.
14:16 afterl So we're going to have to regroup on this to make sure we are getting decent sponsorship money coming in
14:16 afterl In the meantime we're following up on the ones who have touched base with us
14:17 gmcharlt folks who have committed to a sponsorship can be a good source of specific suggestions and introductions to other
14:17 gmcharlt ... potential sponsors
14:17 afterl Okay, good to know
14:17 afterl That's the kind of advice I need right about now
14:18 afterl We
14:18 afterl will keep at it
14:18 elizabethm_ Is there a link to sponsorship info?  I usually send out a request to the PINES vendors no matter the conf location.
14:18 afterl We're working on it
14:18 kmlussier elizabethm_: We're working on that now.
14:19 Shauna_ In the past, other local conference planning groups have provided the EOB and past committees with a list of the sponsors/exhibitors from whom they have not heard back.
14:19 Shauna_ Someone else may have a connection with that vendor and has a better opportunity from hearing back.
14:19 Shauna_ Just wanted to throw that out as a suggestion.
14:20 afterl I can send the Board a link to my spreadsheet, built off of Indiana's
14:20 afterl so you can follow along with our progress
14:20 afterl Thanks to Shauna
14:20 gmcharlt sounds good
14:20 afterl that's all for now on sponsorships
14:21 gmcharlt any questions for kmlussier and afterl?
14:21 montgoc1 kmlussier: How many program proposals have you received at this point?
14:21 kmlussier montgoc1: Just one.
14:21 kmlussier So if you have any ideas, but were hesitant about submitting, please send them along.
14:22 kmlussier I will also start posting the proposals to the wiki as we receive them since we are giving the community an opportunity to provide some feedback before we make final selections.
14:22 montgoc1 OK.
14:22 abneiman kmlussier: I'm sorry if I missed this, but did you guys decide on which track arrangement you were doing?   I know you sent out a survey about it.
14:23 kmlussier No, you didn't miss it because I dont' think I've communicated it yet. There was wide support for the schedule that starts with tutorials on the day of the hackfest.
14:24 kmlussier That schedule also has a continuation of programs on the last day of the conference. Interest group meetings would then become part of the regular programming schedule.
14:24 * kmlussier will make a note to convey that information to the general list.
14:25 abneiman Cool, thank you
14:25 gmcharlt OK, thanks kmlussier and afterl!
14:25 gmcharlt #topic Merchandising
14:25 gmcharlt #info Current proposal is at http://list.evergreen-ils.org/pipermail/eg-​oversight-board/2013-September/000600.html
14:26 RoganH I didn't get a chance to pull together the mockup images due to personal things happening today.
14:26 RoganH But as it stands are there any questions?
14:27 RoganH The dozen or so items suggested for the store are fairly straight forward and I will email them to the list soon.  (I think they all came from Galen and I.)
14:28 RoganH I am making a motion to implement this proposal.
14:29 abneiman Second
14:29 kmlussier +1
14:29 montgoc1 +1
14:29 gmcharlt #startvote Does the Board authorize implementation of the merchandising proposal - http://list.evergreen-ils.org/pipermail/eg-​oversight-board/2013-September/000600.html? Yes, No, Abstain
14:29 pinesol_green Begin voting on: Does the Board authorize implementation of the merchandising proposal - http://list.evergreen-ils.org/pipermail/eg-​oversight-board/2013-September/000600.html? Valid vote options are Yes, No, Abstain.
14:29 pinesol_green Vote using '#vote OPTION'. Only your last vote counts.
14:29 elizabethm_ +1
14:29 RoganH +1
14:30 RoganH Yes
14:30 gmcharlt #vote Yes
14:30 kmlussier #vote Yes
14:30 RoganH #vote Yes
14:30 StephenGWills #vote yes
14:30 Shauna_ #vote  Yes
14:30 montgoc1 #vote Yes
14:30 abneiman #vote yes
14:30 elizabethm_ #vote yes
14:30 George_ #vote yes
14:30 yboston #vote yes
14:31 gmcharlt motion carries
14:31 gmcharlt #endvote
14:31 pinesol_green Voted on "Does the Board authorize implementation of the merchandising proposal - http://list.evergreen-ils.org/pipermail/eg-​oversight-board/2013-September/000600.html?" Results are
14:31 pinesol_green Yes (10): kmlussier, Shauna_, abneiman, StephenGWills, George_, RoganH, elizabethm_, montgoc1, gmcharlt, yboston
14:31 gmcharlt #agreed The merchandising proposal is accepted.
14:31 gmcharlt #action RoganH to work with Conservancy and other EOB as needed to implement the merchandising proposal
14:31 RoganH Followup question.
14:31 kmlussier RoganH++
14:31 kmlussier I love the quote that was selected!
14:32 RoganH Do we want to make a merchandising committee of some kind to handle routine tasks from here?
14:32 RoganH It doesn't have to be oversight members necessarily though at least one should be on it and a Conservancy rep.
14:33 RoganH I did too.  Hopefully we will add more later.
14:33 kmlussier RoganH: I don't think it's a bad idea to have a committee work on it. So that it doesn't all fall on you.
14:34 George_ I could help out with merchandising.
14:34 RoganH And so that if I get hit by a bus others know what's going on.
14:34 RoganH Plus we don't want to bring every little thing to the oversight board.
14:35 gmcharlt I think so.  Given that this touches on project finances, requiring that an EOB member be on it is essential IMO
14:35 yboston If we use non EOB members, I would say we need to remember to put in writing the pbasic procedures we have to follow areind money because of the conservancy. I could use it too :)
14:35 RoganH Galen, do you think a conservancy rep would be able to join us on such a group?
14:35 yboston s/areind/around/
14:35 gmcharlt in practice, I doubt it  due to time constraints
14:35 gmcharlt not that an invitation shouldn't be extended, of cousre
14:36 afterl I would like to volunteer to be on the committee
14:36 gmcharlt but anything that materially affects the structure of the financial relationship has to go through the EOB and the project rep anyway
14:36 GeoffSams joined #evergreen
14:36 RoganH gmcharlt: exactly, so I would like to offer a position ex-officio to remind the group in the future that they need to be consulted
14:37 gmcharlt but things like coming up with ideas, rotating prodcuts, adding new designs, etc. seems like it would be well within the scope of what cuold be delagated
14:37 RoganH they in this case meaning conservancy
14:38 gmcharlt OK, so at this point I'd like the sense of the Board -- should a merchandising committee be formed, with detail to be fleshed out in a proposal to be considered and formally voted on?
14:38 RoganH So, I will work with the volunteers to start coordinating communication and taking it from here and will need to work with the Conservancy to get the financial arrangements in place and satisfy any legal requirements they have.
14:39 kmlussier +1 to moving foward with a proposal to create a merchandising committee.
14:39 montgoc1 Sounds good.
14:39 RoganH I'm jumping ahead.  But you have my opinion there.
14:39 kmlussier Though I tend to agree with gmcharlt that time constraints may make it difficult to get SFC representation on the committee.
14:39 elizabethm_ +1 moving forward with committee
14:39 abneiman +1, I do think it should be voted on, and at least 1 EOB member be involved
14:40 gsams joined #evergreen
14:40 StephenGWills +1 for sure.
14:40 gmcharlt +1
14:41 gmcharlt #action RoganH to draft a proposal for the Merchandising Committe and start organizational activities, pending EOB approval of the proposal
14:41 gmcharlt OK, we need to move on
14:41 gmcharlt #topic Evergreen Hackaway update
14:42 RoganH The 2013 Hack-A-Way was held this year in Grand Rapids, Michigan hosted by Calvin College and sponsored by Equinox Software.
14:42 RoganH I'll have a more detailed report in the newsletter so I don't want to duplicate that here.
14:42 RoganH To me the biggest deals were the great work on the mobile OPAC
14:42 RoganH and decision to move away from the xulrunner based staff client.
14:43 RoganH The staff client change will be a big project and there's a lot to figure out still but we agreed to move towards a web based one.
14:43 RoganH That's all I have now for a .05 dinar update.
14:43 gmcharlt dbwells++
14:43 RoganH I'll take proposals for the next one immediately following the next conference.
14:43 RoganH dbwells++
14:44 yboston dbwells++ remingtron++
14:44 gmcharlt Calvin_College++
14:44 RoganH My only complaint is that I wasn't told the host hotel had a gaming convention that weekend so I could plan to stay.  :)
14:44 gmcharlt heh
14:44 gmcharlt this makes for a nice segue to a subtopic
14:44 gmcharlt #topic Future of the Evergreen staff interface - EOB role
14:44 yboston I really liked having the time to talk to other EOB members face to face for a couple of days, also with other develoeprs
14:47 RoganH Well, I didn't ask for this item but I will say that one of the biggest concerns we had during the chat
14:47 RoganH is that it's such a big project and where will the leadership come from to either allocate resources.
14:47 RoganH And by that I mean either fund the work or rally the troops to dedicate time.
14:47 RoganH As Jason put it "my bosses are telling me to do other things" and he's right.
14:48 RoganH So, could the EOB help convince resource allocators?
14:48 jeff to interject a minor data point, my boss is saying "contribute to web based staff UI efforts"
14:48 elizabethm_ This looks like a great opportunity for the EOB.
14:48 abneiman Can we put together a "pitch kit"?  Something simplified for funders to convince them to give us funds?
14:48 gmcharlt #info EOB mailing list thread on staff interface and resource allocator meeting http://list.evergreen-ils.org/pipermail/eg-​oversight-board/2013-September/000546.html
14:48 RoganH And I'm glad for that jeff, I really, really am. :)
14:49 jeff but this is not a one person or one organization project. :-)
14:49 gmcharlt this ties directly into the resource summit that Ben Hyman has proposed, so I'm going to merge that agenda item with this
14:50 gmcharlt and ask the sense of the EOB on Ben's question -- are we in favor of the general idea for an Evergreen summit on resources and big projects, and would we like him to flesh out a proposal?
14:50 elizabethm_ Yes!
14:50 kmlussier +1 to the idea for a summit.
14:50 elizabethm_ Sorry.  +1 for summit
14:51 RoganH +1 for summit
14:51 montgoc1 +1 for summit
14:52 abneiman +1 to summit
14:52 gmcharlt no dissent, so
14:52 gmcharlt #agreed The EOB is in favor of calling a resource allocator summit, and requests a fleshed-out proposal from interested parties, including Ben Hyman
14:53 yboston I wanted to make a comment on a way the EOB can help
14:53 gmcharlt go for it
14:53 yboston it is multi line, head up
14:53 yboston Besides providing funding, the EOB can select a point person or small committee to help push this issue forward by doing non-funding based things like...
14:53 yboston (off the top of my head)
14:53 yboston 1) (only) proposing the client be worked on during hack fest or hack-a-way
14:53 yboston 2) attending dev loper meetings and give feedback thinking as the community as a whole, instead f just a single isntitution
14:53 yboston 3) running special IRC meeting on the client topic
14:53 yboston 4) helping set up ddodle polls for these meetings
14:53 yboston 5) helping create user survey to get more feedback from communtiy
14:53 yboston 6) volunteer to test prototype web clients, and or provide test data
14:54 yboston (sorry about the spelling)
14:55 gmcharlt a champion, as it were
14:56 yboston yes, also thought of the role of just a facilitator(s)
14:56 gmcharlt some of that would depend on resources for enough devs to participate -- but I think for now, certainly anybody who is interested should advocate for it
14:57 gmcharlt but I think some of that also anticipate the final form of how the work gets done and funded
14:57 gmcharlt (briefly) any other comments?
14:57 * gmcharlt is going to charge forward
14:57 gmcharlt #topic Evergreen testing efforts
14:57 gmcharlt #info Summary of recent activity - http://list.evergreen-ils.org/pipermail/eg-​oversight-board/2013-September/000601.html
14:58 gmcharlt Shauna_: anything to add -- and are there things you need from the EOB?
14:58 Shauna_ Nothing to add unless anyone has documentation they would like to contribute to the effort.
14:59 Shauna_ I did hear back from one other consortia on that front.
14:59 Shauna_ I'll be happy to entertain any questions or comments.
14:59 kmlussier Shauna_++ This all looks great!
15:00 abneiman Shauna_: if your model is successful (and personally I think it will be), are you planning to open it up to the community at large?
15:00 gmcharlt my main comment is that if you want to go ahead and start a testing page on the wiki, I encourage you to go for it
15:00 RoganH I agree and applaud the work.
15:00 RoganH I think once your work is up there it will encourage others to add onto.
15:01 Shauna_ abneiman We are writing the documentation using generic project management software that anyone can get access to.
15:01 Shauna_ So that it is accessible for all to recreate.
15:02 ktomita_ joined #evergreen
15:02 Shauna_ RoganH, good point. I can start a wiki page, send an email to the list and get feedback that way.
15:02 abneiman Shauna_++ excellent, I think this is a great beginning :)
15:02 fparks_ joined #evergreen
15:02 gmcharlt thanks, Shauna_
15:03 gmcharlt kmlussier and I have discussed the last agenda item, the 2015 conference, and agreed to move the initial discussion to the mailing list
15:03 StephenGWills agreed, this is awesome.  it is going to be so helpful for others doing discovery along that path.  thanks.
15:03 gmcharlt so as we're at the end of the meeting
15:03 gmcharlt #topic Next meeting
15:03 gmcharlt #info Next EOB meeting is scheduled for Thursday, 17 October 2013 at 14:00 Eastern
15:04 gmcharlt #endmeeting
15:04 pinesol_green Meeting ended Thu Sep 26 15:04:04 2013 US/Eastern.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
15:04 pinesol_green Minutes:        http://evergreen-ils.org/meetings/evergr​een/2013/evergreen.2013-09-26-14.01.html
15:04 pinesol_green Minutes (text): http://evergreen-ils.org/meetings/evergr​een/2013/evergreen.2013-09-26-14.01.txt
15:04 pinesol_green Log:            http://evergreen-ils.org/meetings/evergree​n/2013/evergreen.2013-09-26-14.01.log.html
15:04 gmcharlt thanks, everybody!
15:04 kmlussier gmcharlt++
15:04 StephenGWills gmcharlt++ (as usual!)
15:04 RoganH gmcharlt++
15:04 montgoc1 gmcharlt++
15:04 yboston gmcharlt++
15:05 fparks joined #evergreen
15:05 ktomita joined #evergreen
15:05 bshum csharp: For the fedora and ubuntu build slaves, we just have to add the new dependency as jeff noted earlier for Business::ISSN or package libbusiness-issn-perl
15:06 StephenGWills I feel as if I should already know this but if I want to sign up for something on Rogan's website fix queue, how does one gain credentials to effect the change on the website?  is it checked into git? some of these changes look like wp-admin changes?
15:06 bshum @later tell dbs For the debian build slave, can you add the package libbusiness-issn-perl as a new dependency? Thanks.
15:06 pinesol_green bshum: The operation succeeded.
15:08 George_ quit
15:11 csharp bshum: I'll get right on that - thanks
15:11 bshum csharp: Thank you sir :)
15:21 jeffdavis Do you have to be on the oversight board to sign up for its mailing list?
15:22 csharp jeffdavis: nope
15:23 bshum Plenty of lurkers.  I just know I haven't had anything interesting to say on there that I don't just poke a board member directly instead :)
15:23 Dyrcona I lurk.
15:23 jeff the EOB mailing list may be limited to only allow posting by EOB members, but anyone should be able to join.
15:23 Dyrcona I deliberately don't say anything on the list for various reasons.
15:24 csharp okay fedora and ubuntu buildslaves are updated and back to slaving
15:24 bshum csharp++
15:24 Dyrcona csharp++ # our own simon lagree
15:25 Dyrcona All right. I should never compare anyone to Simon Legree, but he's the first slave master that came to mind.
15:25 csharp the EOB list is open, but I think there's a (perhaps unspoken) etiquette to leave posts to current members (in the same way we don't chat off topic during meetings here in IRC maybe?)
15:25 Dyrcona Sorry, csharp.
15:25 * csharp shrugs
15:26 csharp Dyrcona: I'm a bad English major because I had to look that up ;-)
15:26 csharp @blame years of not reading classics
15:26 pinesol_green csharp: Your failure is now complete, years of not reading classics.
15:26 bshum I only know that because of the King and I musical.  My mother loves musicals.
15:27 * Dyrcona is running on fumes and Dr. Pepper.
15:27 * eeevil too, and is all out of Dr. Pepper
15:29 * jeff is all out of bubblegum
15:29 * eeevil is all out of asses
15:29 eeevil that's not true
15:31 csharp @quote random
15:31 pinesol_green csharp: Quote #12: "<pinesol_green> There are 10 quotes in my database." (added by Dyrcona at 05:26 PM, June 07, 2011)
15:31 gmcharlt FWIW, I encourage on-topic feedback from anybody subscribed to the EOB maiilng list
15:31 csharp heh
15:32 csharp gmcharlt++
15:32 gmcharlt it's easy enough for us to notate formal board actions and votes when need be
15:33 gmcharlt though if you're subscribing with the expectation that the topics discussed will uniformly fascinating and exciting ... you might be sorely disappointed ;)
15:36 kmlussier gmcharlt++
15:46 kmlussier gmcharlt: Speak for yourself. I always post enthralling messages to the EOB list.
15:47 gmcharlt kmlussier: you do!
15:51 gsams I'm having an odd issue I was hoping to get some insight on, but it doesn't seem to be a reasonable issue
15:52 gsams without changing anything at all, suddenly one of my libraries is getting no_matchpoint errors on checkouts
15:52 bshum gsams: Whatever it is, it's the library's fault.
15:52 gsams all checkouts
15:52 smyers_ joined #evergreen
15:52 bshum (is my kneejerk reaction)
15:52 gsams I'm not really sure what is going on, everything is in place
15:53 gsams there is even a higher level catch all for their library that it is completely missing
15:53 bshum Could be something minor
15:53 bshum Like a missing flag
15:53 bshum Or an extra flag
15:54 bshum My favorite is always how the "reference" flag gets set to T/F (false by default) in any given rule.
15:54 bshum And sometimes that does weird things if the items themselves are marked NULL for reference flag
15:55 gsams their rules do not appear to be any different than they were, or any different really than anyone else's
15:56 gsams they are active, set to the user level, have the Org Unit set, Circ Modifier, True circulate, a duration rule, a recuring fine rule and a max fine
15:57 mmorgan gsams: Did the library register a new workstation, maybe to the wrong org unit? Just a wild stab ...
15:58 gsams mmorgan: I actually get the same result from my workstation when I am registered to their org unit
16:06 bshum It's always a weird matchpoint issue
16:07 bshum Somehow a weird copy location ID ended up in the default rule in the copy_location column
16:07 bshum Blocking matches cause of course that library wasn't using said copy location.
16:07 bshum I vaguely recall csharp or someone encountering weirdness like that once before.
16:07 bshum Maybe that portion of the GUI is a little buggy
16:08 Dyrcona circ matrix matchpoint editor, buggy?
16:09 bshum Dyrcona: :D
16:09 Dyrcona Actually, I was just going to have a look at the branch on lp 1193487
16:09 pinesol_green Launchpad bug 1193487 in Evergreen "Column picker preferences are not saved in the Circulation Policy Configuration interface" (affected: 2, heat: 12) [Undecided,New] https://launchpad.net/bugs/1193487
16:10 Dyrcona It's the kind of little thing that my hallucinating brain can handle right now.
16:10 b_bonner joined #evergreen
16:11 gsams bshum++
16:16 mmorgan Dyrcona++
16:16 mmorgan 1193487 drives me buggy
16:17 kmlussier mmorgan: Pun intended? :)
16:17 mmorgan ;-)
16:28 frank___ joined #evergreen
16:28 mmorgan We have a large number of rows in action.circulation where stop_fines is CHECKIN and xact_finish is NULL. Doesn't seem right to me. Should they have xact_finish filled in?
16:28 Dyrcona you'd think so, but no.
16:29 Dyrcona Although you might call that a bug, that's pretty much the way it has worked for as long as I remember.
16:29 jeff mmorgan: one normal situation that matches your description would be a circ with some fines that have not yet been paid.
16:29 berick so sad it's faster to google '3m sip' than look at one of the 19 copies of the PDF in my downloads folder.
16:29 jeff mmorgan: that said, there has been a class of bug where even after being paid to zero, some circs will not get xact_finish set -- that's a bug.
16:30 jeff berick: one day you'll get bizarro sip.
16:30 Dyrcona and it was fixed or is about to be fixed?
16:30 berick 1998 SIP
16:30 gmcharlt the intent is that xact_finish gets set to a non-NULL date when all financial obligations for the transaction have been settled
16:30 gmcharlt but yeah, if that is in fact the case for the loans in question, and xact_finish is null, that's a bug as jeff describes
16:31 Dyrcona a propos of sip, I thought of removing the http transport and references to NCIP v1.01 in the code.
16:31 mmorgan So if an item is borrowed, and returned on time, should xact_finish get filled in?
16:31 Dyrcona mmorgan: common sense would say yes.
16:31 berick and manual billings were attached
16:31 berick er, no
16:31 jeff mmorgan: assuming nothing odd like an unpaid rental checkout fee, yes.
16:32 berick and /no/ manual billings
16:36 bshum Dyrcona: I believe we committed that fix for closing transactions as part of some 2.5 thing.
16:37 bshum But I might be misremembering whether we did any sort of backporting of that (doubts it)
16:38 jeff i think that there have been multiple instances of bugs of that class (similar/same symptom, different causes leading up to it), thus there might be others lurking. also, have any of the bug fixes included an upgrade script to "fix" existing data? I'm not even sure how I feel about that, just idly wondered.
16:38 Dyrcona Well, I know I did a branch that fixes at leas some of it, and I vaguely recall it going in.
16:38 bshum https://bugs.launchpad.net/evergreen/+bug/965656
16:38 pinesol_green Launchpad bug 965656 in Evergreen "Close transactions after fines are voided, " (affected: 8, heat: 42) [Medium,Fix committed]
16:38 bshum Which seems to have only been applied to master
16:38 Dyrcona but you're talking to a guy who was staring at a moose in his front yard about half an hour ago, and he's ten miles away from his front yard.
16:38 bshum jeff: I don't think anything did upgrade sql to fix any issues
16:39 bshum Though i think one of these patches is supposed to deal with them if it finds an open xact that should be closed and closes it.
16:39 bshum When retrieved
16:39 bshum (but maybe I'm making things up)
16:39 jeff I'm almost okay with that kind of cleanup being left to a manual recommendation in release notes. Like I said, not sure how I feel about it.
16:39 Dyrcona i seem to recall some changes to the close xact logic, maybe it was that branch, maybe it was another.
16:45 * Dyrcona calls it a day.
16:45 frank___ Hello everybody, Does someone know wich are the sql scripts I have to execute to migrate from 2.3.7 to 2.4.2? because there are some alpha and rc that I dont know if I have to execue them!
16:46 csharp frank___: ignore the alpha and RC scripts and just use the 2.3-2.4.0 one
16:52 frank___ csharp: So Do I have to execute this ones in the order? 2.3.8-2.3.9-upgrade-db.sql,  2.3.9-2.3.10-upgrade-db.sql,  2.3-2.4.0-upgrade-db.sql,  2.3-2.4-supplemental.sh,  2.4.0-2.4.1-upgrade-db.sql,  2.4.1-2.4.2-upgrade-db.sql or just 2.3-2.4.0?
16:58 bshum Actually, you'll want to run supplemental.sh after you do the 2.4.0-2.4.1 I think
16:59 bshum There's some long reingests that happen in the supplemental
16:59 * bshum double checks
17:00 bshum "If upgrading from Evergreen 2.3 or before, now is the time to run Open-ILS/src/sql/Pg/version-up​grade/2.3-2.4-supplemental.sh, which contains additional required SQL to complete your Evergreen upgrade!"
17:00 bshum Which is displayed at the end of the 2.4.0-2.4.1 upgrade
17:00 bshum So that's just an exception.
17:00 bshum Normally you follow the sequential process you've outlined frank___
17:00 frank___ ok ok, per
17:00 frank___ perfect
17:01 frank___ thank for your help
17:01 bshum Just expect it to take some time if you have alot of bib records.
17:07 mllewellyn left #evergreen
17:11 mmorgan left #evergreen
18:16 pinesol_green [evergreen|Dan Wells] Translation updates - po files - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=b4cc2ba>
18:22 egbuilder build #344 of evergreen-master-fedora-18 is complete: Success [build successful]  Build details are at http://testing.evergreen-ils.org/buildbot/bu​ilders/evergreen-master-fedora-18/builds/344
18:52 dMiller joined #evergreen
18:59 pinesol_green [evergreen|Dan Wells] Translation updates - newpot - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=8c7c9ee>
19:01 pinesol_green [evergreen|Dan Wells] Translation updates - fix Finnish translator email - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=a9c36ee>
19:31 jeffdavis I want to shove a bunch of MARC records directly into the database of an EG test server.  Would `marc_stream_importer.pl --spoolfile=$MARCFILE --nodaemon --noqueue` be a good way to do this?  Is there a faster/easier way?
19:34 jeffdavis "a bunch" = 38K records
19:35 pinesol_green [evergreen|Dan Wells] Move 'floating groups' release note docs - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=ee61da7>
20:08 sseng_ joined #evergreen
20:33 jboyer-laptaupe joined #evergreen
20:40 jboyer-laptaupe joined #evergreen
23:22 zerick joined #evergreen

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