Training: training objects

[wgj]

Create a training object.

A training should have the following attributes:

• Event Cycle
  • a reference to an event cycle
• Date/Time
  • Time should be defaulted to 10:00 am to 5:00 pm
• Address
  • traditional postal format
• Address Notes
  • some trainings need further directions to compensate for rural addresses.
• Class(es)
  • A collection of class objects.
• Photographer
  • a user responsible for taking photos

[flwyd]

The base Training object is in place. It's linked to a Shift (which is part of an Event), which ties it to the scheduling system. Shifts have Slots (Trainer, Trainee, Audit) which people can sign up for.

What's still needed:

• When signing up for a shift, a little information needs to be collected:

  • Do you need a manual?
  • If you don't need to take the full day of training, which ARTs are you interested in? (Checkboxes based on arts_trainings table.)
  • Other questions?

  This also provides an opportunity for us to present any key information and links needed by folks who don't have a background with the Rangers.

• Training Status model and views to track successful completion of training

  • Result: pass, fail, sit-in, no-show
  • Which ART did they take? (optional, of course)
  • Record which user created/updated this record.

  People can view their own training status. Only trainers (and TiTs?) can create/edit a Training Status record.
  Business logic may trigger as a result of Training Status, e.g. granting access to the Alpha position when a new volunteer passes.