Organization
The course requires students to pick a major implementation project. Topics include extending an existing provenance system, adding provenance functionality to an existing system, and build tools that visualize or manipulate provenance data.
- Choose one of the topics below or suggest your own topic (Sep 21th)
- Each student will meet with the instructor to discuss the topic and get background information to get started
- Project implementation due by end of semester
-
- Written report: What did you do? How did you do it? What were the challenges? What are possible extensions?
- First version due by Nov 15th
- Final version due by Dec 1st
- Oral presentations will hold during the last few classes or in a separate session at the end of the semester. You will give a short oral presentation about the status of your project beginning of November
Projects Ideas
This is not a comprehensive list. Suggest your own topic or contact the instructor for additional topics in a specific area.
- Adding new provenance types to existing systems
- Add causality based provenance to Perm
- Add Why-provenance to Perm
- Extend the How-provenance implementation of Perm to derive new information
- Build a visualization tool for provenance in Perm
- Build a stand-alone provenance index structure that supports at least forward and backward lookup
- Add a provenance data type to Postgres / Perm
- Add a provenance support for updates / Perm
- Your topic
Stuff to get familiar with
- See resources page for links to documentation and tutorials
- Get practical experience with a database system
- PostgreSQL: open-source, quite standard compliant, Perm based on that
- Use Perm which is an provenance-enabled version of Postgres
- Query languages:
- SQL
- Relational Algebra
- Datalog
- Programming skills: C, C++, Java
- *nix operating system or Cygwin for Windows users
