Evergreen ILS Website

IRC log for #evergreen, 2015-09-03

| 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:29 bmills joined #evergreen
07:12 jboyer-isl joined #evergreen
07:18 pgardella1 joined #evergreen
07:20 ericar joined #evergreen
08:26 mrpeters joined #evergreen
08:35 mmorgan joined #evergreen
08:39 rjackson_isl joined #evergreen
08:39 krvmga joined #evergreen
08:46 Dyrcona joined #evergreen
08:50 yboston joined #evergreen
08:59 maryj joined #evergreen
09:01 akilsdonk joined #evergreen
09:09 jwoodard joined #evergreen
09:13 Dyrcona joined #evergreen
09:14 Shae joined #evergreen
09:14 Dyrcona Yay for kernel updates.
09:22 krvmga kernel updates++
09:22 * krvmga served under the kernel during the war.
09:29 Dyrcona heh
09:44 sarabee joined #evergreen
09:52 csharp gonna take down the ubuntu and fedora buildslaves for a bit, FYI
09:53 * Dyrcona plans to look into the failing test. I think the test needs adjustment.
10:12 dbwells Dyrcona: I think you are right.  I peeked at it last night, and we just need to remove the 'e's from the sample record in the test.
10:15 dbwells I think the test might also read better if the "have" and "want" were swapped, but maybe that's just me.
10:15 Christineb joined #evergreen
10:20 Dyrcona In case you didn't know: cpan -u takes a long time to run and updates Perl modules installed from packages as well as those installed via CPAN.
10:20 Dyrcona At least on Ubunut 14.04.
10:34 plux_ joined #evergreen
10:38 yboston joined #evergreen
10:45 Dyrcona It even tries to update your Perl....
10:58 mllewellyn joined #evergreen
11:05 Dyrcona Ubunut... Heh.
11:07 csharp @who is the true Ubunut?
11:07 pinesol_green dbwells is the true Ubunut.
11:07 Dyrcona Hrm.... So I installed pgtap package and that usually just puts the pgtap functions in my database, but it didn't do that this time.
11:08 csharp the_true_ubunut++
11:08 tsbere Dyrcona: You can install pgtap similarly to things like hstore....and is it installed on the DB server?
11:09 Dyrcona tsbere: I've never needed to install it on the server. When I've installed it before it was just added to $PGDATABASE, apparently.
11:12 Dyrcona psql -f /usr/share/postgresql/9.1/e​xtension/pgtap--0.90.0.sql seems to have fixed it.
11:26 csharp mmorgan++ # wranglin' dem bugs
11:30 jeff dem bugs, dem bugs...
11:30 csharp fedora and ubuntu buildslaves are back in the mix, FYI
11:30 jeff csharp++
11:33 * mmorgan sighs. Wish I could fix more of 'em!
11:38 bmills joined #evergreen
11:38 Dyrcona Squash ALLTHEBUGS!!!!!!
11:38 jeff step 1: report
11:38 jeff step 2: sqish
11:39 jeff step 2a: revert sqish, use squish instead.
11:45 mmorgan sqish, squish, squash - sometimes all are required :)
11:53 Dyrcona Hmm. I'm starting to wonder if the fix in lp 1484281 was complete....
11:53 pinesol_green Launchpad bug 1484281 in Evergreen 2.8 "authority data may be deleted during propagation with current values of authority.control_set_authority_field" (affected: 1, heat: 10) [Critical,Fix committed] https://launchpad.net/bugs/1484281
11:53 Dyrcona The test still fails after I "fix" it.
11:57 yboston Dyrcona: the deletes are still propagating?
11:57 Dyrcona No, but a test keeps failing.
11:58 yboston which test? one of mine?
11:58 Dyrcona Also, there is a display_sf_list field that should probably be changed, and there is a 111 entry that probably needs the change.
11:58 Dyrcona http://testing.evergreen-i​ls.org/~live/test.22.html
11:59 yboston My understanding is that the $e can stay in the 111 according to cataloging rules; will double check
12:00 yboston for the record, I thought that the display_sf_list was meant to still display the subfields that were found in the auth tag
12:00 yboston and that I would want to display if the $e is actually there, but not authoirty control the $e in the auth tag, but my interpretation of  display_sf_list could ahve been wrong
12:01 yboston I should have confiremed with miker
12:01 jihpringle joined #evergreen
12:01 yboston *confirmed
12:01 yboston I will look over Open-ILS/src/sql/Pg/live_t/08​47.auth_overlay_generator.pg
12:03 Dyrcona Well, I'm not sure what's going on there either.
12:03 Dyrcona I've spent most of the morning wrestling with our servers.
12:03 Dyrcona I'll have a look a deeper look after lunch. I think I'm missing something.
12:06 yboston Dyrcona: OK, would you like me to update the bug in LP?
12:11 yboston Dyrcona: for when you are back from lunch, my notes from my catalogers state that $e should be authority controlled in auth tag 100, and therefore in bib tags 111/611/711 (maybe 811 too)
12:19 bmills joined #evergreen
12:21 yboston Dyrcona: I screwed up my previosu statement s/auth tag 100/auth tag 111/
12:43 gmcharlt yboston: the $e generally should not be authority controlled
12:44 gmcharlt as otherwise one is saying that one needs a separate name authority record for each bibliographic /role/ a person might  have undertaken
12:44 krvmga i'm getting an error in course reserves whenever i click on an item "item_status() takes exactly 2 arguments (4 given)". has anyone run into this?
12:46 krvmga the exception is coming out of Syrup/conifer/plumbing/hooksystem.py in callhook, line 24 ( which is "return f(*args, **kwargs)"
12:47 jeff beware the dreaded kwargs.
12:47 Dyrcona yboston: For fixing the test or anything else that the original patch mixed, I think we want a new bug.
12:47 krvmga jeff: usually i can snickersnack them but now i'm stumped
12:47 Dyrcona **kwargs
12:49 gmcharlt yboston: ah, but upon reading again, yep, the *111* $e is a different beast
12:52 jwoodard why are government sites impossible to navigate?
12:52 jwoodard all I want is population stats!
13:08 mmorgan krvmga: Is this every item, or only some items? Can you share a link, or is a login required?
13:15 krvmga mmorgan: it's every item. you don't need a log in. go to http://rb.cwmars.org/qcc/browse and click on any title
13:17 Dyrcona So, it gets weirder with this test.
13:17 Dyrcona I run the function in the database that pg_prove says is failing and it looks like it outputs what is expected.
13:18 Dyrcona Think I'll copy and paste it to be certain, or is that cheating?
13:19 kbutler joined #evergreen
13:23 dbs Dyrcona: does something else change the state of the db prior to running the failing test, by any chanceÉ
13:23 Dyrcona dbs: Not as far as I know. I'm using concerto for this test.
13:23 dbs ah le clavier Canadienne Multilinguel
13:24 Dyrcona :)
13:25 Dyrcona I did get the test to pass. I'm about to diff the two versions of the test, but I think the changed part is all one line so the difference may not stand out.
13:25 Dyrcona I wonder if field order didn't change some where.
13:25 Dyrcona did/didn't what's the difference?
13:27 Dyrcona Ah....
13:27 Dyrcona xmlns="http://www.loc.gov/MARC21/slim
13:27 Dyrcona The namespace is appearing in every tag now.
13:28 dbwells Dyrcona: I am seeing the same thing.  That's odd.
13:29 yboston gmcharlt: sorry for confusing you earlier
13:30 gmcharlt nah, purely my fault for not reading ALL of the scrollback
13:30 yboston Dyrcona: let me know if I can help with anything
13:31 yboston Dyrcona: I would love to hear miker thouhgts on display_sf_list versus sf_list
13:36 Dyrcona yboston: I don't think there's anything wrong with your change. The test needs to be updated, but I wonder why I'm getting the name space in every xml element.
13:37 yboston OK
13:37 Dyrcona Looking at the source from the failed testing server it is not getting the nameespace in every element.
13:38 Dyrcona I am going to make the change that I originally thought was needed and push it to a branch after making a launchpad bug.
13:38 Dyrcona I am inclined to blame different versions of libxml for the name space change.
13:38 ericar joined #evergreen
13:44 miker yboston: sf_list is meant to be the set of subfields that should 1) constitute a unique heading value (in combination with the thesaurus) and 2) propagate to bibs; dsiplay_sf_list is only meant to be used in browse, for generating headings from authority marcxml that will be displayed to the user in a web page
13:44 mrpeters joined #evergreen
13:44 miker they're separate so that display_sf_list can exclude non-display fields, such as (say) $e on 111 (or, in the past, other tags)
13:45 yboston miker: thanks
13:45 Dyrcona So, $e should be removed from display_sf_list for 100 and 110?
13:47 yboston mike: for clarification, will  display_sf_list get used by the authority MARC editor? I understood from what you wrote as no, because I think the cataloger should be shown if the auth records 100/110 has a $e
13:47 miker however, it looks like authority.simple_heading_set() in the baseline didn't get the fix that went in with 0848
13:48 miker (just as a note)
13:48 miker yboston: in the authority marc editor? I don't know what you mean by that. the marc editor just shows the whole record
13:49 yboston miker: I think we are ont he same page, just makign sure that display_sf_list is not used by the MARC editor when showing an auth record
13:50 miker yboston: showing an auth record in what manner? like, editing an auth record when you go to Manage Authorities?
13:50 yboston miker: but what about the "authority browse" search results?
13:50 yboston miker: yes
13:50 miker the marc editor doesn't do anything with anything that's not the marc record itself in the main editor
13:51 yboston miker: OK, that is what I hoped
13:51 miker it doesn't "hide" anything from the record you're editing
13:51 miker now, what, precisely, do you mean by "authority browse" ... because that's a loaded term ;)
13:51 miker do you mean "browse the catalog" or "manage authorities"?
13:51 yboston miker: thanks, I will be more clear
13:52 yboston miker: I meant "manage authorities", sorry
13:53 miker I don't know what that uses ... dbs, do you recall OTTOYH how manage authorities generates its headings for display to the user?
13:54 yboston miker: thanks for all the feedback, I'll try to check the code myself later on
13:54 yboston BTW, DIG monthly meeting starts in like 5 mins; at 2 PM EST
13:54 miker yboston: so, it looks like it just concatenats all subfields.
13:54 yboston miker: thanks
13:54 miker auth.text += dojox.xml.parser.textContent(dfNode);
13:55 miker where dfNode matched dojo.query("datafield[tag^='1']", node)
13:56 yboston miker: later on I will do some research and then maybe ping you about how display_sf_list is used. I looked at the code for this fix, but was not clear on it
13:57 miker yboston: it's only used in auth-auth linking (and I'm not sure that's correct), "browse catalog", and the baseline authority.simple_heading_set() (but not the upgraded version as of 0848)
13:58 bshum Sigh, not that I want to add more insanity to standing penalty, but does anyone else think having a max holds group penalty might be useful?
13:58 bshum While max holds on the hold matrix is an option, with how crazy our rules matrix is, it can't support a scenario where we want a specific patron group to be denied additional holds after X amount.
13:58 bshum Since we'd have to define that on every hold matchpoint combination.
13:59 ericar joined #evergreen
13:59 Stompro_home joined #evergreen
13:59 yboston miker++ miker++
13:59 tsbere bshum: Should I ever get around to it fallthrough on holds would allow max holds to fall through. >_>
14:00 bshum tsbere: Right, that too...
14:00 alynn26 joined #evergreen
14:00 bshum I was just thinking least painful development.
14:00 yboston #startmeeting DIG Monthly Meeting Evergreen Documentation Interest Group (DIG) Monthly Meeting.
14:00 pinesol_green Meeting started Thu Sep  3 14:00:32 2015 US/Eastern.  The chair is yboston. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00 pinesol_green Useful Commands: #action #agreed #help #info #idea #link #topic.
14:00 pinesol_green The meeting name has been set to 'dig_monthly_meeting_evergreen_documentati​on_interest_group__dig__monthly_meeting_'
14:00 bshum I know how to add more penalty calculation.  I'm not sure tackling fallthrough on holds matrix would be better... :\
14:00 * bshum disappears so that DIG can do without my insanity.
14:00 yboston #info agenda link: http://evergreen-ils.org/dokuwiki/doku.php?i​d=evergreen-docs:dig_meeting_20150903-agenda
14:00 Stompro_home #info Stompro_home is Josh Stompro LARL MN
14:01 Christineb #info Christineb is Christine Burns BC Libraries Cooperative
14:01 yboston #topic Introductions
14:01 yboston #info yboston is Yamil Suarez @ Berklee College of Music - DIG meeting facilitator
14:01 kbutler #info kbutler is Kate Butler, Rodgers Memorial Library
14:01 alynn26 #infor alynn26 is Lynn Floyd, Anderson County Library
14:01 Bmagic #info Bmagic = Blake GH, MOBIUS - Missouri Evergreen
14:03 yboston #topic Updates from Content Coordinators
14:03 yboston I don't think we have any coordinators here now
14:04 yboston will move on, maybe kmlussier can chime in later
14:04 yboston #topic last meeting's action items
14:04 yboston #info 1) kmlussier will complete the marc stream importer work and check on the status of the RDA docs
14:04 yboston will postpone for next meeting...
14:04 yboston #action kmlussier will complete the marc stream importer work and check on the status of the RDA docs
14:05 yboston #info 2) Stompro will create LP bug for teaching the release notes creation bacth file(s) to handle .adoc file suffuxes
14:05 yboston this was done
14:05 yboston any comments/questions?
14:05 Stompro_home lp 1482336
14:05 pinesol_green Launchpad bug 1482336 in Evergreen "create_release_notes.sh include .adoc files" (affected: 1, heat: 6) [Undecided,New] https://launchpad.net/bugs/1482336
14:05 alynn26 yea! now i do not have to remember to change the file extension:
14:06 kbutler stompro_home++
14:06 yboston regretfully I think the code still needs to be updated for the release ntoes creations cript?
14:06 alynn26 stompro_home++
14:06 yboston *script
14:07 alynn26 one step at a time
14:07 yboston yes
14:07 yboston shoudl I move on?
14:07 yboston moving om
14:07 yboston #info 3) remingtron will continue testing conversion of all .txt files to the .adoc extension
14:08 yboston will postpone, because I am not sure if he is around today/now
14:08 yboston #action remingtron will continue testing conversion of all .txt files to the .adoc extension
14:08 yboston #info 4) kmlussier will send out an email to DIG list to request updates on unfinsished 2.8 new features
14:08 yboston this was done
14:08 yboston kmlussier++
14:09 alynn26 kmlussier++
14:09 yboston which leads to the next past action
14:09 yboston #info 5) kmlussier will follow up with direct emails to request updates on unfinsished 2.8 new features or to ask for works in progress
14:09 yboston not sure if kmlussier did this yet
14:09 yboston did anyone get a direct email?
14:09 kbutler I did not, but I had been at the meeting.
14:10 yboston good
14:10 alynn26 I didn't but i was not expecting one
14:10 kbutler (I put links to my stuff on the wiki earlier today, so am now actually done)
14:10 yboston kbutler++
14:10 alynn26 kbutler++
14:10 yboston #info here is the link to the 2.8 needs http://evergreen-ils.org/dokuwiki/d​oku.php?id=evergreen-docs:2.8_needs
14:11 yboston kbutler: do you mind sending an email to the DIG list anouncing that you shared your work with us?
14:12 kbutler yboston: sure, I can do that.
14:12 yboston that email will serve as a reminder for me, or somene else, to push it into the docs
14:12 remingtron #info remingtron is Remington Steed, Hekman Library (Calvin College)
14:12 yboston for now I will postpone kmlussier action item
14:13 remingtron (sorry so late)
14:13 yboston ¡¡¡¡¡hooolaaa!!!!
14:14 yboston remingtron: I already covered your action item about testign out the new suffix
14:14 yboston I just posponed it for next time
14:14 remingtron yeah, I haven't done anything with it, so I'm glad you postponed it
14:14 yboston did you have any updates, or just stick to it being postponed?
14:14 yboston cool
14:14 yboston should I move on?
14:14 remingtron sure
14:15 yboston #action kbutler will send an email to the DIG list anouncing she posted her 2.8 work for a DIG memebr to add to docs?
14:15 yboston darn, missed the question mark
14:16 yboston BTW, anyone here with some 2.8 docs in progress, please send your partial work to the DIG list
14:16 Stompro_home I started adding links to my in progress work for the older items I'm commited to work on.  After the discussion at the last meeting.
14:17 remingtron Stompro_home++ #sharing your work
14:17 yboston Stompro: do you mind sumarizing your link edits to the DIG list
14:17 yboston I hope it helps to foster collaboration
14:18 Stompro_home Sure, I will do that.
14:18 yboston #action Stompro will send a list to DIG list summarizing the 2.8 docs work he has so far shared
14:19 yboston let me quickly postone my one task
14:19 yboston #action yboston will move the undocumented content of the 2.8 new feature “TPAC Discoverability Enhancements” to its own section in the docs
14:19 pinesol_green [evergreen|Jason Stephenson] LP#1491962 Fix 0847 Live Test - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=12a4f8d>
14:19 yboston my bad, did not get to it, did get good feedback from DIG at last meeting
14:20 remingtron when we're ready, I want to add an item to the agenda
14:20 yboston yes, go ahead
14:20 remingtron documenting Evergreen 2.9 new features
14:21 remingtron I haven't thought about it at all, but 2.9 RC is out and that means 2.9.0 is soon!
14:21 yboston remingtron++
14:21 Stompro_home remingtron++ I was wondering about that also.
14:21 remingtron #link http://evergreen-ils.org/documentatio​n/previews/RELEASE_NOTES_2_9_RC.html
14:22 remingtron there's the release notes, which should include all the new features
14:22 yboston one thing we need is to create the 2.9 new features DIG wiki page
14:22 remingtron I can do that today
14:23 yboston we probably also need to see if we can schedule a hackfest to document new features
14:23 yboston remingtron++
14:23 yboston #action remingtron will create the 2.9 new features needing docs wiki page
14:23 remingtron DIG hackfest always helps make progress
14:24 yboston remingtron++
14:24 yboston we can send out a doodle poll to try to narrow down possible dates/times
14:24 alynn26 remingtron++
14:24 yboston any volunteers to create a doodle poll?
14:24 yboston you get to come up with dates/times tht work for you, you get to decide tie brakers :)
14:25 jihpringle I can do it if you give me a general sense of when we want to do it
14:25 yboston (sorry for my spelling/grammar when I type fast)
14:25 yboston jihpringle++
14:26 akilsdonk_ joined #evergreen
14:26 alynn26 Approximently when do we want to do this?
14:26 yboston let me look over the calendar
14:27 yboston is it me, or have we often ended up doign things on Fridays?
14:27 kbutler I think that is true.
14:27 yboston for the record, EG 2.9.0 is currently scheduled to be released on September 16th
14:27 alynn26 The hackaway is Nov 4th-6th.
14:28 yboston alynn26++
14:28 remingtron I'm game to try a DIG hackfest before the 16th
14:28 yboston me too
14:28 remingtron to keep the spirit of "document everything before it's released"
14:28 yboston remingtron++
14:28 Stompro_home There is the angularjs hack day on the 17th also to think about.
14:28 remingtron Stompro_home: good reminder
14:28 alynn26 remingtron++
14:29 jihpringle I'll put out a poll today with dates for the next two weeks
14:29 remingtron jihpringle: that's sounds great
14:29 yboston darn, I somehow missed the note on when angular day was
14:29 yboston was it on the dev list? or just on IRC?
14:29 remingtron yboston: just during a dev meeting, I think
14:30 yboston remingtron++
14:30 yboston darn, I have been attending those
14:30 * Dyrcona will add Angular day to the calendar.
14:30 yboston so jihpringle are you all set?
14:30 yboston Dyrcona++
14:30 jihpringle yes
14:30 yboston merci
14:31 alynn26 jihpringle++
14:31 Stompro_home jihpringle++
14:31 yboston #action jihpringle will create a doodle poll for scheduling a DIG ahckfest for 2.9 features
14:31 yboston remingtron: BTW
14:31 remingtron jihpringle++
14:31 yboston remingtron: did you plan to moe the pre 2.8 feature list from the 2.8 page and move it to the new 2.9?
14:31 yboston just curious
14:32 yboston *move
14:33 yboston any other comments or questions about 2.9?
14:34 remingtron yboston: yes I'll move all old undocumented stuff to the new 2.9 page
14:34 remingtron including incomplete 2.8 stuff
14:34 yboston ahh
14:34 remingtron so each new 2.X page becomes the new master docs needs page
14:34 yboston very nice
14:34 remingtron until we find a better way :)
14:34 yboston :)
14:35 alynn26 :)
14:36 yboston we are just past the 30 minute mark, did we want to stay on 2.9 or move to old busniess?
14:36 yboston we can talk about web client docs; re-org
14:36 Stompro_home the 2.8 page is dead, long live the 2.9 page.
14:36 yboston Stompro++
14:36 yboston we can also tackle something new
14:37 remingtron I'll email the DIG list once the 2.9 page is live, and I'll request that everyone consider working on one before hackfest day to start momentum
14:37 remingtron thoughts?
14:37 yboston remingtron: I was going to mention something like that about starting early
14:37 yboston at least for those that may not be able to make the date
14:37 yboston remingtron++
14:37 Stompro_home Sounds good to me.
14:37 alynn26 That works for me.
14:38 yboston before I forget, let me repeat somethign we talked about last meeting
14:38 remingtron and I'd recommend making 2.9 stuff the top priority, then continuing with 2.8 and older stuff
14:38 yboston remingtron++
14:38 yboston when we do a DIG hackfest, we need to make sure we share our works in progress
14:38 yboston at the end of the session
14:39 yboston makes it easier to finish loose ends later on
14:39 alynn26 yboston++
14:39 remingtron yboston: yes! thanks for repeating!
14:39 remingtron yboston++
14:39 kbutler yboston++
14:40 yboston muchas gracias
14:40 yboston let me repaste the meetbot "ideas" from last meeting
14:41 yboston #idea encourage volunteers to submit links to their works in progress on the relevant DIG wiki page
14:41 yboston #idea possible palces to store works in progress to allow linking back to content include: dropbox, Google docs/drive, Github forks, Github Gists
14:41 yboston #idea come up with guidelines/suggestions for how to store works in progress or finsished work for DIG to access later on
14:41 yboston #idea always ask volunteers to share works in progress at the end f DIG hackfest or DIG hack-a-ways
14:42 yboston remingtron: did I give you an action item for the 2.9?
14:42 yboston I see it now, I did
14:43 yboston any other comments or questions?
14:43 jihpringle for the hack-a-way anyone hosting onsite or entirely online?
14:44 yboston jihpringle: oops, that is a key question
14:44 alynn26 i would say online with the short turnarround.
14:45 yboston I have hosted before in Boston, but that of course is not convinient for most folks
14:45 jihpringle I've sent out the poll so that info will go in a follow up when the date is announced on Tuesday
14:45 remingtron I can't dedicate a whole day, so I'll be online
14:46 yboston I agree with alynn26, with this short notice it will probably have to be online
14:46 jihpringle anyone in the eastern timezone willing to host the hangout or whatever we want to use?
14:46 yboston dependign on the date that we vote on I can try to book a confernece room here
14:46 yboston I can host one
14:47 jihpringle I'll let email you Tuesday morning with the chosen date and we can send a follow up email to the list with connection details
14:48 kmlussier #info kmlussier is Kathy Lussier, MassLNC (extremely late!)
14:48 yboston ¡¡¡hooolaaaa!!!!
14:48 alynn26 WElcome
14:48 kmlussier Hi!
14:48 remingtron FYI, Monday is an American holiady (Labor Day), so many folks won't be at work
14:49 yboston good point
14:49 remingtron (this Monday, Sept 7)
14:49 Christineb it is a Canadian holiday as well :D
14:49 * kmlussier will be at the beach, but can try documenting from there. :)
14:49 jihpringle I said to the by Monday incase anyone ended up doing the poll on the weekend
14:49 alynn26 Yeah, that going to work.
14:49 jihpringle otherwise everyone has to complete the poll tomorrow
14:50 remingtron jihpringle: sounds good
14:51 yboston good
14:51 yboston so, to recap
14:52 yboston 1) we already have a 2.9 hackfest poll out
14:52 yboston jihpringle++
14:52 yboston 2) we will soon have a 2.9 docs needed wiki page
14:52 yboston with 2.9 features as the priority
14:53 yboston 3) we have folks that have shared their 2.8 works in progress
14:53 yboston kbutler++ Stompro++
14:53 remingtron #link http://evergreen-ils.org/dokuwiki/d​oku.php?id=evergreen-docs:2.9_needs
14:53 yboston remingtron++
14:53 yboston which means we can start signing up for 2.9 taks early
14:54 * kmlussier quickly grabs edit rights on the page so that she can volunteer for conditional negative balances.
14:54 yboston also, if you make any progress, please preemptively share your work and label the feaure as yours
14:54 * remingtron trips over kmlussier's edit rights
14:54 yboston kmlussier++
14:55 yboston BTW, during the hackfest we can try to sneak in talk about re-org and web client docs
14:55 kmlussier remingtron: It's all yours
14:55 yboston we are down to 5 mins
14:55 yboston any final questions or comments
14:55 remingtron yboston: none from me
14:56 kmlussier I have something
14:56 yboston go ahead
14:56 kmlussier I need to scale back on some of my community commitments this year. Therefore, I think it's best if I step down as DIG release coordinator. I'll still be active in DIG, but I need to reduce some of my commitments.
14:57 yboston thanks for the update
14:57 kmlussier It's a great role for somebody to take if they are familiar with documentation and also stay up to date with new features and bug fixes going into Evergreen.
14:57 yboston we will need to find a replacement, even if it takes mreo than one person
14:57 yboston to equal you :)
14:58 kmlussier Ha!
14:58 yboston we need like 2 developers and at least one librarian
14:58 kmlussier One thing I need to do is document what I've done with this role to make it easier for somebody to do it. And then, of course, they can expand upon it. :)
14:59 remingtron kmlussier: yes please!
14:59 yboston shoudl I give you an action item?
14:59 kmlussier If nobody volunteers, I also have some specific people in mind that I can reach out to.
14:59 kmlussier yboston: Sure, go ahead.
15:00 yboston #action kmlussier will document the general wokflow for being DIG release coordinator
15:00 yboston BTW, we are at the 1 hour mark
15:01 yboston I can go a bit longer, or we may want to stop here for now?
15:01 yboston OK, I vote to end now
15:01 remingtron yboston: +1
15:01 alynn26 +1
15:02 jihpringle +1
15:02 yboston kmlussier:  you can mention your stepping down on the list to see if anyone wants to volunteer
15:02 kmlussier yboston: OK, will do
15:02 yboston #action kmlussier will send email to list about stepping down as release coordinator; and will ask for volunteer replacement
15:03 yboston OK folks, will wrap up in a 10 seconds unless there is any final commetns/questions
15:04 yboston #endmeeting
15:04 pinesol_green Meeting ended Thu Sep  3 15:04:04 2015 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/2015/evergreen.2015-09-03-14.00.html
15:04 pinesol_green Minutes (text): http://evergreen-ils.org/meetings/evergr​een/2015/evergreen.2015-09-03-14.00.txt
15:04 pinesol_green Log:            http://evergreen-ils.org/meetings/evergree​n/2015/evergreen.2015-09-03-14.00.log.html
15:04 remingtron yboston++
15:04 alynn26 yboston++
15:05 jihpringle yboston++
15:05 yboston muchas gracias
15:06 sarabee joined #evergreen
15:12 Dyrcona yboston: I added AngularJS day to the community calendar.
15:13 Dyrcona I also updated the developers' meetings page on Dokuwiki with the info from yesterday's meeting: http://evergreen-ils.org/doku​wiki/doku.php?id=dev:meetings
15:19 yboston Dyrcona: gracias
15:20 Dyrcona Would it help with documentation if we forked the rel_2_9 branch today?
15:21 yboston I think DIG can wait
15:21 yboston for example, anything we want to any aorudn now would need to be both in master and 2.9
15:21 Dyrcona I was thinking of forking it today anyway for other reasons.
15:21 yboston I assume dyou would say that
15:22 yboston I would defer ont his to do what ever is easier on you
15:22 Dyrcona ok. that makes sense. :)
15:22 yboston or what helps you out more
15:22 Dyrcona I'll fork it later.
15:22 kmlussier yboston: I'll make sure the community demo server is updated in time for the DIG hackfest.
15:22 kmlussier yboston++
15:22 yboston kmlussier++
15:23 kmlussier Forgot to give karma at the end of the meeting. :)
15:23 Dyrcona dig++
15:23 alynn26 kmluaaiwe++
15:23 alynn26 kmlussier++
15:26 bshum yboston: Is rsoulierre still the primary contact for the docs server itself?  I just wonder who has to be told to add a page for 2.9 when rel_2_9 is cut by Dyrcona.
15:26 bshum cut/branched
15:27 yboston bshum: that server is solely controlled by him, it is owned by his institution
15:27 bshum yboston: That's what I figured, just checking.
15:27 yboston bshum: very good question
15:27 bshum So someone will have to email him to ask him to add the appropriate setup for that, gotcha.
15:28 yboston yes
15:28 yboston he has mentioned that the server is not very powerful, another reason that havign a community owned docs server will increase personall redundancy
15:28 yboston and we might be able to run the doc parsing more than once a day
15:28 yboston etc
15:50 pinesol_green [evergreen|Bill Erickson] LP#1465847 Empty patron search exits early - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=12a3f5b>
16:03 jlitrell joined #evergreen
16:24 Bmagic Anyone out there use metarecord holds primarily? We defaulted our OPAC to have group formats turned on.
16:31 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
16:31 Dyrcona "And there was much rejoicing."
16:32 bshum Huzzah
16:37 dbs Dyrcona++
16:38 Bmagic Dyrcona++
16:42 Dyrcona kmluaaiwe++
16:42 Dyrcona home_keys-- ;)
16:45 kmlussier Ha ha. Maybe I should change my nick.
17:09 bmills joined #evergreen
17:18 gsams I apologize if I butcher your last name at the next conference, but it will almost certainly be in reference to that.  That was fantastic.
17:22 mmorgan left #evergreen
18:00 jeff Bmagic: that sounds like an excellent way to find all the metarecord bugs. :-)
19:33 akilsdonk joined #evergreen
19:49 akilsdonk_ joined #evergreen
19:55 akilsdonk joined #evergreen
19:56 dcook joined #evergreen
20:34 bmills joined #evergreen
22:33 ningalls joined #evergreen
22:50 ningalls joined #evergreen
23:16 bmills joined #evergreen
23:17 ningalls joined #evergreen
23:26 sbrylander joined #evergreen
23:32 sarabee joined #evergreen
23:38 ningalls joined #evergreen

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