Training: class objects

[wgj]

To be instantiated by a training object, ie. we wouldn't have a class that wasn't attached to a "training".

Create a class object,
a class should have the following attributes:

• Time
  • different from a "training's" date/time. Classes may be the length of a training, or a subset of it.
• Class type or class name
  • would be best represented as a predetermined list of class types.
• Total available seats
  • integer
• Trainers
  • A list of users with a role of 'trainer'
• Trainers in Training (TiTs)
  • A list of users attending as TiTs
• Students
  • A list of users and persons attending the training for credit
  • a student can not have previously attended a trainings as a Student
  • if the class is default ranger training, then ask whether the student wants a printed-out paper manual. keep track of this tally.
• Audits
  • A list of users and persons attending the training, who are not attending as Students, Trainers, or TiTs.

[flwyd]

I think this is mostly handled by the scheduling system. A Training has several Slots, each Slot has a Position. Trainer, TiT, Trainee, and Audit are all different Slots, each with their own maximum number of attendees. ARTs can be a Slot as well, or we could model it as a Returning Ranger Morning Session.

It would be useful to add a view for the Training that shows all of this information, presented to Trainers and TiTs.
Wes, could you give some input about how that view should be presented?