15:00:09 <jventuro> #startmeeting 2013-07-30 Evergreen Reports Interest Group
15:00:09 <pinesol_green> Meeting started Tue Jul 30 15:00:09 2013 US/Eastern.  The chair is jventuro. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:09 <pinesol_green> Useful Commands: #action #agreed #help #info #idea #link #topic.
15:00:09 <pinesol_green> The meeting name has been set to '2013_07_30_evergreen_reports_interest_group'
15:00:40 <jventuro> Hi there!  We'll start with introductions as usual.
15:00:55 * jventuro is Jessica Venturo, Bibliomation
15:01:05 * chtrotter is Cristina Trotter, Oconee Regional Library System (PINES)
15:01:18 <jventuro> Please introduce yourself if you're participating (don't be shy!)
15:02:36 <JennB> Hello reports!
15:02:50 * gsams is Geoff Sams, North Texas Library Consortium
15:02:52 <jventuro> Hello JennB!
15:03:01 <gsams> I'll just be listening in as it were
15:03:16 <gsams> I'm trying to become more involved
15:03:20 <jventuro> No problem gsams.  Welcome :)
15:04:04 <chtrotter> Hi, JennB and gsams!
15:04:31 <jventuro> Is this our whole crew today?
15:05:15 <chtrotter> Lots of folks have been joining the chat. Anyone else here for the Reports Meeting? We are doing intros now.
15:06:21 <dagreen> * dagreen is David Green, NC Cardinal (State Library of North Carolina) here to listen in and become more involved, just like gsams
15:06:39 <JennB> Im here for reports. Whee!
15:06:54 <jventuro> Welcome dagreen
15:06:55 <annag> I'm here for the RIG meeting too
15:07:34 <chtrotter> Hi annag and dagreen!
15:08:31 <jventuro> Welcome, all.  I'll give everyone a minute to look over the notes from the conference: http://open-ils.org/dokuwiki/doku.php?id=evergreen-reports:meetings:2013-04-10
15:08:59 <jventuro> Let me know if you have any corrections, additions, questions, etc.
15:09:49 <chtrotter> Real quick: I don't know if some of y'all are just new to RIG, or IRC chat altogether, but I know when I first joined RIG I was clueless about IRC chatting. I found this site helpful: http://www.ircbeginner.com/ircinfo/ircc-commands.html
15:10:52 <chtrotter> The notes look good to me...based on what I could hear via Skype.
15:11:07 <dagreen> Much appreciated on the IRC info, chtrotter. Thank you.
15:11:28 <jventuro> That's a great resource.  chtrotter++
15:13:12 <jventuro> if nobody has any further comments about the notes, I'll get started with the first item in old business, sort of an extension of the conversation we had at the conference.
15:13:50 * csharp is Chris Sharp, GPLS - late, but mostly present
15:14:22 <jventuro> Hi csharp!
15:15:07 <jventuro> OK, first #topic Reworking the Wish List
15:16:09 <jventuro> For the newbies and those who need a reminder, the current wish list can be found here: http://open-ils.org/dokuwiki/doku.php?id=evergreen-reports:rig_wish_lists
15:16:44 <jventuro> It hasn't been updated since 2011, and needs some attention.
15:17:39 <jventuro> I have an idea about how this might work that I'd like to run past the group, and if anyone else has any ideas as we discuss, feel free to share those also.
15:18:50 <jventuro> I thought it might be a good idea to start fresh and ask for ideas for wish list items on the evergreen-reports email list
15:19:39 <jventuro> I would really like for us to track who and where the ideas came from on the wiki so we can follow up
15:19:59 * csharp can help create requested templates
15:20:53 <jventuro> csharp++  I was just going to ask if anyone would like to volunteer to help build templates!
15:21:37 <csharp> happy to
15:22:43 <chtrotter> I like the idea of tracking them on the wiki, too.  I think some of the items that require development or fixes can added to launchpad (such as the desire to share templates), but help on templates in general would be better off on the wiki, I think.
15:24:10 <chtrotter> Does anyone know Brian Feifarek? I see that he noted a couple of wishlist items as "in progress." Maybe we could get an update?
15:24:35 <csharp> I believe he was working with LBA under the IMLS grant
15:24:50 <csharp> so I don't know if he's around much anymore
15:26:03 <jventuro> Do you think it might be a good idea to list names and contact info of whoever is building the template too to avoid such things in the future?  Similar to what DIG does?
15:26:33 <csharp> yeah
15:26:51 <csharp> it would also be good to know contact info for the requestors as well
15:27:07 <csharp> the ones listed there are actually too vague to act on
15:27:14 <chtrotter> Agreed.
15:27:29 <jventuro> Agreed.  That's why I was thinking we could just start fresh.
15:27:31 <csharp> or at least, they are wide open to (mis)interpretation ;-)
15:28:02 <csharp> so whoever's requesting needs to be specific about what they want to see and how they need it filtered
15:29:22 <jventuro> Yes.  I will mention that in the message I send out on the list.
15:30:08 <jventuro> And if we have their contact info, we can get clarification if needed.
15:32:02 <chtrotter> Sounds good to me!
15:32:07 <jventuro> Any other ideas on how we can make this work?
15:34:17 <chtrotter> Well, I would be sure to add request date info and a column for a link to the template instructions. We might need to categorize the wishlist items, since some are template-specific, while others are development ideas.
15:35:20 <jventuro> Good idea.
15:36:08 <csharp> probably also a good idea for requestors to include their EG version, since that may be a factor in template portability
15:36:30 <jventuro> Good call!
15:37:16 <jventuro> Do you guys think this should be a survey instead of an email request?
15:38:36 <jventuro> I like the idea of a survey because it separates out the questions, but I'm afraid it might make some folks hesitant to respond.
15:39:03 <dagreen> Maybe we could ask requesters to send a dummy Excel output? Some of our users are better at describing their needs in that fashion.
15:41:57 <chtrotter> I think it is definitely worth suggesting to requesters, if they find it easier to explain their needs.  The survey sounds like an extra step. I was going to ask how we were going to handle email requests. I was thinking that some email requests get such a quick response it is not worth adding to the wishlist, but if there is no answer after a week or so, we could add it to the wishlist. What do y'all think?
15:42:55 <jventuro> I think that's a good idea.
15:45:06 <chtrotter> Alrightee. So here comes the next question: Who wants to be the lucky person to keep track of the email list for possible wishlist additions?
15:45:19 <jventuro> I was wondering the same thing about email requests.  Should I have requesters respond to the list, or directly to me.
15:46:22 <jventuro> I have no problem with doing that, chtrotter.  I am the list admin :)
15:46:56 <AaronZ-PLS> Looking for an action trigger hook to send a test email every day, is there one that would work?
15:47:59 <jventuro> Hi AaronZ-PLS.  We're having a meeting at the moment.  Would you mind tabling your question for 15 minutes or so?
15:48:58 <AaronZ-PLS> Willdo.
15:49:03 <jventuro> Thanks!
15:49:36 <chtrotter> I would continue to encourage them to be sent to the list first, since there might be a quick response from the community.
15:51:13 * chtrotter has to run for just a minute. Patron needs help. BRB.
15:52:15 <jventuro> OK.  In that case #action Jessica will ask Evergreen-reports list subscribers to send Wish List items and template help requests directly to the reports email list.
15:53:16 <jventuro> So I guess anyone who'd like to help with building the templates can just monitor the reports list?
15:53:35 <csharp> yep
15:54:01 <jventuro> Awesome.
15:54:18 <JennB> Sounds good. The list works for me!
15:55:29 <jventuro> And anything that doesn't get snagged in a period of time can go up on the wiki.
15:55:46 <jventuro> What do we want to set for the time limit?
15:56:45 <JennB> for submitting a report?
15:57:13 <chtrotter> I would say a week or two.
15:58:34 <jventuro> I was thinking the time limit would be how long they go unanswered before they get put on the wiki page, but that's a good point.  Should there be a limit to how long folks can submit ideas?
15:58:42 <csharp> well, I think the onus should probably be on the submitter for following up - "no one answered me on the email list, so I'll put this on the wiki"
16:00:30 <kbutler> I think they'd be more likely to go up if someone(s) in particular were responsible for putting them on the wiki.
16:01:32 <jventuro> I agree with kbutler
16:01:34 * csharp has got to run but will read the scrollback/log
16:02:34 <jventuro> I would certainly encourage folks to post on the wiki, but some things might get lost
16:02:39 <chtrotter> I agree. I think there are many folks who are reluctant to edit the wiki.
16:03:17 <chtrotter> What do you think about sending a blurb out to both lists every once in a while about the new items on the wishlist? Hopefully this will lure in more folks to work on wishlist items.
16:03:37 <jventuro> I think that's a great idea.
16:03:58 <jventuro> How often should that happen?
16:04:27 <chtrotter> Maybe monthly? Or at least with every reminder about the next RIG meeting.
16:05:50 <jventuro> I think monthly is a bit too often.  I was thinking quarterly or twice a year.
16:07:13 <kbutler> With the meeting reminders might be good.  But it might depend on the volume of items. If there are hardly any then it would not make sense to do it frequently.
16:07:51 <jventuro> I can try certainly try sending it out with meeting reminders to see how it goes.
16:08:11 <jventuro> I have a feeling we will see diminishing returns after a while.
16:09:17 <chtrotter> Have we determined how long they should be on the list before adding to the wiki?
16:09:33 <jventuro> 2 weeks?
16:09:57 <chtrotter> Sounds good to me.
16:10:13 <jventuro> Very good.
16:11:04 <kbutler> Sounds good.
16:11:43 <jventuro> #action Jessica will monitor requests and add items that have not been answered within 2 weeks to the wiki.
16:12:05 <jventuro> We're way over time.  Any more to say on this topic?
16:12:30 <chtrotter> No more from me. I gotta run soon.
16:13:12 <jventuro> OK, anything else to bring up before we adjourn?
16:13:26 <jventuro> I think the rest of the agenda can be tabled until the next meeting.
16:14:44 <chtrotter> Sounds good to me. No real news on the PINES development. We are working out  the requirements.
16:15:15 <jventuro> OK, then.  Thanks for coming everybody!
16:15:31 <chtrotter> jventuro++
16:15:36 <chtrotter> Bye, y'all!
16:16:17 <jventuro> #endmeeting