We'll start out with scheduled updates. Jesuits have to be reminded to update documents. The period between updates varies per person (age bracket and custom). It may be a good idea to support different kinds of documents, too.
They need something to last years, so we can't turn it over to the students. Pair programming might be a good idea - forces my code to be readable.
Actually, if it's Java, it can run on their own computers, and then just send the data to a central server every so often. (version 2... =) ) We need to make this as painless to run as possible, which means no external database. It also needs to be as paranoid as heck when it comes to saving.
Data associated with each Jesuit:
id (surrogate primary key) name birthdate description
I promised them a prototype in two weeks.