Thanks for the class - I've only had time to review people.inc.php and compare 
with my table list for people.

yours:
class award {
  var $ID;
  var $FName;
  var $LName;
  var $Type;

  function people($_id=0, $_fn="", $_ln="", $_t="S") {
    $this->ID=$_id;
    $this->FName=$_fn;
    $this->LName=$_ln;
    $this->Type=$_t;
  }
}

mine

first_name
middle_name
last_name
preferred_name
gender
birth_day
birth_month
birth_year
record_id
date_recorded

It will all go into a sql table
Address, phone, email will be separate tables since people can have multiple 
of each.
My plan is to use either MySQL or PostGRES, php, apache, and linux with a web 
interface.


My list of tables:
people, addresses, phones, emails, events, attendance, awards, requirements, 
images, pictures, completed_awards, completed_requirements, 
emergency_contacts, medical_forms, and permission_slips

should be interesting

 On Wednesday 05 July 2006 1:39 am, Robert Nickel wrote:
> Ok.  I've put together the initial base classes to meet the criterion from
> my earlier email (below) about what features should be in the system. 
> However, I haven't defined the paperwork system fully.
>
> Most of the classes are obvious, I hope, but just in case they're not, I
> will be writing up a readme of sorts to go along with these definitions
> later this week as well as the remainder of the paperwork filing classes. 
> [0]
>
> Please take a look and make all of your comments to the list.  I promise
> not to cry if someone says my code sucks. :)
>
> If the attachment doesn't go through, let me know and I can mail
> individually or find somewhere to put it on the net.
>
> --Robert
>
> [0] I have to be up for work in 5 hours so I'm stopping now.
>
> On 2006.06.26 08:57:04 -0700, Robert Nickel wrote:
> > The requirements for the tracking program, in my mind, are quite simple.
> > Reduce the amount of effort required by the Scout Master to track this
> > information and provide meaningful information to the Scout Master or
> > individual scout in a timely manner.  Beyond that, other features are
> > just window dressing.
> >
> > The core features that *must* be implemented (Level 1):
> >
> >   o Troop roster.
> >     - First name, last name, middle initial (optional).
> >     - Flag for leader or scout.
> >   o Configurable rank requirements.
> >     - Since BSA is taking great pleasure in rearranging old requirements
> > and adding in new ones, it's beneficial to have a flexible system for the
> > ranks Scout -> Eagle.
> >     - These rank requirements should be unique items in case the
> > requirements change and the boy is not responsible for the new
> > requirement structure. o Merit badge listing.
> >     - This listing should include the merit badge number, name and
> > whether or not the individual merit badge is a required merit badge.
> >   o Troop positions tracking.
> >     - Ability to input troop positions and who filled them (if anyone)
> > with start and end dates.
> >   o Reporting system.
> >     - Answer questions frequently asked by SM and CC like, "What boys
> > need for first class?" or "What paperwork is this boy in need of?" or
> > "What merit awards have been earned by the troop this year?"
> >
> > The features I believe are worth doing (Level 2):
> >
> >   o Merit awards for youth and adults.
> >     - Duty to God *could* be integrated here but is likely better suited
> > to being a stand alone application if this is to be available for all
> > scouting organizations.
> >     - This is a great place to track awards for On My Honor and other
> > similar items.
> >   o Attendance roster.
> >     - Allow for input of meeting dates and roster of boys attending.
> >   o Paperwork tracking system.
> >     - Input various items that need to be filled out (i.e. a permission
> > slip for each boy attending a campout).
> >     - The system should be flexible enough to accept lists of boys that
> > need to have the paperwork in and a deadline.
> >     - Ideally, this could be used for tour permits and other such items.
> >     - Some sort of comments field for this system would be ideal allowing
> > for todo items and some minor collaboration between leaders.
>
> [...]
_______________________________________________
Ldsoss mailing list
[email protected]
http://lists.ldsoss.org/mailman/listinfo/ldsoss

Reply via email to