Since you already put in a lot of time and effort you should better know where the problems are in a web based system. Outlining the problems would save anyone just starting a lot of time and false starts. .
Please outline what requirements you believe a tracking program should satisfy and what features you believe are needed (perhaps level 1,2 and 3 level requirements/features). Please outline the security/protection requirements (rather than implementation methods) you found. thanks oscar On Sunday 25 June 2006 1:44 am, Robert Nickel wrote: > Although this message is not in reply to a specific message, I'm going to > reference many of the items spoken by folks. > > Having put some serious thought and energy into development of a web based > troop tracking system, I have been following this thread with a great deal > of interest. This has helped me to gel some of the concerns and ideas that > I've had in the past together. > > First; if someone is to sponsor a central database, we should *not* look to > the church for a scouting oriented database. We should offer our efforts > to BSA. This way, the program could benefit all scouts and not be viewed > exclusively as an LDS thing. > > Second; DTG should become part of MIS, or at the very least, be centralized > through the clerks office. This way, all of the features that have been > touted of the etrailtoeagle program can be realized via the church email > system. > > Third; to alleviate the concerns that have been expressed about the volume > of personal information stored in an online database, I would suggest just > not allowing for the storage of that information. What is the requirement > for tracking all of the things that TroopMaster tracks? Personally, I > think TroopMaster suffers from massive feature creep. Things like > insurance values, license numbers and parental contact information should > either be tracked completely offline or on paper. Although the improved > security garnered by this approach is dubious, the fact that we're trying > to track progress and not all the ancillary things associated with scouting > should serve as a primary focus. I think that the discussion has been > healthy but that there are definitely different views of what the scope of > the project is going to be. Without some definition of this scope, the > discussion to date can have *very* different meanings for each person on > the list. > > I think that Tom [0] should set down some initial criterion for the project > before anyone decides to spin off yet another scout tracking system > (YASTS). > > --Robert > > [0] It appears that Tom was the originator of the thread from the link that > I was given. _______________________________________________ Ldsoss mailing list [email protected] http://lists.ldsoss.org/mailman/listinfo/ldsoss
