The meeting opens with a workshop on Shared Media & Data Repositories, and What’s New in Scholarly Systems.
Elli Mylonas and Patrick Yott from Brown lead off the morning talking about Librarians, Academic Support and the Faculty: A dialogue towards planning a digital repository. They enact a conversation between a librarian, a technologist, and a faculty member about digital repositories. The conversation revolves around the tension between a static view of digital objects that allows preservation and access vs. a dynamic view of content that allows for development of the objects over time and reuse over time.
Jim DeRoest, from our very own UW, is talking about the Digital Well asset management system, and how it supports the Research Channel. Digital Well is metadata-centric – the storage is abstracted, which allows for use of different storage back ends. Research Channel has thousands of hours of video stored in the Well, with about 30k objects. The total number of objects in the Well is around 300k ranging from jpgs to high-def uncompressed video (1 hour is several terabytes of data). A good collection to look at is kexp.org – all of the content there is being driven from the Well. The next step is Research1, which will be announced at Internet2. It’s a YouTube-like interface that acts as a portal for research content.
There’s a bunch of discussion of what the funding models for this sort of repository are like. Jack Duwe suggests that one place we might look for business models for “forever” storage is the cemetery industry – what the call “perpetual care”.
Jim Kerkhoff and Peter Keane from the University of Texas at Austin are talking about DASe, their Digital Archive Service. It’s a PHP-based system. This came out of the need to digitize a slide archive in fine arts, containing about .5 million images used in multiple courses. They’ve built it to be flexible, to be able to adapt to changing needs as they emerge, like private collections, modules for custom interfaces, etc. They’re talking about using folders in Xythos as an ingest mechanism for DASe. There’s a question from another campus that’s losing customers to Google Images. Peter notes that it’s very important to remain agile and figure out how to be quickly responsive to needs and understand how to meet the needs.
Qing Dong is talking about Thalia at MIT, an enterprise image storage and management application. It’s designed to support both departmental and personal academic needs, part of a long-germ content management strategy. It’s built on AlFresco, using OpenLaszlo and Flash for the web interface. They’ve built a REST interface.
Tim Sigmon is describing U Virginia’s Academic Information Space, which has a goal to enable users to work with diital resources in an integrated environment. It’s a partnership with the Libraries. The core is the Digital Library (Fedora-based) and the Scholar’s Workbench (based on Sakai and a Fedora-based object repository).
Gary Worley from Va Tech (this must be the Virgina portion of the morning) is talking about how they support digital collections.