The current sql script for the database is attached here.
Web interface to do:
- Reconcile form interface fields with database attributes
- Slim code - figure out how to object orient and limit repetition, if this is possible? - clean
- Clean in-line styling, tables to divs
- Link autocomplete value with database value for proper insertion
- Link each of these values & insert into activity_fact table
- Parameterize SQL queries to hinder SQL injection attacksReconcile form interface fields with database attributes (once data dictionary is final)
Database to do:
- Finish data dictionary explaining each entity and attribute - discuss at 7/1 mtg
- Will's changes based on his email - mutable attributes and "versioning" (will db user still be saved if coming from a web form?)
- Split series name from source table? – see how organized in GCD
- Should we have a field the interface for the data-entry user's name? if yes, where would this value go in the database?
- Otherwise, this may be covered with log-in/privileges?
...