On 2006.07.07 18:43:37 -0600, Oscar Schultz wrote: > True - storing data/forms is challenging. > Tracking awards makes planning and program management easier. > > Access to information however is required for trips.
Agreed. > The required documentation for an outing to occur is: [... concede listing ...] > 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. Ok. I agree that you need access to the paperwork but am failing to see how this means we should input this information into a database. If I track who has what paperwork on file, the filing is a simple thing. Photocopies can (and arguably should) be made anytime someone has a legitemate need. If that means that there are three copies out to leaders, then so be it. > Having good documentation for awards is also required - it make it a lot > easier to plan a program and to keep everyone on target. I'm not seeing the point here. If I know what each boy has earned, then why do I need to have his email, phone number, dob, etc.? These are easily kept and distributed in another (hopefully, less public) medium. > 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 ? I don't see the why we need to handle all of the other information. I'm reluctant to place a leader's convenience over the security of someone's personal information. That's a very slippery slope to embark upon. So that you may better rebut my comments, let me explain that the only use I see for storing the address information is to do mailings. As an LDS leader, I don't have much use for mailings as most of the time quorum presidents do phone calls to get the information to boys not at the weekly meeting. As an LDS leader, I've never needed to wonder about a boy's date of birth. If he's not 18, I don't worry about anything other than working the program. If he's nearing 18, I work with him to get his eagle if that's his interest. Is anyone else doing something else with the DOB? Email may be useful and it would be interesting to see an option to do status mailings. However, I find that there is no substitute for face to face communication with parents when it comes to scouting. I've had *way* too many bad experiences where the parent ends up with half of the information. [...] > > > My list of tables: [...] > > > requirements, images, pictures, completed_awards, completed_requirements, > > > emergency_contacts, medical_forms, and permission_slips I'm curious on the use for the images and pictures tables. The names bring several ideas to mind but I'm wondering what you were after there? Best regards, --Robert
pgpNXOHh5QbHi.pgp
Description: PGP signature
_______________________________________________ Ldsoss mailing list [email protected] http://lists.ldsoss.org/mailman/listinfo/ldsoss
