U. Huddersfield's Library Impact Data Project also comes to mind:
I know they looked at circulation data pretty extensively and did indeed
make some "if you're looking at X, you may be interested in Y" type
California College of the Arts
On Tue, Jun 17, 2014 at 8:35 AM, Blake, Tom <[log in to unmask]> wrote:
> Harvard's Innovation Lab at their law library was working with this type
> of data, I believe...
> Try reaching out to them directly:
> Tom Blake
> Digital Projects Manager
> Boston Public Library
> 700 Boylston St.
> Boston, MA 02116
> 617 859-2039
> Free To All
> -----Original Message-----
> From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of
> Tom Cramer
> Sent: Tuesday, June 17, 2014 11:27 AM
> To: [log in to unmask]
> Subject: Re: [CODE4LIB] best practices for keeping / using library circ
> This email provoked zero responses on list. Was my timing off, is it a
> poorly framed question, or are people just not doing much in this realm?
> (By resending, I'm controlling for the timing factor...)
> - Tom
> On Jun 7, 2014, at 3:20 AM, Tom Cramer wrote:
> > I'm looking for best practices for keeping and using library usage
> data--real life examples of libraries gathering and using things like
> circulation data or e-resource traffic statistics to inform service and
> strategy decisions while safeguarding patron privacy.
> > I'm less interested in operational logging for security / authorization
> purposes, and more interested in things like gathering data to make
> recommendations (people who checked this out also checked this out...),
> collection management / licensing / deaccessioning decisions, or overall
> library / collection usage reporting--especially if the data are tracked
> and used at more than a gross level (i.e., faculty v. graduate v. undergrad
> > What usage data do you keep that may be correlated to patron identity?
> > How do you use it?
> > What do you do to anonymize / aggregate / cleanse / protect patron
> > Does anyone have an approach that they regard as state of the art? Or
> pointers to previous work done in this space?
> > Thanks in advance,
> > - Tom