In a digital environment our actions shed data which can be collected and mined. We leave traces. In this context it is not surprising that 'analytics' has emerged as a central interest. 'Analytics' is often used to refer to how organizations analyse the data they collect to improve decisions or performance.

This extends to the academic arena, and data from academic support systems is now being collected and mined to identify and act on issues:

With the increased concern for accountability, academic analytics has the potential to create actionable intelligence to improve teaching, learning, and student success. Traditionally academic systems—such as course management systems, student response systems, and similar tools—have generated a wide array of data that may relate to student effort and success. Early academic analytics initiatives are seeking to predict which students are in academic difficulty, allowing faculty and advisors to customize learning paths or provide instruction tailored to specific learning needs. [Academic Analytics: A New Tool for a New Era (EDUCAUSE Review) | EDUCAUSE CONNECT]

Tony Hirst made a distinction a while ago between academic analytics and online course analytics, the focus of his interest.

In contrast to the academic analytics, one of the things I set out to explore was how an off the shelf web stats analytics tool (Google Analytics) could be used to help me learn more about what students were doing with our online course materials, and help me identify what - if anything - a "learning site's" goals could be, and what the site might be optimised for. [OUseful Info: Course Analytics - Prequel]

Follow-up posts are here and here.

This trend towards 'analytics' in the learning space, and the connection of web use and individual progress, provides an interesting contrast with general library practices and a concern for privacy.

At the LIR seminar a few weeks ago, I heard an interesting presentation [ppt] by Elizabeth Murphy of the National University of Ireland, Maynooth, about developing electronic 'core' collections to support learning. A part of the discussion was about the differences in expectations around the use of statistics between the library and those managing the university Moodle-based course management system.

Comments: 0

May 26, 2008
Tony Hirst

Dave Pattern posted something a day or two ago showing how he's using loans data to inform what should go into new books rss feeds...

"The way we used to do new books was torturous… I've thankfully blanked most of it out of my memory now, but it involved fund codes, book budgets, Word marcos, Excel and Borland Reportsmith. The way we're doing it now is to mine our circulation data to find out what students on each course actually borrow, and use that to narrow down the Dewey ranges that will be of most interest to them."
http://www.daveyp.com/blog/index.php/archives/305/

May 26, 2008
Lorcan Dempsey

Tony, coincidentally, I was going to mention Dave Pattern's post myself. And to add various 'related entries' on 'making data work harder'.

http://www.google.com/search?hl=en&q=%22making+data+work+harder%22+lorcan&btnG=Search

But the point that was in my mind here was the different perspectives different service providers on campus have about tying usage data to individuals to support action. In a network environment this becomes increasingly an issue as from a user perspective the line between various of these providers does not mean very much.

In this context, 'online course analytics' might be less relevant that 'academic analytics' but I remembered that you had used the 'academic analytics' phrase.

May 26, 2008
Tony

"the different perspectives different service providers on campus have about tying usage data to individuals"

Ah - ok; that's a nice distinction...

It also brings to my mind the 'opposite' case, eg, of data protection/privacy regulations that *don't* allow data to be used (maybe even for an individual's benefit) if the data wasn't collected for the use you (come to) want to put it?

I can see that data privacy/silos relating to who collected the data may prevent some data related services not happening because access to that data is not possible...

For example, I'd *love* to be able to play with OUr library data... ;-)