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/
>