...
- Reconcile "mutable" fields to new tables
- Add physical location fields to web interface
- Link autocomplete value (person, location, source, physical location) with database value, insert into activity_fact as one new record, with activity
- Parameterize SQL queries to hinder SQL injection attacks
- Slim code - figure out how to object orient and limit repetition, if this is possible?
- 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
- Add log in that connects to DB users in config file
- Parameterize SQL queries to hinder SQL injection attacksClean in-line styling, tables to divs
Database to do:
- changes to SQL script
- Split series name from source table? – see how organized in GCD
- Finish data dictionary explaining each entity and attribute, and ER diagram to reflect
- Add db users as per Will's second suggestion - change log in to interface to reflect & connect to DB
...