Re: [CODE4LIB] Tallying needs
Hi Ranti, We mostly used the data as part of our content audit, seeing what we needed to add/remove/collect together in one place on the new site. Sometimes five questions was enough, depending on the content, but usually I grouped them into larger categories if I could. Do you have NVIVO? three times plus Where can I find STATA? nine times plus a couple questions about SPSS told us we needed a page explaining what software we had on all of our computers. (yeah, yeah, I know we should have had it already). For printing it was hundreds of questions about jams, and color printing, and large-format printing. The process essentially consisted of me marking up and sorting spreadsheets; a larger school might want to automate that Does that answer your question? Chris Strauber On Thu, Mar 6, 2014 at 5:21 PM, Ranti Junus ranti.ju...@gmail.com wrote: Hi Chris, I'm curious about your analysis re. when the data would start influencing the redesign process. E.g does 5 queries about a certain topic enough to warrant the redesign, etc. Mind elaborate that a bit? thanks, ranti. On Thu, Mar 6, 2014 at 1:53 PM, Chris Strauber cstrau...@gmail.com wrote: 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 col...@mail.lib.msu.edu 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 [CODE4LIB@LISTSERV.ND.EDU] on behalf of Chris Strauber [cstrau...@gmail.com] Sent: Thursday, March 06, 2014 10:20 AM To: CODE4LIB@LISTSERV.ND.EDU 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 chris.strau...@tufts.edu @cstrauber On Thu, Mar 6, 2014 at 9:54 AM, Collie, Aaron col...@mail.lib.msu.edu 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: col...@msu.edu tweet: aaroncollie site: http://staff.lib.msu.edu/collie/ -- Bulk mail. Postage paid.
Re: [CODE4LIB] Tallying needs
Aaron, In JIRA and a few other systems, there is a vote feature. If used with an agile schema, it seems to me that you could use it to tally the number of times an unaddressed story might address a real instance of a user need. We do something else though. We use different projects (in JIRA) to track different forms of contacts / needs for some of our projects that have high patron support / patron contacts. One queue is used to track support requests and feedbacks; these then spawn the creation of a new ticket in an engineering queue for work (stories, bug fixes, technical tasks) to be done by the dev team. If a new patron feedback comes in that is already represented by a story (or bug) in the dev queue, we link them. Dev tickets that link to multiple customer feedback tickets essentially have multiple votes. In addition to help weighting the stories, this approach also lets us 1) keep track of testing and acceptance criteria (i.e., did we actually address the original request from a patron), and 2.) contact patrons / issue submitters after we release a feature or bug fix, to let them know our most recent release addresses their issue (sometimes months or years after the fact). HTH, - Tom On Mar 6, 2014, at 6:54 AM, Collie, Aaron 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: col...@msu.edu tweet: aaroncollie site: http://staff.lib.msu.edu/collie/
[CODE4LIB] Tallying needs
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: col...@msu.edu tweet: aaroncollie site: http://staff.lib.msu.edu/collie/
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 chris.strau...@tufts.edu @cstrauber On Thu, Mar 6, 2014 at 9:54 AM, Collie, Aaron col...@mail.lib.msu.eduwrote: 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: col...@msu.edu tweet: aaroncollie site: http://staff.lib.msu.edu/collie/
Re: [CODE4LIB] Tallying needs
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 [CODE4LIB@LISTSERV.ND.EDU] on behalf of Chris Strauber [cstrau...@gmail.com] Sent: Thursday, March 06, 2014 10:20 AM To: CODE4LIB@LISTSERV.ND.EDU 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 chris.strau...@tufts.edu @cstrauber On Thu, Mar 6, 2014 at 9:54 AM, Collie, Aaron col...@mail.lib.msu.eduwrote: 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: col...@msu.edu tweet: aaroncollie site: http://staff.lib.msu.edu/collie/
Re: [CODE4LIB] Tallying needs
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 col...@mail.lib.msu.eduwrote: 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 [CODE4LIB@LISTSERV.ND.EDU] on behalf of Chris Strauber [cstrau...@gmail.com] Sent: Thursday, March 06, 2014 10:20 AM To: CODE4LIB@LISTSERV.ND.EDU 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 chris.strau...@tufts.edu @cstrauber On Thu, Mar 6, 2014 at 9:54 AM, Collie, Aaron col...@mail.lib.msu.edu 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: col...@msu.edu tweet: aaroncollie site: http://staff.lib.msu.edu/collie/
Re: [CODE4LIB] Tallying needs
Hi Chris, I'm curious about your analysis re. when the data would start influencing the redesign process. E.g does 5 queries about a certain topic enough to warrant the redesign, etc. Mind elaborate that a bit? thanks, ranti. On Thu, Mar 6, 2014 at 1:53 PM, Chris Strauber cstrau...@gmail.com wrote: 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 col...@mail.lib.msu.edu 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 [CODE4LIB@LISTSERV.ND.EDU] on behalf of Chris Strauber [cstrau...@gmail.com] Sent: Thursday, March 06, 2014 10:20 AM To: CODE4LIB@LISTSERV.ND.EDU 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 chris.strau...@tufts.edu @cstrauber On Thu, Mar 6, 2014 at 9:54 AM, Collie, Aaron col...@mail.lib.msu.edu 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: col...@msu.edu tweet: aaroncollie site: http://staff.lib.msu.edu/collie/ -- Bulk mail. Postage paid.
