Over the past year we've been developing a new collection building tool to be used in conjunction with the MBooks "page-turning" application already available. This tool will allow users to create their own collections of MBooks items and view public collections created by others. Users will also be able to do full text searching across all items within a collection.
The Usability Working Group (UWG), along with our 2 fantastic and hardworking interns, is spending the summer conducting usability research on MTagger. We started by doing a heuristic evaluation and cognitive walkthrough. The goal for these evaluations was to reveal a preliminary set of issues pertaining to the usability, functionality and aesthetics of MTagger and to facilitate prioritizing further benchmarks. This report is now online.
We get questions from MBooks users (most recently from dfulmer in the comments to this post) about how to link to pages, what the URL parameters such as "num" and "seq" mean, and other questions about links and page numbers.
Earlier this week, I had a chance to give a brown-bag session on a new API into our catalog, Mirlyn (Ex Libris's Aleph software).
At the University of Michigan Library, in partnership with Google, we have been busily scanning our collections. This opens up lots of possibilities, including an exciting one that launches today: search the full text of a book from within Mirlyn, the library's catalog.
MLibrary Labs is the University Library's test bed and playground. Here's a summary of all the tools that have been released since we launched it in September 2007.
As is well known, we are digitizing all the bound volumes in our library, including books in copyright. I don't want to address the legal issues surrounding the digitization itself, but instead discuss uses of these materials after digitization. We do not show any part of in-copyright books in MBooks, leading people to wonder why we even bother to digitize them. We can answer that question in a number of ways.
Page 17 of 18