Evergreen ILS Website

IRC log for #evergreen, 2014-09-12

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

All times shown according to the server's local time.

Time Nick Message
00:42 buzzy joined #evergreen
00:54 snigdha26 joined #evergreen
03:32 book` joined #evergreen
03:43 remingtron_ joined #evergreen
04:57 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
05:02 geoffsams joined #evergreen
06:56 b_bonner joined #evergreen
06:57 mnsri_ joined #evergreen
06:57 mtcarlson_away joined #evergreen
07:26 snigdha26 joined #evergreen
07:55 mtate joined #evergreen
07:56 Callender joined #evergreen
08:02 jboyer-isl joined #evergreen
08:06 csharp @quote random
08:06 pinesol_green csharp: Quote #19: "_bott_: I wish I'd get what I wanted instead of what I asked for" (added by Dyrcona at 11:02 AM, November 15, 2011)
08:06 _bott_ ...everyday
08:07 akilsdonk joined #evergreen
08:07 csharp _bott_++
08:10 rsoulliere joined #evergreen
08:12 mrpeters joined #evergreen
08:23 Dyrcona joined #evergreen
08:41 mmorgan joined #evergreen
08:59 eeevil joined #evergreen
09:02 mtate joined #evergreen
09:05 Callender joined #evergreen
09:11 phasefx joined #evergreen
09:19 Stompro joined #evergreen
09:27 gdunbar joined #evergreen
09:37 mllewellyn joined #evergreen
09:44 kbutler joined #evergreen
09:45 kmlussier joined #evergreen
09:46 berick phasefx: pushed to random/collab/phasefx/wheezy_installer -- however, to work, it needs the tip commit from this pulled into master:  working/user/berick/lp1350042​-grid-print-and-show-all-cols
09:46 berick which fixes a bug in the JS test runner
09:47 kmlussier Hi all. We're a little late in getting the DIG hack-a-way started, and yboston is stuck in traffic.
09:47 kmlussier If anyone wants to come into the Google Hangout, can you send me your Google account e-mail via pm? Thanks!
09:59 tspindler joined #evergreen
10:05 yboston joined #evergreen
10:13 buzzy joined #evergreen
10:14 krvmga joined #evergreen
10:25 RoganH joined #evergreen
10:39 kmlussier yboston: Here's the IRC log where we were discussing that holds fulfillment feature in 2.7 - http://irc.evergreen-ils.org/​evergreen/2014-06-23#i_107061
10:44 jihpringle joined #evergreen
10:49 akilsdonk joined #evergreen
10:57 RoganH kmlussier reading through the irc chat and looking at berick's submit I have a feeling there are some very different needs for ILLs out there
10:58 kmlussier I don't know. The new feature is something Dyrcona is using as he works on the NCIP connector.
11:02 berick i'm around if there's anything I can help with
11:02 berick mike sums it up well in the IRC chat log, though
11:02 berick as far as how FF uses it
11:03 RoganH Based on how we deal with ILLs I don't get why you'd want to put holds on a precat (holds are what we use precats for)
11:03 RoganH I understand that if you're using FF you may be able to hold onto that item longer as the relationship is different but for our regular ILL partners that would be an issue.
11:04 berick RoganH: at the borrowing library, where the lender copy does not exist, we create it as a precat, then place a hold for the borrowing patron on the precat copy.
11:04 RoganH berick: my question is, can others put holds on it?
11:04 berick RoganH: not in stock EG, no
11:04 RoganH berick: OK, that makes more sense then.
11:05 RoganH (to me, many things make sense to others that don't to me)
11:06 kmlussier jihpringle, akilsdonk: I think you got sent to some alternate hangout. Try this link and see if it gets you the one we're on: https://plus.google.com/hangout​s/_/g5wg52vcprhjuqsaqvqqjwuplaa
11:06 RoganH speaking of hangout like things has anyone else tried jitsi?
11:08 vlewis joined #evergreen
11:09 kmlussier RoganH: The reason we wanted to use precats in those situations is so that we didn't have a bunch of "deleted' temporary bib records leftover from the borrowing library.
11:10 RoganH kmlussier: I can understand that.  In our workflow we just accept that they have to be cleaned up periodically.
11:13 akilsdonk kmlussier: I'm having issues joining the hangout-- but that's ok.  Is there anything in particular that I should work on?  I see two bitesize doc needs for 2.7 on the wiki that I could work on if no one else has claimed them today.
11:16 kmlussier We have someone working on the holds shelf expire doc.
11:17 kmlussier akilsdonk: Did you try the link above?
11:17 csharp kmlussier: oh - I missed the link
11:18 kmlussier csharp: My invitations for bringing people to some alternate Google Hangout universe.
11:19 kmlussier That is, they were bringing them there
11:20 * RoganH wonders if in this mirror universe everyone has a goatee and glares menacingly to show they're evil.
11:20 * csharp has a nice friendly full beard now ;-)
11:21 kmlussier akilsdonk: We had a question about the 2.7 ESI docs that had been marked as "Done". Were those part of the docs that were added to the working repository?
11:21 kmlussier csharp: You didn't always have a beard?
11:21 akilsdonk kmlussier: I believe Erica added them to the working repository.
11:22 csharp I've vascilated between full beard and goatee (technically a vandyke) over the last several years
11:24 RoganH I've joked about shaving my beard off but the hassle of reintroducing myself to everyone seems too tedious.
11:26 csharp RoganH++ ;-)
11:27 akilsdonk kmlussier: I may have a few 2.7 docs that still need to be added to the repository.  I will double check and add those to the master repository today.
11:28 kmlussier akilsdonk: OK, thanks!
11:36 akilsdonk_ joined #evergreen
11:37 phasefx_ joined #evergreen
11:43 phasefx_ berick++  about to run a test
11:46 krvmga joined #evergreen
11:49 berick phasefx_: cool, for now, it's just reporting the return value, so the JS test suite will be all or none, but it's a start
11:51 jeff osrf-gateway-v1 using duplicate param= param= parameter names sure can get annoying, depending on your client library. :P
11:52 jeff one option is to jump to the translator instead.
11:53 csharp @who will create an API for their API?
11:53 pinesol_green csharp will create an API for their API.
11:53 csharp heh - I deserved that :-)
11:53 jeff funny you should say that... :P
11:55 dbwells Can anyone tell me what "Hold Verify" does when set for a location?
11:56 tsbere dbwells: I think it is supposed to prompt staff before actually capturing for a hold. I could be wrong.
11:56 jeff staff client pop-up before hold is captured-to-available at the pickup lib
11:56 jeff i don't know how it interacts with transits -- it might pop-up at capture time, or just at transit -> available time, or both.
11:57 tsbere jeff: I could have sworn it was capture in general, whether for transit or for the hold shelf. Again, though, I could be wrong.
11:58 dbwells Is anyone using it?  I'm having trouble understanding what exactly the staff might verify.
11:58 jeff original use case: a library branch where all materials in certain AV locations were sent from checkin to another department for inspection/cleaning, and it was desired that those items not be subject to checkin opportunistic hold capture, because "they still need to be cleaned -- there might be parts missing, etc".
11:58 tsbere jeff/dbwells: Just looked at the code. If set "HOLD_CAPTURE_DELAYED" gets fired at hold capture time
11:59 mmorgan dbwells: I believe the pop-up is something like "Hold capture delayed by policy". It has only been set by mistake and has caused some confusion in our consortium.
11:59 jeff the original use case was here (we funded that development pre-go-live, iirc), and has been eliminated for a number of reasons.
11:59 jeff i.e., we no longer make use of it.
11:59 jeff i do not know if others do.
12:02 dbwells Ah, so locations set that way /never/ capture at checkin, and you have to deliberately use the "capture holds" screen to get them to capture.  Does that sound right?
12:03 jeff nope, the workflow is a confirmation pop-up: This item could be captured but was not for policy reasons. Do you want to actually capture it?" (paraphrased)
12:04 jeff what you described would probably be how we would have built/specified it if done today, and not 6 years ago. ;-)
12:06 dbwells jeff: thanks for all the info.  This actually might do what we need in a roundabout way.  Time for actual field testing.
12:06 jeff "This item could fulfill a hold request but capture has been delayed by policy." followed by "Capture" and "Do Not Capture" options.
12:07 jeff strings begin with staff.circ.utils.hold_capture_delayed
12:09 jeff by my read of xul/staff_client/server/circ/util.js, if you use the suppress popups feature in checkin, you'll get a sound but no pop-up, and there will be no capture.
12:13 whargrove joined #evergreen
12:14 whargrove Hi all - quick question: when creating the eg database and schema for a test server, how do I know what the database name should be? can I pass in any string I want to eg_db_config?
12:15 csharp whargrove: yes
12:15 csharp whargrove: "evergreen" is simplest
12:15 csharp and will match many examples out there
12:15 whargrove csharp: right, that's what I thought. Thanks!
12:16 Ghid0rah joined #evergreen
12:19 Ghid0rah Hello everyone. I'm attempting to configure a notification to send daily overdue email notifications. Currently, a patron will only receive 1 email notification per overdue item. Do I used the "Event Repeatability Delay" or "Granularity" field to have it send the notification everyday?
12:20 snigdha26 joined #evergreen
12:21 tsbere Ghid0rah: That sounds very annoying from a patron POV. >_> Setting the repeatability delay and appropriate valid timeframes, though, should be what you want. Granularity, however, is more for the action/trigger runners, if I recall correctly, and otherwise has little effect.
12:23 * csharp would pretty much stop using the library if he got daily emails about overdue items :-/
12:25 tsbere csharp: I disagree. I would, however, stop letting the library have my email address. ;)
12:25 Ghid0rah lol I agree
12:26 Ghid0rah The Liberians orders...
12:26 tsbere either that or filter the library's overdue messages into the void. Maybe set an autoresponder to respond to each of them to annoy the library...
12:26 mmorgan Daily overdue notifications could be useful for certain types of materials, like reserves.
12:27 jihpringle akilsdonk_ : are you looking at the reporter "Switch to XLSX format for Excel report output" doc need?
12:28 Ghid0rah tsbere: So I'd just set say 24:00:00 in the Event Repeatability Delay field?
12:28 nhilton joined #evergreen
12:29 tsbere Ghid0rah: Honestly? I have no clue. Never set that option. :P
12:30 tsbere Ghid0rah: And also honestly, beyond what help I already gave you, I am not personally inclined to help annoy patrons like that ;)
12:30 Ghid0rah They're only high school students ;)
12:30 whargrov1 joined #evergreen
12:31 tsbere Yea, well, I was a sneaky but annoying student in high school myself. If I were being pestered like that, though, I would likely have become much *more* annoying. :P
12:33 akilsdonk_ jihpringle: I have not started on it yet, so if you want to take it, that's fine with me.  Otherwise I can work on it this afternoon.
12:38 csharp kmlussier: we lost sound to the room
12:39 kmlussier there needs to be a better way to do this. :)
12:42 csharp from my perspective, it's working quite well ;-)
12:43 kmlussier A question that came up in the DIG hack-a-way: is there ever a difference between the available time and shelf time for a hold?
12:43 kmlussier We've been finding that they're always the same.
12:43 csharp they are apparently the same in most cases
12:44 kmlussier csharp: It's getting it to work well in a group environment that's difficult.
12:45 pastebot "csharp" at 64.57.241.14 pasted "Open-ILS/xul/staff_client/server/circ/util.js - available time" (21 lines) at http://paste.evergreen-ils.org/11
12:45 mrpeters left #evergreen
12:45 * kmlussier should have gotten some tips from Rogan before starting this morning.
12:47 snigdha26 kmlussier: Hi, I want to help with something in the hack fest. What can I begin with?
12:50 kmlussier snigdha26: Hold on...yboston and I are talking about it.
12:57 kmlussier snigdha26: We're all about to break for lunch (sorry for the bad timing). But a lot of the features from http://wiki.evergreen-ils.org/dok​u.php?id=evergreen-docs:2.7_needs that aren't already being covered are probably difficult for a new person to the community to document.
12:58 snigdha26 kmlussier: Oh! That's okay. But yboston needed to collaborate with a new volunteer ? Any thing I can do?
12:59 kmlussier snigdha26: So yboston was thinking that you might want to look at replacing screenshots from some of our old circulation docs to the new web client that the community is currently testing.
13:00 kmlussier I don't know what time it is there, but would you be around in an hour (maybe a little longer) to work with him on it?
13:00 kmlussier Of course, there are always those biteisze docs that can be looked at if later doesn't work. :)
13:01 snigdha26 kmlussier: It's 10:30 pm here, but I will definitely be around for a while, that's not a problem :)
13:01 kmlussier snigdha26: OK, thanks!
13:01 * kmlussier is usually too tired to do anything by 10:30 p.m. :)
13:02 snigdha26 kmlussier: which circulation docs are being referred to here? The one in the 2.6 version documentation? Haha, Im an undergrad student, used to staying up late
13:05 kmlussier Yes, so those are the docs that are currently relevant to the existing client that you would have used earlier for the demo server.
13:06 kmlussier But we are currently in the process of moving to a web client. Hmmm...I don't have the link handy.
13:07 kmlussier https://webby.evergreencatalog.com/eg/staff/ login: admin password: demo123
13:07 kmlussier Login: admin
13:07 kmlussier Password: demo123
13:08 kmlussier But we're about to head out for lunch now. Let's catch up in about another hour.
13:08 snigdha26 Sure :) Thanks
13:15 chatley joined #evergreen
13:15 RoganH joined #evergreen
13:19 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
13:21 nhilton_ joined #evergreen
13:34 pinesol_green [evergreen|Bill Erickson] LP#1350042 browser unit tests use repo fm_IDL2js.xsl - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=8f37922>
13:39 nhilton joined #evergreen
13:54 ktomita joined #evergreen
14:10 csharp @quote random
14:10 pinesol_green csharp: Quote #73: "< dbs> jumped from LaTeX-like markup on the commodore 64 to WordPerfect w/ reveal codes to straight-up WYSWIWYG stuff, then back to SGML/XML things like DocBook, then abstracted out to AsciiDoc, now working closer to the source - circle of doc life" (added by csharp at 10:17 AM, January 13, 2014)
14:16 nhilton_ joined #evergreen
14:33 nhilton joined #evergreen
14:35 akilsdonk_ jipringle: is the excel report output doc still up for grabs?  I wanted to double check before I start making changes.
14:39 jihpringle akilsdonk: go for it
14:43 akilsdonk_ jipringle: thanks!
14:43 yboston joined #evergreen
14:50 kmlussier DIG hangout link: https://plus.google.com/hangout​s/_/gyvh6nxepcsnaetf3kd255qalua
15:01 snigdha26 kmlussier: Im unable to log into the web client version. The workstation isn't being detected
15:02 pinesol_green [evergreen|Angela Kilsdonk] Bitesize doc change: .xlsx report output - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=ee5187d>
15:09 kmlussier snigdha26: Hold on, let me check.
15:12 kmlussier snigdha26: I think you can log in without identifying a workstation. Did you try logging in with the user name and password and then leaving the workstation menu alone?
15:14 snigdha26 kmlussier: yes I did, it doesnt work
15:15 kmlussier snigdha26: What browser are you using?
15:16 snigdha26 kmlussier: chrome Should I try using firefox?
15:18 kmlussier snigdha26: I don't think it will make a difference. I was using Chrome when I logged in.
15:20 nhilton_ joined #evergreen
15:20 bshum snigdha26: It might be a firewall issue.  The web client has to run on special ports for the websockets and maybe you're trying from somewhere that's blocking those ports from access.
15:23 bshum I'm looking up the websocket ports, I don't remember them offhand :)
15:23 bshum ports 7682 and 7680
15:24 whargrove joined #evergreen
15:29 snigdha26 bshum: That might be the issue. Im behind a proxy server and all ssh connections outside college are blocked at the moment
15:29 snigdha26 :(
15:30 bshum snigdha26: Yeah I'm not sure how it behaves with the proxy
15:30 bshum snigdha26: You might be able to see it fail if you look at the console for errors in whatever browser you're on, like Chrome or Firefox
15:31 bshum Like in Firefox
15:32 bshum I think it's in Tools -> Web Developer -> Toggle Tools
15:32 bshum And then I look at the Console tab
15:32 bshum To see what errors happen
15:32 pinesol_green [evergreen|Kathy Lussier] Minor reparis to release notes and merge parts doscs - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=bb0aed2>
15:32 bshum The one for 8443 for hatch is "normal" I think when you don't have a printer stuff setup
15:32 bshum But I would also expect to see errors for those other ports potentially
15:39 whargrove I am troubleshooting my evergreen test server ... I keep on getting "no data received from server" when issuing the test commands
15:39 whargrove ejabberd does not have an ssl_esock process
15:40 whargrove Could that be causing the no data errors?
15:40 kmlussier A general question about the web client then. If it can't be used when certain ports are blocked, is this going to present a problem for some of our libraries when they need to use it in production?
15:41 bshum snigdha26: Yeah in my console from a server/client that can't talk I get something like:
15:41 kmlussier I'm mostly concerned about schools and academics who may not be able to convince their IT departments to unblock the ports.
15:41 bshum "Firefox can't establish a connection to the server at wss://somewhere:7682/osrf-websocket-translator.
15:41 bshum And it blows up
15:42 snigdha26 bshum: Um, yes. Since its a non-standard port, its blocked for my campus.
15:42 berick kmlussier: the port will have to be open.  (note: we only use the SSL port, it's configurable).
15:43 bshum snigdha26: Yeah that's what I suspected.
15:43 RoganH joined #evergreen
15:44 berick you could potentially run the WS server on port 443 at a different hostname to get through firewalls, though
15:45 bshum berick: I wondered about that
15:45 bshum Like setting up an alternate vhost to run websockets
15:46 berick i think it would have to be a different machine, since port 443 will already be in use by the main apache process
15:46 bshum berick: Ah true
15:46 bshum Is there any reason we don't just have websockets run directly off the main apache service then?
15:46 bshum Does it have to be separate?
15:46 gmcharlt or possible nginx in front
15:46 krvmga joined #evergreen
15:47 kmlussier My question is the same as bshum's. I just didn't know how to articulate it.
15:47 gmcharlt bshum: to keep the apache backends used for WS relatively slim
15:48 gmcharlt as otherwise they'd be pulling in all of the stuff required to run TPAC
15:48 nhilton joined #evergreen
15:49 snigdha26 kmlussier: I can get the permissions in a day or two, but since I will not be able to work on the web client right now, anything else I can do?
15:51 bshum Hmm
15:55 kmlussier snigdha26: yboston and I were talking a bit about this at lunch. Since you've done a couple of fixes to the docs using github, we thought it might be useful to go to the next step to try to get familiar with doing a doc commit through the Evegreen working repository.
15:58 kmlussier If you're comfortable making doc commits to the working repository, I think you would eventually be in a better position to understand how the docs are structured and to understand how you could make the changes recommended in the project.
15:58 snigdha26 kmlussier: Alright, I'll work on doing that!
15:58 kmlussier snigdha26: So where you might want to start is the Quick start section of http://evergreen-ils.org/do​kuwiki/doku.php?id=dev:git
15:59 kmlussier It tells you how to clone the Evergreen git repository and also gives you instructions for sending an SSH key to the Evegreen git admins so that you can get your own directory in our working repository.
16:00 kmlussier Once you've cloned the repositorty, it might be a good idea to look through the docs directory, see where all the files are, and see how they relate to the docs site. Also, take a look at the roots.txt file, which is where we structure that main Table of Contents page.
16:02 whargrove joined #evergreen
16:02 kmlussier Also, if you have trouble setting up git, there are lots of people in here who can help out. I often come in here when I have a problem with git, and people are always very helpful.
16:02 snigdha26 kmlussier: Thanks, I'll get back to you once I've done this
16:03 kmlussier snigdha26: Great! Let us know how it goes and don't hesitate to ask any questions as you proceed.
16:09 berick bshum: yeah, what gmcharlt said.  tpac procs grow to 80+ MB per process.  WS procs have to be very light, because we will need a lot of them.
16:18 pinesol_green [evergreen|Yamil Suarez] Docs: Documented change to Holds Shelf Expire Report - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=470688d>
16:23 mmorgan Setting up a selfcheck station with OpenKiosk and trying to get receipts to print correctly. Anyone know offhand where those margin and header/footer settings are?
16:25 dbs we should nginx everything we can; now that nginx and I have both matured, it may be much more doable now
16:33 kmlussier left #evergreen
16:33 jeff hrm. i suppose "packages are available for debian" was enough of a clue that the license was free-ish, but i was surprised to see that it looks like nginx is two-clause BSD.
16:33 bshum mmorgan: uh, so openkiosk doesn't let you edit that via a GUI it seems
16:33 jeff i had some vague sense that it was less-free than that.
16:33 bshum mmorgan: We found we had to modify the prefs file in the openkiosk profile directly
16:33 dbs jeff: it's 'open core'
16:33 jeff dbs: true, since there's "plus"
16:33 bshum To edit the values for things like the margin/header/footer
16:34 jeff dbs: similar to jasperreports server
16:34 bshum I think what I did was to look at a modified entry from the Firefox profile
16:34 jeff (and we use both here)
16:34 bshum And then made similar changes in the same prefs file for openkiosk
16:34 jeff (er, "both" as in "nginx" and "jasperreports server")
16:34 * berick was confused at first by the "Free 30-day Trial"
16:34 jeff and actually, i might be sticking nginx in front of jasper.
16:35 jeff depends on which of nginx/apache/pound/something-else i can make do what i want it to do with client ssl certs first/easiest.
16:35 mmorgan bshum: looked for that prefs file, but couldn't find it. Should there be a firefox profile for openkiosk?
16:40 tspindler left #evergreen
16:40 bshum Hmm
16:40 * bshum tries to remember
16:41 bshum So you looked in the user's appdata
16:42 bshum Then I can't remember if it's in local/local roaming/roaming
16:42 bshum But there should be an openkiosk somewhere
16:42 bshum And within that profiles
16:42 bshum And then some profileID folder
16:42 bshum And within there a prefs.js file
16:42 bshum It wouldn't be in the Mozilla/Firefox/.. place
16:42 bshum But it's a similar structure
16:43 mmorgan yup. Don't see openkiosk in appdata. Have been down many of these roads :)
16:43 bshum Hmm
16:43 * mmorgan agrees. Hmm...
16:43 bshum Well
16:43 bshum :)
16:43 bshum That was the solution we used :D
16:44 bshum Oh maybe it's under the parent folder
16:44 bshum Like err
16:44 bshum mozdevgroup?
16:44 * bshum doesn't have access to his test system with it today
16:44 * bshum quickly gives it an install to remember
16:44 pinesol_green [evergreen|Kate Butler] Docs: Staff initials settings for patron notes - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=82c76d0>
16:47 mmorgan \me searches for possibly related directory names...
16:48 bshum mmorgan: Local\MDG\OpenKiosk
16:48 bshum I don't have a prefs.js in there yet, but I imagine if I start tweaking settings it would create one for me
16:48 bshum But that's the path you need to walk, perhaps.
16:49 mmorgan Will take stroll down that path. Thanks bshum!
16:58 bshum gmcharlt: Do you have any opinion on how you'd like to see the websockets instructions incorporated into the main README for OpenSRF?  I was figuring we could start a new section
16:58 bshum Maybe before the "Troubleshooting note for Python userS"
16:58 bshum Or maybe right before the "Getting help"
16:59 bshum I imagine we could copy most of the steps listed out in README.websockets with some light tweaking to note users, etc.
16:59 bshum Alternatively I did notice that the present README.websockets mentions scripting more of the work, not sure if that's realistic or we should just write out the necessary steps for now.
16:59 whargrove joined #evergreen
17:00 gmcharlt bshum: a new section for now, I think
17:01 mmorgan Yay! Success!
17:01 mmorgan bshum++
17:01 bshum mmorgan++
17:02 bshum gmcharlt: I imagine we could do something similar (new section) for the actual web client bits too.
17:02 gmcharlt yeah
17:02 bshum gmcharlt: Since there's some tweaks for apache 2.4 for websockets in OpenSRF
17:02 bshum I wonder if we should include a copy of the modified apache.conf file
17:02 bshum And make another directory / instruction step for it
17:02 bshum Kind of like what we do for Evergreen
17:02 bshum With 2.2 vs. 2.4
17:03 bshum Though I don't know if anybody's tested the 2.4 apache.conf with anything other than Debian for you guys, and Ubuntu 14.04 for us.
17:03 bshum Thinking about Fedora :)
17:03 * bshum stares off in dbs' direction
17:03 bshum But we could start with that and see where it leads us
17:03 gmcharlt bshum:  say Fedora three times in a row... ;)
17:04 gmcharlt joined #evergreen
17:05 * dbs pops up
17:05 dbs wearily
17:06 bshum gmcharlt: I'll try putting something together to move the instructions into the main README files today.
17:06 bshum So that I can say I did something for DIG :)
17:11 mmorgan left #evergreen
17:12 bshum Gah, of course I underestimated how rusty I am with asciidoc :)
17:19 whargrove when I am setting up an SIP user, is that done by adding a patron? And putting the user in the SIP permission group?
17:20 jeff that is the underlying Evergreen staff user account that the SIP server uses to perform actions.
17:20 bshum whargrove: more or less, though you also need to define that user/password, etc. in the oils_sip.xml config file that's used by the SIP server.
17:20 whargrove bshum: yes, I have already done that
17:21 whargrove bshum: so there is no difference between a user and a patron? just the permission group
17:22 bshum whargrove: "All the world's a stage and all the men and women merely players"
17:22 bshum But basically, yes, we're all users.
17:22 bshum In the actor schema.
17:22 bshum Cracks me up every time.
17:22 bshum Sorry bad database joke :(
17:22 bshum It's Friday, whee!
17:23 whargrove lol! indeed
17:24 jeff oh. i read "is that done by" as "what is done by"
17:24 jeff oops.
17:24 jeff bshum++
17:28 whargrove jeff: sorry I didn't see your response. Thanks :) I wasn't making the connection between patron and user to create the staff user account
17:30 pinesol_green Incoming from qatests: Test Failure - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
17:33 whargrove joined #evergreen
17:33 bshum Race condition again?
17:33 phasefx that one is probably from me mucking with it earlier
17:33 phasefx I don't think the VM refreshed
17:35 bshum Ah okay
17:35 phasefx yeah, that's what happened
17:36 phasefx Refresh happens at 11am, testing way later, and I jumped in between the two
17:45 bshum Sigh
17:45 bshum Reading the OpenSRF README closely for the first time to try mimicking the same style.
17:45 bshum And now I want to edit the existing stuff
17:46 whargrove ciao all! enjoy your weekend
17:46 whargrove left #evergreen
17:46 mtcarlsoz joined #evergreen
17:46 mrpeters1 joined #evergreen
17:47 nhilton joined #evergreen
17:51 pinesol_green [evergreen|Kate Butler] Docs: Staff generated penalties documentation - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=ea1de03>
17:55 bshum Alrighty, I started fixing up the OpenSRF docs for websockets, but I'll finish the rest tonight
17:56 bshum Need to include more explanation of some steps
17:56 bshum And add something for the apache SSL certificate
17:56 bshum Since you need a proper cert to make it work I think I recall
17:58 bshum But they'll be kicking us out soon so I guess I'll finish it later.
18:00 bshum Heh, and I suppose we'll need to include a disclaimer to install git first since we're cloning something.
18:00 bshum Okay
18:00 * bshum wanders away
18:11 mmorgan1 joined #evergreen
18:11 mrpeters joined #evergreen
18:13 eby__ joined #evergreen
18:13 jeffdavi1 joined #evergreen
18:14 gmcharlt_ joined #evergreen
18:15 jeffdavis joined #evergreen
18:15 pinesol_green` joined #evergreen
18:16 riot_ joined #evergreen
18:17 mnsri- joined #evergreen
18:20 jeff_ joined #evergreen
18:24 phasefx_ joined #evergreen
18:25 gsams joined #evergreen
18:25 dbwells_ joined #evergreen
18:25 remingtron_ joined #evergreen
18:26 berick joined #evergreen
18:26 sarabee_ joined #evergreen
18:26 sseng_ joined #evergreen
18:28 mtcarlson_away joined #evergreen
18:28 jcamins joined #evergreen
18:28 phasefx__ joined #evergreen
18:29 eeevil joined #evergreen
18:31 Librator joined #evergreen
18:31 dreuther_ joined #evergreen
18:33 chatley_ joined #evergreen
18:34 pmurray joined #evergreen
18:34 pmurray joined #evergreen
18:54 serflog joined #evergreen
19:07 serflog joined #evergreen
19:22 serflog joined #evergreen
19:23 pinesol_green joined #evergreen
19:38 serflog joined #evergreen
19:38 Topic for #evergreen is now Welcome to the #evergreen library system channel! | We are publicly logged. | Large pastes at http://paste.evergreen-ils.org
19:44 tsbere joined #evergreen
19:54 pinesol_green joined #evergreen
19:55 kmlussier joined #evergreen
19:58 eby joined #evergreen
20:03 csharp @dunno add You keep using that word. I do not think it means what you think it means.
20:03 pinesol_green csharp: Error: You must be registered to use this command. If you are already registered, you must either identify (using the identify command) or add a hostmask matching your current hostmask (using the "hostmask add" command).
20:05 csharp @dunno add You keep using that word. I do not think it means what you think it means.
20:05 pinesol_green csharp: The operation succeeded.  Dunno #33 added.
20:18 bshum_ joined #evergreen
20:37 kmlussier csharp++
21:01 bshum joined #evergreen
21:14 kmlussier joined #evergreen
21:25 dbwells_ joined #evergreen
21:25 mmorgan1 joined #evergreen
21:36 bradl joined #evergreen
21:57 tsbere joined #evergreen
23:53 remingtron__ joined #evergreen
23:53 kmlussier1 joined #evergreen
23:55 gmcharlt joined #evergreen

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