One-page proposal abstract due: Tuesday, February 1, 2011 (with brief discussion of each project in class)
Full proposal due: Tuesday, February 22, 2011 (plus class presentation; approximately 10 minutes per project)
Project written report due Tuesday, May 3, 20119
Project presentation times last week of class (presentations of approximately 20 minutes per project)
As term project in this class you are to either create a digital library from a collection that you have access to or to identify a project relating to digital libraries and then design and prototype a solution.
If you choose to create a digital library, the collection should be significantly-sized. The strongest projects are likely to have a specific "client" in mind. Your project can use off-the-shelf tools when apprpriate, but you should design your library keeping the needs both of readers and creators of the collection in mind. The readers will need to find items of interest in the collection. The organization of the materials in the colleciton can help with this, which suggests that the design of the metadata records to be associated with the items in the collection will be important. You should identify the expected audience for the readers of the collection as the collection's organzational scheme may reflect their specific characteristics. Creators of the collection will be concerned with getting materials into the collection, which includes creating digital objects when necessary. In this case, the standards to be used in digitizing are part of the design of the collection.
If you take the second option, you have wide lattitude in selecting the topic to be solved--it should be related to the course's content, of course. An appropriate topic could be centered around the design of a specific tool to be used in digital libraries or on infrastructure for digital libraries.
The project may be a group project or an individual project. Note that the project undertaken by a larger group should be correspondingly larger than that proposed by an individual. All team members will receive the same grade on the assignment.
Proposal abstractA short proposal abstract is the first step in the development of the term project. The abstract should give a short description of the collection you want to create or the problem you want to investigate, why this is of interest, the approach you plan to take in solving it, and the names and primary roles of the team members (individual or group).
Full proposalA written proposal develops the problem statement, provides background, and makes the work schedule more complete. The project can be modified after the proposal is turned in based on the feedback or on other relevant factors. However, the proposal should be a complete and comprehensive description of what you plan to do, how you plan to carry it out, and how you plan to acquire any resources necessary for completing the project. Probably you can accomplish this in one to two pages of text, but feel free to use as much space as necessary. You also should survey and report on any related literature and/or projects. Include a timeline indicating what will be done and by whom.
In summary, the proposal should describe:
The project report (written) is to be an overall presentation of the problem, the design, the prototype, the respective evaluations, and a discussion of lessons learned. This is the "archival" description of your project, so it should be complete and understandable on its own. Most likely this will be at least 10 to 20 pages in length--i.e., at least the length and detail of a standard Computer Science conference paper. Some of the things to include in the project report describing a project centered on a technique or infrastructure are:
Oral project presentations/demonstrations will be scheduled at the end of the term. Signups for time slots will be available later in the semester.Turn in materials on paper and place a copy on your course Web site. Please include your email address on all materials turned in.