Evergreen ILS Website

IRC log for #evergreen, 2014-01-31

| 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
02:20 DPearl joined #evergreen
03:30 DPearl joined #evergreen
08:04 collum joined #evergreen
08:15 akilsdonk joined #evergreen
08:33 Shae joined #evergreen
08:36 kbeswick joined #evergreen
08:36 adbowling-isl joined #evergreen
08:41 mrpeters joined #evergreen
08:43 mmorgan joined #evergreen
08:45 Dyrcona joined #evergreen
08:52 * Dyrcona should check for updates before signing into IRC. :)
08:53 * Dyrcona is going to reboot the laptop.
08:56 ericar joined #evergreen
08:57 Dyrcona joined #evergreen
08:59 _bott_ joined #evergreen
08:59 _bott_ left #evergreen
08:59 _bott_ joined #evergreen
09:02 csharp mac--
09:02 csharp apple--
09:02 Dyrcona yes, definitely.
09:03 csharp if you're going to be UNIX-based, why not follow UNIX conventions? tell me that huh? HUH?
09:03 Dyrcona Because you're Apple, not NeXT.
09:05 Dyrcona 'Course, when dealing with UNIX, you have to ask which UNIX conventions: POSIX, SUSP, System V, Release 7, BSD?
09:06 csharp that's a good point too
09:15 Dyrcona I guess you could throw GNU in there, too. :)
09:17 * berick mutters something about throwing stones in glass Evergreen houses
09:17 berick we're getting better, though!
09:19 Dyrcona You know, it took hundreds of years to build some of the European cathedrals.
09:19 Dyrcona I can only imagine what a mess a similar effort would make of software. :)
09:27 RoganH joined #evergreen
09:33 zerick joined #evergreen
09:38 jboyer-isl I will admit a certain curiosity about what ails csharp.
09:38 jboyer-isl mac-wise, that is.
09:39 ningalls joined #evergreen
09:43 jboyer-isl I learned something today: If you call window.openDialog and you don't set resizable=yes, you like making people sad, and that's terrible.
09:51 kmlussier joined #evergreen
09:56 mllewellyn joined #evergreen
10:00 dluch joined #evergreen
10:54 remingtron_ joined #evergreen
10:58 mcooper joined #evergreen
11:08 akilsdonk joined #evergreen
11:15 timhome joined #evergreen
11:15 rjackson-isl joined #evergreen
11:30 csharp jboyer-isl: I was trying to find where the staff client profile folder lives on a Mac
11:30 csharp for the logs, it was ~/Library/Application Support/open_ils_staff_client
11:30 jboyer-isl Oh, yeah. Hiding ~/Library a version or two back kind of sucks.
11:31 csharp it took quite a bit of frustration to discover that though, as does almost anything on a Mac in my experience
11:31 jboyer-isl It had such a nice icon before too.
11:31 csharp user friendly my ass
11:31 jboyer-isl They way they see it is this - How user friendly is the software that you're using that you need to know where those files are stored?
11:31 jboyer-isl I can see that one from both angles.
11:33 csharp from the IT support perspective, especially when you're mainly steeped in Windows/Linux conventions, that's a hard transition
11:33 jboyer-isl Although now that you mention it, I don't think it's ever been called "power-user friendly." The difference is not that subtle.
11:34 jboyer-isl That's true. (Though Windows' convention is also rough coming from Linux
11:34 jboyer-isl Windows loves swinging around the hidden bit these days.
11:36 jboyer-isl I've been meaning to ask you, chsarp: you use pg-pool at PINES, right?
11:37 csharp yep - for load balancing reports queries
11:37 jboyer-isl I've been wanting to look into it and didn't know how hard it was to set up to work properly with Evergreen. (as in, routing things that may not look like they make db changes but should be routed to the r/w db anyway)
11:37 jboyer-isl Only reports?
11:38 csharp yeah - we're still using slony for replication
11:39 jboyer-isl So are your bricks pointed straight at the master db, or do they all route through pg-pool also?
11:40 csharp at this point they point at the master - in a previous cluster pgpool was used to load balance search queries
11:41 csharp our replicas are used for redundancy and reports only at this point
11:41 jboyer-isl I see. Is that because of the upgrade, or has it been that way for a while?
11:41 csharp it became that way when we bought a monster master DB that could handle the normal business load
11:42 csharp that was... 3-4 years ago
11:42 jboyer-isl That does make sense.
11:46 bradl csharp: we're still awaiting the release of our political prisoner, Tux
11:50 jeff heh
11:52 bradl csharp: I've been banned from QTS as a result of my previous rescue attempt. Apparently it's frowned upon to enter another org's cage. :)
11:53 berick cue mission impossible music
11:59 * csharp heads up there now to add extra security around the cluster
12:00 csharp @blame csharp
12:00 pinesol_green csharp: everything was going great until csharp came along
12:01 csharp @blame search tux
12:01 pinesol_green csharp: 1 found: #8: "$who stole bradl's tux doll!"
12:01 csharp @blame csharp 8
12:01 pinesol_green csharp: csharp 8 musta been an Apple employee.
12:01 csharp heh - guess I need to learn the syntax
12:07 Dyrcona @blame 8 csharp
12:07 Dyrcona ???
12:08 * Dyrcona thinks he blew it up.
12:08 berick @blame Dyrcona
12:08 pinesol_green berick: everything was going great until Dyrcona came along
12:08 Dyrcona @blame Dyrcona
12:08 pinesol_green Dyrcona: It really IS Dyrcona's fault!
12:08 berick heh
12:09 berick @blame 8 csharp
12:09 pinesol_green berick: csharp stole bradl's tux doll!
12:09 berick maybe the opening spaces?
12:10 Dyrcona Oh, yeah. I didn't notice those.
12:10 Dyrcona I thought I might have blown something up, 'cause pinesol_green has no help for blame or praise.
12:14 bradl csharp: don't worry, T-bone at QTS has you covered. It did take me a while to count the floor tiles between our cages, through.
12:14 bradl Who knew they didn't like customers accessing that crawlspace??
12:21 Dyrcona Evergreen gets a mention under "still being categorized" on this list: http://perlmaven.com/perl-​based-open-source-products
12:31 kmlussier And Koha is listed under Enterprise applications.
12:32 Dyrcona Yeah, I commented to the author on G+ that Evergreen should be in the same category as Koha.
12:43 jeff has anyone played with a "same day" or "due at end of day" circulation duration?
12:43 jeff i'm giving it a try now.
12:47 Dyrcona jeff: How do you configure that?
12:48 Dyrcona I can see how that might have some application, like for checking out a room or a laptop or some other equipment that is meant to be used in the library, or special collections maybe.
12:54 jeff laptop, yep.
12:54 jeff in-building same-day use
12:54 jeff trying with a circ duration of zero, seeing if it'll push to 23:59 tonight.
12:55 schatz joined #evergreen
13:01 * Dyrcona doubts that will work, but go for it!
13:08 mmorgan jeff: we have at least one library with a same day due date. config.rule_circ_duration.normal = 00:00:00
13:08 mmorgan an item checked out on 1/28 got the due date 2014-01-28 23:59:59-05. Seems to work fine.
13:10 jeff excellent. that was my theory. thanks! hopefully it'll work as expected here.
13:10 jeff helps if i set my circ policies to active.
13:10 hbrennan joined #evergreen
13:11 jeff yep -- works!
13:13 Dyrcona That's good to know.
13:20 tsbere I suppose "0" is technically a number of 24 hour periods
13:22 jeff there's no remainder after dividing it by one day. :-)
13:23 jeff i just called my circ duration rule "sameday"
13:26 tsbere Hmmm
13:27 tsbere Set a duration to "1 second", no renewals, recurring fines each hour, and you get effective automatic charging for items, provided you set a rental fee on the item for the first interval
13:28 KresiusMengg joined #evergreen
13:28 jeff typically when reporting, we exclude certain groups of patrons. i think i want to use a view for that, and have the view exclude those same groups, but also exclude patrons with a certain stat cat, or who have an entry in this tadl.reporting_excluded_users table, or maybe who have a specific user setting...
13:28 KresiusMengg left #evergreen
13:29 jeff tsbere: in terms of charging by the hour?
13:29 tsbere jeff: Yea. Though ensuring you don't hit max too soon might be an issue.
13:30 tsbere not to mention overnight issues <_<
13:31 Dyrcona jeff: Sound overly complicated. Are the exclusions based on some rarely changing property of the user, or is it arbitrary for each report?
13:32 jeff Dyrcona: the idea is "don't count circs by test or otherwise not-real patrons". usually this is just done with an infrequently (never!) changing patron profile on the "patron" account.
13:32 jeff but right now i'd like (for training and/or for testing-for-real) to have some patrons who are in other groups also be excluded, without excluding that entire group.
13:33 jeff i don't want to edit every report to "also exclude these patrons" or "also exclude patrons with this attribute", hence the idea that "at this point, if i decide to do this, i want a view to help me" :-)
13:34 jeff (a reporting view for sql reports, not necessarily a full-on view in the IDL and such.
13:34 jeff )
13:35 jeff but another option is to change a test user in the excluded group to a non-excluded group to test "can this user really check out only one chromebook and no other items at all", then return the user to the excluded group -- but that involves:
13:35 jeff 1) hope nobody runs a report that would be affected
13:35 jeff 2) don't forget to change the group back
13:35 jeff sometimes i think i just worry too much about reporting on "not real" things.
13:36 jeff other times i think "more test servers!"
13:36 * jeff shrugs
13:36 jeff i'm just babbling now
13:37 tsbere jeff: Make a table of "don't report on these user ids", fill it however you want (perhaps with a DB function), then ensure that reports say "and the user id is not in that table" either directly or via a view?
13:37 rfrasur joined #evergreen
13:37 tsbere Would likely be faster than looking up stat cat or user pref entries, though you could do that to populate the table
13:37 jeff tsbere: quite reasonable, but if since i'm needing to touch every report to do that, i figure maybe now is the time to rely on a view. :-)
13:38 tsbere jeff: As I said, directly or via a view. ;)
13:38 jeff the view relying on a cache table to do the actual exclusion is still possible
13:38 jeff ah, yep. you left room for the view in your statement. :-)
13:39 tsbere I just figure you should keep the extra table lookups to a minimum for something like that.
13:40 tsbere "id is not in this table that we can do an index check on" would likely be a lot faster than "does not have this stat cat entry set to this value" or "does not have this user pref set to this value" type things
13:46 Callender joined #evergreen
13:47 jeff heh. can't use the context menu in Items Out to check in non-cat items. :-)
13:47 bshum parts--
13:47 bshum (not related to anything, just saying because I hate parts)
13:48 rfrasur bshum++ #randomness on Fridays is a thing.
13:49 bshum I'm holding my breath waiting for signs of movement for https://bugs.launchpad.net/evergreen/+bug/1099979
13:49 pinesol_green Launchpad bug 1099979 in Evergreen "Merge Parts" (affected: 3, heat: 14) [Wishlist,Triaged]
13:49 rfrasur o0(Optimism is adorable)
13:50 bshum Ha!  Sounds about right.
13:50 Dyrcona DPearl is doing something in that area.
13:50 tsbere hmmm.
13:51 * tsbere has a "rename part" function that merges into an existing part with the same name when the new part already exists, perhaps he should contribute it to that bug
13:55 rfrasur Just so you know, there's a vast difference between Duck Brand double sided tape and Scotch Brand.  Scotch wins hands down.  Too bad the Duck Brand was cheap enough to lure me into buying it.
13:55 * rfrasur must suffer to the end.
13:55 jcamins rfrasur: do you know any people just getting started with sewing clothes?
13:56 rfrasur no, but I know people who sew clothes.
13:56 jcamins rfrasur: actually, more specifically, I think you need to know a woman who is just getting started sewing her own clothes. Men are, I gather, much easier to fit.
13:56 rfrasur more straight lines, yes.
13:57 jcamins Anyway, if you know someone who doesn't have a dressmaker's dummy you can let them use the tape to attach all the scraps that go into the dummy together.
13:57 hbrennan This seems like an okay time to jump in with a question.. I've been browsing the chat for 30 minutes.. :)
13:57 * rfrasur laughs
13:58 rfrasur jcamins, it's library tape.  I can't just give it away.  Too bad though.
13:58 hbrennan We are trying to delete a location, and have deleted all items in this location... verified by a report... but it still won't let us delete is
13:58 hbrennan it*
13:58 Dyrcona a copy location?
13:58 hbrennan stating that "we might not be able to delete if items are attached"
13:58 bshum dbwells: I updated the symlink for README_2_5.html to point at the 2_5_2 version of the file.  And then I noticed that the file generated still had rel_2_5_1 as the stamp in the instructions so I bumped that on the web server's copy.
13:58 hbrennan shelving location
13:58 Dyrcona hbrennan: Same thing.
13:58 jcamins rfrasur: ugh. I guess you could sponsor a craft competition? That's sort of reaching, I fear.
13:58 bshum (probably just a minor detail in the actual rel_2_5 branch)
13:59 hbrennan I'm still trying to get rid of my Sirsi lingo :)
13:59 hbrennan so I'm never sure
13:59 Dyrcona hbrennan: When copies are deleted, they aren't really deleted. You'll probably need to change the location on the deleted copies.
13:59 hbrennan That's what we did
14:00 hbrennan we had two music locations, and now they are one
14:00 hbrennan I meant to say we've edited the location for all the items
14:00 hbrennan so they are all in 'Music' and we want to delete the location 'Audio -- Music' so catalogers won't use it
14:00 DPearl left #evergreen
14:01 hbrennan Would something like this require an overnight rest for Evergreen to figure out that nothing was attached to this location anymore?
14:04 dbwells bshum: thanks.  I actually saw the new README was exactly the same size, so I didn't upload it, but I forgot to flip the version number when I copied it server-side.
14:04 bshum dbwells: Ah no worries.
14:06 Dyrcona Gee, I hope DPearl wasn't offended that I mentioned his work. :)
14:06 rfrasur jcamins: It's no big thing, and this basically a big craft project anyway.  Still getting all the bits and pieces put together for the seed library.  Hopefully it'll be ready to go for the board meeting next week.
14:07 Dyrcona hbrennan: Recent versions of Evergreen also reference the copy_location in action.circulation.
14:08 jeff hbrennan: also, deleted copies count -- if any copies (even deleted) still reference it, you won't be able to delete it.
14:08 hbrennan We haven't deleted anything, just manually changed the location for each item in the wrong spot...
14:08 hbrennan would that keep things "stuck" too?
14:09 rfrasur Were there things that were deleted from it previously though?
14:09 rfrasur Like from a weeding project or something?
14:09 Dyrcona hbrennan: Doing it with SQL in the database is the best way to be sure.
14:10 hbrennan Unlikely.. we only had a few (less than 5) items in the 'Audio -- Music' location, which was created when we migrated a year ago
14:10 hbrennan so that was a new location to Evergreen, and we did our weeding before that
14:10 hbrennan Not impossible, but highly unlikely
14:10 hbrennan ahhh again with SQL
14:10 hbrennan I want to learn it so bad
14:11 hbrennan After I get my CCENT, CompTIA A+, and build a house this summer...
14:11 rfrasur hbrennan: are you going to Boston?
14:11 jeff I'm still interested in adding a deleted boolean to asset.copy_location -- anyone have a good reason why not?
14:11 hbrennan Yes!
14:11 rfrasur I think there's a session on SQL for librarians
14:11 hbrennan Yep, very last session on Saturday,.. with Rogan I think?
14:12 rfrasur Yes.
14:12 hbrennan I am becoming more and more suspicious of the reporting module, since everyone says to use SQL
14:13 rfrasur Well, the reporting module is good for some things, but only basic db maintenance.
14:13 hbrennan Dyrcona: So it's likely *something* deep in the bowels of our system is still attached to this location?
14:13 bshum @blame reporting module
14:13 pinesol_green bshum: It really IS reporting module's fault!
14:13 hbrennan bshum++
14:14 hbrennan My first experience with the reporting module made me dislike it.. it reports a bunch of circs on Sunday, when we're closed
14:14 hbrennan and circs for every hour of the day, when we're closed
14:14 rfrasur lol, that report is apparently all sorts of broken.
14:15 hbrennan Yep... the total was close to what we were expecting, but seeing "work" happening 24 hours a day was amusing
14:15 jeffdavis Did those circs turn out to be renewals?
14:16 rfrasur could have been online renewals.  That's true.
14:16 hbrennan Hmmm.. perhaps
14:16 hbrennan that would be interesting
14:16 hbrennan I wasn't allowed to take reports training (already in too many sessions during our migration) so I had someone else do it
14:17 bshum eeevil++ # 2.4 goodies
14:17 rfrasur weren't allow by who?
14:17 hbrennan My director
14:17 hbrennan I wanted to do ALL THE THINGS
14:18 rfrasur yeah, but if you do IT stuff, you probably think in the right enough direction to get the most out of reports
14:18 * rfrasur refrains from questioning other directoring methods.
14:18 hbrennan Yep, and one person who did the reports training is now retired...
14:18 jboyer-isl jeff: re: a deleted flag on copy locations, if someone doesn't beat me to it this year, that's what I'm planning to at some point. Our copy location table is looking like a car lot.
14:18 jboyer-isl EVERYTHING MUST GO.
14:18 rfrasur jboyer-isl++
14:19 hbrennan jboyer-isl++
14:19 hbrennan Housekeeping is good
14:19 hbrennan Thinking of other ways.. can I make a location un-usable by staff?
14:19 jeff hbrennan: if you're reporting on circulations, you'll count online renewals by default, unless you exclude them.
14:19 hbrennan It's not ideal, but we just want people to stop using it!
14:20 rfrasur Yes.  I recommend fear.  But that doesn't have much to do with the DB
14:20 jeff hbrennan: one option might simply be to rename the copy location to ZZZ-DO-NOT-USE :-)
14:20 jboyer-isl hbrennan: One way is to change the name to something obviously unwanted and starting with a Z or something to sort it to the bottom of the list.
14:20 hbrennan jeff: Thanks. Good to know
14:20 jeff hbrennan: but keep in mind that people might be using it not just out of habit, but because a copy template sets it for them.
14:21 bshum @quote add "<jboyer-isl> Our copy location table is looking like a car lot. EVERYTHING MUST GO."
14:21 pinesol_green bshum: The operation succeeded.  Quote #76 added.
14:21 rfrasur Jeff is 100% right on that.
14:21 jboyer-isl bshum++ # Ha!
14:22 rfrasur We actually dealt with that.  Emptied out an obsolete location and it kept having stuff put in it even though everyone knew to knock it off.  It was because of the templates.
14:25 hbrennan stepping away for a sec
14:26 hbrennan and I'm back
14:26 hbrennan jeff: Genius. I like the renaming
14:26 hbrennan That was the original problem.. someone set up a template wrong
14:27 rfrasur hbrennan++
14:27 hbrennan Luckily our staff is only 9 people
14:27 hbrennan I'm sure I can whip them into shape
14:27 hbrennan jeff++
14:27 rfrasur in shape enough
14:27 hbrennan and jboyer-isl++
14:28 hbrennan and rfrasur++
14:28 hbrennan cuz it's Friday
14:28 rfrasur ;) thankfully
14:29 jihpringle joined #evergreen
14:30 mmorgan jeff: re: your earlier question about a deleted flag for copy locations, bug 1210541
14:30 pinesol_green Launchpad bug 1210541 in Evergreen "Copy locations table should have a 'deleted' flag" (affected: 2, heat: 12) [Undecided,New] https://launchpad.net/bugs/1210541
14:32 hbrennan An SQL question.. can that be set up to not allow changes, just general queries?
14:32 eeevil bshum++ # pointing me at the WP login
14:32 jeff hbrennan: yes.
14:32 hbrennan My IT manager does not like giving out editing power
14:33 hbrennan but if I could just ask for info and play around with it..
14:33 hbrennan jeff: Awesome
14:33 hbrennan I might try and get something set up before the conference, so I know a little more going into it
14:33 hbrennan * looking up SQL For Dummies...
14:34 rfrasur hbrennan: what day are you coming in for the conference?
14:34 eeevil hbrennan: your friendly support provider probably has scripts ready-made to help you add such a readonly user, he said with a wink and a nod
14:34 hbrennan all of 'em
14:34 hbrennan eeevil: Ah-ha. I will be in touch, wonderful Equinox people
14:34 rfrasur was just thinking if you were there in time for the tutorials/hackaways, you might get some in person assistance on SQL
14:35 hbrennan I'm flying in from Alaska
14:35 hbrennan so I actually get to Boston at 7am day after St Pattys
14:35 jeff hbrennan: keep in mind that unless you're running queries on a copy/replica of the database, you can impact the rest of the system by running a large or mis-guided query.
14:35 eeevil hbrennan: you might check out SQL for Smarties, too. the author is a little prickly, but it's a good book
14:36 hbrennan jeff: Good to know. I'm sure IT would be happy to make a copy
14:36 hbrennan eeevil: Didn't know there was thing, and had to look it up in case you were making a joke
14:36 * rfrasur did too
14:37 eeevil heh ... no, it's real
14:38 hbrennan SQL seems like an easier way to share "templates" for reporting too
14:39 hbrennan just a few magic lines
14:39 bshum Once upon a time, the reports taskforce (before it became an interest group) used to share SQL reports in the wiki.  They probably exist, though undoubtably need updating / love.
14:40 hbrennan bshum, you created one for me that I'm saving for the special day when I know what to do with it
14:40 hbrennan Does something exist for reports, too?
14:41 hbrennan Reading something a few weeks back about transferring reports to a another staff account.. it seemed... difficult
14:41 bshum I haven't explored it much myself, but I'm amusing myself with the potential irony that you'd probably be best served using SQL to copy/share report templates :)
14:42 hbrennan Ha. Once again... I just need 40 more hours in the week
14:42 hbrennan just to learn coding and other fun things
14:42 hbrennan Why did I get a psychology degree again?
14:43 * bshum still wishes he had gone to school for something more entertaining.
14:43 hbrennan I'm sure that's something to ask pinesol, if I knew how
14:43 hbrennan That's really the answer. My degree was FUN.
14:45 sseng hello. in the staff client, on the "checkout" tab, is there a setting to let it remember the "Auto-Print" checkbox next to Done? on master, each time I pull up a patron, I have to check the "Auto-Print" checkbox again, but I remember that this remained checked when on 2.4.1
14:45 rfrasur bshum: there's still time
14:45 Dyrcona @8ball Is SQL easier than that staff client?
14:45 pinesol_green Dyrcona: I see nothing, I know nothing!
14:45 bshum @eightball Does Dyrcona need to spend more time with pinesol_green?
14:45 pinesol_green bshum: The outlook is hazy, please ask again later.
14:45 rfrasur hbrennan: There's plenty of time to NOT have fun, so...yeah.
14:46 hbrennan rfrasur: Haha. I'm only 28, so yes, a lifetime of not fun to look forward to!
14:46 Dyrcona sseng: I have not noticed that, and I'm sure if that were a general problem our members would be howling about it.
14:46 rfrasur :D, well, it doesn't ALL stink.
14:47 Dyrcona sseng: We run master in production.
14:47 kmlussier I was using the Auto-Print checkbox in master today. But I can't remember if it was sticking or not.
14:47 stevenyvr joined #evergreen
14:48 sseng Dyrcona: Oh I see.I built a recent one today, but am going to double check just in case seeing things : kmlussier. thanks!
14:48 Dyrcona I'm going to try it myself on my development image.
14:51 Dyrcona It is not sticking between patrons for me, but I actually didn't check anything out. I guess I should find some barcodes.
14:53 Dyrcona No, it doesn't stick for me on my development system.
14:54 Dyrcona It's also not printing, but I think that is my OS trying to print to a server on another network.
14:54 sseng Dyrcona: tried it again here to, no stick (with or w/o checking out an actual book)
14:55 kmlussier joined #evergreen
14:55 bshum joined #evergreen
14:55 mceraso joined #evergreen
14:55 sseng Dyrcona: but, saw that it "stick" on earlier versions and thought there might be some settings (can't seem to find one that could be controlling that though)
14:56 Dyrcona sseng: Dunno. I suggest making a bug on Launchpad if there isn't one already.
14:56 sseng Dyrcona: alright. but just to confirm, it not sticking is a bug, right? that is to say, the expected behavior would be for it to stick?
14:56 kmlussier Dyrcona: I do remember that your dev server was able to print this morning. :)
14:57 Dyrcona sseng: If you think it is bug, then I'd say, file the bug. I have no real opinion at the moment.
14:57 Dyrcona kmlussier: Well, it wouldn't be the server. It would be my laptop.
14:58 sseng Dyrcona: alright, thanks again!
14:59 Dyrcona sseng: It does stick in a client downloaded from my production server.
14:59 Dyrcona This means that the change happened since December 8th or so.
14:59 Dyrcona sseng: You file the bug. I'll confirm it.
14:59 sseng Dyrcona: alright
15:00 kmlussier sseng: Are you looking at checkout or checkin?
15:00 sseng kmlussier: the "checkout" tab
15:00 Dyrcona kmlussier: I'm looking at checkout.
15:02 kmlussier OK, I was confused. I'll be quiet now.
15:08 sseng Dyrcona: ok, done. link to lp bug: https://bugs.launchpad.net/evergreen/+bug/1275074
15:08 pinesol_green Launchpad bug 1275074 in Evergreen ""Auto-Print" checkbox next to "Done" on the "Checkout" tab does not remember checked state between patrons retrieval" (affected: 1, heat: 6) [Undecided,New]
15:13 Dyrcona sseng: I confirmed, set the importance to Medium (not that that matters), and added a comment describing the difference between my production and development systems.
15:14 sseng Dyrcona: great, thanks!
15:14 Dyrcona I'll take a look at some point soon to see if I can find anything that looks like the culprit.
15:24 jeff yesterday we did only 7% of circ with the staff client.
15:25 mmorgan 93% selfcheck? or are there renewals included in your counts?
15:27 Dyrcona sseng: heh. I think it is my fault via some botched gittery.....
15:28 * bshum tries to watch innocently from afar and fails...
15:30 jeff mmorgan: i'm not including renewals in that figure. 92% selfcheck, 1% "other"
15:30 Dyrcona git_rebase--
15:30 jeff (where "other" is via NCIP, which means that staff performed the checkout, but it was with a different client)
15:30 Dyrcona git_cherrypick--
15:31 mmorgan interesting!
15:31 jboyer-isl Dyrcona: Isn't rebase the alternative to cherry-pick? Not that you can't still hate on both, of course.
15:31 jboyer-isl AN alternative, that is.
15:32 Dyrcona jboyer-isl: rebase forces you to cherry-pick because merges often fail after. both rewrite history in essence.
15:32 Dyrcona git merge is your friend.
15:33 Dyrcona There is a commit of mine that likely made it into master with more changes than it should have had because of a botched rebase, apparently.
15:35 jboyer-isl I see. I haven't dealt much with merges since this is pretty much the only project I use git with.
15:37 bshum I enjoy the clean look of freshly rebased git branches, but I can see how it can get confusing if you're doing alot of different projects
15:37 bshum I've wondered why we don't do merges though.
15:38 gmcharlt it's tricky to use merges for backports
15:39 bshum @hate backporting
15:39 pinesol_green bshum: The operation succeeded.  bshum hates backporting.
15:39 gmcharlt but, other than habit, there's of course more room for merging onto master
15:45 Dyrcona I'm not entirely sure that I can blame rebase for this mess, but I'm fairly certain it had something to do with me screwing up in git.
15:46 Dyrcona I don't think that commit was supposed to have so many line changes in it.
15:46 bshum sseng: I'll update the bug but I just pushed a revert for the bad commit that messed up the auto-print.
15:46 bshum Thanks for letting us know.
15:46 bshum sseng++
15:47 Dyrcona sseng++
15:47 Dyrcona Dyrcona--
15:47 jtaylorats joined #evergreen
15:48 smyers_ joined #evergreen
15:49 sseng Dyrcona: ++ bshum: ++ : great!
15:49 pinesol_green [evergreen|Ben Shum] Revert "Eliminate an annoying and useless warning in the JavaScript Console." - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=db7b99e>
15:49 bshum bshum-- # bad commit
15:51 jtaylorats To make sure I'm not overlooking something...to import MFHD records I just need to put them in serial.record_entry with the "record" number of the bib to which they are attached?
15:52 jtaylorats ...and I guess include owning_lib.
15:54 bshum Blah....... rel_2_5 had that commit backported.  Finding and reverting there too.
15:57 Dyrcona whitespace--
15:57 dbwells jtaylorats: Yes.  At that point they will display in the OPAC and be editable in the client.  If the records contain any kind of individual copy/volume level data, there is no code which will do anything special with that type of data.
15:57 * Dyrcona decides to program in BrainFuck from now on.
15:58 kmlussier Dyrcona++ bshum++ # Doing your part to contribute to Evergreen even if you are human and sometimes make mistakes.
15:58 jtaylorats Thanks.   That is the last piece.  I've gotten the test migration done for the entire database.
15:58 jboyer-isl Dyrcona, have you seen Whitespace? http://compsoc.dur.ac.uk/whitespace/
15:59 jtaylorats Now to wipe it out and put all the pieces together and do it again :-)
15:59 jtaylorats Appreciate all the help.
15:59 jboyer-isl bshum++ # everybody makes mistakes, but when it's reverted from rel_2_5 you'll be a hero in Evergreen Indiana. :)
16:00 Dyrcona Well, I'm freaking out and blaming git because of whitespace changes.... My commit added an if or something that altered the indentation of most of the file.
16:00 kmlussier @blame git
16:00 pinesol_green kmlussier: git stole bradl's tux doll!
16:01 * Dyrcona needs more green spaces.
16:01 Dyrcona @blame 9 Dyrcona
16:01 pinesol_green Dyrcona: Dyrcona is why we can never have nice things!
16:01 bradl nuh-uh, it was csharp
16:02 Dyrcona I guess if this were Python and not JavaScript, we'd have seen the problem sooner..... ;)
16:03 mrpeters left #evergreen
16:04 bshum jboyer-isl: Heh, well it's fixed for rel_2_5 now too.
16:05 bshum Every time I think about being a "hero" I think of the movie Sky High.  Where there's heros and sidekicks.
16:05 bshum I always thought I was more of a sidekick.
16:05 jboyer-isl Huzzah! Thanks. We were just about to cut off changes to a new test environment 10 mins ago :)
16:05 jboyer-isl I haven't seen that one, but I vaguely remember when it came out.
16:28 pinesol_green [opensrf|Bill Erickson] osrf_control router-de/re-register and reload commands - <http://git.evergreen-ils.org/?p​=OpenSRF.git;a=commit;h=5b3f804>
16:28 pinesol_green [opensrf|Galen Charlton] typo fix - <http://git.evergreen-ils.org/?p​=OpenSRF.git;a=commit;h=0c0b02e>
16:28 pinesol_green [opensrf|Galen Charlton] x - <http://git.evergreen-ils.org/?p​=OpenSRF.git;a=commit;h=d90a415>
16:28 gmcharlt gah
16:29 * gmcharlt can repeat Dyrcona's words of 12:45:53 PST almost exactly
16:29 Dyrcona gmcharlt++
16:29 * bshum should make it another quote
16:31 gmcharlt and now, y'all know the commit message I use for commits I intend to interactive-rebase-away instantly
16:31 bshum Quite informative.
16:40 jeff it hook to reject pushes containing commits consisting solely of "x" or matching "ARG!"? :-)
16:40 jeff s/it hook/git hook/
16:42 Dyrcona I think it could be instructive to beginning programmers to leave those commits in.
16:42 Dyrcona When all you see is a pristine history, you think everyone else is perfect but you.
16:44 pinesol_green Showing latest 5 of 9 commits to OpenSRF...
16:44 pinesol_green [opensrf|Mike Rylander] Protect subrequests from post-complete messages - <http://git.evergreen-ils.org/?p​=OpenSRF.git;a=commit;h=af8cab4>
16:44 pinesol_green [opensrf|Bill Erickson] OpenSRF client disconnect robustification (Perl) - <http://git.evergreen-ils.org/?p​=OpenSRF.git;a=commit;h=c5ca743>
16:44 pinesol_green [opensrf|Bill Erickson] recover osrf_control router start - <http://git.evergreen-ils.org/?p​=OpenSRF.git;a=commit;h=14287dc>
16:44 pinesol_green [opensrf|Bill Erickson] osrf_control router-de/re-register and reload commands - <http://git.evergreen-ils.org/?p​=OpenSRF.git;a=commit;h=a98d4b5>
16:44 pinesol_green [opensrf|Galen Charlton] fix typo and remove repeated word - <http://git.evergreen-ils.org/?p​=OpenSRF.git;a=commit;h=2cc896b>
16:46 pinesol_green Showing latest 5 of 9 commits to OpenSRF...
16:46 pinesol_green [opensrf|Mike Rylander] Protect subrequests from post-complete messages - <http://git.evergreen-ils.org/?p​=OpenSRF.git;a=commit;h=af8cab4>
16:46 pinesol_green [opensrf|Bill Erickson] OpenSRF client disconnect robustification (Perl) - <http://git.evergreen-ils.org/?p​=OpenSRF.git;a=commit;h=c5ca743>
16:46 pinesol_green [opensrf|Bill Erickson] recover osrf_control router start - <http://git.evergreen-ils.org/?p​=OpenSRF.git;a=commit;h=14287dc>
16:46 pinesol_green [opensrf|Bill Erickson] osrf_control router-de/re-register and reload commands - <http://git.evergreen-ils.org/?p​=OpenSRF.git;a=commit;h=a98d4b5>
16:46 pinesol_green [opensrf|Galen Charlton] fix typo and remove repeated word - <http://git.evergreen-ils.org/?p​=OpenSRF.git;a=commit;h=2cc896b>
16:46 bshum Oy.
16:46 bshum It's doing it again.
16:46 bshum Now I remember why I hate merge
16:47 bshum pinesol_green hates it.
16:47 pinesol_green bshum: it. doesn't seem to hate anything.
16:48 pinesol_green Showing latest 5 of 9 commits to OpenSRF...
16:48 pinesol_green [opensrf|Mike Rylander] Protect subrequests from post-complete messages - <http://git.evergreen-ils.org/?p​=OpenSRF.git;a=commit;h=af8cab4>
16:48 gmcharlt bshum: the day is getting weirder
16:48 pinesol_green [opensrf|Bill Erickson] OpenSRF client disconnect robustification (Perl) - <http://git.evergreen-ils.org/?p​=OpenSRF.git;a=commit;h=c5ca743>
16:48 pinesol_green [opensrf|Bill Erickson] recover osrf_control router start - <http://git.evergreen-ils.org/?p​=OpenSRF.git;a=commit;h=14287dc>
16:48 pinesol_green [opensrf|Bill Erickson] osrf_control router-de/re-register and reload commands - <http://git.evergreen-ils.org/?p​=OpenSRF.git;a=commit;h=a98d4b5>
16:48 pinesol_green [opensrf|Galen Charlton] fix typo and remove repeated word - <http://git.evergreen-ils.org/?p​=OpenSRF.git;a=commit;h=2cc896b>
16:48 bshum gmcharlt: Yeah the bot doesn't like merge commits :\
16:48 bshum It'll just keep looping like that.
16:48 bshum I'm unloading Git for a moment while I try looking again
16:49 gmcharlt do I recall correctly that pushing one more commit calms it?
16:49 bshum Yeah I think so.
16:49 gmcharlt bshum: cool, that gives me a reason to ask you to sign off on opensrf lp1170484 and push it ;)
16:50 bshum bug 1170484
16:50 pinesol_green Launchpad bug 1170484 in OpenSRF "Complain louder if loading shared library for C service fails" (affected: 1, heat: 6) [Low,New] https://launchpad.net/bugs/1170484
16:50 bshum Heh
16:51 Dyrcona Ah well, so much for merge commits.....
16:53 Dyrcona kmlussier: Figured out why my staff client wasn't printing earlier.
16:53 Dyrcona kmlussier: It actually did print to a pdf file.
16:55 kmlussier Dyrcona: Mine was printing to PDF too, but I was expecting it since I always have the staff client print to PDF.
16:55 pinesol_green Showing latest 5 of 10 commits to OpenSRF...
16:55 Dyrcona Well, I'm going to sign out.
16:56 pinesol_green [opensrf|Bill Erickson] OpenSRF client disconnect robustification (Perl) - <http://git.evergreen-ils.org/?p​=OpenSRF.git;a=commit;h=c5ca743>
16:56 pinesol_green [opensrf|Bill Erickson] recover osrf_control router start - <http://git.evergreen-ils.org/?p​=OpenSRF.git;a=commit;h=14287dc>
16:56 pinesol_green [opensrf|Bill Erickson] osrf_control router-de/re-register and reload commands - <http://git.evergreen-ils.org/?p​=OpenSRF.git;a=commit;h=a98d4b5>
16:56 pinesol_green [opensrf|Galen Charlton] fix typo and remove repeated word - <http://git.evergreen-ils.org/?p​=OpenSRF.git;a=commit;h=2cc896b>
16:56 pinesol_green [opensrf|Galen Charlton] LP#1170484: log failure to load library for C app as an error - <http://git.evergreen-ils.org/?p​=OpenSRF.git;a=commit;h=989ac27>
16:56 kmlussier Dyrcona: Have a nice weekend!
16:56 * bshum watches it explode now
16:57 pinesol_green [opensrf|Bill Erickson] LP#1066131: srfsh.py should not require opensrf.settings - <http://git.evergreen-ils.org/?p​=OpenSRF.git;a=commit;h=2fae356>
16:59 gmcharlt bshum: while you're in the area, a look at 1155446 would be nice
17:00 * bshum doesn't really want to test on Lucid
17:00 bshum But I'll look at the rest of it.
17:00 gmcharlt well, lucid is less relevant now than it was in March of last year
17:01 gmcharlt I'll see how wheezy likes it
17:01 bshum I'm checking precise right now.
17:07 gmcharlt works on wheezy
17:08 mmorgan left #evergreen
17:10 * bshum taps fingers impatiently waiting for packages to download...
17:10 gmcharlt run, you little bits, run!
17:20 bshum gmcharlt: Looks okay to me on precise.
17:20 bshum I'll sign off and push it
17:20 gmcharlt thanks
17:22 pinesol_green [opensrf|Galen Charlton] LP#1155446: add Debian/Ubuntu deps required for Python tests to pass - <http://git.evergreen-ils.org/?p​=OpenSRF.git;a=commit;h=02a93da>
17:25 * jeff waits patiently to see if collectionHQ extract will complete
17:26 bshum egbuilder: status
17:26 egbuilder evergreen-master-debian-6.00-x86_64: idle, last build 1h30m42s ago: build successful
17:26 egbuilder evergreen-master-fedora-18: idle, last build 1h31m08s ago: build successful
17:26 egbuilder evergreen-master-ubuntu-12.04-x86: idle, last build 1h31m15s ago: build successful
17:26 egbuilder osrf-master-debian-6.00-x86_64: offline
17:26 egbuilder osrf-master-fedora-18: idle, last build 21m17s ago: build successful
17:27 jeff complete in 18:34 -- hooray.
17:55 fparks I was wondering if anyone is familiar with instantiating a query parser with custom boolean operators?
17:59 fparks I was informed that[ my $qp = OpenILS::Application::Storage::Dri​ver::Pg::QueryParser->new(operator => { and => 'and ', or => 'or ', disallowed => 'not ' }); ] would work, but I haven't had any luck. And from poking around in the code I don't see how it would work.
18:31 dbwells fparks: It doesn't look like you can set them all at once.  I'd try calling QueryParser->operator($op, $value) for each one you want to change.  Good luck!
18:39 fparks dbwells: Thanks.
19:51 stevenyvr joined #evergreen
23:18 zerick joined #evergreen

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