Evergreen ILS Website

IRC log for #evergreen, 2013-06-06

| 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:05 paxed morning
00:20 jeff morning!
00:20 zerick joined #evergreen
00:23 paxed i guess i should get to work...
00:27 mtcarlson joined #evergreen
01:47 Mark__T joined #evergreen
03:12 mrpeters joined #evergreen
04:34 edoceo joined #evergreen
04:58 paxed "ohai, i'm a staff client UI. but you can't use messagecatalogs, 'cause i'm not a xul one"
06:28 Hagerstown_Staff joined #evergreen
06:30 rfrasur Hmm, good to know that not everyone wakes up at 6 a.m. thinking re: EG.  Nonetheless - how would one go about making the OPAC protected from view unless someone had authentication credentials either from a card number or something else?
06:51 bkuhn joined #evergreen
07:10 collum joined #evergreen
07:39 rfrasur I'll be back w/ many questions - oh so many.
07:52 serflog joined #evergreen
07:52 Topic for #evergreen is now Welcome to the #evergreen library system channel! | We are publicly logged. | Large pastes at http://paste.evergreen-ils.org
08:14 akilsdonk_ joined #evergreen
08:20 tspindler joined #evergreen
08:33 paxed eeevil: whenever you've got time.
08:39 mdriscoll joined #evergreen
08:48 gdunbar paxed: fair warning - I'm stealing eeevil for a large chunk of the day
08:49 kmlussier joined #evergreen
08:50 misilot joined #evergreen
08:51 Dyrcona joined #evergreen
08:53 paxed gdunbar: bah!
08:55 gdunbar paxed: You're welcome to fly over to Georgia so we can fight over him...  ;-)
08:56 * Dyrcona missed something.....
08:59 paxed gdunbar: nah, he's not my type... :P
09:02 jeff_ @later tell rfrasur I'm interested in why you want to make the catalog "protected from view". Any details?
09:02 pinesol_green` jeff_: The operation succeeded.
09:11 serflog joined #evergreen
09:11 Topic for #evergreen is now Welcome to the #evergreen library system channel! | We are publicly logged. | Large pastes at http://paste.evergreen-ils.org
09:15 jonadab joined #evergreen
09:24 kivilahtio joined #evergreen
09:32 berick jeff_: hope I didn't step on your toes with LP 1187035.  I just noticed it was assigned to you.
09:32 pinesol_green Launchpad bug 1187035 in Evergreen "Remove obsolete OpenILS::Utils::Editor" (affected: 1, heat: 6) [Wishlist,New] https://launchpad.net/bugs/1187035 - Assigned to Jeff Godin (jgodin)
09:42 jeff_ berick: zero toes were harmed!
09:42 berick excellent
09:42 jeff_ all i had in mind was to clean up my commit message and test / get exactly the kind of eyes you put on it -- thanks for catching the $e->request bits
09:42 kivilahtio Hi all! Is there a guide on how to get logging statements to show in the open-ils.serials_stderr.log or opensrf logs?
09:42 kivilahtio I have read Dan Scott's articles about easing gently into OpenSRF and I get syntax errors! Also went through the opensrf.xml & opensrf_core.xml and found references to the unix_log files named <unix_log>open-ils.serial_unix.log</unix_log>
09:42 kivilahtio This should export the $logger-object to the package?      use OpenSRF::Utils::Logger qw/:logger/;
09:42 kivilahtio Then you just call it       $logger->error("SERIALS: ALL CLEAR!");
09:42 kivilahtio Easy peesy lemon squeezy
09:42 kivilahtio I get no entries in any *srf.log regarding the created logging statement. Error level logging should be enable by default, and considering the enormous amount of info and debug notifications we have in our osrfsh.log et al.  it should work.
09:42 kivilahtio Also, how do you push print statements to the open-ils.**_stderr.log? Seems like the easiest destination for debugging. Already tried print(); and warn();
09:42 kivilahtio Any links I haven't found?
09:44 kivilahtio btw heres the good introduction to OpenSRF http://journal.code4lib.org/articles/3365.
09:44 jeff_ kivilahtio: if you're getting syntax errors, that would prevent the service from even starting, and thus it would not log anything. have you checked for syntax errors using perl -c /path/to/Serials.pm, for example?
09:46 kivilahtio jeff_: yeah i forgot to add to cpan some debug libraries but I'll try again
09:46 kivilahtio perl -c Serial.pm                             Serial.pm syntax OK
09:47 kivilahtio jeff_ osrf_ctl.sh -l -a restart_perl throws no errors
09:48 jeff_ kivilahtio: okay, and you have zero lines matching open-ils.serial or Serial.pm in your osrfsys.log file (or wherever you have directed logging)?
09:48 dbwells joined #evergreen
09:49 jeff_ Even if you aren't making any open-ils.serial calls, you should still have some lines matching open-ils.serial related to the service starting and connecting to jabber, etc.
09:49 remingtron joined #evergreen
09:49 kivilahtio jeff_: yes I get such entries
09:50 kivilahtio jeff_: I haven't done any tweaking to the logging configurations
09:50 jeff_ Okay. So far, so good. If you've added additional logging statements and they are not appearing, it's possible that those logging statements are never being executed due to how the program flow / conditionals / etc are happening... those lines may never be hit.
09:51 jeff_ kivilahtio: Do you have the code in question up somewhere?
09:53 kivilahtio jeff_:  http://pastebin.com/RfnJqfTp
09:53 dbwells_ joined #evergreen
09:55 remingtron @later tell bshum You changed the way IRC messages can be hidden from the logs, right? The IRC web page still has the old info. http://evergreen-ils.org/irc.php
09:55 pinesol_green remingtron: The operation succeeded.
09:56 remingtron pinesol_green: Thanks! You're a great bot.
09:56 pinesol_green remingtron: I am only a bot, please don't think I'm intelligent :)
09:56 pinesol_green remingtron: Have you tried turning it off and back on again?
09:57 Dyrcona remingtron: bshum also said something about it not working properly. I don't know if that has since been fixed.
09:57 kmlussier I'm fairly sure it was fixed.
09:57 bkuhn joined #evergreen
09:58 kivilahtio jeff_:  I found some entries on the row 100 million something, maybe there just is so much static there that I couldn't find it
09:58 dbs yup
09:58 jeff_ kivilahtio: I would remove this line, as I don't think that syntax will work, and isn't used anywhere else: OpenSRF::Utils::Logger->error("SERIALS: ". $obj->as_string());
09:59 kivilahtio jeff_: yeah I kinda figured that out after the OpenSRF tutorial, but it didnät work before that either. I'll try
10:00 kivilahtio jeff_: do you have any idea about the open-ils.serials_stderr.log ?
10:00 kivilahtio can one push statements there?
10:00 jeff_ kivilahtio: i would expect this line to work, assuming that $obj exists and has an as_string method. have you tried logging just a basic scalar, or a fixed value, as a test? $logger->error("HELP I AM STUCK IN A SERIAL FACTORY"); or the like?
10:00 kivilahtio jeff_:  yes :)
10:01 jeff_ hrm. strange. perhaps the Serial.pm file which you are editing is not the Serial.pm file which is being loaded by the system? (going back to basics)
10:01 jeff_ (rather -- trying the simple things)
10:02 kivilahtio jeff_: yeah. but it should work and I'll try to work from there, thanks
10:02 phasefx we should expose a private API call for testing logging, if one doesn't already exist
10:03 jeff_ kivilahtio: good luck -- sorry, I'm out of ideas for the moment. also, I'm not certain on the stderr logs, though I would have expected warn() to hit them -- which is why I was wondering if the file you were editing was not the file being used by the system when starting services.
10:03 phasefx registered OpenSRF method, that is
10:04 kivilahtio phasefx: what do you mean? add it to the opensrf.xml ?
10:04 kivilahtio phasefx: or the opensrf_core.xml? I couldn't find any serials related entries there
10:04 phasefx kivilahtio: I mean, it would be neat to be able to use srfsh and just say something like  request open-ils.actor opensrf.log.error "testing 123"
10:04 kivilahtio phasefx: ah
10:05 phasefx not that such a thing would have necessarily been of help here
10:08 kivilahtio phasefx: I think i solved the osrfsh.log issue, still getting nothing in the serials_stderr.log
10:08 kivilahtio i just looked back 30 rows when I should have looked back for 3000 rows thank to our crazy logging granularity
10:09 paxed hm, i changed the logging to debug level a week or two ago
10:10 kivilahtio paxed: figured as much :) but thought some things are better left unsaid
10:10 paxed i was trying to figure out something, and never changed it back
10:10 paxed oh, it was due to the search result sorting not using the locale.
10:11 kivilahtio paxed: I was wondering why we had 16GB of logs, well I just removed them all, I hope you don't mind?
10:11 paxed doesn't matter, we'll be able to get more!
10:11 phasefx kivilahtio: I'm not sure, but maybe serials_stderr.log would just take stuff explicitly going to STDERR
10:11 phasefx print STDERR "foo!\n";
10:12 kivilahtio phasefx: of course! why didnt i figure that out !
10:13 kivilahtio phasefx: not working
10:14 phasefx kivilahtio: there have been commits recently to "reduce" what shows up serials_stderr.log, could find one of those and work backwards
10:16 gmcharlt phasefx: kivilahtio: the most recent change was to redirect warns (from Perl services) to the main OpenSRF log
10:17 gmcharlt so warn $foo would go to the main log, but print STDERR should go to *stderr.log
10:17 kivilahtio gmcharlt: phasefx: I used to do debugs by opening mah own file stream but thought maybe tryi to do things the Evergreen way for change
10:18 gmcharlt kivilahtio: assuming you're running OpenSRF 2.2, using warn to report debug messages should keep those messages nicely integrated with everythign else that the method you're debugging logs
10:20 phasefx for debugging I've always used logger and put a phasefx prefix in my output for easy grepping
10:21 kivilahtio gmcharlt: no beef with warn or print STDERR. Getting no nothing on my logs
10:22 gmcharlt hmm - are you logging to file or syslog?
10:23 kivilahtio gmcharlt: no idea. I am using $logger in Serial.pm :D
10:23 kivilahtio gmcharlt: my best guess is syslog
10:23 gmcharlt ok, so the log destination is configured vai the logfile directives in opensrf_core.xml
10:23 kivilahtio gmcharlt: $logger output ends up in the osrfsh.log
10:24 kivilahtio gmcharlt: now it work after i cut the logging level to 2. Still nothing in open-ils.serials_stderr.log
10:25 kivilahtio <logfile>/openils/var/log/osrfsys.log</logfile>
10:26 kivilahtio I mean $logger has always worked I just couldn't find the output. Serials_stderr still a question
10:29 kivilahtio any idea where those are defined? Couldn't find anything from /openils
10:29 kivilahtio grep -Pnir 'serial_stderr' /openils
10:30 berick kivilahtio: *_stderr.log captures any (unexpected) messages that are sent to STDERR, like warn() and die()
10:30 jeff (unless you're using a recent opensrf which defines a __WARN__ handler, in which case warn() won't end up there)
10:31 berick correct
10:31 jeff (but the __WARN__ handler shouldn't affect printing to stderr directly)
10:31 gmcharlt right
10:31 kivilahtio print STDERR "CRAZY CAT";        warn "CRAZY CAT";    No entries... ;(
10:32 * dbs just pushed a commit to the Evergreen_Website repo to fix the ! -> [off] docs
10:32 pinesol_green [evergreen_website|Dan Scott] New bot, new way of hiding lines from the logs - <http://git.evergreen-ils.org/?p=Ever​green_Website.git;a=commit;h=5ec1388>
10:32 paxed so, when're the 2.5 commits starting to trickle in??
10:33 dbs and applied.
10:33 gmcharlt dbs++
10:33 jeff kivilahtio: when a service is started, it should try to open the stderr log file. if it fails, it will log at the error level, "server: unable to open STDERR log file: [...] " if it succeeds, it will log at the internal level (which you probably are not logging), "server: redirecting STDERR to [...]"
10:34 jeff kivilahtio: you might want to restart the service(s) and look for errors in the opensrf log mentioning STDERR -- also, verify that file ownership and permissions on the stderr files permit your user (likely opensrf) to write to them.
10:34 dbs paxed: I'm working on testing a commit for bug 1020625 atm
10:34 pinesol_green Launchpad bug 1020625 in Evergreen "TPAC unable to link to specific organization by shortname" (affected: 1, heat: 6) [Wishlist,Confirmed] https://launchpad.net/bugs/1020625
10:37 kivilahtio jeff: no errors with keywords serial and redir
10:37 kivilahtio write persmission for oser opensrf
10:37 jeff kivilahtio: just to be clear, the log lines would have the string STDERR, all caps.
10:38 paxed i've been looking into improving my branch for bug 1156545 - but there doesn't seem to be a good way to use money conversion routine and yaous unless i include all kinds of javascript in non-xul staff client UI... .(
10:38 pinesol_green Launchpad bug 1156545 in Evergreen "Currency symbol and format should not be in po-file translatable texts" (affected: 1, heat: 6) [Medium,Triaged] https://launchpad.net/bugs/1156545
10:39 paxed dbs: oh. reminds me. do you think it might be possible to enable the l() macro in tt2 templates stored in the db, such as A/T ones?
10:40 pinesol_green [evergreen|Angela Kilsdonk] Asciidoc fix for documentation - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=05bda47>
10:41 phasefx paxed: it's kludgy, but if it's in the staff client, you can push data into any given window's scope during onload from the parent window
10:41 dbs paxed: sounds painful :/
10:41 paxed phasefx: oh? any examples of that in eg?
10:42 phasefx paxed: in opac.js, the staff client pushes data into the embedded opac
10:42 phasefx for something wrapped in util.browser, browser.js does a lot of it
10:42 paxed dbs: i was thinking of bug 1091588 - even if you'd have to set the locale in the template, it would make translating the template easier at least.
10:42 pinesol_green Launchpad bug 1091588 in Evergreen "Send out emails in patron's preferred language" (affected: 1, heat: 6) [Wishlist,Confirmed] https://launchpad.net/bugs/1091588
10:43 dbs paxed: I understand, I still think it's likely to be painful. but anything is doable
10:43 phasefx paxed: give me a specific interface to consider and I can tell you what it'll take
10:43 paxed phasefx: Open-ILS/src/templates/acq/po/view.tt2
10:44 kmlussier I was just noticing that the most recent 2.4 doc additions aren't appearing in the official docs. That would be my acq admin and staff client additions that were pushed Friday night as well as some docs from akilsdonk_. Should they be showing up by now?
10:44 akilsdonk_ kmlussier: I'm working on that right now :)
10:44 * dbs is going to push a fix for Makefile.install for Fedora as a separate commit, hopefully nobody minds that there's no sign-off. because I doubt anyone will sign off on it anytime soon :)
10:45 akilsdonk_ I have a few docs that aren't showing up, and I'm trying to figure out why and fix them
10:45 kmlussier akilsdonk_++ Thanks! I meant to ask the other day, but your recent commits reminded me. I wasn't sure if my docs broke something.
10:46 phasefx paxed: so all the acq interfaces are wrapped in browser.xul/browser.js, so that's good
10:46 dbs akilsdonk++
10:47 akilsdonk_ kmlussier: I'm finding that my missing docs seem to be the result of bad asciidoc
10:47 phasefx paxed: in browser.js, there's a push_variables method (you can also push functions, but if we want to let the acq interfaces work or potentially work outside of the staff client, we should be wary of that)
10:48 dbs akilsdonk_ kmlussier: some of the builds are pickier / better at showing errors than others; if you can do "a2x --format epub" that's one of the pickiest
10:48 pinesol_green [evergreen|Lebbeous Fogle-Weekley] TPAC: First part of locg param can be branch shortname - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=dcf9cb3>
10:48 pinesol_green [evergreen|Dan Scott] Fedora RPM for bzip2 headers is bzip2-devel - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=3b828af>
10:49 phasefx paxed: I think we want to push a more direct reference to hash.aous from OpenILS.data into the xulG object being pushed by browser.js.  Then the acq interface can look for that (and fallback to something else if it's not there)
10:50 paxed phasefx: another thing, i think commonStrings isn't available in there either.
10:51 paxed phasefx: this is like a Frankenstein's monster ...
10:51 phasefx yeah
10:52 dboyle joined #evergreen
10:52 kmlussier dbs: Thanks for the tip. I'll try it next time.
10:52 phasefx paxed: an alternative is to push a wrapper function to util.money.format.. but again, I would code it so that the acq interface has a graceful fallback (even if it's no-I18N)
10:56 phasefx or, we can ignore the staff client and have redundant code and translations, done the dojo way.  Even if the xulG way is convenient, this probably cleaner/better for if we ever move away from XUL
10:57 paxed i feel like i'm a leetle bit over my head there.
10:58 paxed all of the money routines need i18n love.
10:59 paxed so might be better to rewrite the whole damn thing.
10:59 phasefx if none of the math was done client-side, I'd say make the server-side do the heavy lifting for I18N
11:01 paxed there's not much heavy lifting involved. just currency formatting, and the money separator chars.
11:02 paxed what i wrote earlier sums up my frustrations...
11:03 paxed "ohai, i'm a staff client UI. but you can't use messagecatalogs, 'cause i'm not a xul one"
11:06 kbeswick joined #evergreen
11:08 phasefx paxed: thinking about it, I think any dojo interface should be using dojo for this :-/
11:08 phasefx of course, I don't know how dojo i18n works...
11:08 paxed that makes two of us then :P
11:10 BigRig_ joined #evergreen
11:11 BigRig_ joined #evergreen
11:14 BigRig joined #evergreen
11:17 BigRig_ joined #evergreen
11:17 phasefx paxed: hrmm, I don't think the dojo stuff is even integrated into the update_pofiles script
11:18 phasefx it's got to be
11:18 paxed phasefx: you mean bug 1187316
11:18 pinesol_green Launchpad bug 1187316 in Evergreen "Translation toolchain misses some dojo nls files" (affected: 1, heat: 6) [Undecided,New] https://launchpad.net/bugs/1187316
11:19 BigRig__ joined #evergreen
11:19 zerick joined #evergreen
11:19 phasefx ah, I was looking for something less hard-coded
11:20 phasefx like, find all nls directories and their content :)
11:20 paxed blame dbs, maybe?
11:20 paxed :)
11:20 phasefx I blame dbs for nothing; he's the man :)
11:20 Ruth joined #evergreen
11:31 gmcharlt phasefx: I DO blame dbs ...
11:31 gmcharlt ... for inflicting a lot of cool stuff on Evergreen ;)
11:35 rfrasur jeff_:I was thinking about how Evergreen (or maybe Koha...but, of course, I love Evergreen) could be a software solution for clandestine libraries in conflict areas...but then was thinking about insurgency from unfriendlies and how would you protect a user base and still provide an OPAC
11:35 BigRig joined #evergreen
11:36 gmcharlt rfrasur: don't use circulation, for one, or at least nothing besides checking everything out to a dummy patron so that you know what's out
11:37 gmcharlt to be clear, I'm speculating
11:38 rfrasur gmcharlt: there's that, and the alias feature would be perfect in some ways.  But as far as using an OPAC, I was thinking how can you let disparate threatened user groups know what's available...but keep that from whoever the unfriendlies might be.
11:39 rfrasur circulation would be another consideration - but right now, I'm just thinking about how you let people know what's available to them without putting them in danger (or more danger...or whatever risk level is deemed appropriate)
11:39 gmcharlt hmm - distribute LiveDVDs that contain a copy of the catalog, not just a blank DB?
11:39 phasefx and while you're distributing the ILS, distribute public domain e-books, etc. while you're at it
11:39 rfrasur yes
11:40 rfrasur I dunno.  I just woke up thinking...this is something that could theoretically be used...can be light on cost..and can be customized to be more secure that some of the light online things.
11:40 * rfrasur wakes up thinking weird things
11:41 rfrasur (of course...then you also have to think re: translations)
11:41 BigRig_ joined #evergreen
11:43 ktomita joined #evergreen
11:46 kivilahtio author of the Serials::regenerate_summaries() is a naughty boy. There was a control statement bug there! Maybe someone will help me submit a patch tomorrow. Gotta go do some parkour!
11:47 BigRig joined #evergreen
11:48 rfrasur parkour...you go w/ your bad self.
11:48 * rfrasur will think diligently about parkour.
11:48 * rfrasur will not do any parkour outside of thought.
11:49 kivilahtio PARKOUR! We are going to a military obstacle course, kewlö!
11:49 kivilahtio good night chamos!
11:49 rfrasur kivilahtio++
11:49 rfrasur One of my knees just gave out at the thought.
11:50 rfrasur The other is threatening.
11:50 * rfrasur stops thinking so diligently
11:52 yboston joined #evergreen
11:54 eeevil rfrasur: you could put the opac behind the auth proxy, a la the /exporter location, in the apache config. at least then you can password protect the whole catalog
11:55 rfrasur eeevil:I knew it could be done...but didn't know how.  Thanks :-).  Now I have some of the right words to say (in the future...when there's someone to say them to)
11:59 phasefx heh, I can't edit bug status in launchpad with my version of chromium
12:02 mllewellyn joined #evergreen
12:08 dbs paxed: testing 1187316 right now
12:09 Ruth joined #evergreen
12:10 dboyle joined #evergreen
12:10 paxed how do you handle the ssl cert for the staff client in automatic client installs?
12:10 BigRig_ joined #evergreen
12:11 dbs poor little python works so hard to "make newpot"; dude, it's just strings
12:12 paxed well, you can't run very fast without legs ...
12:15 BigRig joined #evergreen
12:16 dbs paxed: added a commit to add the new POT files and their subdirs as well, so that "make updatepo" and "make newpo" wouldn't error out
12:16 dbs paxed++
12:17 paxed oh, i missed those. hmph. :/
12:19 pinesol_green [evergreen|Pasi Kallinen] Add missing dojo nls files to the i18n toolchain, and fix one of the files so they be built. - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=9b5a19f>
12:19 pinesol_green [evergreen|Dan Scott] Add new POT files to git so "make newpo" will work - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=d51fa3a>
12:19 paxed dbs: how about bug 1158218 too? ;)
12:19 pinesol_green Launchpad bug 1158218 in Evergreen "Improve db-seed-i18n.py to actually grab all strings for translation" (affected: 1, heat: 6) [Undecided,Triaged] https://launchpad.net/bugs/1158218
12:20 jihpringle joined #evergreen
12:20 paxed dbs: "so they be built" ??! :D
12:20 dbs that be right
12:24 dbs paxed: that one requires more testing, and I don't really have time. putting the whole thing on one line is known to work, and there are tests for it in tests/testSQL.py ; I'm loathe to add support for multiline parsing without corresponding tests
12:25 paxed ok, i guess i should write tests for it then too.
12:27 dbs added a comment correspondingly; in this case, it's just extending existing test data & expected output so it should be pretty easy to do
12:45 sseng_ How does a person add a predefine message in the drop down list for the "Apply Standing Penalty/Message" in the "Messages" tab of the staff client? Been trying to search around but not coming up with much.
12:45 stevenyvr2 joined #evergreen
12:47 ericar joined #evergreen
12:51 phasefx sseng_: you add a new Penalty Type from the Admin -> Server Administration menu
12:52 phasefx it won't populate the message area for you, but the type itself can serve as a message
12:52 dbs sseng_: http://en.flossmanuals.net/everg​reen-in-action/managing-patrons/
12:53 phasefx oops, Local Administration, per dbs' link :)
12:53 sseng_ phasefx: dbs : going to give that a go, thanks!
12:54 dbs feel free to purchase a copy of Evergreen in Action to support the project: http://evergreen-ils.org/dokuwiki/do​ku.php?id=books:evergreen_in_action :)
12:55 sseng_ dbs : got a copy =)
12:57 sseng_ phasefx: dbs : There are exisiting standing penalties, but, these doesn't appear to show up in the dropdown list at all for the  "Apply Standing Penalty/Message" in the "Messages" tab of the staff client. The dropdown appears to alwasy be empty.
12:57 phasefx sseng_: it's new ones you create that will show up in the drop-down.. the stock ones get used in other ways
12:57 kmlussier dbs++
12:58 sseng_ phasefx: ah I see, thanks!
12:58 phasefx sseng_: you'll also need to logout of and back into your staff client after creating some, for them to show up
13:00 dbs sseng++
13:00 sseng_ phasefx: showing up now, thank you!
13:01 mtcarlson joined #evergreen
13:07 ldwhalen joined #evergreen
13:07 jdouma joined #evergreen
13:09 * dbs shakes head slowly at mutt and google's ssl certificates
13:11 paxed dbs: i'm adding some contrived test cases, not just examples lifted out of 950.*.sql
13:11 dbs paxed: cool, exercise it thoroughly :)
13:13 kyleonalaptop joined #evergreen
13:16 mjingle joined #evergreen
13:27 paxed i'm having a braino. how do i delete a remote branch? i know the syntax, but i can't seem to be able to do it...
13:28 dbs Dyrcona++
13:28 Ruth joined #evergreen
13:28 mjingle joined #evergreen
13:28 jcamins_ git push remote :branchname
13:28 dbs git push working :remote_branch_name
13:29 paxed istr i tried that earlier... ahwell, i'll try again in a bit.
13:30 * dbs is pretty sure you can't do "git push origin :master" :)
13:30 rfrasur does anyone know if the planning committee for eg2014 has been announced yet? and if there's a website?  I've not seen anything come through listserv, but have been known to miss things.
13:31 dbs well, not if "origin" is mapped to the remote at git.evergreen-ils.org, anyway
13:31 dbs rfrasur: I think kmlussier, bshum, and amy terlaga are involved...
13:32 rfrasur dbs: thank you.  I'll give a shout-out to them.
13:34 kmlussier rfrasur: We have just started with the planning and don't expect to have a web site up until August.
13:35 rfrasur kmlussier: okay :-D - just been thinking as I've been talking to other EG librarians and wanted to know in what directions to send those thoughts.  I apologize in advance.
13:35 * kmlussier fears that August will come sooner than expected. :(
13:35 kmlussier rfrasur: I'll take whatever thoughts you want to send my way. :)
13:36 rfrasur kmlussier: Also, if there's something that doesn't require a vast amt of tech know-how, I'd be willing to TRY and help.
13:36 paxed dbs: the branch now has test cases too. dunno if it was ok to delete the remote branch and recreate it from my local one ...
13:37 rfrasur hmm, I suppose in this "room," I should say...barely any tech know-how
13:38 paxed (what's the best way to handle a case where your local repo doesn't have the same branch? i just created a branch, cherry-picked the changes from the remote one, hacked, amended commit, deleted the remote branch and pushed my local out as the same name branch...)
13:39 dbs paxed: okay with me
13:40 dbs you could "git push -f remote local_branch:remote_branch" if you want to force your new branch to replace the old branch
13:40 * paxed is scared of -force flags :)
13:41 paxed aiui, the user branches on eg server are more-or-less volatile and non-canonical anyway, so deleting and recreating shouldn't hurt
13:41 ericar joined #evergreen
13:41 dbs to an extent, yeah. -f is basically the same as delete & recreate
13:42 paxed ah
13:42 dbs in fact, when I run "git fetch working" it says your branch was "(forced update)" :)
13:43 paxed huh.
13:44 Dyrcona Yep, me, too.
13:45 Dyrcona Another way to force update is with the + sign before the branch name.
13:45 pinesol_green [evergreen|Pasi Kallinen] Improve the db-seed-i18n.py -script to actually grab all strings. - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=f572768>
13:45 Dyrcona git push remote +branch:remote_branch
13:46 * Dyrcona fetches && pulls for the xth time today.....Somebody has been busy. :)
13:48 * dbs jumps when dwells cracks the whip
13:48 dbs sadly, all of my typing skills have gone down the drain
13:50 paxed how soon should i relete the branch once the changes have been committed?
13:50 ldwhalen joined #evergreen
13:50 paxed s/relete/delete/
13:51 * dbs is a terrible person to ask
13:52 * dbs has 309 branches in working
13:53 berick yeah, paxed, you can give it about 5 years ;)
13:53 paxed hah
13:53 Dyrcona paxed: Do you want to delete the branch from your repository or from the remote?
13:53 Dyrcona git branch -D branch_name # for local
13:53 paxed Dyrcona: yeah, i know.
13:54 paxed i dunno what the problem earlier today was, i just couldn't delete a remote branch, no matter what i tried.
13:54 paxed but it works now.
13:54 Dyrcona git push remote :remote_branch_name
13:54 Dyrcona cool.
13:56 yboston heads up, the DIG monthly meeting will be starting at 2 PM EST
13:56 dbs DIG++
13:56 kmlussier Speaking of meetings, I'm a little late on this, but I think we're due for a developers meeting. Next week sound good?
13:57 * dbs runs "a2x --format epub root.txt" just for fun
13:57 rfrasur yboston: is it in here or in the developer channel?
13:57 rfrasur err...is there a developer channel?
13:57 * rfrasur goes to look
13:57 * dbs gets "returned non-zero exit status 1" - bah
13:57 berick kmlussier: +1
13:57 kmlussier rfrasur: I was just about to ask the same question. :)
13:58 rfrasur kmlussier++
13:58 * dbs reruns with "a2x --verbose --format epub root.txt" and gets "asciidoc: FAILED: my_lists.txt: line 64: 'UTF-8' codec can't decode "1)      Physical location � the physical library location where the search takes place"
13:58 * dbs shall fix!
13:59 kmlussier rfrasur: I've often heard this channel refered to as the developers channel, but I personally object to that characterization.
14:00 sal_ joined #evergreen
14:00 * kmlussier would love to see more non-devs like rfrasur and me in this channel.
14:00 dbs ah, latin1 encodings
14:00 * dbs loves seeing rfrasur and kmlussier in this channel
14:00 dagreen joined #evergreen
14:00 yboston rfrasur: I am not an expert on Evergreen practices, but normally Evergreen meetings happen on this channel, but there is an alternate channel so other can use while a meeting is taking place. I forget what the other channel is called or its URL/name
14:00 rfrasur kmlussier:I said that and then thought...oh snap...I think that's here.
14:00 rfrasur yboston:gotcha.  I knew most other meetings were...but yeah.
14:00 yboston (not an expert an Evergreen IRC practices)
14:01 rfrasur dbs++
14:01 mjingle rmlussier: I'm not a dev, yet! :)
14:01 yboston s/an/on/
14:01 yboston oops, it is 2 PM already
14:01 rfrasur lol
14:01 * rfrasur shuts up...kinda
14:01 kmlussier mjingle++ I like the "yet" part of that statement. :)
14:02 yboston #startmeeting 2013-05-02 - DIG Monthly Meeting Evergreen Documentation Interest Group (DIG) Monthly Meeting. The agenda can be found here http://evergreen-ils.org/dokuwiki/doku.php?i​d=evergreen-docs:dig_meeting_20130606-agenda
14:02 pinesol_green Meeting started Thu Jun  6 14:02:08 2013 US/Eastern.  The chair is yboston. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:02 pinesol_green Useful Commands: #action #agreed #help #info #idea #link #topic.
14:02 pinesol_green The meeting name has been set to '2013_05_02___dig_monthly_meeting_evergreen​_documentation_interest_group__dig__monthly​_meeting__the_agenda_can_be_found_here_http​___evergreen_ils_org_dokuwiki_doku_php_id_e​vergreen_docs_dig_meeting_20130606_agenda'
14:02 yboston #topic Introductions
14:02 yboston Please feel free to start introducing yourselves...
14:02 rsoulliere joined #evergreen
14:02 * kmlussier is Kathy Lussier, MassLNC
14:03 * yboston is Yamil Suarez @ Berklee college of Music - DIG meetings facilitator
14:03 * rfrasur is Ruth Frasur, Evergreen Indiana
14:03 * rsoulliere is Robert Soulliere, Mohawk College
14:03 pinesol_green [evergreen|Dan Scott] Fix Latin-1 encoding that broke doc output - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=96c877e>
14:05 yboston we might be a small crowd today, but any meeting that Robert and Kathy attends is a success to me
14:05 yboston #topic Updates from Content Coordinators
14:05 yboston We will continue having the content corrdinators try out the "#topic" AND "#info" Meetbot commands for their reports
14:05 yboston So content coordinators, please use "#topic" for the first post/line of your report
14:05 yboston then use "#info" for every other chat post/line of your report.
14:05 yboston for example...
14:06 yboston #topic this is a test report first post/line
14:06 yboston #topic this is a test report first post/line
14:06 yboston #topic this is a test report first post/line
14:06 yboston #info this is a test report second post/line
14:06 yboston (sorry having pasting issues)
14:06 yboston who would like to go first..
14:07 kmlussier #topic DIG Release Coordinator Report
14:07 kmlussier #info Nothing to report in terms of release coordination.
14:08 kmlussier #info I did get some udpated 2.4 acq docs done, but have a few more to work on.
14:09 kmlussier #info I also added some staff client docs for configuring pre-set tabs in the staff client when logging in.
14:09 kmlussier End of report.
14:10 yboston btw, I had my intern convert some old preset-tabs documentation too, have not compared it with what you did yet
14:10 kmlussier yboston: I think it's the same thing, except I added auto-login stuff that wasn't available in 2.1.
14:11 kmlussier The original docs came from me, and I had them sitting on a PC in asciidoc format all ready to go.
14:11 kmlussier Correction, they came from Tracy Swaim at MVLC. I just adapted them.
14:11 yboston kmlussier:  my apologies for not coordinating better
14:12 kmlussier yboston: Sure, I also knew you were upgrading, so probably should have checked. The question came up in IRC recently, which is why I went looking for them.
14:12 yboston rsoulliere: do you have anything to report on or comment on?
14:12 rsoulliere sure, I can go...
14:12 rsoulliere #topic Conversion Coordinator Report
14:13 rsoulliere #info  Nothing new to report this time except that we are getting a few more folks contributing directly to the repository.
14:15 rsoulliere That is the end of my report.
14:15 rsoulliere ... in case you were waiting for mre ;-)
14:15 rsoulliere "more"
14:15 yboston BTW< I am having IRC display issues, which makes it hard to see what folks are saying
14:15 yboston so thanks rsoulliere  and kmlussier
14:16 yboston I will go next
14:16 yboston actually, let me log on and off for a quick moment
14:16 yboston never mind, that will stop the meetbot meeting
14:16 rick__ joined #evergreen
14:17 yboston #Topic Berklee Spring 2013 intern update
14:17 kmlussier yboston: No, I don't think it will stop the meeting. IRC kept kicking me out of one of the meetings I was chairing, but I think it went on.
14:17 yboston #info intern is done with her work, I have started to update this DIG outline page with the sections she converted. Her two last major contributions was Corralling and converting all of the different "cataloging" sections spread out over the various versions of the documentation, into a single section
14:17 yboston #info on the intern's last day I had her convert the only section that covered "action triggers" in versions 1.6/2.0 of the docs, and I sent a copy to Chris Sharp of PINES, to see if he wanted to update a few things. This is something we talked about after his great presentation on action triggers at the last conference
14:17 rick__ I am having problems getting SIP Server up and running
14:18 yboston #info on the intern's last day I had her convert the only section that covered "action triggers" in versions 1.6/2.0 of the docs, and I sent a copy to Chris Sharp of PINES, to see if he wanted to update a few things. This is something we talked about after his great presentation on action triggers at the last conference
14:18 yboston rick__: we are having a documentation meeting until around 3 PM EST
14:18 yboston rick__:  can you repeat your question when we are done meeting, so someone else can help you?
14:19 kmlussier yboston++ Corralling the cataloging documentation was a big job that was sorely needed.
14:20 yboston my approach is to have it all in one asciidoc document, but I have not decided how to best organize it
14:20 yboston or order it. I also assume there are several sections that can be merged
14:20 yboston I just wanted to at least have it in asciidoc format
14:21 yboston #info  "Corralling the cataloging documentation was a big job that was sorely needed."
14:22 kmlussier yboston: I'm wondering, is it best to have it in one asciidoc document or is it best to break it out into several documents to make it easier to re-organize in the future?
14:22 kmlussier It's a question I've been pondering as I've been working on my own docs.
14:22 yboston #info I just wanted to at least have it in asciidoc format. my approach is to have it all in one asciidoc document, but I have not decided how to best organize it or order it. I also assume there are several sections that can be merged
14:23 yboston kmlussier: there are definite some pro and cons to having a single file, I am not experienced enough to know them off the top of my head
14:24 yboston kmlussier: I mostly just recreated the approach taken by the older docs we converted, if they were in multiple files we mostly kept them in multiple files.
14:24 kmlussier yboston: Sounds reasonable.
14:24 rsoulliere I've taken a 1 file per chapter approach.
14:25 yboston kmlussier:  for the cataloging docs, i think at first they were in a single file, and since I was in consolidation mode for now I kept them in a single file
14:25 yboston actually it was the intern that did the "dirty work"
14:27 yboston I was hoping that whenever I am done submitting the cataloging docs, that I will announce it in the cataloging list (and others) to see if we can get volunteers to expand/edit/merge the docs
14:28 yboston #info I still need to write a little bit of new content on cataloging with authorities in the cataloging chapter, since the sections are currently blank
14:29 yboston that is basically all for me. please, please continue with your comments or questions to me, or we can move on to something else
14:29 kmlussier yboston++ Another area that desperately needs docuementation. Good work!
14:29 kmlussier +1 to moving on.
14:29 yboston let me try to reconnect, since it is hard to read the responses
14:30 yboston joined #evergreen
14:30 yboston what did I miss?
14:30 yboston :)
14:30 yboston (beside kathy asking to move on?
14:30 kmlussier lol - we volunteered you for everything!
14:30 yboston :)
14:31 rfrasur kmlussier++
14:31 gmcharlt #(notreally)agreed yboston will write ALL THE DOC
14:31 yboston :)
14:31 kmlussier gmcharlt++
14:32 rfrasur gmcharlt++
14:32 yboston the only "old business" I had listed was  "Brainstorm on ideas from Vancouver conference (Yamil)"
14:32 yboston we can also do some brainstorming on ideas for the next conference, and ideas for a documentation hack-a-way
14:33 yboston BTW, since I will not be traveling to this conference (since it will be in Boston/Cambridge) I plan to travel for the developer hack-a-way in Spetember, in case someone from DIG was to join me there
14:33 rfrasur I think this is an area where librarians could potentially (as evidenced by Ms. Lussier) contribute, but I wouldn't know where to begin directing people who want to get involved.
14:34 krvmga joined #evergreen
14:34 kmlussier yboston: I was considering the trip, but it ends on the day before my daughter's birthday, so I'm feeling conflicted.
14:35 yboston rfrasur brings up an important point. a lot of people in the community, including the Evergreen Oversight Board, how do we lower the bar for participation
14:35 krvmga i'm at a tech services roundtable atm, which is why i'm not at the DIG meeeting
14:35 rfrasur Is the hackaway in MI? (am I vaguely remembering it around Calvin College?)
14:36 * yboston waves at krvmga
14:36 yboston rfrasur: yes
14:36 * krvmga waves at yboston.
14:36 kmlussier yboston: I'm somewhat stumped on lowering the barrier. I think it's important that we always reiterate that we take documentation in any format, but we've done it all along.
14:36 ltreat joined #evergreen
14:36 rfrasur (my hometown means free board)
14:36 kmlussier I think the biggest barrier is time.
14:37 rfrasur kmlussier: I'm not sure about the bar being lowered as just saying what exactly needs to be documented.
14:37 rfrasur where do they go to see what is and what needs to be, etc.
14:38 krvmga i think that's a good idea.
14:38 yboston for me since I know exactly what needs to be done, time is definitely my biggest issue, but that is also because we can thick of so many things that I could work on for DIG
14:38 krvmga i was thinking of sponsoring a contest to help with the reports documentation that we're working on right now
14:38 yboston I am think of what small taks can I decide for a beguiner volunteer that can be broken down in simple chimks, where time is not such a concern
14:38 kmlussier rfrasur: Sure, with the 2.4 release, I tried to identify some of those needs by pulling this together - http://evergreen-ils.org/dokuwiki/d​oku.php?id=evergreen-docs:2.4_needs
14:39 kmlussier And I was thinking if I went through the 2.3 release notes, I could come up with a similar list of things that still haven't been documented from 2.3
14:39 rfrasur kmlussier++
14:39 yboston sorry, "simple chunks"
14:39 ldwhalen joined #evergreen
14:39 kmlussier But, then, there are things like some of the admin interfaces for the new search features. I think there are very few people in the DIG community who would know how to document those.
14:40 rfrasur yboston: I think that'd be a great way to get more involvement from libs...and then, with experience, new people could take larger chunks.
14:40 rfrasur honestly, I think (know) a lot of librarians that know stuff but are afraid they don't know enough to be of value.
14:40 kmlussier yboston: bitsize documentation needs? :)
14:41 Rogan_ joined #evergreen
14:41 rfrasur (funsize?)
14:41 kmlussier Sorry, I meant to say bitesize.
14:41 yboston kmlussier: exactly, just like what we do for google summer of code candidates
14:41 yboston kmlussier: but of course it takes effort to come up with those
14:42 rfrasur bitsize might be appropriate at times :D
14:42 yboston also I am thinking of giving a session of just solely teaching people how to write ascii doc.
14:42 krvmga all the bitesized things i have require more detailed knowledge ofthe system in order to document
14:42 rfrasur yboston++
14:42 yboston at the conference, and asking people to bring their laptops so we all leave the session with some documentation ccreated
14:42 krvmga yboston: how about converting from various formats into asciidoc?
14:43 rfrasur krvmga: developer level knowledge?
14:43 yboston like from microsoft word to asciidoc
14:43 yboston ?
14:43 krvmga rfrasur: in many cases
14:43 krvmga yboston: one of my staff has done a pile of documentation of report data sources but its all in an excel spread sheet !!!
14:43 rfrasur yboston: I'd go to that session and encourage others to do the same.  during the hackfest or conference proper?
14:44 yboston rfrasur: either
14:44 krvmga yboston:so i'm trying to work with her to get it out of the sheet and into asciidoc
14:44 yboston or maybe create a screen cast
14:45 krvmga yboston: or, for instance, i have a bunch of documentation in LaTeX
14:45 krvmga there may already be a converter for that
14:45 rfrasur yboston:here's one vote in favor fwiw
14:47 yboston krvmga: you definitely made me think what to do after I teach the basics of asciidoc, I can bring in some word submission and have the class convert different chunks, for example
14:48 krvmga yboston++
14:48 rfrasur yboston++
14:48 gmcharlt krvmga++ # LaTex
14:48 krvmga gmcharlt: lol
14:49 gmcharlt anybody_writing_doc_in_structured_format​s_including_Word_using_styles_properly++
14:49 rfrasur gmcharlt++
14:49 krvmga gmcharlt++
14:49 yboston my main theme is that I want people to participate in a hands on training session via a webinar/google hangout/confernce session. they need to bring their laptops and get their hands dirty
14:50 krvmga yboston: yes, i think that's a great plan.
14:50 rfrasur yboston: great idea.  how about tomorrow?
14:50 * rfrasur kids...or not.
14:51 kmlussier yboston++
14:51 yboston at the latest I want to do this at the next conference, but I would prefer it happens outside of the usual DIG meeting time
14:51 yboston but perhaps that will be the only time
14:51 kmlussier Related to that, we have been talking about having a full-day DIG hackfest at next year's conference, and I really would love to see that happen.
14:52 rfrasur yboston: I agree that it should be separate
14:52 rfrasur kmlussier++
14:52 krvmga kmlussier++
14:52 yboston even if we only end up working for two hours and then an hour for our DIG meeting, that will be a step forward
14:52 phasefx random thought, try to invite trainers
14:52 kmlussier phasefx++
14:53 yboston phasefx++
14:53 rfrasur kmlussier: that sounds like a great idea.  would having a DIG training workshop (or whatever you want to call it) be appropriate during hackfest?
14:53 rfrasur phasefx++
14:53 krvmga phasefx++
14:54 yboston rfrasur: I think it is, though there is the tough decision if it should happen in the same room
14:54 kmlussier rfrasur: I think it would be a great way to kick off the hackfest. They can then apply the new skills they learned during the hackfest.
14:55 yboston one of the things we want to extoll is that anyone in the community can contribute something, even if they are not coders
14:55 krvmga kmlussier: yes, good observation
14:55 rfrasur I'll be honest.  I didn't go to the hackfest this past year because it didn't seem like something I could contribute...
14:55 rfrasur yboston: exactly
14:55 kmlussier rfrasur: But if you knew there was something specifically for people who want to do documentation, would you have looked at it differently?
14:56 rfrasur kmlussier: yes - and that's why I was interested in who was planning what.
14:57 yboston back to the theme of trainers. I want to see sessions where we do hands on training (if possible). we there will be some explanations and some pre-panned bite size problems for everyone to solve, that are solvable in a straighahead way
14:58 yboston without toying up a developer that could be collaborating with other developers during the hackfest
14:58 rfrasur kmlussier:two reasons - first, speaking for myself, if I knew there was something that I could do (like write documentation), I'd be there to do it.  Second, more broadly, you put people working toward a common goal (the awesomeness and world domination of EG) together and it builds enthusiasm...and giving them something to do gets them there.
15:00 yboston btw, it is 3 PM EST
15:00 rfrasur yboston: This is a great idea.  I wouldn't know how to implement it, but it's a great idea.
15:00 rfrasur "this" referring to everything you said.
15:01 yboston #idea think of ways to offer hands-on documentation training during conference hackfest
15:01 yboston #idea think of ways to offer hands-on documentation training during developer hack-a-way or separate DIG hack-a-way
15:03 yboston should we wrap up for now? or do we want to go on a little longer?
15:04 kmlussier I need to wander off.
15:05 krvmga i'll just be hanging out here in case i need to ask a question
15:06 yboston OK folks, until next month
15:06 krvmga thanks!
15:06 krvmga yboston++
15:06 kmlussier yboston++
15:06 yboston #endmeeting
15:06 pinesol_green Meeting ended Thu Jun  6 15:06:30 2013 US/Eastern.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
15:06 pinesol_green Minutes:        http://evergreen-ils.org/meetings/evergr​een/2013/evergreen.2013-06-06-14.02.html
15:06 pinesol_green Minutes (text): http://evergreen-ils.org/meetings/evergr​een/2013/evergreen.2013-06-06-14.02.txt
15:06 pinesol_green Log:            http://evergreen-ils.org/meetings/evergree​n/2013/evergreen.2013-06-06-14.02.log.html
15:07 b_bonner joined #evergreen
15:10 rfrasur apologies - important phone call
15:10 rfrasur yboston++
15:10 mtcarlson joined #evergreen
15:17 Dyrcona gmcharlt: Got a couple minutes to talk about NCIP?
15:26 acoomes joined #evergreen
15:35 gmcharlt Dyrcona: OK, the repos for NCIPServer now exist on git.evergreen-ils.org
15:35 Dyrcona gmcharlt++
15:52 pinesol_green [evergreen|Pasi Kallinen] Allow translating the staff client tab names - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=ad86ef5>
15:59 bshum We could probably skip having the staff.client.portal.toggle_tpac.message_* values on that index.xhtml page.  Since we don't have that toggle anymore.
15:59 paxed indeed
15:59 bshum dbs: Thanks for fixing the IRC web page.  Been away from my desk all day driving around CT.
16:02 pinesol_green [evergreen|Steven Callender] Add the copy number to the list of data being pulled for access by the TPAC. - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=8f03641>
16:02 Dyrcona Is there a configuration that needs to be done to have working/NCIPServer pick up commits to NCIPServer's master branch?
16:05 gmcharlt Dyrcona: yep -- and now that there's a master branch to pull from, I'll set that up
16:05 Dyrcona gmcharlt++ # Thanks muchly.
16:06 jeff_ so is the community in general leaving the MCLS NCIP work / iNCIPit cgi alone, in favor of a from-scratch implementation?
16:07 Dyrcona jeff_: It would appear so, yes.
16:07 jeff_ just verifying. i'd like to know where to focus my efforts.
16:08 bshum Maybe its just me, but it looks like phasefx is committing from the future.  By just a few minutes but it's wigging me out man!
16:08 gmcharlt :)
16:09 * phasefx wiggles his chaos fingers
16:09 Dyrcona jeff_: Looks like we might be putting your RESTful API to the test, too.
16:10 gmcharlt bshum: there's a reason we never let phasefx drive at exactly 88 mph
16:10 jeff_ cool. in any context of NCIP, or unrelated?
16:10 Dyrcona jeff_: In context of NCIP.
16:10 bshum gmcharlt++ :)
16:10 gmcharlt jeff_: and with any luck, in the context of NCIP and Koha too
16:10 mtcarlson joined #evergreen
16:11 mcarlson joined #evergreen
16:11 Dyrcona jeff_: My goal is to make NCIPServer something that Koha can use, too, thought that might not happen right away.
16:11 Dyrcona s/thought/though/
16:11 jeff_ sure. similar goal with the REST api.
16:19 rs233 joined #evergreen
16:20 jeff_ can you expand at all on how you see the REST and NCIP bits cooperating?
16:21 rs233 Hi, I have been having issues and have just about exhausted my options for getting the SIP Server running correctly
16:22 pinesol_green [evergreen|Pasi Kallinen] Allow translating more strings in xul-files. - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=109e8e0>
16:22 pinesol_green [evergreen|Jason Etheridge] fix copy/paste error - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=8c4192c>
16:22 Dyrcona rs233: Go ahead if someone can answer your questions, they will.
16:23 gmcharlt jeff_: the NCIP responder (a la the XC toolkit) would be ILS-independent, and require a specific ILS connector to be written
16:24 gmcharlt the idea being kicked around is that the connector would choose to communicate with Koha or Evergreen strictly via the RESTful API
16:24 jeff_ cool. i am interested in these discussions. where are they taking place?
16:25 Dyrcona jeff_: Right here, right now.
16:25 jeff_ excellent. i'm in the right place. :-)
16:25 rs233 I followed the instructions on installing the SIP Server but when I go to start the server it states it is alread runnin ... when I restart it says No Such process
16:26 jeff_ is the intent to use the XC toolkit's NCIP bits, or not?
16:26 jeff_ i.e., xcncip2toolkit and such
16:26 gmcharlt jeff_: I'm considering it for the Koha piece due to a timing issue
16:26 Dyrcona rs233: Try ps ax | grep SIPServer and see if it is running.
16:26 mjingle joined #evergreen
16:27 tspindler left #evergreen
16:27 Dyrcona jeff_: NCIPServer is intended to be a Perl NCIP responder that can be used with mod_perl.
16:27 rs233 ps ax | grep SIPServer shows it is Not infact running
16:28 Dyrcona rs233: Ok. What command line do you type to start it?
16:28 Dyrcona rs233: There is more than one way to start it actually.
16:28 rs233 oils_ctl.sh -d /openils/var/run -s /openils/conf/oils_sip.xml -a start_sip
16:29 bshum Maybe the PID is in the way
16:29 bshum An older one
16:29 gmcharlt specifically, check to see if there's a file called  /openils/var/run/oils_sip.pid (or something close to that name)
16:29 gmcharlt if, you can delete it and try the startup command again
16:32 bshum Huh
16:32 bshum When I try to add a copy to a copy bucket, it errors out unhappily.
16:33 bshum Transaction commit error
16:33 bshum Looking at the logs, it's complaining about a foreign key reference issue where the target copy ID isn't in asset.copy
16:33 rs233 same result after rm oils_sip.pid and re-issuing start command
16:33 bshum But looking up the ID it's there.
16:35 eeevil bshum: it's in serial.unit, dollars to donuts
16:35 bshum Bleh
16:35 bshum I bet that's it :(
16:35 bshum It is a magazine or something
16:36 eeevil bshum: there is a DROP CONSTRAINT for copy buckets in an upgrade script, I think (hope!), that removes that fkey, IIRC
16:36 eeevil if not, you can drop that fkey. it's fine
16:36 eeevil (except you lose the magical delete, but they don't delete today anyway -- copies are protected)
16:37 bshum Right.
16:37 bshum @hate serials
16:37 pinesol_green bshum: The operation succeeded.  bshum hates serials.
16:37 eeevil paxed: gdunbar stole me for more of the day than anticipated ... I'm happy to try to find time again tomorrow if you like ... sorry :)
16:39 bshum eeevil: I haven't found it in any upgrade script yet.  But I assume something like...
16:40 bshum ALTER TABLE container.copy_bucket_item DROP CONSTRAINT copy_bucket_item_target_copy_fkey;
16:40 paxed eeevil: whenever's good for you, i pm'd you the address and the passwd.
16:42 Dyrcona rs233: You're sure the pid file was actually deleted?
16:42 rs233 yes i checked ls efore and after the rm command
16:43 eeevil paxed: I see that now! thanks, I will look for a likely time ASAP
16:45 pastebot "rs233" at 204.193.129.146 pasted "SIPServer response" (3 lines) at http://paste.evergreen-ils.org/13
16:45 eeevil bshum: probably similar
16:45 * eeevil disappears in a puff of smoke
16:45 rs233 Dyrcona: pasted response from restart cmd
16:46 paxed eeevil: assuming i'm not asleep, pinging me here couple hours beforehand would be sufficient. you can also sudo su on the server.
16:46 bshum eeevil: If it works and I can't find a bug or fix somewhere, I'll put something to LP.  Thanks!
16:47 bshum Yep, it works.
16:47 bshum eeevil++
16:49 Dyrcona rs233: Is there a /tmp/oils_sip.pid file?
16:50 rs233 Dyrcona: no
16:50 Dyrcona rs233: Look again for /openils/var/run/oils_sip.pid and delete it if it is there.
16:51 rs233 Dyrcona: done
16:51 bshum eeevil: Found it, bug 1152753.  I'll mark it up as confirmed, etc.
16:51 pinesol_green Launchpad bug 1152753 in Evergreen 2.4 "Serial Units won't go into Copy Buckets" (affected: 2, heat: 10) [Medium,Confirmed] https://launchpad.net/bugs/1152753
16:51 Dyrcona rs233: run just ./oils_ctl.sh -a start_sip
16:51 rs233 ls
16:52 rs233 lol
16:52 Dyrcona :)
16:53 pinesol_green [evergreen|Lebbeous Fogle-Weekley] "Return to record" after submission of phone number on SMS page fixed - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=fd91f3a>
16:53 pastebot "rs233" at 204.193.129.146 pasted "SIPServer" (12 lines) at http://paste.evergreen-ils.org/14
16:54 rs233 Dyrcona: Pasted output
16:56 Dyrcona rs233: Where is your SIPSever installed?
16:59 Dyrcona rs233: If you're SIPServer directory is not /opt/SIPServer, you'll want to make /opt/SIPServer a link to your SIPServer directory.
16:59 Dyrcona s/you're/your/
16:59 * Dyrcona growls at himself.
17:00 mdriscoll left #evergreen
17:00 Dyrcona rs233: Does the above make sense?
17:01 rs233 Dyrcona: my opt directory appears to be empty, and I am not completely sure where SIPServer could be installed... havent had alot of luck from the Vendor configuring the server as of late
17:02 moodaepo_nb joined #evergreen
17:02 jeffdavis joined #evergreen
17:03 mrpeters left #evergreen
17:06 rs233 Dyrcona: I reissued git command in opt directory and verified SIPServer installed tried running SIP again same results
17:08 Dyrcona rs233: oils_ctl.sh expects the SIPServer to be in /opt/SIPServer
17:08 Dyrcona rs233: Well, the stock one does.
17:09 Dyrcona rs233: Delete the pid file again. When you start sip add -l some_filename to the end. -l will log SIP output to whatever file comes after it.
17:13 pastebot "rs233" at 204.193.129.146 pasted "SIPServer" (6 lines) at http://paste.evergreen-ils.org/15
17:14 rs233 Dyrcona: Pasted
17:14 Dyrcona rs233: Looks like a problem with your configuration file. probably missing a close tag around line 151.
17:15 pinesol_green [evergreen|Jason Etheridge] lp1183525 Edit Item Attributes pop-up dimensions - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=3e10372>
17:17 Dyrcona I think this could be bug-worthy. oils_ctl.sh should probably send errors somewhere other than /dev/null by default.
17:17 mjingle joined #evergreen
17:19 * gmcharlt gibbers
17:19 gmcharlt Dyrcona: yeah, I think that's bug-worthy
17:22 phasefx berick: I'm going to push a branch with the Current Shelf Library column
17:23 phasefx well, first I'm going to make sure I didn't break master :)
17:24 rs233 Dyrcona: I think I found where A problem is where I added a line to the xml that was not exactly correct.. I believe the Server is runnin now will try some testing
17:25 Dyrcona rs233: Good luck!
17:25 berick phasefx++
17:25 rs233 I might be back tomorrow lol
17:44 rs233 left #evergreen
17:59 ldwhalen joined #evergreen
18:04 mllewellyn joined #evergreen
18:48 _bott_ joined #evergreen
18:48 phasefx_ joined #evergreen
18:48 paxed joined #evergreen
19:04 _bott_ joined #evergreen
19:04 phasefx_ joined #evergreen
19:04 paxed joined #evergreen
19:27 mjingle left #evergreen
19:51 RBecker joined #evergreen
20:04 pinesol_green [evergreen|Lebbeous Fogle-Weekley] Acq: Be fuzzy about case when retrieving EDI documents - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=28c1000>
20:20 pinesol_green [evergreen|Ben Shum] Remove unnecessary TPAC toggle strings on staff client splash page - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=e9531be>
21:21 mtcarlson joined #evergreen
23:36 ldwhalen joined #evergreen
23:53 zerick joined #evergreen

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