True - storing data/forms is challenging. Tracking awards makes planning and program management easier.
Access to information however is required for trips. The required documentation for an outing to occur is: a permission slip per person, a required medical form (normally a class 2) per person, a valid trip permit, and the safe scouting guide. If the group is split into multiple vehicles/groups each adult group leader should have a copy. To prevent document loss normally copies at home are recommended for the duration of the trip as well. Just imagine getting to a hospital for help and having to wait for paperwork because it is in the lake/river with your canoe or back in the busted vehicle . Worst case docs from home can be faxed in minutes. When each leader has a copy - no problem except for collecting the doc at the each of each trip. When an emergency occurs the activity/trip leader needs access to forms normally on paper. Having good documentation is fundamental to success. Having good documentation for awards is also required - it make it a lot easier to plan a program and to keep everyone on target. What is needed is how to organize the data to protect the data, methods to limit access, and how to track access to the data. I plan to use linux, apache, mysql, and php. There are controls at each level - so how to lock down access at each level ? oscar On Friday 07 July 2006 7:21 am, Slide wrote: > On 7/6/06, Oscar Schultz <[EMAIL PROTECTED]> wrote: > <snip> > > > 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 > > Be careful with some of this information; are you planning on storing > medical information or just a flag saying they have turned in the > medical form? Storing medical information would probably be a bad > idea. > > slide > _______________________________________________ > Ldsoss mailing list > [email protected] > http://lists.ldsoss.org/mailman/listinfo/ldsoss _______________________________________________ Ldsoss mailing list [email protected] http://lists.ldsoss.org/mailman/listinfo/ldsoss
