Open Source Integrated Library System

Evergreen on IRC

#evergreen Logs for Wednesday, October 19th, 2011

< Tuesday, October 18th, 2011Raw Log FileThursday, October 20th, 2011 >
#TimeNickMessage
#00:46:33matt_carlson has joined #evergreen
#00:55:11matt_carlson has quit IRC
#01:10:37sndwrx has joined #evergreen
#02:06:35matt_carlson has joined #evergreen
#02:08:49darshan has joined #evergreen
#02:10:24darshani am about to install ubuntu lucid lynx 10.04 ,
#02:10:37matt_carlson has quit IRC
#02:11:15darshani just want to knew isshould use server edition or desktop edition
#02:12:37darshani am about to install ubuntu lucid lynx 10.04 ,i just want to knew i should use server edition or desktop edition
#02:13:18darshan?
#02:13:19darshan?
#02:15:06sndwrx
#02:15:23sndwrxAre you installing Ubuntu for the purpose of running an Evergreen server?
#02:16:51denials has quit IRC
#02:17:40denials has joined #evergreen
#02:18:25darshanyes
#02:19:37sndwrxWell I would say server edition, since it won't include some of the unnecessary desktop extras that are present in desktop edition.
#02:20:05sndwrxBut take that with a grain of salt because I've yet to set up an Evergreen test environment. :)
#02:20:49darshani have to install Evergreen server-side software
#02:20:55darshanbut neways thnkx
#02:23:32sndwrx
#02:24:00sndwrxThough if I'm not mistaken, I believe I saw a Debian bundle for Evergreen, somewhere on the site.
#02:25:16darshani get a plus suggestion and green flag for installing it in ubuntu 10.04 lucid
#02:25:35sndwrxAh that's right. They offer virtual images for Evergreen 2.0.3 on Deb Squeeze and Evergreen 1.6.1.4 on Deb Lenny.
#02:26:20darshanbut only having one question of whether to use desktp or server edition
#02:26:32darshanno
#02:26:46darshanm i want to go ubuntu
#02:26:52sndwrx nods.
#02:27:28sndwrxAgain I'd say probably server, but that's somewhat dependent on your familiarity with the Linux environment.
#02:27:40darshanok
#02:27:49sndwrxAnd considering I haven't worked with Evergreen first-hand as of yet, it's kind of like the blind leading the blind. :)
#02:27:54darshanwhy other people are not replying
#02:28:21sndwrx
#02:28:24sndwrxWhere are you?
#02:28:35darshanfrom india
#02:28:41darshanits 11.58am
#02:28:43sndwrxOh, neat.
#02:28:46darshan:)
#02:28:51darshanok
#02:28:57darshanjust say me
#02:29:08darshanat what time they loggin and logout
#02:29:22sndwrxI'm not sure. Tonight is my first night in this channel.
#02:29:27darshanso that i would meet all of u in best time
#02:29:36darshanok
#02:29:42darshanur welcome
#02:30:12sndwrxI would imagine that most people are in and out throughout the day and evening, US time.
#02:30:23darshanok
#02:30:42darshansee this link
#02:31:03darshanhttp://webchat.freenode.net/?channels=evergreen#
#02:31:26darshanhere u will nicely knew who are actually online
#02:31:51darshanand every one here is well master in all their way
#02:32:01darshanso can gain much more help
#02:32:17darshanbut they at loggin at 9.00pm IST
#02:33:05sndwrxoh, I see.
#02:33:49darshandats why i m in bottelneck condition as my time is totally opp to us time
#02:33:59darshan*US
#02:34:31darshanok den babye
#02:34:43darshanu should leave now
#02:34:52darshangn
#02:36:35sndwrxSorry that I'm no help.
#02:36:42sndwrxHave a good day.
#02:36:53darshanit's ok
#02:36:55darshanthnkx
#02:38:14darshani am about to install ubuntu lucid lynx 10.04 ,ican i ne1 tell me, should i use server edition or desktop edition
#02:38:20darshanfor evergreen
#02:38:39darshanserver-side software
#02:42:01sndwrxAccording to the Evergreen documentation, they acknowledge that there may be differences between desktop and server editions, and the walk-through guide outlines the steps taken on a server edition Ubuntu installation.
#02:42:11sndwrxAs seen here: http://docs.evergreen-ils.org/1.6/draft/html/serversideinstallation.html
#02:43:43sndwrxBut that is for Evergreen version 1.6.1.x.
#02:43:49sndwrxWhat version do you intend to install?
#02:45:09sndwrxAh, this link pertains to the 2.x versions of Evergreen and makes a similar statement: The following steps have been tested on the x86 (32-bit) and x86-64 (64-bit) architectures. There may be differences between the Desktop and Server editions of Ubuntu. These instructions assume the Server edition.
#02:45:13sndwrxhttp://docs.evergreen-ils.org/2.0/draft/html/serversideinstallation.html#serversideinstallation-ubuntudebian
#02:47:27darshanat first as that doc tells
#02:47:41darshani m installing opensrf
#02:47:59darshanInstalling OpenSRF 1.6.x On Ubuntu or Debian
#02:48:08darshanso i m with ubuntu
#02:48:10darshanthen
#02:48:31darshanInstalling Evergreen 1.6.1.x On Ubuntu or Debian
#02:48:51darshani m going as by that doc
#02:49:02darshannothing new from my side
#02:49:50sndwrx;nods.
#02:49:52sndwrxer
#02:49:54sndwrx nods.
#02:50:05darshanmeans?
#02:50:13darshannods means?
#02:50:20darshanwhat do u want to say
#02:50:22darshan?
#02:51:56sndwrxSorry, it's like an indication of nodding my head in understanding.
#02:56:09darshankk
#03:52:56darshan has quit IRC
#07:46:07collum has joined #evergreen
#07:50:29fortin has joined #evergreen
#08:28:45Dyrcona has joined #evergreen
#08:29:23_bott_ has quit IRC
#08:30:23_bott_ has joined #evergreen
#08:33:21Dyrcona has quit IRC
#08:34:48test_ has joined #evergreen
#08:35:18test_hello?
#08:36:03test_ has left #evergreen
#08:42:29mrpeters-islhas there been any progress made on https://bugs.launchpad.net/evergreen/+bug/838525
#08:44:27mrpeters-islmore, has anyone tested eeevil's suggestion
#08:46:45tsbereI have not touched his suggestion
#08:47:19tsbereI could run a couple of queries, though, in our test DB
#08:49:23mrpeters-islpart of me kind of leans toward going back to our original trigger i posted there, since it was working for us
#08:49:33akilsdonk has joined #evergreen
#08:49:46mrpeters-islbut, on the other hand eeevil's seems more efficient
#08:57:25Dyrcona has joined #evergreen
#08:59:21Dyrcona needs to sign up for ESL classes, apparently. :)
#09:00:47tlilleberg has joined #evergreen
#09:11:15fortin has quit IRC
#09:12:31Meliss has joined #evergreen
#09:19:21tsberemrpeters-isl: eeevil's suggestion? Probably bad. :(
#09:20:06mrpeters-islwhat'd ya find?
#09:20:28tsbereThe DB says my dob is correct. The staff client says it was a day earlier.
#09:20:36mrpeters-islyeah...fun
#09:22:51tsbere has a different theory
#09:23:50tsbereToo bad our training system is a VM that is apparently unhappy
#09:24:39tsbereload average: 18.76, 21.62, 16.78 might explain that...
#09:31:10DyrconaFun with timezones.
#09:31:27yboston has joined #evergreen
#09:34:41mrpeters-islis there a trick to hiding virtual fieldmapper columns in the staff client? For example, g.payments_list.init in bill_history.js is building the picker based on all of money.payment_view. I want to get rid of the virtual fields that display no data in the staff client.
#09:38:24sal_ has joined #evergreen
#09:40:47tsberemrpeters-isl: Updated the launchpad entry there with my findings.
#09:41:01mrpeters-islgood deal. thank you for testing!
#09:41:11akilsdonk_ has joined #evergreen
#09:41:18Callender_ has joined #evergreen
#09:41:22akilsdonk has quit IRC
#09:41:33tsberemrpeters-isl: All my findings are negative. :(
#09:41:36akilsdonk_ is now known as akilsdonk
#09:41:52mrpeters-islgood to know, i'll let rjackson-isl know
#09:42:20tsbere should apparently be glad that he works with one time zone
#09:42:47mrpeters-islwe just have a couple areas that are on central time
#09:42:53Callender has quit IRC
#09:42:54Callender_ is now known as Callender
#09:43:05mrpeters-islnorthwest/southwest of here
#09:44:09tsbereI suspect that the problem is the system is treating things without a time zone as being in GMT, and then "converting" to local to be helpful.
#09:44:20tsbere(for the without timezone and date tests)
#09:51:51eeeviltsbere: the problem is simply that we need a way to say, per transaction, what timezone we want to /read/ in
#09:58:25tsbereeeevil: "SET TIME ZONE '-5:00'" ?
#09:58:52tsbere suspects the issue is more the javascript on the *client* though
#09:59:53tsbereIn theory, the server should be using the same time zone all the time, excepting daylight savings time calcs.
#10:01:48eeeviltsbere: we have a choice ... we can fix things in one place on the server (using SELECT set_config(...) where appropriate) or in all the places in the client
#10:04:07tsbereeeevil: I am trying to figure out how to fix things on the server when as far as I can tell the server is doing things, and returning things, correctly, but then the *client* is taking that information and munging it based on the timezone it has (assuming anything the server hands it is in GMT unless it has a time zone attached)
#10:04:47tsbereThe "munge dob by a few hours with a trigger" method works when you are dealing with one time zone. But what do you do if someone sets up a single system serving multiple continents?
#10:05:16tsbere(beyond tell them "Don't set up a single system serving multiple continents" anyway)
#10:06:11tsbereMore importantly, you might care about the distinction across time zones for some information, like checkout dates/times, but not for others, like dob.
#10:06:22tsbereSo a global catch all server-side won't be as much help
#10:07:40tsbere changed his local time zone 3 times in testing and saw things change locally, for the record, as for incorrect vs correct
#10:08:02tsbereThat is "workstation's time zone", didn't touch the server boxes
#10:08:56eeeviltsbere: i'm in a meeting now, and i'm being extra terse, but i'm talking about the server being told what timezone to work in for any given transaction. its not just a global setting i'm talking about
#10:10:13eeevilsomething much bigger, which i don't have time to go into right now, but this is a long standing problem, not something we've never thought about ;)
#10:11:18tsbereeeevil: Then perhaps I am not sure how that helps the issue, then. The issue I am looking at is "dob is wrong when you look at it from the next time zone over" made worse when you strip the time zone and dob is treated as midnight UTC, then converted to your local timezone. When the sever hands you a time zone it does the same conversion based on what the server handed over.
#10:12:50tsbereAKA, we are treating dates as timestamps, and timestamps are timezone-adjusted, so all of our dates are timezone adjusted.
#10:13:17tsbereWhich, to fix, I think means touching *everywhere we treat a date as a timestamp*
#10:13:17fortin has joined #evergreen
#10:15:04eeeviltsbere: which is really only dob
#10:15:40eeevilwhich is why I suggested using the date type, and slowly adjusting up from there if we need to
#10:15:54eeevil redirects attention to meeting
#10:20:34hopkinsju stretches... yawns
#10:21:03hopkinsjuIf I want to change the default skin, do I need to do something somewhere other than apache conf?
#10:21:18mrpeters-islhopkinsju: change it....how?
#10:21:37hopkinsjuI've got a customized skin that I want to start using instead of 'default'
#10:21:55csharpthe 1.6.1-2.0 script found about 7800 duplicated authority records... does anyone have a magic spell handy to dedupe these?
#10:21:55mrpeters-isleg_vhost.conf i think would be the place to start
#10:22:26hopkinsjumrpeters-isl: That's what I figured, but thought there may be a setting somewhere in evergreen that also needs attention.
#10:23:00mrpeters-isli think that'd be it
#10:32:55hopkinsjumrpeters-isl: ... and it was :-)
#10:33:50Dyrcona is going to reimplement the friends stuff from scratch.
#10:34:10jeffDyrcona: cool. going from a spec, or winging it?
#10:34:49Dyrconajeff: working on a spec actually. i'll post it where everyone can see it later today.
#10:34:56jeffDyrcona++
#10:38:52dbs has joined #evergreen
#10:38:52dbs has joined #evergreen
#10:41:30dbssenator: I have experimented in the past (a month or so ago) with removing the fixed-widthness of TPac, and it mostly works. It would be nice to have an updated version of, say, http://evergreen-ils.org/dokuwiki/doku.php?id=dev:opac:template-toolkit:todos so that we can work together towards an agreed-upon goal, yeah?
#10:42:29senatori think there is a newer version of that, or something similar. an outline of work yet to come. checking
#10:42:41dbs finds bugs + pullrequests help cement communication on common goals, but would be nice to have a concrete list of goals too
#10:42:46dbssenator: oh sure, there's the release notes
#10:43:21dbsbut that's kind of the wrong document for tracking purposes I think: http://evergreen-ils.org/dokuwiki/doku.php?id=dev:opac:template-toolkit:release_notes
#10:50:49senatordbs: yeah let's use the features part of that as the core of something new
#10:50:52senatordoing that now
#10:50:58dbssenator++
#10:55:20berickyou_guys++
#10:57:42senatordbs: http://evergreen-ils.org/dokuwiki/doku.php?id=dev:opac:template-toolkit:plan this is barely changed from the features part of the release notes, but perhaps you know best what, if anything, needs to be saved from the old todos doc and incorporated here? my thought is that we can deprecate the todos document after saving anything that's still important.
#10:57:59dbssenator: i'd drink to that
#10:58:10hopkinsju@karma you_guys
#10:58:10pinesol_greenhopkinsju: Karma for "you_guys" has been increased 5 times and decreased 0 times for a total karma of 5.
#10:59:24senatordbs: unless there's already a launchpad bug on this very topic, and i don't see it, i'll create one just for ongoing layout improvements and link it to the new doc as well
#11:00:36senatorhttps://bugs.launchpad.net/evergreen/+bug/857572 was where you've already done some work on this i see
#11:00:38dbssenator: nope, my experiments were during my amazonian phase so I was focused on that to begin with. btw, I completely concur with your CSS cleanup commit stmt
#11:01:25senatorwhile we're talking about it, do you have anything outstanding in this area that's just waiting at pullrequest for a review/merge?
#11:01:36senatordbs++ # let's clean it up
#11:03:25dbsI have a number of outstanding pull requests, but don't think there are (m)any in the TPac area - will check
#11:04:24senatordoes someone have the url handy for their favorite "show me all the pullrequest bugs" launchpad search?
#11:04:25berick has one tpac pull request, though it's not css/layout/visual in nature 856688
#11:04:47tsberehttps://bugs.launchpad.net/evergreen/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.tag=pullrequest&field.tags_combin
#11:04:47tsbereator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on
#11:04:55tsberesenator: tad long. :(
#11:04:56senatorknew that would happen
#11:04:59senatortsbere: thanks :-)
#11:05:02senatortsbere++
#11:05:10tsbere keeps it on his bookmarks toolbar
#11:05:50tsbereat least I use a client that says "oh, that was too long" and continues it as a second shot
#11:07:51senatoryep. autowrap.pl for all you irssi-ers who find yourself getting truncated
#11:08:03dbs uses http://ur1.ca/5f9q5 (sort by date descending) but same thing
#11:09:07senatordbs: new bug here https://bugs.launchpad.net/evergreen/+bug/878264 i'd add it to the new plan doc, but you're editing it atm
#11:09:14senator takes sec to checkout berick's bug
#11:10:03dbssenator: sorry, added my TODO (replace config.tt2 with YAOUS's)
#11:10:27senatortsbere: this is a bug where you had questions about equivalent feature for jspac. note in bug says there was going to be an irc discussion about it
#11:10:32senatorhttps://bugs.launchpad.net/evergreen/+bug/856688
#11:10:43senatordid that discussion happen? you good now, or are there still unresolved issues?
#11:10:47berickarg, yeah, need to address that
#11:10:56tsberesenator: gmcharlt commented that he agreed with me on that one
#11:11:09dbsbtw, Conifer may hold another TPac hackfest in Windsor in early December
#11:11:10tsbereBeyond that there was no real discussion on it
#11:11:20dbs thinks there was more discussion in IRC than that
#11:11:23dbs will chck
#11:12:16tsbereThere was an overall discussion on new features in TPac vs JSPac, I think
#11:12:29tsbereBut not much more on that specific bug ;)
#11:12:36berickif there are consortia where some systems use jspac and some use tpac, then making them both work is valid. if not, then there are lots of tpac features that jspac does not have, this is just one more
#11:12:54berickand since it's configurable, no one is required to use it
#11:13:12dbsYep, some discussion here (and if we agree on general policy, then we have the answer for the bug no?): http://evergreen-ils.org/irc_logs/evergreen/2011-10/%23evergreen.11-Tue-2011.log
#11:13:56dbsaround 12:19:15 things begin
#11:13:59senatordbs: cool re editing plan doc, link to lp bug added there
#11:14:44tsbereMy view was "features that limit things, like what org units the patron sees in a list, should be implemented in both, but new features, like sorting options, can be implemented only in TPac"
#11:15:15tsbereThe bug in question limits hold pickup locations. I think that should be implemented on both sides, as it *limits* what a patron is allowed to pick.
#11:15:34dbsAnd gmcharlt said "yes, it would best be implemented in the middle layer"
#11:15:44berickmiddle layer is not really gonna cut it
#11:16:15berickwe serve the org tree up to each UI differently and it redners the tree depending on the page-specific context
#11:16:57bericks/differently/as a whole/
#11:17:29bericki don't know if we want to get into re-fetching the org tree depending on the context. it gets bulky
#11:17:45berickjspac needs autogen field additions
#11:18:08berickfor this particular feature
#11:19:12berick is just blurting things out and will have to come back to this
#11:19:57dbsgit rm Open-ILS/web
#11:20:04senatorhehe
#11:20:22tsbereThat would be fun, watching all the javascript files hiding in there go away for staff interfaces ;)
#11:21:22bericktsbere: my argument is that it only limits the orgs if you use the feature. if you only use jspac, the feature is not supported, so don't use it. however, i'm certainly not firm on that stance.
#11:21:51bericki just need to carve out some time for jspac
#11:22:08dbstsbere: yeah yeah, go ahead and be pedantic
#11:22:14dbsbastard :)
#11:22:46tsbereberick: We are currently in a "continuous demo" mode for the TPac with several of our libraries. As it stands some holds can't be placed yet in TPac at all, which means those testing it have to revert back to JSPac, which means if we were to start using that feature (we have a couple we would like to flag that way, I am told) we would get different pick lists for each OPAC....
#11:22:53gmcharltdbs: but being pedantic on this channel is so much fun ;)
#11:23:47dbsgmcharlt: a taste of my own medicine
#11:24:08bericktsbere: ah, so, "if there are consortia where some systems use jspac and some use tpac" is true! that's all I needed to hear ;)
#11:25:09hopkinsju thinks the acronum YAOUS only exists to test peoples ability to search IRC logs
#11:26:41senator:-)
#11:27:35senatorso if the problem with 856688 is not that anyone needs it to work in the jspac per se, but that to have the tpac enforcing something on users that be easily circumvented just by visiting the jspac, then perhaps gmcharlt's suggestion about doing some enforcement at the middle layer can resolve this after all?
#11:28:04bericksenator: no, it sounds like it does need to be supported in the jspace
#11:28:06bericker, jspac
#11:28:54bericktsbere: what types of holds can't be placed?
#11:28:56berickin tpac
#11:29:11tsbereLast time I checked part and metarecord holds weren't yet there in tpac (at least in master)
#11:29:26tsbere doesn't check often, though
#11:30:03berickpart holds have been added
#11:30:06berickmr holds still pending
#11:31:07tsbereI also have to find some time to re-implement a few features that exist in JSPac that our staff want around but haven't made it into TPac
#11:31:16tsbere wrote the original features anyway
#11:41:46Dyrconaberick: Does pending mean you are working on it, or it is pending sponsorship?
#11:45:37dbsberick: could be added to http://evergreen-ils.org/dokuwiki/doku.php?id=dev:opac:template-toolkit:plan :)
#11:52:45fortin has quit IRC
#12:03:06dbssenator: collab/dbs/tpac-non-fixed-width is a tiny step, but even that makes a big difference - much more usable on-screen space for wide displays, and does a good job in most places with smaller width displays
#12:03:09hopkinsjuI think a kickstarter clone for EG feature sponsorship would be pretty awesome.
#12:07:58dbs thinks having more developers / writers / testers contributing to EG would be awesome
#12:14:53dbssenator: of course there are still scads of inline widths and semiauto.css definitions that are affecting the display but it's a start
#12:16:10berickDyrcona: mr holds need sponsorship (unless I go nuts one weekend and just do it).
#12:16:16berickdbs: will do, thanks
#12:17:36senatordbs: thanks. mind if i take that and add some 1em margins to a few divs? i think having the text right up against the left edge of the browser window like that might look weird to someone
#12:17:45senatorwell, it's a collab branch. i'll push a commit there and you can see what you think
#12:18:19dbssenator: no, I don't mind at all, I think I said in the commit it clearly needs further adjustment
#12:18:46dbs is working on merging the used bits of semiauto.css into style.css
#12:20:12dbsdoesn't appear to be much, huzzah
#12:21:44dbs is inclined to just put the bits as-is into style.css and rename ".red" and crud like that after
#12:25:01senatornot against
#12:25:07senatorpushed my margin commit to your branch
#12:25:17senatordo we want to let this branch grow for a while or merge often?
#12:28:04dbssenator: I'm inclined towards sooner rather than later, although arguably a lot of the pull requests are higher priority than this
#12:28:29senatoryeah i've just been looking at those, and...
#12:29:44senatorwell basically i just have a lot of excuses for not being able to test many of them (no 2.1, no idea how to use sru, etc etc)
#12:29:52senatorbut i'll try to pick a few where i can
#12:36:40dbssenator: feel free to ask for a test case in the bug report (e.g. for sru, I could guide you through the URLs for a before/after comparison)
#12:37:32youdonotexist has joined #evergreen
#12:40:24dbs wonders if cursor:pointer is really necessary
#12:41:06tsberechange it to hourglass just to mess with people's heads
#12:41:34dbsgenerally that's only needed for js-activated stuff, and the whole point of tpac is to avoid js...
#12:41:41dbstsbere++
#12:44:59senatordbs: re cursor pointer, i vaguely recall that there's something that's built out of an image and link with borders such that it looks like button. that's probably what that's about. and it probably doesn't need to be kept that way, so i say feel free to change.
#12:46:13dbsYeah, I think we've killed most image-built things so far. It was probably intended for the buttons
#12:46:15senatordbs: and sure, i'd appreciate a testing guideline on sru
#12:50:11dbshah, Indiana++ # racing analogies for conference tracks
#12:53:57berickheh, nice, i can already see the "how to check the oil in your Evergreen install!" and "Hold on tight!" conf proposals ;)
#12:55:33gmcharltit's off to the bookcart races!
#12:56:00tsbereheh
#12:58:47jeffso, riffing on "the whole point of tpac is to avoid js", is there any objection to a tpac mode/skin/something that uses js in a careful "progressive enhancement" kind of way?
#12:59:24jeffor is there another plan of attack for an interface that doesn't eschew js, yet isn't the current jspac?
#12:59:47tsbereFeel free to add anything locally you want ;)
#13:00:03tsbereI think the major goal is "avoid adding features with JS, period, everything needs to work with it turned off"
#13:00:06jefflocally wasn't what i was thinking.
#13:00:16bjwebb has quit IRC
#13:00:19jeffright. the whole idea behind "progressive enhancement"
#13:03:28bjwebb has joined #evergreen
#13:03:49berickjeff: i think there is a lot of desire for what you're talking about.. we just need some concensus on how to do it.
#13:04:52jeffsounds good. i guess i was just checking to see if i had missed any relevant concensus. thinking too far ahead, perhaps.
#13:05:24moodaepoProgressive-Enhancement_Graceful-Degradation++
#13:23:10sal_ has quit IRC
#13:24:11dbsjeff: there was a thread about this some time ago - me saying "so, uh, dojo.js as a base for JS enhancements?" vs senator saying "let's manipulate the DOM directly and handle cross-browser compatibility ourselves"
#13:24:46tsberesenator: Updated the age hold protection ticket with an explanation
#13:25:24jeffdbs: that was the last i remember seeing. thanks for the reminder. :-)
#13:25:38senatorhey to be fair i wanted to avoid all but the most trivial dom manipulation
#13:25:41senatortsbere: looking
#13:30:57edoceo has quit IRC
#13:32:17berickdbs: hahaaa..
#13:39:52dbssenator: it's fun to paint you in an insane light though :)
#13:40:02dbs is plugging away at the semiauto.css replacement
#13:43:31matt_carlson has joined #evergreen
#13:46:53tsbere_ has joined #evergreen
#13:47:05tsbere has quit IRC
#13:47:07tsbere_ is now known as tsbere
#13:47:16tsberesenator: Updated the ticket again. <_<
#13:48:06matt_carlson has quit IRC
#13:48:28matt_carlson has joined #evergreen
#13:48:29senatortsbere: ruminating
#13:48:51senator(not literally. there's no grass around my desk.)
#13:56:59phasefx:D :o :D
#13:59:21tsbere finds holds to be mildly annoying
#13:59:46mrpeters-islI took a stab at including the ESI report templates in the initial db build for clean installs. http://git.evergreen-ils.org/?p=working/Evergreen.git;a=commitdiff;h=9c54468e148aaf6d73589cfd1b4e1051ad71b0d4
#14:00:19tsberemrpeters-isl: That include dealing with any "they don't quite work right" issues?
#14:00:40mrpeters-isltsbere: i changed one's title, commented out the others for future revision
#14:00:53tsbereok
#14:01:12mrpeters-isli am going to take a stab at building them, but I don't understand nullability very well just yet. So i'll use this to learn :)
#14:04:07dbs wonders what kind of madness is meant for width="1%" on a table cell that contains two objects
#14:11:39dbsI mean, I know what the display intent is, but it's still madness
#14:14:40tsberedbs: Graphical layouts are madness! We should go back to text only. ;)
#14:15:01phasefxgraphical text layouts
#14:15:30phasefxwith IBM-extended ASCII, of course
#14:15:32tsbereIn fact, lets just spit out the raw results of the DB queries. Make everyone learn to read dumps. :P
#14:15:40senatorebcdic!
#14:15:43senator shoots self
#14:16:10phasefx thinks the character codes on the commodore 64 included color. One value would get you an A, another a red A :)
#14:16:14dbsmock if you will, but this css sucks
#14:16:21dbscss / html
#14:16:46tsberedbs: While I agree with you, please note that in part it is because I think css and html suck *in general* ;)
#14:17:21dbsthere can be clean html & css, just as there can be clean perl and php.
#14:17:44dbsalso, cows can have two heads
#14:17:53tsbereClean html/css, maybe. Still sucks. :P
#14:18:38bradldbs: does a two-headed cow wear a moo moo? /me ducks
#14:21:36gmcharltsenator-- # we killed EBCDIC in ILS-land with the last NOTIS system -- let not the zombie rise again
#14:21:39gmcharltsenator++
#14:21:44gmcharltsenator++ # balancing things out
#14:21:51senatorheh
#14:23:38tsberegmcharlt: Interestingly, while the overall effect was likely a +1, you likely didn't have a -1 to begin with. ;)
#14:24:10tsbere was around recently when we discovered that the bot only sees the ++ or -- at the end of the line, and includes everything before that point as the thing to be bumped
#14:24:20gmcharltheh
#14:24:23gmcharlt@karma senator
#14:24:23pinesol_greengmcharlt: Karma for "senator" has been increased 33 times and decreased 0 times for a total karma of 33.
#14:24:28sfortin has joined #evergreen
#14:24:39jeffsenator++ # thus, this has no effect
#14:24:41jeff@karma senator
#14:24:41pinesol_greenjeff: Karma for "senator" has been increased 33 times and decreased 0 times for a total karma of 33.
#14:24:42gmcharltsenator: so your karma remains flawless
#14:24:55tsberestupid bot karma parsing--
#14:24:58jeffand by the way senator++
#14:25:01tsbere@karma "stupid bot karma parsing"
#14:25:01pinesol_greentsbere: Karma for "stupid bot karma parsing" has been increased 0 times and decreased 1 time for a total karma of -1.
#14:25:09jeff@karma "and by the way senator"
#14:25:09pinesol_greenjeff: Karma for "and by the way senator" has been increased 1 time and decreased 0 times for a total karma of 1.
#14:25:10jeffyeah.
#14:25:33jeffso, we're all been holding it wrong.
#14:25:49Dyrconakarma++
#14:25:53Dyrconadogma--
#14:26:24senatorhaha, i'm much relieved :-)
#14:27:04Dyrcona used NOTIS for a brief period in the late '90s.
#14:27:40dbstsbere++ # btw, some of us have known that for years and years
#14:28:44DyrconaComputing sucks in general.
#14:29:01DyrconaAs the Doctor said, "Computers are sophisticated idiots...."
#14:30:18gmcharltDyrcona: the really funny thing is that if a different leg of the trousers of time had been gone down, NOTIS could have been the first F/OSS ILS
#14:30:42Dyrcona shudders.
#14:31:14Dyrconagmcharlt: You mean there is another reality where NOTIS is still being used and is F/OSS?
#14:32:00DyrconaAnd some version of me is probably hacking on it..... :(
#14:32:16gmcharltDyrcona: yeah, essentially one where free software as a concept had penetrated the general zeitgest a little more quickly
#14:32:46kmlussier has joined #evergreen
#14:39:27hopkinsjuSpeaking of IRC bots... anyone ever visit #drupal? Druplicon is pretty amazing as far as they go.
#14:41:52dbszoia in #code4lib is much much smarter than pinesol. its karma plugin understands comments, thus undermining the passive-aggressive incrementing of somebody without actually giving them karma
#14:42:29dbs probably bit off more than he should have by wiping so much of semiauto.css. hmm.
#14:44:55jeffdbs: thanks for mentioning that. i would have gone off and needlessly hacked on the stock karma plugin one of these nights.
#14:48:50hopkinsjuYeah, that's a pretty fun bot
#14:49:41hopkinsjuI like Zoia's last.fm functions
#14:50:38moodaepodbs: I thought the source bot behind pinesol and zoia are the same...did the Supybot karma plugin get hacked to be better in #code4lib?
#14:51:05dbsmoodaepo: oh, ages ago
#14:52:05tsberesenator: Any more thoughts on age hold protection overriding today?
#14:52:22dbsmoodaepo: https://github.com/gsf/supybot-plugins/tree/master/plugins/Karma
#14:52:25moodaepo might get the updated ones and replace our plugins
#14:52:49dbsmoodaepo: in that case, https://github.com/gsf/supybot-plugins/
#14:53:24moodaepoRight I remember coming across that a while back
#14:53:38senatortsbere: i'll probably wind up merging your work unless something doesn't work in tests, which would be weird since it tested fine for you, but i do want to revisit this conversation about how to do all the event checking "Right"
#14:53:58moodaepodbs++
#14:54:03senatorprobably will ask eeevil for input especially, since he's behind so much of the holdiness. but he's busy right now.
#14:56:42dbs is going to toss this semiauto.css cleanup, take another clean crack at it more incrementally.
#14:57:43hopkinsju@roulette
#14:57:43pinesol_greenhopkinsju: *click*
#15:01:30tsberesenator: If you have a place I can dump it I can write up what I think *should* happen for hold overrides. (You can tell me to dump to the dev list, dokuwiki, whatever)
#15:01:43tsbereOr make a new LP bug and point me at that (or have me make one)
#15:02:26senatortsbere: i'd say we're roughly at the point where it's good to introduce a dev list discussion
#15:02:52tsbereBut the tracking of a LP bug may be useful too.
#15:03:01tsbereOr community editing ability of a wiki page
#15:18:23phasefxhow scary/important would this be for backporting to rel_2_1? 7a4c9360fb48e3b17d503f59692aef7d509e7590 re: integrating unified vol/copy editor with Fast Add in the MARC editor. It's bundled with some other fixes that are vaguely defined as "robustification" (phasefx--)
#15:20:04phasefxcherry-picks cleanly at least
#15:22:04senatortsbere: sure. just anything to get a quorum of the knowledgeable people on the topic to start discussing the idea
#15:25:59phasefx is going to vote for not backporting unless folks run into problems
#15:26:10phasefxre: fast add
#15:35:48dbs deletes 155 unused CSS definitions from semiauto.css
#15:36:50tsberesenator: Threw an email to the dev list. Now sick of thinking about it. :P
#15:38:15senatordbs: what's your plan about that by the way? those were generated from actualy style attributes that (at least at one time) appeared in tpac pages. their names aren't meaningful and many of the classes wouldn't be easy to apply semantically, but i thought of them as a start to getting rid of the corresponding style attributes in the actual tt2 files
#15:38:55dbssenator: "my plan"? check the commit log on the collab branch
#15:39:23dbsif a CSS definition isn't used, I'm not sure what you expect me to do with it
#15:39:57dbshttp://git.evergreen-ils.org/?p=working/Evergreen.git;a=commit;h=d6557d0254c87eb009c7475c574279350333ffb2 fwiw
#15:40:55dbsI concur with getting style attributes out of the HTML where possible, but that's orthogonal to getting rid of dead wood
#15:41:14senatorright i see that. but they were waiting to be used. the styles defined in each one came from style attributes that may in many cases still exist in tt2 files. many may not, as they were generated like 6 months plus ago
#15:42:29senatorexample:
#15:42:38dbssenator: sorry, i don't see any value in "waiting to be used". as the commit log suggests, I checked to see if any of the css definitions were in fact being used
#15:44:13dbsis contentslider.css waiting to be used? because I'm about to delete that, too
#15:45:03senatorno, that can go. it's formerly used.
#15:47:01dbsthanks.
#15:50:42phasefxif an item is floating, it floats the whole consortium, correct? looks like there's no way to restrict that
#15:52:54tsbereI believe that is the case, yes
#15:53:21phasefxI bet folks will want to change that at some point :) thanks
#15:53:21tsbereAlthough *technically* you can restrict it, kindof.....it won't float to a location that suppresses transits with where it lives.
#15:53:32tsbereOr currently lives
#15:54:52tsbere half considered laying the groundwork today for "let different OUs decide on opac visibility of statuses individually"
#15:55:51phasefx brain melt
#15:57:03tsbereI have already mentally mapped what I think is needed to accomplish that
#15:57:27tsbereOriginated from one library wanting lost items to show up when we have them hidden globally.
#15:58:07Meliss has quit IRC
#15:58:09matt_carlson has quit IRC
#16:08:58mrpeters-isltsbere: complicating, i'm sure -- but I love the idea of more flexibility for those who want to be!
#16:09:23tsberemrpeters-isl: Unless someone (internal or otherwise) gives me a good reason to implement it I am not sure I want to. :P
#16:09:44collum has quit IRC
#16:09:53mrpeters-islunderstandable!
#16:24:48tsberemrpeters-isl: I am more interested in maybe doing the hold override stuff I emailed the dev list about. And not too interested in actually doing that, honestly. :P
#16:32:37dbs at long last adds a test scenario for SRU case insensitivity to https://bugs.launchpad.net/evergreen/+bug/875819
#16:47:15kfrg56 has joined #evergreen
#16:55:09senatordbs: thanks
#16:55:16senatori had negative results though
#16:55:23senatorbug updated
#16:59:48tlilleberg has quit IRC
#17:02:31dbssenator: hmm. but you don't get those errors prior to the patch?
#17:03:18kmlussier has quit IRC
#17:04:02senatordbs: correct, i do not
#17:04:39kmlussier has joined #evergreen
#17:09:40akilsdonk has quit IRC
#17:10:09senatordbs: with an adjustment i can get your tests to pass, though. does the amended commit at the head of collab/senator/LP875819-fix-SRU-qualifier seem to jive with what you meant?
#17:10:20dbsyeah, I've already got a fix
#17:10:28tsbere wonders what went wrong where when running make_release.sh for 2.1.0, as his tests just now edited the readme to include the _0 on the stamp ID as part of what it does
#17:11:28kmlussier has quit IRC
#17:12:47dbssenator: I've force-pushed the correct commits to the branches in question
#17:15:55Dyrcona@later tell bshum I will bug you about scripts for wowbrary.
#17:15:55pinesol_greenDyrcona: The operation succeeded.
#17:16:31senatordbs: definitely works now. pushing
#17:17:07dbsthanks senator
#17:23:18dbs wonders why we have "Another Search" button in TPac, when we have a search bar and an "advanced search" button
#17:26:31dbstwo "advanced search" links, if we include the breadcrumb
#17:29:22sfortin has quit IRC
#17:29:38Dyrcona has left #evergreen
#17:35:26senatortsbere: fwiw i have tried to test your branch a couple of times today, but keep running into other bugs currently afflicting hold placement in the tpac. i hope to get to it again tomorrow though. of course if you find other willing testers, don't wait up :-)
#17:38:53dbssenator++
#17:46:25dbs has quit IRC
#18:05:00yboston has quit IRC
#18:15:09tsberesenator: Heh. Go figure. No problem, if it isn't in there by Sunday then our libraries will just have to live without it for a few more weeks ;)
#18:35:55kfrg56 has quit IRC
#18:47:46youdonotexist has quit IRC
#21:30:49wlayton has joined #evergreen
#21:33:04dbwells_ has joined #evergreen
#21:33:33dbwells has quit IRC
#21:34:46tater-laptop has joined #evergreen
#21:54:57atheos has quit IRC
#21:55:16atheos has joined #evergreen
#22:09:37wlayton has quit IRC
#22:15:33tater-laptop has quit IRC
#22:59:09eeeevil has joined #evergreen
< Tuesday, October 18th, 2011Raw Log FileThursday, October 20th, 2011 >