Most welcome--please post back your results if you find anything you're
happy with.

Chris


On Thu, Mar 6, 2014 at 10:30 AM, Collie, Aaron <[log in to unmask]>wrote:

> Yes, we do use DeskTracker for reference stats, but I would say this is
> more of a "what actually happened" rather than a "what didn't happen, but
> could have, and here is a tally mark for it."
>
> Certainly possible with the system we have, I'm just thinking a more
> generally.
>
> Thanks for the thoughts, Chris.
>
> -Aaron
> ________________________________________
> From: Code for Libraries [[log in to unmask]] on behalf of Chris
> Strauber [[log in to unmask]]
> Sent: Thursday, March 06, 2014 10:20 AM
> To: [log in to unmask]
> Subject: Re: [CODE4LIB] Tallying needs
>
> We've used our LibAnswers (reference and service desk) and LibAnalytics
> (instruction) data to inform our website redesign process in pretty much
> exactly that way. I did it pretty roughly, with spreadsheets and some
> by-hand analysis, but the data would also be pretty susceptible to
> scripting for a school or library with more transactions. Your reference
> and instruction folk are probably keeping internal stats in some form you
> could use for that.
>
> Chris Strauber
> Instructional Design Coordinator
> Tisch Library, Tufts University
> [log in to unmask]
> @cstrauber
>
>
> On Thu, Mar 6, 2014 at 9:54 AM, Collie, Aaron <[log in to unmask]
> >wrote:
>
> > Hello,
> >
> > Pardon my ignorance here, but we were discussing use cases and user
> > stories and noting how static they are (in our implementation of them)
> for
> > capturing user needs for more general library services. Im my experience,
> > there is one story per need, and additional expressions of that
> particular
> > need don't really get "counted" to assist with prioritization.
> >
> > I'm curious if anyone has used any sort of ticketing system for a more
> > traditional library function like reference or instruction that might
> > "tally" expressions of need (e.g. we've heard a request for an NVIVO
> course
> > 4 times in the last semester). Maybe something like Agile or Kanban
> already
> > account for accumulation of stories or prioritization based on stats, and
> > I'm just not aware of it?
> >
> > -Aaron
> >
> >
> > W. Aaron Collie
> > Digital Curation Librarian
> > MSU Libraries
> > tel: 517.884.0867 email: [log in to unmask]
> > tweet: aaroncollie site: http://staff.lib.msu.edu/collie/
> >
>