Evergreen ILS Website

IRC log for #evergreen, 2014-09-04

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

All times shown according to the server's local time.

Time Nick Message
04:51 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
06:26 wsmoak joined #evergreen
07:38 rjackson-isl joined #evergreen
07:47 mtate joined #evergreen
07:48 phasefx joined #evergreen
07:48 eeevil joined #evergreen
07:48 Callender joined #evergreen
07:49 gdunbar joined #evergreen
07:50 egbuilder_ joined #evergreen
07:51 collum joined #evergreen
07:56 jboyer-isl joined #evergreen
08:03 akilsdonk joined #evergreen
08:10 csharp @distractme
08:10 pinesol_green csharp: well, that's what you get for not being a shell script
08:17 csharp jboyer-isl: would you be willing to share your "set a whole bunch of circs to Lost" script you were working on here?: http://irc.evergreen-ils.org/​evergreen/2014-08-13#i_116825
08:21 csharp oh - wait - now I see the gist - nevermind ;-)
08:31 Shae joined #evergreen
08:32 ericar joined #evergreen
08:37 mdriscoll joined #evergreen
08:37 pmurray_away joined #evergreen
08:46 pmurray joined #evergreen
08:46 Dyrcona joined #evergreen
08:47 mmorgan joined #evergreen
08:54 * Dyrcona shudders.
08:54 * Dyrcona is apparently connected to orwell.freenode.net.
08:54 Dyrcona Maybe that is appropriate. :)
08:55 * csharp is connected to verne
08:57 tspindler joined #evergreen
09:03 csharp so what would $e be in the context 'OpenILS::Application::Cat::Asset​Common->set_item_long_overdue($e, $circ->target_copy);'
09:03 csharp the staff member's ID?
09:03 csharp or is $e some sort of hash or something
09:04 csharp I'm just trying to call that function directly in a script and I'm not sure what to put in for that value
09:04 kmlussier joined #evergreen
09:05 jboyer-isl csharp: I was thinking $e was usually a CStoreEditor or something similar. (Note I haven't verified that at the moment)
09:09 csharp so where to I get me one them there CStoreEditor thingies? ;-)
09:09 * csharp could use a "Perl for Evergreen 101" class
09:11 jboyer-isl I haven't had to do that yet. :D If it's unauthenticated, I think you can just do OpenILS::Utils::CStoreEditor->new, though I could very easily be wrong about that. (If you grep around the Eg source for that line though you'll see how it's been done elsewhere.)
09:12 jeff this file calls OpenILS::Application::Cat::Asse​tCommon::set_item_long_overdue already. You can see that it gets its editor (which it also calls $e) by making a call to new_editor.
09:12 jeff as to where new_editor comes from:
09:13 jeff when you "use OpenILS::Utils::CStoreEditor;", you get new_editor -- it's listed in that package's @EXPORT_OK array, and thus you don't need to explicitly bring it in or reference it by its full package name.
09:14 akilsdonk_ joined #evergreen
09:14 jeff new_editor is essentially a wrapper for OpenILS::Utils::CStoreEditor->new: sub new_editor { return OpenILS::Utils::CStoreEditor->new(@_); }
09:15 jeff as you can see in the MarkItemLongOverdue.pm -- oh, hah. i didn't actually mention which file that was in my first statement this morning.
09:15 jeff OpenILS::Application::Trigger:​:Reactor::MarkItemLongOverdue, Open-ILS/src/perlmods/lib/OpenILS/Applicat​ion/Trigger/Reactor/MarkItemLongOverdue.pm in the repo.
09:17 csharp jeff: thanks - that's the kind of thing I'm looking for
09:17 jboyer-isl csharp: I recommend you start from this version of my script, (the first gist was missing a lot of good stuff): https://gist.github.com/Hi​tScan/0bddf6e454481438f27d
09:17 jeff and perhaps correcting myself a bit, i think you need to do this to actually get new_editor: use OpenILS::Utils::CStoreEditor qw/:funcs/;
09:18 csharp jboyer-isl: thanks!
09:18 jeff or you can use it without the qw/:funcs/ and explicitly call OpenILS::Utils::CStoreEditor->new
09:18 jboyer-isl jeff should have you in good hands while I'm at meetings the rest of the day. good luck!
09:18 jboyer-isl csharp++ jeff++
09:19 csharp jboyer-isl++ # pioneering and sharing
09:22 csharp jeff: so I could potentially call the MarkItemLongOverdue.pm file directly, right?
09:23 * csharp gets easily lost in perl stuff :-/
09:24 csharp I'll back up and let you know what I'm doing.  I'm going to gather a list of copy IDs and feed them into what I'm trying to create to have them all marked "LongOverdue" (which is basically "marked lost by the system, not a human")
09:25 csharp that way when we get the LongOverdue A/T definition going, it can just work on everything going forward
09:26 eeevil csharp: how long is the list you're looking at?
09:27 jeff csharp: I wouldn't recommend using OpenILS::Application::Trigger:​:Reactor::MarkItemLongOverdue outside of A/T
09:28 eeevil and I second jeff's recommendation against trying to use a reactor outside a/t. there's a lot of environment that you'd need to mock up
09:30 jeff csharp: if you look at that file, it does most of its work inside a sub called "handler", which expects (among other things) an A/T-style $env hash with params. the actual elements of that hash that are used by that specific sub are few, but it's also going to do things like make log entries that claim to be trigger-related, and it's going to fire any A/T events that are defined for longoverdue.auto (which you may or may not have)
09:31 eeevil csharp: a/t is meant to handle that stuff for you, so unless you're talking about a list on the order of several hundred thousand items (and even then, with judicious use of delay settings for the definition), you may just want to let a/t handle it. you'll notice that the the reactor is also potentially creating cascaded events (could be notifications, etc) after marking the item longoverdue
09:32 eeevil jeff: jinx :)
09:42 csharp eeevil: let me do a count of items that match our criteria
09:42 yboston joined #evergreen
09:44 csharp eeevil: looks like 309,524 at the moment that I would need to process
09:44 csharp I'll look into processing with A/T (doing this all on a test server at the mo)
09:46 eeevil if you used the min and max delay to do it in several-month chunks (change the def after each run) I bet that'll be less work in the long run
09:46 csharp eeevil: excellent - I didn't know if that was a sane approach or not
09:47 eeevil well, if you set it up as a special granularity for the time being, those could be processed in one go in parallel with the normal events. with --granularity-only
09:47 eeevil it would take a while (and do it on a server with plenty of RAM), but it'll clear the backlog
09:47 eeevil then you'd just remove the granularity and things would ... go
09:48 csharp great - that would be ideal
09:50 eeevil and the delay chunking method would be the fallback if 300k events is truly too many (but given enough RAM, it should be doable)
09:51 csharp ok cool
09:56 mmorgan csharp: About a year ago, we ran a backlog of overdue notices by manipulating the A/T trigger delays. We chunked it up by month. Some runs took about 20 minutes to complete, but it worked well.
10:05 csharp mmorgan: thanks for that feedback!
10:06 chatley_ joined #evergreen
10:08 dcook joined #evergreen
10:09 gdunbar joined #evergreen
10:09 phasefx__ joined #evergreen
10:09 goood joined #evergreen
10:09 Callender_ joined #evergreen
10:10 jcamins_ joined #evergreen
10:10 phasefx_1 joined #evergreen
10:33 dcook__ joined #evergreen
10:33 phasefx_ joined #evergreen
10:38 Dyrcona In a class on RDA cataloging and someone says we're going to use 3xx tags for metarecords. Does anyone have any plans for that?
10:39 Stompro joined #evergreen
10:40 Dyrcona I think this person is speaking generically and not about Evergreen, but thought I should ask.
10:49 Dyrcona I don't see how that is going to work, unless you make a master bib record that contains RDA tags for all of the media and carrier types, but then how do you know which one a patron wants when they place a hold?
10:50 Dyrcona Guess, holds code would have to change drastically to accommodate that.
10:50 kmlussier Dyrcona: When we started the MVF project, I know we had some discussion about whether we would be able to leverage the 3xx fields to identify formats, but I'm fuzzy on how easy/hard it would be.
10:51 * kmlussier isn't being terribly helpful.
10:51 Dyrcona kmlussier: I don't think it's going to be easy, particularly while the majority of records are not up to RDA standards.
10:52 kmlussier There was also a brief dicussion about it here: https://bugs.launchpad.net/evergreen/+bug/1125621
10:53 pinesol_green Launchpad bug 1125621 in Evergreen "RDA 336, 337 338 fields" (affected: 7, heat: 42) [Medium,Confirmed]
10:56 kmlussier gdunbar: I'm doing some release notes cleanup today and noticed that bshum added a placeholder for acknowledgements. I think gmcharlt_ added the acknowledgements last time. Would you be able to help me identify "organizations that commissioned developments in this release of Evergreen."?
10:56 kmlussier I know 3 of the organizations off the top of my head. :)
10:56 gdunbar kmlussier: I can and will - I'll shoot you an email if that's okay
10:56 gmcharlt joined #evergreen
10:56 kmlussier graced: Perfect. Thanks!
10:56 graced np
10:57 graced :)
11:02 vlewis joined #evergreen
11:10 * kmlussier wonders if we should have a separate reports section for the release notes instead of lumping new reports features in with administration.
11:13 bshum kmlussier: Might be a good idea. +1 to adding that in the future.
11:14 * bshum is waiting for his flight. Was nice to see folks in GA! :D
11:15 kmlussier bshum: What's your next stop?
11:16 bshum Connecting flight through Houston on the way up to Calgary, Alberta.
11:17 bshum I'm hoping they don't lose my luggage between countries.
11:17 Dyrcona bshum: Good luck!
11:18 bshum As an FYI, 2.7.0-RC is due today. I'll pull in any signed off bug fixes or ask folks to help push things for that throughout today.
11:19 bshum I'll poke at getting a tarball done later tonight when I get to more stable wifi.
11:20 csharp bshum: enjoyed seeing you too
11:20 csharp see you again in 2 weeks ;-)
11:20 eby__ joined #evergreen
11:24 jeff i am starting to reach the limits of what i can do for cataloging QA style reports with normalized values in mfr. now approaching XSLT-or-do-it-outside-the-DB stages.
11:27 * bshum found some free wifi, so will add a proper LP milestone for RC now
11:29 bmills joined #evergreen
11:32 eeevil jeff: display fields! :)
11:32 kmlussier We do have a small number of signed-off patches if there is any interest in getting those merged before RC - http://bit.ly/Yev82A
11:33 eeevil bshum: safe travels to the great, white tundra. and STOP WORKING ON VACATION ;)
11:34 csharp heh
11:34 jeff eeevil: thought of that, but i'm having a hard time justifying display fields for EVERYTHING :-)
11:34 jeff eeevil: but perhaps...
11:36 jihpringle joined #evergreen
11:37 bshum eeevil: Hehe, thanks :)
11:38 bshum I'll stop working soon enough, I hope.
11:39 bshum Or at least in the next couple minutes cause I have to board my flight.
11:39 bshum kmlussier++ # championing signed-off bugs (and signing off too)
11:43 * bshum disappears into line for his first flight.
11:46 ericar joined #evergreen
11:49 kmlussier yboston: At one point in the release do we see a 2.7 version of the docs?
11:50 yboston that is normally decide and done by Robert
11:50 yboston *decided
11:50 yboston though I am pretty sure he waited untilt here was a 2.7 git branch
11:51 kmlussier OK, I'll ask him if/when he pops in for the DIG meeting.
11:51 yboston I would send him an email in case he can't make it
11:51 kmlussier And that happens at full release time?
11:51 yboston not sure
11:55 kmlussier Yeah, I'll e-mail him if he doesn't make it. I'm just wondering because I wanted to create links from the Release Notes to the documentation for a new feature. We have docs for one new feature already, but I think I'll wait until we have the 2.7 docs before adding the link.
11:58 dbs makes sense to me to create the rel_2_7 branch at the same time that the RC comes out, but I guess that's up to bshum
12:00 jwoodard joined #evergreen
12:07 buzzy joined #evergreen
12:11 Griff`Ron joined #evergreen
12:12 Griff`Ron left #evergreen
12:13 kmlussier It's time for my daily call for OPW volunteers. gmcharlt has volunteered to be a mentor for the self-check and awesome box projects - http://wiki.evergreen-ils.org/doku.php?id=opw. But we would need a second mentor for each of those projects to move forward with them. Would anyone else be interested in volunteering to help with either of those projects?
12:13 kmlussier gmcharlt++
12:14 kmlussier dbs++ bshum++ - #volunteering earlier to co-mentor the mobile project.
12:16 rfrasur joined #evergreen
12:32 ericar_ joined #evergreen
12:40 ericar_ joined #evergreen
12:54 kbutler joined #evergreen
13:07 buzzy joined #evergreen
13:30 erick joined #evergreen
13:32 Guest59205 hello everyone
13:35 jeff greetings, erick! it looks like someone on the freenode irc network has already claimed that name, but you might be able to use something like this to go with another variant: /nick erick__
13:36 jeff in the meantime, you're showing up as Guest59205 :-)
13:36 rfrasur Hey there G and everyone else.
13:37 jeff rfrasur: good afternoon!
13:37 rfrasur :D
13:40 Guest59205 sorry is just I'm new in here
13:40 rfrasur G, no worries.  Are you Erick?
13:42 Guest59205 yes I'm
13:42 rfrasur Rock on.  I'll stop calling you G then ;)
13:42 * rfrasur is Ruth.
13:46 rsoulliere joined #evergreen
13:51 Guest59205 I'm working as a programmer in a library with evergreen, they have a requirement  the bug #1183872  "For our library it would be of great help to have the capability to add the patron's photo every time we register a new patron. Or add the image to the patron's profiled already on the system." my question  is if it's feasible to do it?, and there is anyone working on this? and what should I know to start working with that?,
13:51 pinesol_green Launchpad bug 1183872 in Evergreen "Add patron's photo at registry process" (affected: 6, heat: 30) [Wishlist,Triaged] https://launchpad.net/bugs/1183872
13:54 yboston heads up, the DIG monthly meeting starts at 2 Pm EST
13:55 kmlussier Guest59205: You might want to take a look at this thread: http://markmail.org/message/axvbryhjrqainpql
13:55 jihpringle joined #evergreen
13:59 Christineb joined #evergreen
14:00 yboston #startmeeting 2014-09-04 - DIG Monthly Meeting Evergreen Documentation Interest Group (DIG) Monthly Meeting
14:00 pinesol_green Meeting started Thu Sep  4 14:00:28 2014 US/Eastern.  The chair is yboston. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00 pinesol_green Useful Commands: #action #agreed #help #info #idea #link #topic.
14:00 pinesol_green The meeting name has been set to '2014_09_04___dig_monthly_meeting_evergreen_docu​mentation_interest_group__dig__monthly_meeting'
14:00 yboston The agenda can be found here http://evergreen-ils.org/dokuwiki/doku.php?i​d=evergreen-docs:dig_meeting_20140904-agenda
14:00 yboston #topic Introductions
14:00 yboston Please feel free to start introducing yourselves...
14:00 yboston #info yboston is Yamil Suarez @ Berklee college of Music - DIG meeting facilitator
14:01 rsoulliere #info rsoulliere is Robert Soulliere, Mohawk College
14:01 Guest59205 thanks kmlussier in fact I'm already done a separate application where I can upload the photo url to the system, but at the library asked me if there is a way that in the staff client can exist an option like this
14:01 kmlussier #info kmlussier is Kathy Lussier, MassLNC
14:01 kbutler #info kbutler is Kate Butler, Rodgers Memorial Library
14:01 rfrasur #info rfrasur is Ruth Frasur @ Hagerstown - Jefferson Township Library - Evergreen Indiana
14:01 remingtron_ joined #evergreen
14:02 jihpringle #info jihpringle is Jennifer Pringle, BC Libraries Cooperative
14:03 remingtron #info remingtron is Remington Steed, Hekman Library (Calvin College)
14:03 Christineb #info Christineb is Christine Burns, BC Libraries Cooperative
14:04 yboston will start with old topics / old actions first
14:04 yboston #topic past action items
14:04 yboston action: "remingtron will create a DIG long term goals wiki page and will include ideas for improving PDFs"
14:04 yboston that was done
14:05 yboston don't think we need discussion on it?
14:05 yboston http://evergreen-ils.org/dokuwiki​/doku.php?id=evergreen-docs:todo
14:06 yboston next one
14:06 yboston action: yboston will help kbutler with her 2.6 task "Add granular settings for requiring staff initials for notes. "
14:06 yboston tI did not reach out to Kate, will postpone
14:06 remingtron for the record, the specific section is "Non-docs tasks": http://evergreen-ils.org/dokuwiki/doku.php?​id=evergreen-docs:todo&amp;#non-docs_tasks
14:06 kbutler and I have not been around to be helped so. :)
14:06 yboston that worked out well
14:06 yboston :)
14:07 yboston #action yboston will help kbutler with her 2.6 task "Add granular settings for requiring staff initials for notes. "
14:07 yboston next one
14:07 yboston action: remingtron will ask for volunteers to help with documenting the new browser staff client on the general EG list
14:07 yboston I know he did, but don't htink he got feedback publicly
14:07 remingtron http://markmail.org/thread/ke5u3tbl62ghnajw
14:08 remingtron I haven't heard anything yet
14:08 yboston any direct feedback from anyone?
14:08 remingtron nope
14:08 jihpringle remingtron: is there a deadline when you'd like to see documentation done, ie. the circ module?
14:09 jihpringle I'd like to volunteer but turns out September is going to be a busy month for me
14:09 remingtron I'd love to see a preview version of the docs (aka. a draft) when the preview of the browser client is released with 2.7
14:09 remingtron so work would continue after that too
14:10 kmlussier I was wondering if it would be wortwhile to have a separate DIG hack-a-way day just to focus on web client documentation. Of course, it couldn't be done in time for the 2.7 release.
14:10 yboston I am open to a second event
14:10 yboston or if there is time during the upcoming one
14:11 kmlussier The nice thing about getting the documentation done early is that it also can serve as an opportunity to test functionality in the new web client.
14:11 yboston kmlussier: good point
14:11 jihpringle I'd be happy to work on it during the current hack-a-way or participate in a future specifc one
14:11 kmlussier yboston: I think doing both in one day would be ambitious.
14:12 yboston can't fault me for dreaming :)
14:12 kmlussier :)
14:13 remingtron I think sometime we should have a broader discussion about how our docs are used. I guess I'm having a mid-DIG crisis. "Does anybody even READ this stuff?" Getting Google Analytics on the docs would help, and any user feedback.
14:13 remingtron :)
14:13 rfrasur remingtron - are Google analytics already set up or is that something you'd like?
14:13 * rfrasur thinks that's a great idea, fwiw.
14:13 kmlussier remingtron: Oh, I think people read it. Analytics are good, but my sense is that the docs are used.
14:14 kbutler remingtron: you mean like those things they have on google and ms doc sites 'did this answer your question y/n' sort of stuff?  That might be helpful.
14:14 remingtron rsoulliere: we don't have Google analytics on the docs yet, right?
14:14 dbs Piwik is what we use for analytics on the core evergreen-ils.org web site
14:14 yboston dbs: thanks, good to know
14:15 dbs Please don't split the analytics streams :)
14:15 rsoulliere remingtron: I had set it up for tracking some pages...
14:15 remingtron kbutler: no, just page accesses and click tracking and such
14:15 rfrasur dbs - maybe rather than Google analytics...just analytics?
14:16 remingtron rfrasur: sure, any kind will do
14:16 kbutler remingtron: ahh ok. That's useful too.
14:16 dbs Ideally just one, though, so we can see patterns across the various evergreen properties
14:16 Stompro How possible would it be to add per page comments to the documentation like the Postgresql or php docs.  That moves the feedback extremly close to the source and removes a barrier to leaving feedback.
14:16 dbs e.g. "Are people going from the docs to one section of the wiki consistently? Maybe we should get that wiki page into the docs..."
14:17 dbs I hate the per page comments on the PHP docs.
14:17 yboston can we turn this into some action itmes? like putting a request through rsoulliere and maybe the EG web team for setting up analytics
14:17 dbs Speaking as someone who used to volunteer to moderate them.
14:17 rfrasur I do agree with kmlussier.  I know, anecdotally, that people are using them.  But some quantitative proof could only be helpful (right?).
14:18 dbs Our community would more likely be close to the PostgreSQL doc comment style (relatively quiet and low volume) though.
14:18 Stompro As someone just getting back into Evergreen, I've found the Official docs extremely useful.
14:18 _bott_ joined #evergreen
14:18 jihpringle would it be useful to send out something to the general list reminding everyone the docs are out there and guiding people new to EG to the docs?
14:18 dbs docs++
14:19 * dbs withdraws from the DIG meeting, sorry for interrupting
14:19 remingtron dbs++ #thanks for your perspective
14:19 yboston I think the docs have a good presence on the EG site. a big icon in the middle and a main menu item
14:20 yboston though, this train of dicsuion reminds of sending out a survey to solicit feedback
14:20 yboston *discussion
14:20 yboston never thought to ask how often peopel used the offical docs
14:20 remingtron rsoulliere: would you be able to work with the EG web admins (bshum?) to get piwik setup for the docs? I'm guessing it's similarly easy to Google analytics
14:21 yboston I do think they get used. I definetly use them all the time
14:21 remingtron probably just add a javascript to the template
14:21 rsoulliere yes, I was going to enquiry about the requirements for stting it up in the shared environment.
14:22 remingtron yboston: sounds like we have an action item for rsoulliere
14:22 * phasefx tends to link to the documentation when helping people, fwiw
14:22 yboston like  "rsoulliere: look into setting up analytics in offical docs site"
14:23 yboston (with better spelling)
14:23 yboston #action rsoulliere: look into setting up analytics in official docs site like on the main EG site
14:23 rsoulliere OK, will do.
14:24 remingtron phasefx: thanks for feedback!
14:24 yboston back on the topic of new staff browser and volunteers, anything else ebfore I move on to the next old action item?
14:24 yboston or we can keep the current dicsusion running
14:25 remingtron (sorry to derail the topic)
14:25 kmlussier Do we want to schedule an event or should we wait to hear if remingtron gets more feedback?
14:26 yboston alternatively, do we want to see how the hack-a-way goes to see if we find new volunteers that might want to help witht he new client docs?
14:26 remingtron let's revisit the browser client docs at next meeting. 2.7 features are more important at this point, and I'll report mid month about any feedback.
14:26 kmlussier Sounds like a good approach to me.
14:26 remingtron or...I'll report pre-dig-hackaway
14:26 yboston me too, good idea
14:27 yboston #action remingtron revisit the browser client docs at next DIG meeting or earlier
14:27 remingtron great
14:27 yboston btw, I like the discussion that we drifted to
14:27 yboston next action item
14:27 yboston action: yboston start a thread on DIG mailing list on targeting small older docuemntation tasks for the month of August; like working on 1 to 3 features from the 2.5 list between now and the next meeting?
14:28 yboston no work done :( postponed
14:28 yboston #action yboston start a thread on DIG mailing list on targeting small older docuemntation tasks for the month of September; like working on 1 to 3 features from the 2.5 list between now and the next meeting?
14:28 yboston next one
14:28 yboston action: kmlussier(and others) identify 2.7 doc needs and add to the 2.7 wiki page
14:28 yboston thanks for doing this Kathy
14:29 yboston #link http://evergreen-ils.org/dokuwiki/d​oku.php?id=evergreen-docs:2.7_needs
14:29 yboston any comments or updates?
14:29 kmlussier We need lots of help with the 2.7 docs, so feel free to sign up for something!
14:31 yboston I hope we put a big dent at the hack-a-way
14:31 yboston on this list
14:31 buzzy joined #evergreen
14:31 yboston BTW, the remaining old action items have been taken care of, thanks to jihpringle sending out the doodle poll for the hack-a-way
14:31 remingtron for the record, the goal is to have all new 2.7 features documented by Sept 18 (expected 2.7 launch day)
14:32 kmlussier Some of the tasks, like the switch to XLSX or the change in holds shelf expire date, probably only require small changes in existing docs.
14:32 yboston nice, should we label does as bitesize?
14:32 remingtron yes, good idea
14:32 kmlussier Sure, I can do that.
14:33 remingtron maybe even link to the github file from the todo list
14:33 yboston remingtron: cool
14:33 remingtron at least for bitesize ones
14:33 yboston kathy can I put you done for that or are you already doing it?
14:34 yboston :)
14:34 kmlussier I added the bitesize label already.
14:34 yboston also, at this point we can start with new action items; I would like to jump to talk about the DIG hack-a-way, but we can start with another new item like
14:34 yboston Potential DIG Outreach Program for Women projects (Kathy)
14:34 yboston kmlussier: thanks!
14:35 kmlussier I can revisit a little later for the github links.
14:35 kmlussier yboston: do you need to do a #topic for that?
14:36 yboston I was just mentioning a potential next topic, not starting it, but I can start with that one then switch to the hack-a-way
14:36 kmlussier Oh, sorry. Misunderstood. :)
14:36 yboston lets do the kathy item first,then switch to hack-a-way
14:37 yboston #action Potential DIG Outreach Program for Women projects (Kathy)
14:37 yboston sorry
14:37 yboston #topic Potential DIG Outreach Program for Women projects (Kathy)
14:37 kmlussier I sent out an e-mail to the list on this: http://markmail.org/message/ecnsuuets32glrve
14:38 kmlussier #link http://wiki.evergreen-ils.org/doku.php?id=opw
14:38 kmlussier I thought of two potential DIG-related projected for this program. I wanted to hear if others thought either of these projects would be worthwhile.
14:39 kmlussier Or if you think there are some other documentation projects that could be added to the list.
14:39 kmlussier And, also, if you think a project is worthwhile, if anyone has the time/interest in volunteering to mentor the intern who would work on the project.
14:39 yboston I like what you listed, can't think of aything else tight now but I am sure I will think of soemthing
14:40 kbutler kmlussier: I really liked the idea of updating the style/functionality of the docs with things like the extra links at the top.
14:40 yboston I will put myself down as a mentor for both docs related item
14:40 yboston items
14:40 kmlussier I have to say I wasn't as excited about the web client documentation because a part of me thinks it might be better to have it done by people more familiar with the software.
14:40 kmlussier But it is a big job that needs to be done.
14:40 kmlussier yboston++
14:41 remingtron kmlussier: I'd add docs usability improvements to the revamp idea
14:41 remingtron (analytics, getting user feedback, considering ways to integrate the docs or links to them in the software)
14:41 kmlussier remingtron: Thanks, I all that. I think that's part of what I was getting it, but didn't clearly state.
14:41 kmlussier /s/all/add
14:42 kmlussier Typos. :P
14:42 remingtron kmlussier: yeah, same idea as what you already had down
14:42 yboston BTW, we are at the 42 minute mark, nervous that we will run out of time to talk about hack-a-way, though we may be fine
14:43 kmlussier As long as everyone things these are good idea, then I'll go with it. If we don't get a 2nd mentor for the web client docs by tomorrow, I'll probably remove it from the list.
14:43 kmlussier But I think I'm okay with focusing on the other one too.
14:44 remingtron yeah, I think the revamp is the better project for an intern
14:44 yboston May I switch to talking about hack-a-way?
14:45 kmlussier yboston: Go for it!
14:45 yboston #topic DIG hack-a-way planing
14:45 yboston kmlussier asked around for votes on where to have the Massachusetts one, and people were TOO flexible
14:46 yboston kmlussier: what would you like to do?
14:46 kmlussier kbutler showed a slight preference for Worcester.
14:46 yboston I wonder if Worcester, MA will lead to more volunteers
14:46 yboston specially first time ones
14:46 kmlussier I don't know if bshum or mceraso have a preference.
14:46 remingtron I'm remote from Michigan
14:47 kmlussier remingtron: You don't want to drive down to Worcester? ;)
14:47 bshum kmlussier: Worcester is fine.  (spells it right, but can't pronounce it for his life...)
14:47 yboston BTW, chime in those that are planning to join in remotely
14:47 * mceraso agrees with bshum (even about the spelling)
14:47 jihpringle I'm planning to join remotely
14:47 yboston (wooster)
14:47 remingtron bshum: W....ster
14:48 kmlussier bshum: WŎŎS-tah
14:48 kbutler I'm fine with Worcester.
14:48 kmlussier yboston: You forgot to drop the "r"
14:48 yboston woostaah
14:49 yboston So lets do Worcester
14:49 kmlussier OK, I'll let tspindler know.
14:50 tspindler kmlussier, just happened to look and see this
14:50 yboston can I get a volunteer to collect the Google hangout compatible email address to set up a hang out?
14:50 yboston actually, I could do that since I am not hosting :)
14:51 yboston #action yboston collect the Google hangout compatible email address to set up a hang out
14:51 yboston #action (all DIG members) send yboston your Google hangout compatible email address for the DIG hack-a-way hangout
14:52 yboston in terms of goals, I think we are pretty clear on focusing on new 2.7 features.
14:52 yboston any other issues to bring up today?
14:52 jihpringle we settled on the day but did we ever talked about start and end times?
14:52 yboston (we have 8 minutes)
14:53 remingtron I can probably only join for the morning
14:53 yboston from expereince, I always needed until 9:30 AM EST to be set up with a hangout at the earliest
14:53 kmlussier 9:30 works for me, but may be a little early for jihpringle. :)
14:54 yboston so for ending time?
14:54 kmlussier But maybe people can join in as they start their workday.
14:54 yboston usually we end aorund 5 PM EST
14:55 yboston what are the food options in Worcester?
14:55 kmlussier I'll talk to to the C/W MARS folks about it. There are places we can go, but it might be easier to call something in.
14:55 jihpringle I won't be around at 9:30am EST but I'll try to be around by 10:30/11am
14:56 kmlussier There's nothing we can really walk to.
14:56 yboston kmlussier: can you send out ifnormation like the street adress, room number?
14:56 kmlussier Yes, I can do that.
14:57 yboston #action kmlussier will send out information on the Worcester, MA venue
14:58 yboston not sure if you want those that will attend to send you their email or sending on the DIG list?
14:59 yboston any final thoughts. comments, questions?
14:59 yboston (we are reaching the 1 hours mark, but I can keep going)
14:59 kmlussier It would be good if people could just contact me directly if they're planning to go to Worcester. So that we know how many people to plan for. But i'll include that info in the e-mail I send out.
15:00 yboston BTW, I am extremely excited to have a set set of goals for the hack-a-way
15:00 yboston anything else for now?
15:00 remingtron I'm excited that we're being more on-time for releases
15:00 remingtron hack-a-way++
15:01 yboston remingtron++ you helped a lot with that
15:01 yboston OK folks will shut down now
15:01 kmlussier remingtron++ indeed
15:01 yboston #endmeeting
15:01 pinesol_green Meeting ended Thu Sep  4 15:01:17 2014 US/Eastern.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
15:01 pinesol_green Minutes:        http://evergreen-ils.org/meetings/evergr​een/2014/evergreen.2014-09-04-14.00.html
15:01 pinesol_green Minutes (text): http://evergreen-ils.org/meetings/evergr​een/2014/evergreen.2014-09-04-14.00.txt
15:01 pinesol_green Log:            http://evergreen-ils.org/meetings/evergree​n/2014/evergreen.2014-09-04-14.00.log.html
15:01 rfrasur yboston++
15:01 rfrasur kmlussier++
15:01 rfrasur remingtron++
15:01 mnsri joined #evergreen
15:01 rfrasur peace be unto y'all
15:02 remingtron yboston++ #fearless leader
15:02 kbutler yboston++
15:03 rsoulliere joined #evergreen
15:23 Stompro Is there a trick to getting changes to menu.js in chrome/content/main/ in the staff client to take effect?  I've made a few changes but I cannot see any effect in the client behavior.
15:25 phasefx Stompro: you're editing locally?  I think that stuff gets compiled into other files, but those should get invalidated when you change the source
15:27 Stompro Yes, trying to edit locally.
15:27 phasefx I added alert('foo'); to main.js and it worked for me
15:28 phasefx adding <button label="foo"/> to main.xul also worked
15:28 phasefx Stompro: do you have something like deep freeze running?
15:30 jeff deep free undoes changes at reboot.
15:30 Stompro Phasefx: no, nothing like that running.
15:30 remingtron Stompro: another thought, I've found that some client files have copies on the server, and that has confused me about which one to edit sometimes
15:30 jeff but Windows vista and up will happy confuse things if you try to edit some files in some ways. :P
15:31 phasefx Stompro: try creating a different profile with -profileManager
15:31 jeff remingtron: good point, though in this case i think phasefx's test local edit confirmed that the file in question should be local and not server-sourced
15:31 jeff Stompro: what is the full path to the file on disk that you are editing, and what's the local OS?
15:32 Stompro phasefx: when you said "main.js" did you mean "menu.js" ?
15:32 phasefx Stompro: no, I tried main.js so I wouldn't have to bother logging in
15:32 jeff oh hey.
15:32 phasefx I think xpti.dat might cache some stuff, but it should be recreated with each profile
15:33 Stompro Jeff: Win7 pro 64 - path:C:\Program Files (x86)\Evergreen Staff Client 2.6\chrome\content\main
15:33 Stompro Jeff: +\menu.js
15:33 jeff well, i can confirm that menu.js isn't a file served up under /xul on the web server -- so that helps a bit. :-)
15:33 dbwells_ joined #evergreen
15:36 Stompro Phasefx: Where are the evergreen client profiles stored?  ProgramData, local windows profile folde?
15:36 phasefx Stompro: if you start up the client with -console, it'll print out the path.  Mine is something like C:\Users\phasefx\AppData\Roaming\Ope​nILS\open_ils_staff_client\Profiles
15:37 phasefx Stompro: as an aside, the client can be configured to use the program folder for this, but it doesn't out of the box
15:38 pinesol_green [evergreen|Remington Steed] Docs: Fix filenames to match references in the docs - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=703a9b0>
15:39 ldw joined #evergreen
15:39 Stompro Phasefx: Thanks, mine is in the same location, I'll try creating a new profile.
15:40 jeff keep in mind that cache files are not stored there.
15:40 jeff cached can be found in %LOCALAPPDATA%\OpenILS
15:41 phasefx hrmm.. I don't see anything useful there, but I do see xpti.dat and compreg.dat in the other place
15:41 Stompro Jeff, thanks, deleting the local appdata cache did the trick without having to create a new profile.
15:42 phasefx I do wonder why that was needed.  Windows <shudder> :)
15:42 Stompro Thanks for all the assitance.
15:42 jeff i wonder if a "clear cache" in the client would have been equally as successful.
15:43 phasefx doh
15:43 Stompro Jeff: I did try that but it didn't help.
15:44 jeff and now i can't determine how to reproduce the Windows behavior that I've seen in the past where it permits you as a non-admin to write to certain locations, but it's actually lying and it's a fake copy of the location, specific to your user.
15:44 RoganH joined #evergreen
15:46 Stompro I had to run notepad++ as administrator before I could save over the chrome files because of the default permissions, even though I'm in the administrator group.  I guess more security is good.
15:51 jeff the "feature" of Windows that I was trying to describe earlier appears to be known as UAC file and registry virtualization. %LOCALAPPDATA%\VirtualStore and HKCU\Software\Classes\VirtualStore
15:51 jeff I doubt it came into play here, but I've had it bite me before with other software.
15:52 jeff The fun part is when one app uses Windows APIs that support UAC Virtualization, and another app does not. They both get a different view of the same directory.
15:55 jeff or to be more accurate, when one Windows application behaves in a manner that causes Windows to enable virtualization for it... and the other does not.
16:00 _bott_ joined #evergreen
16:13 Stompro If I make changes to "./Open-ILS/xul/staff_client/chrom​e/locale/en-US/offline.properties" do I need to worry about other locales?  It doesn't look like there are any other localized versions of offline.properties in the source though.
16:26 tsbere Stompro: I believe there are tools that pull from the en-US files to make the templates for the other languages. I am not an expert on the process, though.
16:27 eeevil Stompro: other translations are part of the packaging process for release tarballs
16:27 eeevil Stompro: so, if you're using a git checkout, you'll have only en-us (unless you do the translation dance yourself, which you can do)
16:32 Stompro eeevil: So is there a translation team that looks for new items/strings that need to be translated before release?
16:33 eeevil Stompro: translations are managed using the launchpad tool. we grab whatever translations exist for the current strings and runs some scripts to generate DTDs, .properties files, and the like
16:35 Stompro eeevil: Ok, thanks for the info.  I'll just assume that someone else will fix it up down the line then, if my change makes it in.
16:39 tspindler left #evergreen
16:41 Christineb left #evergreen
17:06 wsmoak joined #evergreen
17:06 wsmoak joined #evergreen
17:09 mdriscoll left #evergreen
17:12 mmorgan left #evergreen
17:24 pinesol_green Incoming from qatests: Test Failure - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
20:03 kmlussier joined #evergreen
20:34 kmlussier joined #evergreen
21:00 jeff phasefx: live test failure looks like another race condition -- what do you think?
21:01 phasefx jeff: yeah, I think so, but no insight or tuits for fixing it
21:03 jeff is there any way to allow for on-demand re-run of the tests by some folk, either via web or ssh?
21:03 buzzy joined #evergreen
21:07 phasefx jeff: not conceptually difficult, but some work is needed; my main concern is that we're using ganeti for it, and multiple folks can't do things concurrently with that.  That said, virtualbox works fine with these tools :)
21:09 phasefx maybe it's time to work in support for multiple drones, or fold it into buildbot somehow
21:10 jeff i was just thinking "enable someone to trigger a sooner-than-in-12-hours re-run"
21:10 jeff not "multiple concurrent test runs / testing different branches / etc"
21:10 jeff that might have been unclear, or i might have misunderstood your answer. :-)
21:11 phasefx we can cron it more frequently; my concern with concurrency is with us doing ganeti-stuff with other vm's at the same time
21:11 phasefx I'm not a ganeti guru though
21:12 jeff ah
21:13 phasefx I have a home server running all the time; could set up a separate and more frequent track there.  No risk of tripping over anyone there
21:14 phasefx another option is to get less pristine with blowing away EG between runs.. and say, not restore from a vm snapshot.  Not a huge fan of that
22:17 kmlussier joined #evergreen

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