Revision as of 08:21, 3 May 2006

I have some questions for better understanding ....

IT Priorities

Database combining online and CNVC office information.

• What means database ?
  

To me it means an industrial strength database capable of replacing Quickbooks for Payroll and other accounting needs, Excel for the various spreadsheets people have apparently created due to lack of a suitable database, and Access for the few limited non-relational freestanding databases like donor lists we apparently do have at the CNVC office and on the ASP part of cnvc.org.

• It means something like mysql ?
  

From what I gather, yes MySQL would be a very strong contender because it's not only a powerful database with web integration capability built-in. It's also open source and thus free for us to use and share throughout the NVC network.

• I like to differentiate between database and something named presentation layer. For me its more clear by defining database as something which contains data and presentation layer as something which allows to access the data.
  

Ah, so the Database is the application that stores the data, and the Presentation Layer is the Forms and Reports you use to view or edit the data. The Data itself is the information contained in the database, for example a collection of Fields that might include Name, Address and Phone. All of those Fields would be distinct sections of Data that might be used on a Donor Contact Info presentation layer Form?

• Why it means database ? For easy query ?
  

Yes, CNVC has an urgent need for all the Data we now have to be input only once rather than written on papers and typed into all of the different applications I listed above.

• How you like to have the access ? By web ? By "fat" client (windows/java application) ?
  

All of those, and probably more ways.

• Accessible by whom ?
  

We need to have many levels of access. Some things would be accessible to anyone on the web. Some would require registration first to give minimal security and accountability. Some would be for access by members of a group. Some for access by selected individuals. Some would be visible to one level of access and modifiable by another level of access.

• You like to split the database from the online database ? If yes, you like to import data to online database ?
  

That's something we'd need to decide based on security. Is it possible to have absolutely unbreakable security with online data? My guess is no, so we'd need to have only some data online yet all of it integrated somehow. Like if the online part were a subset of all CNVC data, and the part not online would be physically isolated. Maybe the online data could periodically be updated by a send-only process requiring physical access to the offline database server?

Variable levels of strong security.

• What means strong security ? Not accessible by everybody ? Only trusted verified persons ? Secure connection ?

Trainer contact info.

• Address data ?
• What else ? I like to know the list of columns you like to have.....
• Accessible by everybody ?

Donor contact info.

• Address ?
• Payment overview ?
• Something else ?

Local and Regional NVC group contact info.

• Address ?
• Contact person ?
• Accessible by everybody ?

Online tools integrating various CNVC and other online resources.

• Is "Online tools" the synonym for online like web and accessible by others ?

Database Selection Criteria

The following database qualities are offered for consideration by the IT Committee:

• I like to differ between database and something named presentation layer. For me its more clear by defining database as something which contains data and presentation layer as something which allows to access the data.

ONE POSSIBLE DISTINCTION BETWEEN 'IT NEEDS' AND 'DATABASE SELECTION CRITERIA'

I believe ‘IT Needs’ might include the gathering of either human or economic resources that allow members in the IT Committee to keep themselves informed in regard of solutions that continue to emerge through which we might address ‘problems’ we haven’t encountered as yet – e.g. how to maintain transparent financial records in an organisation where both income and expenditure are considerably larger than income and expenditure incurred by CNVC in 2006, how to handle payroll or protect against fraud in an organisation with a far larger number of employees than we have at present, etc. etc.

‘Database Selection Criteria’ meanwhile appear to me something that might be most effectively determined by the individuals who are required to input and/or retrieve data from that database. My personal preference would be to notice a forum that allows for broad discussion of IT Needs and, beyond a few key pointers that might be considered applicable in all selection processes perhaps – e.g. preferably Open Source – less attention to detail by individuals who are not required to use a item of software or hardware on a daily basis.