Open Source Integrated Library System

Evergreen on IRC

#evergreen Logs for Tuesday, December 14th, 2010

< Monday, December 13th, 2010Raw Log FileWednesday, December 15th, 2010 >
#TimeNickMessage
#00:09:38dbs has quit IRC
#00:26:39rsinger has joined #evergreen
#00:45:22youdonotexist has quit IRC
#00:52:28rsinger has quit IRC
#01:03:58rsinger has joined #evergreen
#01:10:18rickd_ has quit IRC
#01:10:18_bott_ has quit IRC
#01:10:51rickd_ has joined #evergreen
#01:10:51_bott_ has joined #evergreen
#01:11:05rickd_ has quit IRC
#01:11:40rickd_ has joined #evergreen
#01:31:37rsinger has quit IRC
#02:16:47jennam has quit IRC
#02:17:25Guest75568 has joined #evergreen
#02:53:55rsinger has joined #evergreen
#03:11:35rsinger has quit IRC
#03:13:44rsinger has joined #evergreen
#03:55:34pinesol has joined #evergreen
#03:55:34phasefx2 has joined #evergreen
#03:59:35rsinger has quit IRC
#04:09:17rsinger has joined #evergreen
#04:24:17dbwells has quit IRC
#04:42:04rsinger has quit IRC
#05:13:39rsinger has joined #evergreen
#05:40:54rsinger has quit IRC
#06:14:34cbandito_ has joined #evergreen
#06:15:59cbandito has quit IRC
#06:16:12cbandito_ is now known as cbandito
#06:24:53brendan2 has quit IRC
#06:52:14rsinger has joined #evergreen
#07:01:29brendan2 has joined #evergreen
#07:24:49granitize has joined #evergreen
#07:25:47granitize has joined #evergreen
#07:46:28sfortin has joined #evergreen
#08:22:44kmlussier has joined #evergreen
#08:44:57Dyrcona has joined #evergreen
#08:57:38dbwells has joined #evergreen
#09:12:44Meliss has joined #evergreen
#09:21:11bshum has joined #evergreen
#09:33:27jenny has joined #evergreen
#09:37:16leed has quit IRC
#09:38:41leed has joined #evergreen
#09:39:30yboston has joined #evergreen
#09:40:21collum has joined #evergreen
#09:45:33leed has quit IRC
#09:46:19bshumHmm... in the config.hold_matrix_matchpoint table there's a field for "stop_blocked_user" but no corresponding entry in the Hold Policies editor in the staff client.
#09:46:32leed has joined #evergreen
#09:46:35bshumAnother missed field, or intentionally hidden and always expected to be left as "true"
#09:47:05bshumOops, default "false" according to the table definition.
#09:53:32r123 has joined #evergreen
#09:53:54r123 has left #evergreen
#09:55:17tsberebshum: It could be a "we intended to use this, but never coded it" thing. Wouldn't be the only one.
#09:55:32bshumtsbere: That's what I'm wondering.
#09:58:40bshumIf so, I would tell folks here not to worry about entering a value for that field during entry. Thus far, I think we've set all our rules to use true for that field.
#10:00:42Dyrconabshum: I think its blocks stopped users anyway. IIRC, that check comes before the hold_matrix_matchpoint table is checked.
#10:03:13tsberebshum: In trunk, at least, that field IS used by the DB functions. If true it looks for standing penalties that look like '%CIRC%' and returns a false success.
#10:07:42bshumDyrcona, tsbere: Ahh, I see. That makes sense.
#10:07:52bshumThanks guys
#10:11:47kmlussier has quit IRC
#10:22:04mrpeters-islhey guys, anyone know about "admin_offline_manage_xacts.css"? I have a bunch of logs indicating it's missing (but referred to) and I can't seem to find it on SVN anywhere? File does not exist: /openils/var/web/xul/rel_1_6_0_0/server/skin/admin_offline_manage_xacts.css, referer: http://xen.evergreen.lib.in.us/xul/rel_1_6_0_0/server/admin/offline_manage_xacts.xul
#10:28:49bshummrpeters-isl: Hmm, most odd
#10:39:34mrpeters-islheh, its not breaking anything but i thought if the file was out there somewhere i could fix it :)
#10:39:49bshumI don't see the file either.
#10:40:56bshumI guess we don't notice this one because we've rarely used the offline xact management interfaces.
#10:41:04bshum knocks on wood
#10:42:31mrpeters-islphasefx: ping?
#10:57:40kmlussier has joined #evergreen
#11:17:22bshumHmm, the dropdown to select a circ modifier for a new circ policy rule doesn't order the names alphabetically?
#11:17:30bshum(in the staff client)
#11:17:55bshumMaybe sorting by code instead of name?
#11:23:17_bott_ has quit IRC
#11:30:12afterl has joined #evergreen
#11:32:03_bott_ has joined #evergreen
#11:32:26kmlussier has quit IRC
#11:39:30mrpeters-islbshum: i think thats right
#11:39:50mrpeters-isli remember something similar
#11:41:06bshumLet's just call that confusing when things don't appear in any logical order :)
#12:00:53eeevilwell ... is it meeting time-ish?
#12:00:53dbs has joined #evergreen
#12:00:54dbs has joined #evergreen
#12:01:03bshumIt is
#12:01:46eeevilwheee
#12:02:45Dyrconais there an agenda that I can't find somewhere?
#12:02:51dbshttp://evergreen-ils.org/dokuwiki/doku.php?id=dev:meetings:2010-12-14
#12:02:52bshumhttp://evergreen-ils.org/dokuwiki/doku.php?id=dev:meetings:2010-12-14
#12:02:54bshumHaha
#12:02:59Dyrconatyvm
#12:03:03dbsFrom wiki -> index -> dev -> meetings
#12:03:48dbs has done none of his action items from the last meeting, it has been a week chock full of other stuff (sigh)
#12:04:38eeevilwho's got the gavel
#12:05:23eeevilok, I'll pick it up
#12:05:34eeevilHEAR YE, HEAR YE
#12:05:48eeevilsomeone want to record the minutes?
#12:06:19bshumeeevil: I'll do it.
#12:06:24eeevilthanks
#12:07:42eeevilok, review of prev action items ... Dyrcona++, wrangling was very helpful ... do you still plan to do the committed->release for b5?
#12:07:54Dyrconayes
#12:08:04jeffDyrcona++ # and wrangling++
#12:08:13eeevilrock ... should we consider that another bug squashing day?
#12:08:31dbsDyrcona++
#12:08:33Dyrconaif you want. i'll go through the bugs from my email again and check on their states.
#12:08:53eeevilthanks ... there are some new ones too, I think
#12:09:09Dyrconai have a question about targeting bugs at a series.
#12:09:26dbsideas for a future bug-squashing day would be to coordinate efforts of volunteers to help reproduce + confirm bugs, or confirm that patches fix bugs, etc
#12:09:27Dyrconathere are a couple that i think should be targeted at 2.1, but I don't know how to do that.
#12:09:48Dyrconadbs: yep.
#12:10:00bshumI attempted to nominate one of those to 2.1, but it requires intervention of a release manager.
#12:10:02eeevilDyrcona: we need to give you "create milestone" access, perhaps?
#12:10:26eeevilfwiw, I don't have that either, afaict
#12:10:30dbsWould need to create the 2.1 series, then create milestones
#12:10:36dbsI can delegate that power
#12:10:58Dyrconaok. that would be good.
#12:11:12eeevildbs: in order to pin Dyrcona in his role, I'd support that :)
#12:11:16Dyrconai think the 2.1 series is there.
#12:11:19dbsI think we would ideally have a 2.1 branch cut as well, although perhaps we could just point at trunk
#12:11:24eeevildbs: may I have series/milestone perms too?
#12:12:34eeevildbs: I promise not to reintroduce 4-number versioning! ;)
#12:13:25dbsDyrcona: actually, for 2.1, when there are no milestones, "Target to release" should let you point to 2.1
#12:13:36dbsYup, I'm happy to share those around
#12:13:43dbssingle point of failure == not good
#12:13:52dbsmuch better to have multiple points of failure!
#12:13:57eeevilheh
#12:14:23eeevilso, b5 and 1.6.1.5 cut ... waiting on staff client for the latter
#12:14:29dbsI'll create an "Evergreen release team" and put you, Dyrcona, and myself in it to begin (at least to start)
#12:14:44eeevilalso, 1.6.2.0-RC1 cut and uploaded
#12:14:47eeevildbs: thanks!
#12:14:54Dyrconadbs++
#12:15:34eeevilI think that closes the review fo last week (I'll note that I did not write release notes for 1.6.1.4 ...0
#12:16:03eeevilI'm not sure what (4) is "Review Opportunity Items from previous meeting"
#12:16:08eeevilbut, let's do that
#12:16:31phasefx is rolling those clients right now; such a slacker :)
#12:16:40eeevilphasefx++
#12:16:53bshumI think that's a leftover, there weren't any opportunity items remaining from last time.
#12:17:04eeevilok
#12:17:39eeevil2.0 beta status ... well, I just now identified a significant issue (label vs label_sortkey on call_number table: https://bugs.launchpad.net/evergreen/+bug/690242)
#12:18:03eeevilbut other than that, I don't think there's anything /new/ coming in
#12:18:30dbseeevil: yeah, was looking at that. ugh.
#12:18:52eeevilthere is certainly some cleanup ... but if we can agree on a fix for 690242, I'd like to call the next cut RC1 to encourage more testing
#12:18:53dbsa seq scan on asset.call_number can't be that bad! :)
#12:19:12eeevil:)
#12:19:14Dyrcona;)
#12:20:12eeevilthat's my thoughts on (5)
#12:20:39DyrconaRC1++
#12:21:48kmlussier has joined #evergreen
#12:22:04eeevilanyone else?
#12:22:32dbsSo, in RC1 we'll ramp up with loads o' data and lots of challending unicode data to shake out any other issues like #690242 (which wouldn't show up in a plan with only a few records in the DB)
#12:22:53dbsCan we also update acq.open-ils.org or some other public server with RC1 for a more public kicking?
#12:23:05bshumeeevil: I have my question about custom metabib tables, but you had mentioned fixing that *later*
#12:23:29bshum*table entries
#12:23:34eeevildbs: "ramp up..." yes, and "acq.open-ils.org", yes I think so ... phasefx even "volunteered" yesterday :)
#12:23:40dbsfabulous
#12:24:08phasefxso, trunk or RC1 for acq.open-ils.org?
#12:24:11eeevilbshum: I don't recall those specifically, sorry
#12:24:22eeevilphasefx: I think RC1
#12:24:24dbsphasefx: RC1 I think
#12:24:26phasefxk
#12:24:30bshumeeevil: I'll write up something more specifically. It's an issue with something in the 1.6.1-2.0 upgrade script.
#12:24:43eeevilbshum: ahh... ok
#12:25:11eeevilbshum: oh, not /tables/ but existing index defs ... yeah, I want to do that, but tuits are all the wrong shape
#12:25:19dbsbshum: short term might be to, on your side, update the ID of anything past 15 in config.metabib_field to +100 and do the corresponding dance in the metabib.*_field_entry tables
#12:25:20eeevilanyone wants to step in, feelf ree
#12:25:34eeevildbs: indeed
#12:25:36dbsfe elf ree
#12:25:47bshumdbs: Right, I've been erasing those entries and redoing them at the higher IDs
#12:26:36dbsbshum: I'll see if I can work up a single transaction to maintain them across the migration. Going to try and migrate our 1.6.1.4-ish system to a 2.0 b5 test system this week, I think
#12:26:55dbsGiven my track record on action items recently, though...
#12:27:02bshumdbs: Cheers and good luck
#12:27:02Dyrconais this a case of just setting the sequence at 100 to start, and hardcoding ids in upgrade scripts below 100?
#12:27:04slipscomb has joined #evergreen
#12:27:19bshumThat's what I was wondering when I reported the problem initially Dyrcona
#12:27:26bshumI know we've done that with permissions
#12:27:36bshumLike the first 1000 are reserved or something, right?
#12:27:53bshum(supposed to be)
#12:27:54dbsDyrcona: just that, as well as maintaining existing entries that people might have added prior to incorporating that
#12:28:08Dyrconaah, more complicated, I see.
#12:28:39dbse.g. foolish people who read my blog!
#12:29:08eeevilI was planning to just push ones we don't supply (based on class + name) out of the way after confirming fkeys in all the right places
#12:29:17bshumdbs: I should add a comment there about the evils of following your instructions as written :)
#12:29:39eeevilON UPDATE CASCADE fkeys, I mean
#12:29:56DyrconaI think we've gotten a bit off track.
#12:30:15eeevilok ... so, nothing new in the 1.6.1 branch, so no upcoming releases
#12:30:38dbsHey, developers are meeting and discussing the development of Evergreen, that's pretty on track!
#12:30:39eeevil1.6.2.0-rc2 soon-ish, probably with 2.0-rc1
#12:31:15bshumeeevil: What significant pieces were put into 1.6.2? (though I know we're strongly urged to follow 2.0 only)
#12:31:49eeevilbshum: batch MARC update, hard due dates ... something else ...
#12:31:54dbsMostly backports of parts of 2.0: MARC editor niceties
#12:32:04bshumAh, I see.
#12:32:11dbsspine label printing
#12:34:54agJohn has joined #evergreen
#12:35:29eeevilanything else to air during the meeting?
#12:35:33moodaepo has quit IRC
#12:35:56dbsWhen's our holiday party?
#12:36:09eeevilright this very moment
#12:36:16dbwellsSorry, this wasn't on the agenda, but anyone have quick thoughts about this message I posted earlier today? http://libmail.georgialibraries.org/pipermail/open-ils-dev/2010-December/006638.html
#12:36:30eeevildbs: the AUTO+@@ stuff?
#12:36:34eeeviler, dbwells
#12:36:41eeevildang tab complete
#12:36:48dbwellseeevil: yes, exactly
#12:36:52mrpeters-isldbwells: i was excited about seeing the prospects of it
#12:37:00mrpeters-islhow would it work?
#12:37:14mrpeters-isljust a button in the copy editor or something to autogen a barcode?
#12:37:24alxp has joined #evergreen
#12:37:45eeevildbwells: how about making ^@@ the only reserved pattern ... then, the auto barcode would be "@@AUTO", and be replaced by "@@"||id
#12:38:07dbwellseeevil: makes good sense to me
#12:38:20eeevilinstead of reserving /both/ all versions of "auto" and anything starting with @@ (instead, just the latter)
#12:39:04eeevildbwells: so, I like it
#12:39:06phasefxincidentally, there is other autobarcode functionality serving a different purpose
#12:40:27eeevilphasefx: eh???
#12:40:36dbwellsDoes any other marker make better sense to anyone? '@@' was just the first thing that came to mind.
#12:41:07phasefxin volume/copy creator, you press the Auto-Generate barcode button and it takes the first barcode entered and increments for every other item being created in that batch, also taking into account check digits
#12:41:32phasefxbut in this case, you _do_ care about the barcodes
#12:42:27eeevilphasefx: well, I think that's a whole other thing -- dbwells' is a placeholder, the copy creator is giving (presumably) real data, no?
#12:42:33dbwellsphasefx: right, thanks. I have now begun calling these 'placeholder' barcodes rather than simply 'auto'
#12:42:48phasefxso these things are orthogonal, but if we want to expose a convenience button or something for @@auto, some thought may be needed for not making it ocnfusing
#12:43:03eeevilok, we're all on the same page, then
#12:43:09dbwellscool :)
#12:43:24phasefx didn't mean to derail, just a minor warning :)
#12:43:34Dyrconai've seen a lot of systems use a D_ to begin barcodes, probably old follett systems or something.
#12:44:09Dyrcona has no idea now why he bothered to mention that.
#12:44:45phasefxDyrcona: it may help someone one day search for and find this conversation :-D
#12:45:41DyrconaI like the idea of auto-generated barcodes and a button to generate one, next the staff will want the system to print the barcode.
#12:45:52mrpeters-islheh
#12:46:18eeevilhttp://www.barcodesinc.com/free-barcode-font/
#12:46:40dbwellsdbs: any thoughts on the feasibility of your recent recall functionality getting backported to 1.6.2? It is a feature on our most-wanted list
#12:46:43Dyrconaeeevil: there's also a perl module that generates a png.
#12:46:51dbsdbwells: perhaps 'DUMMY' + copy_id to make that signal clear?
#12:47:36dbsdbwells: it should be pretty straightforward to backport, but I don't really want to encourage more adoption of 1.6.2.x :)
#12:47:51dbwellsdbs: fair enough :)
#12:47:59eeevilagreed
#12:48:04dbsA bit late in the cycle, too, given that 1.6.2.0-rc1 is already out
#12:48:29phasefxstaff client up too now, evergreen-setup-rel_1_6_2_0_rc1.exe
#12:49:11phasefxand evergreen-setup-rel_1_6_1_5.exe
#12:50:01dbseeevil: I got an email from one of your co-workers asking for academic-oriented bib records, I'm happy to put more into Open-ILS/tests/datasets if the current sets aren't enough
#12:50:44dbsI can also commit some sets of authority records from IISH - they gave me the go-ahead to do that to help out with testing
#12:53:11eeevildbs: I think (don't know for sure) they're looking for a large-ish set ... not sure what "too big" is to put in tests/datasets, but I know one goal is to populate public test/demo servers with different "personalities" ... academic, public, school, law, etc ... with more appropriate record sets
#12:53:59dbsRight. And having a standard, large set of bib records to test with would be helpful all around, no matter what the personalities
#12:54:11eeevilagreed
#12:54:40dbsFor a large set, http://books1.scholarsportal.info/marc.html should have the Open Content Alliance records available to the world
#12:55:10dbsMostly pre-copyright content, but satisfies the definition of "large"
#12:55:10eeevilahh, nice ... and that's obviously going to be academic-focused, yes?
#12:55:46dbsLargely, I think.
#12:57:29dbsa lot of minimalist records though, due to retrospective conversions
#12:57:31gmcharltand the UMich records
#12:57:41gmcharlt~650,000 bibs, IIRC
#12:57:47dbsyeah. the UMich records might be a better source
#12:58:01gmcharltI glanced at them, generally they look good
#12:58:53dbsgah. next meeting starts in two minutes and I need to find a phone or headset
#13:00:29dbscsharp: actually - is the governance meeting starting now?
#13:03:28gmcharltdbs: call's starting up now
#13:04:01dbs looks around for call details
#13:04:07dbsfutilely
#13:04:17gmcharltdbs: sec
#13:04:53dbsnothing in my inboxes, thank heavens for IRC!
#13:06:05b_bonner has joined #evergreen
#13:11:04phasefxso meeting adjourned?
#13:13:28bshumGuess so
#13:13:30bshum:)
#13:27:04slipscomb has left #evergreen
#13:29:14b_bonner has quit IRC
#13:52:45atz_ has quit IRC
#14:39:47dbscute: <datafield xmlns:marc="http://www.loc.gov/MARC21/slim" tag="undefined" ind1=" " ind2=" "> -- nice tag there.
#14:41:21dbs38 of those suckers in our database. must come from a template
#14:41:56jeffor muscle memory
#14:42:23jeff(if it is/was possible to create that in the staff client)
#14:43:15dbsjeff: huh. insert datafield, but fail to give it a tag of any kind, and blammo - you get the magic JS value "undefined"? makes sense
#14:45:04dbsSounds buggable. On save in the MARC editor, check for null tags and pop up a dialogue explaining the problem and setting the cursor to the offendiing tag
#14:52:13Meliss has quit IRC
#14:52:30jenny1 has joined #evergreen
#14:53:38jenny has quit IRC
#15:01:22gmcharlt is now known as miskatonic
#15:01:28miskatonic is now known as miskatonic_u
#15:01:39miskatonic_u is now known as gmcharlt
#15:01:57csharpdbs: sorry for the lack of email reminder about the call - you weren't the only one who noticed :-/
#15:01:59gmcharlt has quit IRC
#15:01:59gmcharlt has joined #evergreen
#15:02:03csharp slinks away
#15:06:53Meliss has joined #evergreen
#15:07:02dbscsharp: s'ok! gmcharlt had my back :)
#15:07:46gmcharltdbs++ # thanking me for getting him into another meeting
#15:08:01dbsgmcharlt+=
#15:08:10dbserr, +-
#15:08:16gmcharltlol
#15:33:31kmlussier has quit IRC
#15:52:10collum has quit IRC
#15:58:26bshum has quit IRC
#15:58:51Meliss has quit IRC
#16:15:06sfortin has quit IRC
#16:19:27jenny has joined #evergreen
#16:19:45jenny has left #evergreen
#16:20:49jenny1 has quit IRC
#16:25:06granitize has quit IRC
#16:32:53dbs has quit IRC
#17:08:40yboston has quit IRC
#17:09:12Guest75568 is now known as jennam
#17:09:16jennam has joined #evergreen
#17:11:18atz has joined #evergreen
#17:28:47Dyrcona has quit IRC
#19:51:13jennam has quit IRC
#20:09:48Guest75568 has joined #evergreen
#21:16:15Guest75568 is now known as jennam
#21:16:22jennam has joined #evergreen
#21:21:24tpham has joined #evergreen
#21:37:31youdonotexist has joined #evergreen
#21:46:55jennam has quit IRC
#21:52:41Guest75568 has joined #evergreen
#21:52:48Guest75568 is now known as jennam
#21:52:55jennam has joined #evergreen
#22:12:39alxp has quit IRC
#23:07:38youdonotexist has quit IRC
#23:35:19tpham has quit IRC
#23:45:50r1231 has joined #evergreen
#23:58:01youdonotexist has joined #evergreen
< Monday, December 13th, 2010Raw Log FileWednesday, December 15th, 2010 >