Skip to content

Updates 11th October 2014

Jump to bottom
endymion1818 edited this page Oct 11, 2014 · 1 revision

We have now, thanks to the work of Oli, moved over to Spring 4. It also makes sense to use Glassfish 4 as this now supports many of the features that we use.

Details of how to upgrade are pending.

I have committed 005.sql that reflects the latest requirements for projects.

Just to reiterate so that we are all on the same page:

Edifice will not be used to manage projects except for creating projects so that it can be used to invite and record attendance, generate gate list.

Hence, a lot of the project related tables have now been dropped. So the new tables are:

  1. AvailabilityStatus: Reference table for codes for whether volunteers are not available or not, and reasons for not available.

  2. Project: A much reduced table to store project table. Those with Project access should be able to access this.

  3. ProjectDepartmentRequired : A table to store which departments are required, the date and the number of days they will need to attend. An example would be: Electrical Department, at Feltham on 24/10/14 for 2 days for first fix Electrical Department at Feltham on 11/11/14 for 2 days for second fix Hence, the unique constraint for Project Id, Department Id and WorkDate

  4. ProjectAvailability: This is simply to whether a volunteer is available or not. Some of the fields are: EmailSent: Has an email been sent to the volunteer or not PersonResponded: Has the volunteer clicked on the link sent in the email to the volunteer - this is to address that read-reciept of an email can be disabled by the volunteer. OverseerConfirmed: Has the overseer confirmed what days the volunteer is required on the project ConfirmationEmail: Has the volunteer been sent a confirmation email giving him details of the project, the date he is required.

  5. ProjectAttendance: This is to store the dates on which the volunteer has indicated that he is available, and the overseer has confirmed that he is required to attend. Once the volunteer has attended, this is updated.

So that everyone understands the process of inviting;

  1. A project is created by the Chairman’s office.

  2. Department overseers indicate if they are required to attend and, if so, on what date. (This should be done by the chairman, but as the work programme is sent to all overseers, department overseers can update/add an entry for this)

  3. The overseer selects which volunteer he wants to invite on the project.

  4. An email is sent to the volunteer with a secure link to indicate his availability.

  5. The volunteer makes his availability known.

  6. The overseer confirms which on which dates, that the volunteer is available, to attend.

  7. A confirmation email is sent to the volunteer giving him the dates and location, and other relevant details.

  8. The admin department updates volunteer attendance the day after.

Could you please take a look and see if:

  1. The above makes sense;
  2. I have missed anything out;
  3. The SQL is appropriate for the task.

Please eMail Raminder if this doesn't make sense.

Clone this wiki locally