Goal
To creatively examine, mine, or browse the CiteSeer metadata using
techniques (related to those) learned in class.
Teams
For this project, we will have three larger teams. They are:
- Team 1: Matt Kreibel, Andy Powers, Chris Janneck, and Lan Nie
- Team 2: Vinay Goel, Xiaoguang Qi, Walter Scheirer, and Phil Garcia
- Team 3: Chris Kramer, Chad Hogg, and Keith Erekson
Projects are intended to be implemented using pair programming techniques.
That is, multiple members are expected to simultaneously work on the
bulk of
the project (sharing one workstation); this encourages both peer teaching
and better coding as multiple eyes are understanding what is being done.
In this project, you may use any code and any platform desired. The
CiteSeer metadata is available in /proj/searchengines/ on the Suns.
What to Hand In
Your final report should look like a conference paper. It should
introduce the problem/idea, describe
background to the problem and techniques used, and related work. It
should also describe
the experiments and their results and a discussion of the significance of
those results.
A discussion section should emphasize
contributions that your group has provided -- solutions to problems
encountered, and improvements to interfaces or performance, etc.
Your group will also give an in-depth presentation and demo (~30-40
minutes) of your work and implementation.
Important Dates
A proposal detailing the ideas and approach is due by Thursday November
18. An email outlining the plans and progress so far is due
Tuesday November 23. The completed assignment and
substantial written report
is due Monday December 6. Code does not need to be handed in, but
it must be present in your group directory, and the report (which should
discuss your code) should also specify its location. Presentations will
be held during our final exam slot from 12-3pm on Sat December 11.
Grading
I suggest you read my advice on what
I think constitutes good writing, programming, and presentations.
Your report and in-class summary will be graded on clarity,
correctness, and
presentation, so
make it professional. Code will also be examined for clarity and
correctness.
Finally, you will also be asked for for an evaluation of
yourselves and each other -- the relative contribution, effort provided,
and quality of work. This will be another component of your project
grade.
Last modified 22 November 2004, by Brian Davison.