DA Project Overview

Keep It Simple Stupid (KISS)

The first goal is to simply digitize the collection.

The main objective is to keep the process as simple as possible. To that end:

• we will use off the shelf, freely available, tools (iTunes client, daap server);
• metadata will limited to what is provided by the Grace Note Media Database which is explained here;
• the collection will be digitized in a linear order (accession number) to reduce record keeping.

Music Library Format

The music will be ripped using an iTunes client and saved in the Apple Lossless format. This format reduces the storage needed by half when compared to the orginal file while losing none of the quality.

Labor Not Expertise

By keeping everything simple, digitizing the collection becomes a matter of applying labor. No technical nor professional knowledge is needed!

The digitizing process requires that a CD be placed in the CD tray of the ripping station and imported. When ripping is completed a playlist is created by selecting the imported songs and the CD removed. Repeat this 2000 times and voila!

The digital library will be made available from a DAAP server to iTunes clients. iTunes clients are available for both Mac's and PC's. Access to this server will be limited to specific locations on campus.

University Computing will determine the physical location of this server dependent on network configuration.

Recap

Goal one is about delivering CD quality audio to limited sites on campus. It will provide high quality access to the complete collection but only in the library or a music lab. Working with UC we hope that it will provide access to classrooms in White Hall.

It requires limited technology, limited record keeping and no expertise. Excluding access to the collection itself, it is also limited in its application. No special playlists will be created, no downloading, no access outside of specified locations.

Different Constraints

Providing access remotely has several constraints that make this a totally different proposition:

• remote access requires authentication;
• bandwidth needs to be considered. On campus we have a minimum of 100Mb to work with while going off campus we're limited to 20Mb or less;
• it requires that playlists be made explicit because we're using the HTTP client (or at least a client using HTTP) rather than the DAAP client to access the library;
• a mechanism (interface) must be built to allow music faculty to create playlists which will then be placed on reserve and available to their students.

Authentication

Remote authentication can be handled by the library's existing proxy service. This service is how we allow off campus access to the databases that we subscribe to.

Bandwidth Considerations

To reduce the bandwidth requirements we're proposing that the original digitized tracks be converted to an FM radio quality mp3.

The resulting file will be somewhere between 3 to 4 times smaller than the original. It is imagined that at even the busiest times outgoing bandwidth will be no more than 10Mbs. Multiple tools are available to monitor this activity.

It's our intention to do this conversion programmatically with no human intervention. A question remains as to whether the entire library should be converted as it is built and as items are added or to only convert tracks when they are placed on reserve.

Playlist Delivery

Playlists will be delivered as both HTML pages and RSS feeds. RSS feeds can be subscribed to with music clients like iTunes which makes this format attractive. HTML pages will be used as a default.

Playlist Construction

Allowing faculty to create playlists for their courses requires that some kind of interface be built that allows the faculty member to compile a playlist from all the possibilities in the library. It also requires another layer of authentication as to who will be allowed to create playlists.

Allowing faculty the ability to create playlists and put these playlists on reserve is important because we don't want to create a staffing issue in the library.

Recap

Providing remote access requires much more expertise that simply digitizing the collection.

We feel that we have that expertise here in the library but it will take a commitment of time and effort to make this kind of access happen.