[Ldsoss] Advancement tracker

[A. Rick Anderson]

Thomas Haws wrote:
> On 6/23/06, *Steven H. McCown* <smccown at earthlink.net 
> <mailto:smccown at earthlink.net>> wrote:
> 
>     As for databases, what are the database requirements?  If the program
>     operation is to be done at the ward level, then we're probably
>     (depending on
>     the ward size) talking about 30-150 kids or so.  If at the stake, then
>     multiply that by 8 or so.  Are those numbers sufficient to warrant a
>     database?  If so, what type (not brand)?  Granted, I'm not a DBA,
>     but isn't
>     a flat file faster for those numbers?
Excellent question.  I doubt any would deny that for these numbers, some 
form of flat file would be sufficient.

However, from a performance and sizing perspective, I don't think we'd 
see significant impact from an embedded database, such as Darby. 
Especially since Sun will be including an embedded database as part of 
the JDK in the next release of Java.

 From a security perspective, I'd rather store information in a database 
then in a flat file.  That's a gut reaction, not an argument based 
strictly on technical merits.  It just provides another layer of 
penetration that an intruder must breach to get to the data.  If we use 
Darby's encryption capability to store the data, that would provide yet 
another layer of security.

Long-term wise, I know that Steve and some others are not a proponents 
of an online solution, but if the BSA or a large BSA-Sponsor were to 
eventually host such a service, then scaling the solution would be 
simply a matter of swapping in an industrial grade database.

Thomas Haws wrote:
> I think that's worth asking.  Is the nature of advancement tracking such 
> that it lends itself to 1 portable file per individual, whether that 
> file be flat or xml-ish?
Having the ability to export/import/print the data to flat files such as 
XML, CSV or report format would be a nice use-case to support.

I'd argue that having the ability to export/import a single set of 
records for a specific individual is probably one of the primary 
use-cases that we would want to support.

For example, a parent could install the Scout Tracker software on 
his/her personal desktop and sync with the troop's database, just like a 
disconnected scout leader.

Generalizing this requirement suggests that the functional requirement 
would be that an authorized user should be able to view and download 
records that pertain to the "scouts" and the activities that are 
assigned to them.  But, of course, they should ONLY be able to 
view/download assigned youth.

Some possible actors for such a use-case would be:
Individual Scout, Parent, Merit Badge Counselor, YM/YW leader, 
Advancement Coordinator, Assistant Scout Master, Scout Master, Eagle 
District Coordinator (?don't remember their real title).

ex:
A parent should be authorized to view, update and download only records 
of scouts/YW for which they are legal guardians.

With this capability we have empowered not only the ward leaders, but 
the parent and child.

-- 
A. Rick Anderson