Open Source Integrated Library System

Evergreen on IRC

#evergreen Logs for Tuesday, March 29th, 2011

< Monday, March 28th, 2011Raw Log FileWednesday, March 30th, 2011 >
#TimeNickMessage
#00:00:21mtisi has left #evergreen
#00:02:50mtisi has joined #evergreen
#00:13:41bshum has quit IRC
#00:24:57AaronZ-PLS has quit IRC
#00:35:53bshum has joined #evergreen
#00:56:44dbs has quit IRC
#01:49:36hitesh has joined #evergreen
#04:00:46m3th0d has joined #evergreen
#04:45:10twofish has quit IRC
#04:47:16twofish has joined #evergreen
#05:14:09hitesh has left #evergreen
#07:02:50m3th0d has quit IRC
#07:03:11m3th0d has joined #evergreen
#08:18:40m3th0d has quit IRC
#08:20:35m3th0d has joined #evergreen
#08:23:05Dyrcona has joined #evergreen
#08:29:02kmlussier has joined #evergreen
#08:33:59KingNightWolf has joined #evergreen
#08:46:01gdunbar has joined #evergreen
#08:49:45dbs has joined #evergreen
#08:54:50dbsdev meeting at noon EST today, eh?
#08:57:33dbsbshum++ # for setting up the agenda
#09:07:45bradldbs: EDT, I hope ;)
#09:08:05dbsbradl: uh, yeah. doh.
#09:09:05bradl is going to run for office on a singular platform: getting rid of DST :)
#09:11:10dbs votes for bradl
#09:11:31dbsHell, get rid of timezones too please. UTC FTW
#09:11:41m3th0d has quit IRC
#09:18:05bshumdbs: Should I send a tiny note to the dev list reminding folks about the meeting today?
#09:18:24bshumdbs: I started composing one for the community meeting but as usual forgot to write one for the dev meeting first :S
#09:18:26dbsbshum: I was just writing that tiny note up
#09:18:35bshumdbs++ Cool
#09:19:25dbsand sent
#09:28:15DyrconaI am setting up a SIP server and I am confused by this sentence "Make sure that all <login>s use the same institution attribute, and make sure the institution is listed in <institutions>." in http://www.open-ils.org/dokuwiki/doku.php?id=evergreen-admin:sip
#09:28:16jcpl-jasonb has joined #evergreen
#09:28:44DyrconaIt seems to imply that all logins have to use the same institution and that you can only have 1 institution.
#09:29:24DyrconaHowever, the comments in the oils_sip.xml imply otherwise, and it looks like you would want to configure different institutions if they have different selfcheck parameters.
#09:30:11DyrconaI'm just asking for a little clarification. I suppose I could just try things and see what happens. :)
#09:34:16bshumDyrcona: When you find out let us know ;)
#09:34:25bshumYour logic sounds good to me though, about having multiple institutions.
#09:34:55dbsDyrcona: We have set up SIP with multiple institutions, working fine
#09:34:58jenny has joined #evergreen
#09:35:31Dyrconadbs: Ok, thanks for the answer. That is what I thought.
#09:36:10dbsHrm. shrinksafe.jar packaged with dojo 1.3.3 appears to use an older, more lax version of rhino that allows some of the new OpenSRF JS tests to pass that should not
#09:38:21jenny has quit IRC
#09:41:02jenny has joined #evergreen
#09:43:05dbsmeh, turns out it's just a change in the ordering of object attributes in the JSON serialization
#09:48:08yboston has joined #evergreen
#09:52:52AaronZ-PLS has joined #evergreen
#10:23:47sgirard has joined #evergreen
#10:26:09eeevil_ is now known as eeevil
#10:33:59Dyrconamy sip server doesn't start.
#10:40:44dbsDyrcona: using the code from github or sourceforge? we're still using the sourceforge code
#10:40:57Dyrconagithub.
#10:41:20Dyrconaoils_ctl.sh says it is starting SIPServer then nothing. it's not running.
#10:41:32Dyrconai'm looking at oils_ctl.sh to see what it does now.
#10:41:42dbsDyrcona: yeah, I don't know anything about the github code, sorry
#10:41:52bshumDyrcona: When we used the latest SIP code we didn't have too much luck getting it to start initially
#10:42:27bshumgmcharlt had me poking around with some other branch at first
#10:42:38DyrconaI did get it to run from the command line with perl, so maybe I'll try that again and see if we can talk to it.
#10:42:38bshumAlso wasn't sure if it was a bad SIP file on my part
#10:43:05Dyrconabshum: yeah. not sure if mine is 100% either.
#10:44:46Dyrconaran perl SIPServer.pm /openils/conf/oils_sip.xml and something is listening on port 6001 at least. :)
#10:45:19DyrconaNow to see if it gives us answers that make sense.
#10:45:53adbowling-isl has quit IRC
#10:46:57lisppasteDyrcona pasted "SIP errors" at http://paste.lisp.org/display/120985
#10:47:07DyrconaThat doesn't look good.
#10:47:19DyrconaI'll try the sourceforge code.
#10:52:14DyrconaActually, it is working.
#10:52:27DyrconaI can login and get my own patron record back.
#10:52:32moodaepoDyrcona: I've got the sourceforge SIPServer working but I test against it using yaz-client from my workstation.
#10:52:40eeevilheads up, for those watching the esi git repo ... I'm about to merge a fun pile o' stuff into trunk! wheee!
#10:53:06Dyrcona didn't know that yaz-client does SIP, too.
#10:53:10dbseeevil: mysql compatibility, finally
#10:53:55eeevildbs: YES!
#10:54:03phasefxwith MyISAM no less
#10:54:06eeevildbs: actually, couchdb
#10:54:17eeevilwho needs typed fields?
#10:54:35dbsexcellent, the couchdb-lucene integration rocks these days
#10:55:07dbsyou've got the opensrf erlang client rolling too? incredible!
#10:55:32dbs["__c":["__p":[1234]]]
#10:55:41moodaepoDyrcona: Ignore me I was thinking of something else! : )
#10:56:46moodaepo << slap. wake up.
#10:57:24dbsDyrcona: cool, I'm not sure the tests in sourceforge are any different than the github tests. found the test harness a pain to set up, so we tested the old-fashioned way: throw into production
#10:57:24moodaepoeeevil++
#10:59:46DyrconaActually, I'm not so sure it is working, now. gonna do some more digging.
#11:01:42lisppasteeeevil pasted "merge feature rundown" at http://paste.lisp.org/display/120986
#11:03:36dbseeevil: sounds like some good stuff
#11:04:06kmlussiereeevil++ :-)
#11:05:52eeevilgrabbing 0504
#11:07:16mrpeters has joined #evergreen
#11:11:39tater-laptop has joined #evergreen
#11:13:57phasefxwe should make the Show * Fields options in the patron editor sticky
#11:15:21tsberephasefx: The "suggested" version has an org setting to default to it in trunk/2.1
#11:15:27phasefxah, sweet
#11:20:14joseph_ has joined #evergreen
#11:25:14adbowling-isl has joined #evergreen
#11:27:39DyrconaSIPServer from git seems to always return 0 checksums.
#11:29:41m3th0d has joined #evergreen
#11:32:25dbsDyrcona: http://lists.katipo.co.nz/public/koha/2011-March/027989.html might be pertinent, I don't know what version of the code atz forked to github
#11:33:07atzDyrcona: checksums are bogus.
#11:34:06atzthere are a ton of tests added including extensive debugging to help look at how they are built
#11:34:29tsbereI have code that generates them (and the server is happy with them, apparently) but then fails because every checksum returned is apparently 0000. :(
#11:34:30atzbut when newer systems are used, the specs don't account for behavior.
#11:34:46atzlike integer representation bit-depth
#11:35:41atzand then UTF-8 checksums are non-spec also. but koha does UTF-8 throughout now.
#11:36:12atzbasically, those checksums were designed for *serial* cable communication.
#11:36:28mdriscoll has joined #evergreen
#11:36:36Dyrconawell, that's what SIP was originally designed for.
#11:36:49atzTCP/IP has it's own checksumming built in. so if you can, just disable them in SIPconfig.
#11:37:01atzDyrcona: exactly
#11:37:17Dyrconaatz: i set error checking to false is there something else that I need to do to disable checksums?
#11:37:27atzthat should do it.
#11:37:49atz(probably need to reset sipserver after config change)
#11:38:39atzalso you might have to touch your client system.
#11:39:24suho has joined #evergreen
#11:39:25dbsatz: might be good to document some of those design decisions in the README?
#11:40:06atztrue
#11:42:15atzif you want to see the internals, do: perl t/0001_checksum.t 1
#11:45:14atzi'm not sure how you would get it to always return 0000 though. that seems odd to me.
#11:45:36atzmaybe if one side had them disabled, but the other side kept sending them.
#11:47:50tsbereMy client code *always* sends a checksum at this point, and (without a quick change I just made) *always* expects one back.
#11:48:20atz*nod*
#11:48:30tsbereNote that I didn't write said client code.
#11:48:34tsbereI got it from google code.
#11:48:38tsbereBut that is what it does.
#11:50:04atztsbere: some kind of integration package?
#11:50:26tsbereatz: http://code.google.com/p/php-sip2/
#11:53:36collum has joined #evergreen
#11:56:09tater-laptop has quit IRC
#11:57:07atzhmm... pretty old stuff... only 1 line of code touched in 3 years.
#11:57:42atz5 lines.
#11:58:43dbsmmm, meeting real soon now
#11:59:24ChanServ changes topic to "Dev meeting agenda: http://ur1.ca/3p7td | Welcome to the #Evergreen library system channel! | We are publicly logged. | Large pastes at http://paste.lisp.org/new/evergreen"
#11:59:30ColinC has joined #evergreen
#12:00:02slipscomb has joined #evergreen
#12:00:17bshumMeeting time!
#12:01:18bshumAny volunteers for lead/notes?
#12:01:20jenny1 has joined #evergreen
#12:01:31jenny1 has left #evergreen
#12:01:59jenny1 has joined #evergreen
#12:02:23jenny has quit IRC
#12:03:52dbsAgenda is short, I can lead :)
#12:03:57bshumdbs++
#12:03:59dbsDo we have quorum?
#12:04:05bshumGood question
#12:04:17berick is present
#12:04:19eeevil is here
#12:04:23phasefx is here
#12:04:30Dyrcona wonders what would constitute a quorum in this case.
#12:04:49dbsDyrcona: nothing official, just "enough people to bother with a meeting" :)
#12:04:51atzyeah, need a defined body before you can guage a set fraction of it
#12:05:05dbs turns meeting over to atz
#12:05:25atzdbs: hah, nice to see you too.
#12:06:09dbsso... action items from past meetings
#12:06:15dbsMike Rylander requested community testing for binary upgrade from 8.4 to 9.0 (via pg_upgrade).
#12:06:21dbsAny results?
#12:07:33berickmy tests were successful on squeeze and lenny
#12:07:39dbsI'm pretty sure that some people reported success in various cases on IRC over the past week or two
#12:08:33berickthat reminds me, we need to get hstore into the installer makefile
#12:08:35eeevilberick: with binary upgrade or pg_upgradecluster?
#12:08:36berickcontrib, that is
#12:09:01dbsOkay, eeevil - good enough for you? Or do you want to reissue the call?
#12:09:15berickeeevil: pg_upgradecluster wait, what's the difference?
#12:09:34eeevilberick: well, I have not confirmed that that uses pg_upgrade
#12:09:45eeevilso it may just be doing a dump/reload
#12:10:15berickk
#12:10:24eeevildbs: let's leave a standing call? I'd really love a full report from {someone-not-me}
#12:10:28dbsLet's put a call out for testing to the mailing list, and try to get results on the list
#12:10:35dbseeevil: will do
#12:10:38eeevildbs++
#12:11:19dbsNext - tsbere's grace period patch has been committed; thanks to eeevil and phasefx for their eyes, and tsbere for patiently taking suggestions from the likes of dbwells and I
#12:11:28dbstsbere++
#12:11:59dbsNext: Jason Etheridge to review patron opt-in patch (https://bugs.launchpad.net/evergreen/+bug/510959) - any movement on that phasefx?
#12:12:05m3th0d has quit IRC
#12:12:08phasefxI applied it to a local branch off of trunk, after adjusting for the perlmod path. Applies cleanly and doesn't seem to break anything when opt-in is set to false. Haven't tested things with opt-in set to true yet. I can do that, and/or just push to trunk/rel_2_1 as is and let others test. We still need to actually add the org unit settings it uses to org_setting_type table, as well
#12:13:16eeevilphasefx: let's push into mainline with the ou setting type? I'd hate that to be forgotten ;)
#12:13:24dbsCool, can you add your results so far and the latter details to the bug?
#12:13:26dbsor that :)
#12:13:45phasefxsure, can make the branch public too
#12:14:04dbsphasefx++
#12:14:17phasefxsitka++
#12:14:36dbssitka++ indeed
#12:15:07dbsGoogle Summer of Code - we've seen lots of activity on lists and IRC, student proposals opened yesterday and are open through April... 8th I think?
#12:16:00joseph_1:00pm on the 8th.
#12:16:19dbsphasefx, gmcharlt, and I can provide feedback to the submissions as they come in
#12:16:32b_bonner has joined #evergreen
#12:16:38dbsalso - it's still possible for other mentors to join us
#12:16:51eeevil hopes someone will propose adding http-translator transport to opensrf-java as part of their plan, instead of trying to implement direct JSON-in-Java
#12:17:15eeevilif a plan comes in that I'd be particularly well suited to mentor, I'll jump in
#12:17:59dbseeevil: cool; we'll keep you in mind
#12:18:14dbsjoseph_: thanks for the confirmation!
#12:19:08dbsBugs with attached patches at http://ur1.ca/3p7ya - note that the oldest bug has the newest patch, I think (patron editor "reset password" button by Dyrcona)
#12:20:19Dyrconayes. it currently says "Generate Password" but that's easy to change. :)
#12:20:27dbsDyrcona++
#12:20:40dbsAny volunteers to shepherd any of these through?
#12:20:55dbs can test out the "Generate password" patch
#12:21:28dbs520175 (context selectors for circ and hold matrices) may not even be applicable in the current circ world
#12:22:31eeevildbs: IMO, it should be expanded with a second selector to choose the field to filter on, since there are multiple ou-ish fields now
#12:23:17zigo-_- has joined #evergreen
#12:23:42eeevilI'll take the SIP2 patch
#12:23:48eeevilsince I piped up on the bug
#12:23:54dbseeevil++
#12:24:38tsbereI am not sure, but 744492 may be invalid, as that macro is apparently for something different than previously thought?
#12:24:40zigo-_- has quit IRC
#12:24:53dbstsbere: yes, that confusion needs to be sorted out
#12:25:52dbsThere might be other possible resolutions - documentation, UI, etc - for the patron_barcode vs. PATRON_BARCODE thing
#12:26:25phasefxI'll throw some info on the bug
#12:26:36dbsthanks phasefx
#12:27:30dbsReleases: gmcharlt took the reins and released OpenSRF 1.6.3 on March the 18th with a nice fix for Unicode issues
#12:27:53joseph_ has quit IRC
#12:28:37mrpetersgenerate password patch works fine
#12:28:37dbsOpenSRF 2.0.0 release processes plods along; the Unicode fix in 1.6.3 reduces the pressure to rush out OpenSRF 2.0.0
#12:28:40mrpetersusing it in production now
#12:29:17dbsthanks mrpeters, if you could comment on the bug that would be most helpful
#12:29:31mrpetersyep - home sick, but will get to it asap
#12:30:27dbsEvergreen releases: any hot stuff for 1.6.1.9? no bugs are targeted at it currently
#12:31:13eeevilnot that I recall...
#12:31:15dbsEvergreen 2.0.x has had a bonanza of patches so far, suggesting a release soon-ish
#12:31:22Dyrconai created the milestone yesterday at bshum's request.
#12:31:25bshumI'm hoping to go through all the bugs again sometime. Have to start making things more visible in the queues (over 130+ bugs in waiting according to the list)
#12:31:55bshumShould get the bug team together and hammer some of those away
#12:31:58eeevildbs: k ... I'd like cut a 2.1 preview as well
#12:32:16eeevildbs: so, end of the week at the latest? or do you want sooner
#12:32:18dbseeevil: cool, that fits with target date
#12:32:42eeevilsooner for 2.0.5, I mean
#12:33:36dbsi don't think it needs to be sooner, personally
#12:35:03eeevilk
#12:35:13dbsAt your leisure, sir!
#12:36:15bshumWould like to see the generate password fix with 2.0.5 at least (if that works as intended).
#12:36:19dbsSo, final item: https://bugs.launchpad.net/evergreen/+bugs?orderby=-datecreated shows lots of "New" bugs, some of which have had comments
#12:38:17dbsI guess that's what bshum was getting at
#12:39:20dbseeevil: for a bug that we've discussed on the list, I'll add the i18n attributes and markers for the default facet definitions, targeting 2.0.5
#12:39:20Dyrconayeah. i've been remiss in my bug wrangler duties, but being sick for two weeks'll do that.
#12:39:34eeevildbs++
#12:39:39dbsDyrcona: hey, you have a whole team of wranglers man
#12:39:58Dyrconayeah.
#12:40:20dbseeevil: it's really a bitesize bug I suppose, but i18n is something we need to support in the OPAC so it's also a critical bug IMO
#12:40:25bshumMaybe we should consider tagging bugs with 1.6 or 2.0 or 2.1 depending on their targets?
#12:40:57bshumThis nominating for series targeting has gotten a bit weird (from my light reading on LP permissions and setup)
#12:40:58Dyrconayes. we should try to target any open bugs at series.
#12:41:42dbseeevil: as for the facet diacritics, I wasn't 100% sure if you were suggesting that parsr address his problems with an NFC or NFD normalization step at the indexing stage, or whether we should add one to the defaults, or what
#12:44:32eeevildbs: I was actually suggesting that perhaps he should strip diacritics from facets in a negative-number indexing normalizer ... or add them ... but (at least, IM-monolingual-O) they are different facets because they're different (source) languages
#12:45:17gmcharltfwiw, +1 to doing NFD/NFC conversion in the normalizers
#12:45:20eeevilpoint being, facets are complete-exact-match strings, so normalize to your happiness level :)
#12:45:22gmcharlt(in haste, in another meeting)
#12:45:28kmlussier_ has joined #evergreen
#12:45:40kmlussier has quit IRC
#12:45:41dbseeevil: yeah, there's a lot going on in that bug. I was focusing on the apparently identical "Québec"s, one of which was NFC and one which was NFD
#12:45:55kmlussier_ is now known as kmlussier
#12:46:03eeevildbs: on that we completely agree, yes
#12:46:08eeevilone NF to rule them all
#12:46:32dbsgmcharlt: you data slinger you! normalize the data when it comes in, damnit! :)
#12:46:50eeevil(and NFC displays better in most browsers, so ...)
#12:46:56gmcharltdbs: life is messier :)
#12:47:08gmcharltand while NFC is usually better for display, NFD is useful in other contexts
#12:47:12gmcharltas you know, of course
#12:47:25eeevil(even though I much prefer NFD for ease of reading in non-UTF8 terminals)
#12:47:33gmcharltso having normalizers to do the conversion othe fly (or to deal with databases that have notyet seen the one true NF light) is still a win
#12:47:36dbseeevil: and I agree completely with exact-match strings, too; makes a huge amount of sense for facets
#12:48:12eeevilfwiw, NFC is fine for this application, IMO ... you don't do much with facets except equality comparison, which works fine
#12:49:35eeevilI'd go as far as to say we just shove that into the ingest stream ... a BEFORE INSERT trigger on metabib.facet_entry, eh?
#12:49:46eeevila "force_to_nfc" SP
#12:49:47joseph_ has joined #evergreen
#12:49:48dbs would happily drink to that
#12:50:01gmcharlt+1
#12:50:30eeevilok ... I'll do that after the unavail_holds patch (about to commit the 2.x version to trunk)
#12:50:53dbsright on
#12:51:41dbsMan, for a light agenda we're closing in on the hour. Any other important matters?
#12:53:37bshumJust an FYI, for DIY sys admin hackfest hours, we've got some light planning underway already. If you have any ideas for things to discuss/do so that we can hit the ground running, please feel free to contact either me or moodaepo.
#12:54:05bshumCourse we won't try stealing too many people from the main developer events ;)
#12:54:48dbsOh yeah. git... I've been reading through eeevil's massive patch to trunk/2.1, and kinda wish it was broken up into more discrete chunks. wishes/horses though
#12:56:02eeevildbs: that's something we should (all) pow-wow about at the conf and try to figure out some best practices ... I know it's huge and suboptimal :(
#12:57:06dbs is in favour of that, but keeps sliding back to using plain SVN
#12:57:23dbsbut I like git when I use it :)
#12:57:56eeevilheh
#12:58:23dbsBiggest problem for me is that emails containing huge commits get truncated, and I'm an email-commit-reader. *tiny violins*
#12:58:34eeevil:)
#12:58:54dbsOkay, let's wrap up. Another meeting in two weeks and conference craziness to follow
#12:59:19tsbereQuick question while I am digging through here anyway: Should "required" surveys actually flag themselves as such for display and requiredness purposes on patron registration?
#12:59:55bshumdbs++ # for leading. I'll write in minutes
#13:00:02bshum(later)
#13:01:00bshumCrazy, but is it bad for an ISSN to be used in multiple records? i.e. multiple 022a using the same string.
#13:01:35dbsbshum: not if they're records for the same serial
#13:01:51dbs is _so_ helpful
#13:01:56dbsbshum++
#13:02:23eeevildbs / gmcharlt: opinions of implementation of force-to-nfX? just plperlu is my fast-path thought
#13:02:23bshumdbs: That makes sense, just trying to figure out why we can't seem to bring up the record via ISSN or marc expert search. But of course, I can find its entry in the metabib tables
#13:02:33bshumThanks
#13:03:16joseph_ has quit IRC
#13:04:00jcpl-jasonb has quit IRC
#13:04:39dbseeevil: sounds like a practical approach to me, given that postgresql has no built-in composition normalization ("It's all UTF8 to me!")
#13:05:15shopkins has joined #evergreen
#13:06:18eeevildbs: hrm.. http://justatheory.com/computers/databases/postgresql/unicode-normalization.html see third comment
#13:07:34dbsDarren Duncan? I met him at OSCON 2005. My confidence is not high as a result...
#13:08:01slipscomb has left #evergreen
#13:08:44gmcharlteeevil: +1 to plperlu
#13:09:15gmcharltand I wouldn't be surprised if NFD and NFC in Unicode::Normalize is XS anyway
#13:10:12eeevilgmcharlt: they are ... my concern now is the use of nfc ... " One main reason that I cite is that NFC doesn't provide a single codepoint for many instances of graphemes using multiple combining characters with a base character, but just provides support each of the combining characters with the base separately. So to get such a grapheme with base 'B' and 2 combining characters '1','2', you can choose either the 2 codepoints 'B1' plus '2' or 'B2' + 1 but
#13:10:20eeevilprobably got trunc'd
#13:10:43dbwellseeevil: AFAIK, converting to NFC involves converting to NFD first, so you should not end up with B2+1 if the NFD is B+1+2.
#13:11:10eeevildbwells: you mean specifically in Unicode::Normalize? or the process in general
#13:11:25dbwellsI mean the process in general.
#13:11:37dbwellsas I understand it, anyway
#13:11:59eeevilyes, according to unicode.org, you are correc
#13:12:00eeevilt
#13:12:21eeevilso, nfc it is
#13:12:50eeevildbs: your doubts seem well-founded (if I followed your meaning)
#13:13:21dbseeevil: I'm still recovering from the resurgent memory of that meeting
#13:13:35eeevilheh .. I don't know that I've had that pleasure
#13:14:41dbsHe's actually a really nice and smart person. Just a very strange fit for a meeting focused on Apache Derby
#13:15:06dbs needs to work on his social grace
#13:15:07dbss
#13:15:26eeevilfigure 5, third example: http://unicode.org/reports/tr15/
#13:15:31eeevildbwells++
#13:15:33eeevilon to the code
#13:17:52jenny2 has joined #evergreen
#13:19:34jenny1 has quit IRC
#13:20:11m3th0d has joined #evergreen
#13:27:42b_bonner has quit IRC
#13:29:13eeevilgrabbing 0505
#13:32:30gmcharlteeevil: yep, just read that; Duncan's concern is bogus
#13:36:12AaronZ-PLS has quit IRC
#13:36:22AaronZ-PLS has joined #evergreen
#13:40:25sylvarPossibly dumb question about BibTemplate: Is there a way to do a dojo query for tag 440 or 490, other than datafield[tag^=4] datafield[tag$=0] datafield:not([tag=400]) datafield:not([tag:410]) ... ?
#13:40:44ColinC has quit IRC
#13:44:53senatorsylvar: datafield[tag=440], datafield[tag=490] should work iirc
#13:45:08senatorit's just using css3 selectors
#13:45:16sylvarthanks senator, I'll give it a whirl
#13:45:17senatormore orless
#13:46:12sylvarbrilliant! senator++
#13:48:12kmlussier has quit IRC
#13:48:24kmlussier has joined #evergreen
#13:55:43jenny1 has joined #evergreen
#13:56:43jenny1 has left #evergreen
#13:58:06jenny2 has quit IRC
#14:09:05ashishm has joined #evergreen
#14:10:24jenny1 has joined #evergreen
#14:12:29collum has quit IRC
#14:14:57Jbergy has joined #evergreen
#14:22:55ashishm has quit IRC
#14:43:37jamesrf has joined #evergreen
#14:45:21lpd has quit IRC
#14:48:08jeffdavis has joined #evergreen
#14:51:32yboston has quit IRC
#14:54:51m3th0d has quit IRC
#15:03:29jeffdavisare there any plans for moving to the latest version of dojo?
#15:03:51bshumjeffdavis: That's one of those GSoC ideas I think.
#15:05:47bshumjeffdavis: http://evergreen-ils.org/dokuwiki/doku.php?id=dev:summer_of_coding_ideas - Modernize Evergreen's Web Interface
#15:06:11jeffdavisah there it is, thanks bshum
#15:06:53tsbereI keep thinking about poking at that personally, and I keep saying "way too much work right now"
#15:09:04phasefxthat lucky gsoc student gets to spend 40hrs a week at it :)
#15:12:09dbsHopefully hooking into DOH to add some testing of the interface
#15:12:13dbs can always hope
#15:19:58levacjeep has joined #evergreen
#15:21:30bshumHuh
#15:21:53bshumRemind me, but ISxN should be stored in the metabib.real_full_rec without the - hyphen?
#15:22:24levacjeepHi everyone, I work for NRCAN and we are working on re-skinning one of our site which uses evergreen. I am having problems with conditional IE comments, for some reason the XML files seem ignore these. Would anyone have any suggestions? thanks :)
#15:24:14dbslevacjeep: conditional IE comments? Use /* */ instead of //
#15:25:28Dyrcona wonders if having a sip user with a permission.work_ou causes any problems.
#15:27:50levacjeepdbs: when I call the stylesheet I add it like so: <!-- [if IE 7]><link href="css/ie7.css" rel="stylesheet" type="text/css" /><![endif] --> But it gets ignored, how would I use those it with /* */
#15:33:48kmlussier has quit IRC
#15:36:41levacjeep has quit IRC
#15:37:02dbs@later tell levacjeep: oh sorry, i was assuming JavaScript comments
#15:37:02pinesol`dbs: The operation succeeded.
#15:44:01lisppastebshum pasted "hyphens in ISSN values" at http://paste.lisp.org/display/120993
#15:45:57AaronZ-PLSAnyone up for a 1.6.0.8 permissions question?
#15:46:00agJohn has joined #evergreen
#15:47:40bshumAaronZ-PLS: Go for it, sure someone might know ;)
#15:47:58brian_f has joined #evergreen
#15:48:21AaronZ-PLSDoes the MARK_ITEMS_DAMAGED permission exist in 1.6.0.8?
#15:48:44dbsbshum: which ISSN search are you using? Advanced->ISSN? keyword:? or identifier|issn:?
#15:49:04bshumdbs: Using the Advanced --> ISSN search
#15:49:06AaronZ-PLSI have been told that it does, but it does not seem to have any effect
#15:49:12bshumdbs: For OPAC/staff client
#15:49:49dbsAaronZ-PLS: MARK_ITEM_DAMAGED
#15:51:13mrpeters-home has joined #evergreen
#15:51:47AaronZ-PLSdps: Sorry, I mistyped it into here. I have it has MARK_ITEM_DAMAGED in EG, but I get a permission error when I try to mark an item as damaged
#15:51:58AaronZ-PLSWe would like to let circulators mark items as damaged without giving them UPDATE_COPY rights
#15:53:02shopkins has quit IRC
#15:53:13AaronZ-PLSI get an error which says: Permisson Denied: UPDATE_COPY with the debug info of: open-ils.circ.mark.item.damaged
#15:53:50bshumdbs: Is this related to this bug you think? https://bugs.launchpad.net/evergreen/+bug/728671
#15:54:48berickAaronZ-PLS: that is fixed in 2.0, possibly after the next cut
#15:55:06bericknow you can mark item damaged if you have either permission
#15:55:43dbsbshum: ISBN / ISSN searching is a rat's nest, and the rat has changed the layout of its nest a few times (I've been a decorator for the rat)
#15:56:12berickchangeset for reference: http://svn.open-ils.org/trac/ILS/changeset/19416/branches/rel_2_0/Open-ILS/src/perlmods/OpenILS/Application/Circ.pm
#15:57:17dbsdbwells had some thoughts (and maybe even commits?) relevant to ISxN searches recently
#15:58:10AaronZ-PLSberick: How about 1.6.2?
#15:59:40bshumdbs: That's the feeling I've got. For what it's worth, if I hack the MARC record entry so that it uses a space instead of the dash, then update the full bib rec entries, then I can find that record with search.
#16:00:03bshumdbs: So it seems like the actual stored format of ISSN in the bib is causing the grief.
#16:00:20dbsbshum: no, not in the bib, in metabib.full_rec
#16:00:48bshumdbs: Right, changing the bib entry and then updating the metabib.real_full_rec
#16:00:49dbsissn's used to get normalized when they were extracted from the bib and plopped into metabib.full_rec
#16:00:57bshumdbs: Aha
#16:01:08bshumdbs: So maybe the normalization isn't working right for us...
#16:01:16dbsand the left-hand "Advanced" search searches against mfr.value
#16:01:33dbshowever - we don't normalize mfr.value (much?) anymore in 2.0
#16:02:07dbsso really, the solution is to change Advanced->ISSN search to use an identifier|issn: search instead
#16:02:20berickAaronZ-PLS: looks like it made it into 1.6.2.3 http://svn.open-ils.org/trac/ILS/browser/tags/rel_1_6_2_3/Open-ILS/src/perlmods/OpenILS/Application/Circ.pm
#16:02:27dbs(I'm interested in finding out how these searches work for you with identifier|issn)
#16:02:52bshumdbs: I wondered about that, since we do have entries in the metabib.identifier_field_entry table.
#16:03:33bshumThat's where I went first to find out if we had the right entries in the system.
#16:04:03AaronZ-PLSberick:Thanks
#16:04:16dbsIIRC, dbwells was not happy with the state of a plain "identifier: foo" search; the wrong normalizations are applied to the input terms in that case (because you want to normalize differently for ISBNs vs ISSNs)
#16:04:39dbsso you need to specify the specific kind of identifier to get reasonable results
#16:04:48dbs babbles babbles babbles
#16:05:22bshumWell, each identifier has its own field class doesn't it? (pokes open pgadmin again...)
#16:06:43dbsbshum: yep
#16:07:01dbsnot sure what your point is
#16:07:28bshumI'm not sure either, I mutter when it's near the end of the day :(
#16:07:52bshumLet me know what I can do to help (if I can)
#16:09:08dbsbest way to help would be to ensure that identifier|issn searches work :)
#16:14:38bshumHmm, guessing that's something to do with using SRU
#16:15:34dbseh?
#16:15:57adbowling-isl has quit IRC
#16:15:59dbsjust type "identifer|issn: 1234-5678" into the search box, that should do it
#16:16:00mrpeters-home has quit IRC
#16:16:14bshumOh, well that makes much more sense.
#16:16:46dbsI guess by "Advanced" search we need to distinguish between the "Advanced search page" and the advanced search widget
#16:16:51dbs weeps
#16:17:53bshumSearching for identifier|issn: 00377333 (without the dash) got the record to come up
#16:22:51dbsYeah, and with the dash it fails right?
#16:22:59bshumThat's correct.
#16:23:14dbsI get the same results, albeit with a 2.0.2-ish test system
#16:23:50bshumTrue, I should say that ours is a 2.0.1/2-ish production system.
#16:24:31dbsFor great fun, the same search fails without a hyphen on the advanced search page, and succeeds with a hyphen there :)
#16:26:08bshumI see that behavior only if the metabib.real_full_rec stores the ISSN without the dash in it (which it doesn't seem to be doing correctly in our database).
#16:27:37dbs"correctly" has yet to be determined for 2.0 I think
#16:29:04rjackson-isl has quit IRC
#16:33:26bshumWell, thanks dbs, until we know how that's supposed to behave, I'll suggest to our libraries to use other means of finding the bibs they want or using the identifier|issn search option.
#16:34:54Dyrconabshum: it is supposed to behave the way *you* want it to behave. if it doesn't, change the code. :)
#16:37:38bshumDyrcona: Right, right....
#16:37:58bshumI should learn more about how it's supposed to behave then.
#16:38:57dbwellsbshum: sorry I missed the ISSN conversation, I was out. It looks like you guys mostly sorted out the current state of things, which is that the various ISSN searches are broken in various ways :)
#16:39:58dbsdbwells: correctamundo, and as academics you and I have a special interest in this area :)
#16:42:45dbwellsI got derailed a bit by our upgrade 9 days ago, but I am going to comment what I know on the one open ISSN bug, and also make time tomorrow to code a fix for at least one of the two.
#16:49:07dbsdbwells: awesome. I'm going to be derailed by upgrading in May, I don't have many excuses for being derailed right now other than "ebooks"
#16:52:19dbwellsdbs: does your library use SFX for any ebook management. We have been struggling to deal with our growing ebook "collections" in some sort of reasonable and unified way, but have so far kept our SFX instance as ejournal only.
#16:52:36dbwellsSorry, forgot the '?' after the first sentence.
#16:53:30dbsdbwells: no, SFX for ejournals only so far, but we think it would make a ton of sense to get our ebooks into SFX, use OpenURLs in the catalog, and (most importantly), enjoy the added coverage that Google Scholar would offer for the ebooks once they're in SFX
#16:54:47dbwellsdbs: thanks, just curious at this point.
#16:55:54dbsdbwells: large parts of our current confusion come from running a consortial catalogue where different schools have loaded different sets of MARC records for the same ebooks; I'm trying to tease all of it out to get to a consistent state
#16:59:57KingNightWolf has quit IRC
#17:01:25dbwellsdbs: I certainly feel your pain and wish you luck. Before my current position, I was hired with the title of 'Digital Objects Specialist', and it was pretty much my whole job to straighten out and clean up large ebook loads. So you should explain that you are now doing two jobs and need a raise :)
#17:02:15dbsdbwells: hah, well that makes me feel a little bit better for not having sorted this out yet, at least :)
#17:04:05jeffwe synthesize marc records where the vendor doesn't provide them, or use the vendor-provided ones with our 856 tags added. we import those that we have, vandelay finds dupes, we import the non-dupes and then there's a GRPL 856 merge tool that pulls our 856 tag from the queue-of-dupes and puts it on the existing record.
#17:04:27jeffonly some of our vendors then provide a "delete these now -- you don't have them anymore", and i haven't dealt with that yet.
#17:05:21jeffit's almost-but-not-quite the opposite of the "export bibs from evergreen into something else" problem, which i have a little better grip on.
#17:12:50mrpeters-isl has quit IRC
#17:14:52dbsjeff: yeah, a process going forward is relatively easy, the problem is dealing with the past 3 years of crap
#17:15:27jeffyep
#17:15:55dbsberick++ # for paying attention to GSoC questions
#17:19:23berickoh, yeah, *I'm* the nail that's holdin' this whole thing together ;)
#17:31:49Dyrcona has quit IRC
#17:57:04jenny1 has left #evergreen
#18:00:42moodaepoAnyone with access to a 2.0.4 around? Need to confirm a bug jenny1 has found. PSR-010 gives a FIXME error > http://evergreen-ils.org/dokuwiki/doku.php?id=qa:gpls_pines_evergreen_test_cases
#18:12:52suho has quit IRC
#18:42:11tater-laptop has joined #evergreen
#18:48:52tater-laptop has quit IRC
#18:59:14sgirard has left #evergreen
#19:17:04Jbergy has quit IRC
#19:40:52pmpaway has quit IRC
#20:05:27granitize has joined #evergreen
#20:06:16granitize has left #evergreen
#20:33:54jamesrfmoodaepo: confirmed i get a FIXME with "params is undefined" in the debug output
#20:34:52jamesrfanyone who's a committer, in trunk Open-ILS/src/sql/Pg/030.schema.metabib.sql +143 has a typo
#20:35:23gmcharltjamesrf: on it
#20:36:28dbsGotta kick testing.evergreen-ils.org up a notch and get it to start trying to create schemas with every commit one of these days
#20:36:37brian_f has quit IRC
#20:41:21gmcharltjamesrf: fix pushed, thanks for the catch
#20:41:24gmcharltjamesrf++
#21:00:46tater-laptop has joined #evergreen
#21:07:32StephenGWills has left #evergreen
#21:17:35finnapz has joined #evergreen
#21:26:44pmpaway has joined #evergreen
#21:35:23pmpaway has quit IRC
#22:18:23Digital_Pioneer has quit IRC
#22:34:43tater-laptop has quit IRC
#22:42:16rcj7 has joined #evergreen
#22:43:08pmpaway has joined #evergreen
#23:11:31rcj7 has quit IRC
#23:54:08jamesrf is now known as jamesrf-afk
< Monday, March 28th, 2011Raw Log FileWednesday, March 30th, 2011 >