Evergreen ILS Website

IRC log for #evergreen, 2015-12-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:30 dcook joined #evergreen
07:51 ericar joined #evergreen
08:03 mrpeters joined #evergreen
08:07 collum joined #evergreen
08:52 mmorgan joined #evergreen
08:57 Dyrcona joined #evergreen
08:59 drigney joined #evergreen
08:59 phasefx_ joined #evergreen
09:00 miker joined #evergreen
09:02 akilsdonk joined #evergreen
09:02 jyorio_ joined #evergreen
09:03 collum joined #evergreen
09:25 maryj joined #evergreen
09:58 dbs kmlussier++
09:58 kmlussier dbs: Thanks! What did I do to deserve that?
10:00 dbs your comment about Evergreen meetings being fun, and all of your meetings being about Evergreen
10:01 yboston joined #evergreen
10:01 kmlussier heh
10:03 kmlussier Facebook memories tells me that three years ago today dbs, rsoulliere, Lindsay Stratton and I were arriving at the Googleplex.
10:04 lualaba joined #evergreen
10:04 lualaba hello wss://localhost:8443/hatch' failed:  (port is opened ) any idea?
10:04 lualaba WebSocket connection to 'wss://92.241.95.30:7682/o​srf-websocket-translator' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED
10:06 rjackson_isl joined #evergreen
10:07 berick lualaba: port is open for me too.  that looks like apache is not accepting the request.  i suggest looking at /var/log/apache2-websockets/error.log
10:07 berick and access.log (in same directory)
10:07 berick on the server
10:08 lualaba ok i wiil check and second issue?
10:08 berick second issue?
10:08 berick ohh
10:08 berick you can ignore the /hatch error
10:08 berick that's not really a problem
10:09 lualaba ok thank you. i will check
10:16 jwoodard joined #evergreen
10:17 lualaba_ joined #evergreen
10:17 lualaba_ how to configure apache websocj=kets any documenation?
10:18 berick lualaba: http://evergreen-ils.org/documentati​on/install/OpenSRF/README_2_4_1.html
10:18 berick 14. Optional: Websockets installation instructions
10:24 lualaba_ no any errors in log  other_vhosts_access.log. websocket.log not exist
10:36 dbs kmlussier: oh, that was a good investment of time!
10:38 kmlussier dbs: Yeah, but I wish we could do more of those on our own. So many things, so few tuits.
10:38 dbs indeed :/
10:41 lualaba_ joined #evergreen
10:41 lualaba_ Fixed problem with websockets, after configuration, Thank you
11:14 vlewis joined #evergreen
11:25 Christineb joined #evergreen
11:35 graced joined #evergreen
11:41 Stompro Hello all, if I'm trying to figure out why cancellations in EDI responses from B&T are not getting registered, where should I start looking?  The response does get registered with the PO, but the line items doen't get canceled.  I'm looking at the edi_fetcher.pl to try and see where it sends the response.
11:43 bmills joined #evergreen
11:43 berick Stompro: EDI.pm / process_parsed_msg() is where the action happens
11:44 berick see also cancel_lids()
11:45 berick though, by the time cancel_lids() is called, the logic of determining if something should be canceled has already happened
11:48 maryj joined #evergreen
11:49 Stompro Thanks berick
11:50 tsbere_ joined #evergreen
11:51 sciani joined #evergreen
12:16 yboston joined #evergreen
12:42 jihpringle joined #evergreen
13:09 Christineb joined #evergreen
13:43 csharp okay, I'm working on bug 1413352 and I can now see that on a stock master install, the estimated_unit_price is not being populated in acq.lineitem during acq marc ingest
13:43 pinesol_green Launchpad bug 1413352 in Evergreen "New Brief Record estimated price does not populate" [High,Confirmed] https://launchpad.net/bugs/1413352
13:44 csharp I'm now trying to figure out when that *should* be happening
13:54 berick csharp: for brief records in particular, the problem is they are created via the open-ils.acq.lineitem.create API, which does not appear to extract price info from the record
13:55 berick it looks like ingested records should be setting the price, though
13:56 csharp berick: I was just working on a theory of the problem resting between "price" and "estimated_price" in the lineitem marc attrs
13:57 berick csharp: ah, that could be it
13:57 berick csharp: btw, hyperion.. awesome.  read for 3 hrs last night w/o hardly blinking.
13:58 csharp berick: great!  glad you're enjoying it as much as I did
14:00 Dyrcona Ah, the sci-fi Canterbury Tales. :)
14:01 yboston hello, the DIG monthly meeting will start in a few moments
14:01 berick Dyrcona: yes, good comparison
14:01 yboston #startmeeting DIG Monthly Meeting Evergreen Documentation Interest Group (DIG) Monthly Meeting.
14:01 pinesol_green Meeting started Thu Dec  3 14:01:51 2015 US/Eastern.  The chair is yboston. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:01 pinesol_green Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:01 pinesol_green The meeting name has been set to 'dig_monthly_meeting_evergreen_documentati​on_interest_group__dig__monthly_meeting_'
14:02 yboston The agenda can be found here http://wiki.evergreen-ils.org/doku.php?id=​evergreen-docs:dig_meeting_20151203-agenda
14:02 yboston #topic Introductions
14:02 yboston Please feel free to start introducing yourselves...
14:02 yboston #info yboston is Yamil Suarez @ Berklee College of Music - DIG meeting facilitator
14:02 Christineb #info Christineb is Christine Burns BC Libraries Cooperative / Sitka
14:02 jihpringle #info jihpringle is Jennifer Pringle BC Libraries Cooperative / Sitka
14:04 yboston looks like we might have a small crowd today?
14:04 kmlussier #info kmlussier is Kathy Lussier, MassLNC
14:04 dbs #info dbs is Dan Scott, Laurentian University
14:05 kmlussier Sorry, I was making my lunch.
14:05 dbs (but only one eye on IRC)
14:05 yboston we have 5 and a half present. Should I proceed?
14:06 kmlussier sure
14:06 yboston OK
14:06 yboston #topic previous meeting action items
14:06 yboston #info 1)need a volunteer to complete the marc stream importer work and check on the status of the RDA docs
14:07 maryj #info maryj is Mary Jinglewski, Equinox Software
14:07 yboston unless someone here is ineterested int aking this action item I will move on
14:07 kmlussier yboston: We have a volunteer for the marc stream importer work. I just need to follow up with him.
14:08 yboston kmlussier: should I retire the action item for now?
14:08 Stompro_home joined #evergreen
14:08 kmlussier sure
14:08 yboston OK
14:08 yboston moving on
14:08 yboston #info 2) jihpringle will research the state of missing RDA content
14:09 yboston jihpringle: anything to add? should I just postpone until next meeting?
14:09 jihpringle sorry, we've had a crazy busy few months and I haven't had any time
14:09 yboston I wil postpone then
14:09 jihpringle I should have more time in the next month or so
14:09 yboston #action jihpringle will research the state of missing RDA content
14:10 yboston #info 3) yboston will check that kbutler recently shared work has been pushed to the repo
14:10 yboston done
14:10 yboston moving on
14:10 yboston #info 4) Codey Kolasinski of C/W MARS has volunteered to work with kmlussier on the MARC stream importer docs
14:10 yboston kmlussier: this is what you meant. should I just defer?
14:11 yboston I wil postpome it for now
14:11 kmlussier Yes, I'll see Codey next week
14:11 yboston #action Codey Kolasinski of C/W MARS has volunteered to work with kmlussier on the MARC stream importer docs
14:11 yboston #info 5) yboston will move the undocumented content of the 2.8 new feature “TPAC Discoverability Enhancements” to its own section in the docs
14:11 yboston needs to be deffered
14:12 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:12 yboston #info 6) kmlussier will document the general workflow for being DIG release coordinator
14:12 kmlussier Defer for now, but I plan to do it before the next point release goes out.
14:12 yboston OK
14:12 yboston #action kmlussier will document the general workflow for being DIG release coordinator
14:13 yboston #info 7) jihpringle will send out an email to the list to ask DIG members to sign up for pending 2.9 new features
14:13 yboston jihpringle: anything to add? should I just defer until next meeting?
14:13 yboston or maybe this happned?
14:13 jihpringle didn't I do that ahead of the DIG hackaway?
14:14 yboston you might have, I just don't rember
14:14 yboston *remember
14:14 yboston I'll take you word
14:14 jihpringle joined #evergreen
14:14 yboston I can move on
14:15 yboston #info 8) alynn26 will write to the DIG list to start discussion on DIG priorities before the next release in March
14:15 yboston since she is not here, I will defer
14:15 yboston #action alynn26 will write to the DIG list to start discussion on DIG priorities before the next release in March
14:16 yboston that is the end of the previous action items
14:16 jihpringle yboston: I just checked and the 2.9 email definitely went out ahead of the DIG hackaway so that can be marked as complete
14:16 yboston jihpringle: nice
14:17 yboston I see soem items int he "new business" section for this meeting
14:17 yboston #topic new business
14:17 yboston #info 1) Decide on January meeting date
14:18 yboston I will be flying around our usual meeting time
14:18 yboston we need to pick a differnt date or have a sustitute facilitator
14:18 yboston *substitute
14:19 yboston I can set up a doodle poll the first week of janaury
14:19 yboston *January
14:19 kmlussier A different date is okay with me.
14:19 jihpringle me too
14:20 Christineb me too
14:20 yboston #action yboston needs to create a doodle poll and share it with the list to pick a date/time for January DIG meeting
14:21 yboston #info Should we plan to have a web docs hackfest?
14:21 yboston sorry, that shoudl have said "web clients" doc
14:22 maryj No time like the present to start.
14:22 kmlussier Yes, I think we should try to get the web client circ docs into good shape for the 2.10 release.
14:22 yboston I am all for it
14:22 yboston coudl I get a volunteer to set up a doodle poll?
14:22 jihpringle I can do that
14:23 kmlussier I also started reviewing the docs Michelle Purcell submitted a while back so that those can be merged into master.
14:23 yboston jihpringle: thanks
14:23 jihpringle I'm assuming late January/February if 2.10 is scheduled for March
14:24 yboston yes
14:24 yboston I was just thinking that
14:25 eady joined #evergreen
14:25 yboston any thoughts from those here of when we shoudl shoot for the hackfest? or should we make the poll broad enough to see which of the two months works better for for folks?
14:26 kmlussier Could we shoot for January? Then, if there is still work to be done, we have more time to schedule another one if we need to.
14:26 maryj I agree with kmlussier. Always good to have some time to followup after a hackfest.
14:26 kmlussier I could take an action item to review/update the existing wiki page at http://wiki.evergreen-ils.org/dok​u.php?id=evergreen-docs:webclient
14:26 yboston kmlussier: OK
14:27 yboston lets shoot for January
14:27 jihpringle I'd prefer February over January - January is already mostly full for us
14:27 yboston #action jihpringle will carete a doodle poll for scheduling a web clients doc hackfest to happen in January
14:28 yboston jihpringle: two options
14:28 maryj suggested compromise: doodle poll for late Jan/early Feb?
14:28 yboston jihpringle: 1) make the poll cover both January and february and let the majority rule
14:29 maryj yboston++
14:29 jihpringle that works for me
14:29 yboston jihpringle: 2) I can make myself avialbale to assi your folks to have a secong mini hackfest in february
14:29 yboston *assist
14:29 jihpringle option 1 sounds good
14:29 jihpringle I'm assuming we're looking at an all day event?
14:30 jihpringle but thanks for the offer yboston
14:30 yboston let's shoot for an all dat event, but of course folks may only be able to give a hlaf day or a few hours
14:31 bmills joined #evergreen
14:31 yboston the we shoudl plan for another hackfest to prep for the 2.10 release sometime in March
14:32 yboston any comments or questions related to this topic or in genreal?
14:32 jihpringle do we want to poll for a date for the 2.10 hackfest now as well?
14:33 yboston maybe not, since I am not sure if the date will slip
14:33 yboston #action kmlussier will update the wiki page for web client docs
14:33 yboston but we can decide that as a group if we want to start planing that hackfest
14:34 yboston let me look up the release date on the community calendar
14:35 kmlussier I don't think the 2.10 dates are on the calendar yet.
14:35 yboston BTW, looks like the calendar is not showing up on this page https://evergreen-ils.org/communicate/calendar/
14:35 yboston kmlussier: thanks
14:35 yboston so in that case I humbly suggest that we wait to plan that hackfest
14:36 yboston kmlussier: usually we can start documenting by the beta release? (I can never remember)
14:36 kmlussier The dates are in the bottom of this email http://markmail.org/message/bbdo7pf4ersxpqrb
14:36 yboston kmlussier: also, let me know if you want help with testing the documentation for docs release manager
14:36 kmlussier yboston: Yes, beta is new feature cutoff, so we can start documenting then.
14:37 yboston #link  http://markmail.org/message/bbdo7pf4ersxpqrb
14:37 yboston Schedule
14:37 yboston -------------------------------------
14:37 yboston * 5 February 2015: feature slush - at this point in the release, all
14:37 yboston significant feature branches should have LP bugfixes and pull
14:37 yboston requests. I would reserve the right to bump any new feature branches
14:37 yboston that come in after this date to the fall 2016 release.
14:37 yboston * 19 February 2015: feature freeze - no non-bugfix patches to be pushed
14:37 yboston * 25 February 2015: beta release
14:37 yboston * 10 March 2015: release candidate
14:37 yboston * 17 March 2015: 3.0.0 released
14:38 yboston to recap...
14:38 yboston we have convered plans for web client docs, we started thinking of 2.10 new features
14:39 yboston another general topic that matters is thinking about a docs reorganization when we have time
14:39 yboston we might need to have samples of reorg docs ready to further that discussion
14:39 yboston which we don't have right now
14:40 yboston any comments or questions on this or any topic?
14:40 maryj yboston, may I ask in what way might the docs be reorganized?
14:40 yboston maryj: excellent question
14:40 yboston here is the link for that project
14:40 yboston #link http://wiki.evergreen-ils.org/doku​.php?id=evergreen-docs:reorg_2014
14:40 maryj thank you, yboston!
14:41 yboston there has been a desire to reorganize the docs for various reasons
14:41 yboston one common reason is to split the docs to have parts meant for server admins versus front line staff
14:42 yboston some want to split the docs so that we have sections just for highly techinical unix/DB system adminsitrators versus Evergreen adminstrators
14:43 sciani left #evergreen
14:43 yboston hope this makes some sense so far
14:44 maryj yboston, it makes total sense. Seems to be the #1 request when I'm visiting EG libraries - break it down by role.
14:44 jihpringle maryj there are a few suggestions here: http://wiki.evergreen-ils.org/doku.php​?id=evergreen-docs:reorg_2014:comments
14:44 maryj jihpringle++
14:44 jihpringle that page is linked to the one yboston posted
14:45 yboston jihpringle++
14:46 yboston we might want to plan another meeting just to talk about re-organization in 2016
14:46 maryj I don't have any further questions about the reorg except may if there is interest in establishing a timeline for this?
14:46 maryj Has anyone thought about including this as an Evergreen conference panel/informal meeting/etc?
14:47 jihpringle I think it would be a good topic for the conference
14:47 maryj Definitely.
14:48 yboston I was thinking that we spend an hour during the conference docs hackfest on it (if not more time than that)
14:48 jihpringle yboston ++
14:48 maryj yboston - you may need to bring some sticky notes.....
14:48 maryj yboston++
14:49 yboston #idea meet about docs reorganization during DIG hackfest at next conference
14:49 jihpringle it may also be an idea to tie the re-org to the web client docs
14:49 jihpringle since we're going to be editing most of the content anyways
14:49 yboston jihpringle: wow, that is a great idea
14:51 kmlussier I think the key is to create the docs in small enough chunks so that they can be easily reorganized at any time.
14:51 yboston I wil make this an action item, to keep discussing using the web client docs as an excuse to think about/try a docs re-org
14:51 kmlussier Or you could organize them in a couple of ways at the same time.
14:52 yboston #action yboston will add agenda item fro discussing docs re-org tied to web cleint docs
14:52 maryj I wonder if a tag heirarchy could be implemented for each small chunk of documentation so you could remix them into the different types of organizing that kmlussier is talking about....
14:53 phasefx just curious, is it easy to do "Did you know?" style sidebars, etc. with asciidoc
14:53 yboston maryj: I am not 100% sure what you mean by "tag heirarchy"
14:54 maryj Heirarchy might be a wrong term; better term might be "controlled vocabulary" for the tags.
14:54 maryj ^yboston
14:54 yboston maryj: though with AsciiDoc we can create smoll docs files that we include in the main docs. There shodl not be an issue in puling the same content twice. For exmaple, if we are mocking up experiments
14:55 kmlussier phasefx: You can do admonition blocks. Not sure it's really the same thing.
14:55 maryj yboston: okay! No worries, whatever is simpler. :)
14:55 kmlussier Hey, look, they have something called sidebar blocks. Never tried that. http://www.methods.co.nz/a​sciidoc/chunked/ch16.html
14:56 phasefx kmlussier: that looks similar to what I had in mind, at least one of the examples in their documentation.  Was musing use of those for more technical tidbits
14:57 phasefx An Example Sidebar
14:57 yboston phasefx: technical tidbits have always been a concern
14:57 kmlussier phasefx: I sometimes use the TIP admonition block for "Did you know?" type things.
14:58 yboston BTW, we are basically at the 1 hour mark
14:58 yboston we should start wrapping up soon
14:58 maryj Are there further new business items, yboston?
14:59 yboston no more new busniess
14:59 yboston *business
14:59 yboston any final questions or comments on this or any other topic?
15:00 maryj nope; will be mulling things over until the next meeting
15:00 yboston Ok folks, thanks for coming
15:00 yboston jihpringle++
15:00 yboston (for your volunteering)
15:01 yboston #endmeeting
15:01 pinesol_green Meeting ended Thu Dec  3 15:01:00 2015 US/Eastern.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
15:01 pinesol_green Minutes:        http://evergreen-ils.org/meetings/evergr​een/2015/evergreen.2015-12-03-14.01.html
15:01 pinesol_green Minutes (text): http://evergreen-ils.org/meetings/evergr​een/2015/evergreen.2015-12-03-14.01.txt
15:01 pinesol_green Log:            http://evergreen-ils.org/meetings/evergree​n/2015/evergreen.2015-12-03-14.01.log.html
15:01 kmlussier yboston++
15:02 maryj yboston++
15:09 Bmagic yboston++
15:30 bmills joined #evergreen
15:49 jlitrell joined #evergreen
15:55 Dyrcona Whee! Lots of adding closed dates and altering of due dates today.
16:13 gmcharlt_ joined #evergreen
16:25 dbs joined #evergreen
17:14 mmorgan left #evergreen
17:32 genpaku joined #evergreen
17:39 finnx joined #evergreen
17:54 Stompro_home joined #evergreen
17:54 jwoodard is anyone on that can explain a library setting to me?
17:57 berick jwoodard: probably depends on the setting.  ask away..
17:59 jwoodard Auto-Extending Grace Periods extend for all closed dates
17:59 jwoodard What does it do?
17:59 jwoodard I read the description but it does not make much sense to me.
18:10 bmills joined #evergreen
18:11 berick jwoodard: i read it a few times.. not sure either
18:14 miker jwoodard: if the grace day falls on a closed day, like when the item is due the day before the closure, use the first day after the closure as the grace day
18:15 berick miker: so it's circ.grace.extend.into_closed plus one day?
18:15 jwoodard miker: so for that setting if the grace period keeps falling on a closed date it will keep extending the grace period until it falls on an operating day?
18:15 miker right
18:15 miker iirc
18:16 jwoodard That should be the default for the first setting!! lol
18:16 jwoodard thanks!  miker++
18:16 miker well, depends on post-closing workflow
18:17 miker whether you backdate after a closure. then you don't need it
18:18 * miker disappears
18:21 dbwells jwoodard: The description is crazy (I think the should end with "open dates."), but I think I can help explain what it does.  Our library has a 3 day grace period.  We want grace to only count against open days.  If something is due the day before Christmas closing (one week), the three day grace does not start until we open again.  So they get the whole closing plus three days.  The default option will allow days 1 and 2 to get used by the closed
18:21 dbwells days, then give one day of grace when we reopen.  (And yes, we are pretty generous.)
18:22 dbwells There is a chance I have something exactly backwards :)
18:24 csharp generosity++
18:25 * csharp sees a culture of pettiness in libraries sometimes :-/
18:26 dbwells jwoodard: Here is the original commit which confirms that the first modifier should read "only consumed by open days" http://git.evergreen-ils.org/?p=worki​ng/Evergreen.git;a=commitdiff;h=28b84​267a5b3df29ae95043cea4f371ba100e98a
18:27 dbwells (at least according to the commit message)
18:27 dbwells And here is the original bug where the options came forth, if it helps: https://bugs.launchpad.net/evergreen/+bug/787542
18:27 pinesol_green Launchpad bug 787542 in Evergreen "backdated checkin does not honor grace period" [Medium,Fix released]
18:29 * dbwells also disappears
19:06 jwoodard thanks dbwells++
19:06 jwoodard we have a grace period of one day and we backdate but I like the setting to be enable just in case

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