The current sql script for the database is attached here.
To Web interface to do this week:
- Parameterize autocompletes
- Reconcile Series/Issue Autocomplete bug (can type in any letter and the issue choices still pop up)
- Change "create new" links to buttons
- Upon main form submission, return to index.php
- Add note field to letter & review? (look at Richard's "notes" in spreadsheet)
- Add fields to physical location - end up separating this from location??
- Collection name
- Collection ID number
- repository (ex. Bodlein Library)
- institution (ex. U of Oxford)
(we decide how to insert private collections)
Web interface to do:
- Clean in-line styling, tables to divs
- Add log in that connects to DB users in config file
- CSS for mobile (tablet, at least)
- Autocomplete changes (for all autocomplete fields like person):
- selected person, input box disappears, replaced by an non-editable box with selected person's info (and X in the corner which takes user back to blank input box in case they select the wrong person)
- after creating a new person, have that person already selected (as above) when the person clicks out of the pop-up form
- Add log in that connects to DB users in config file
- Clean in-line styling, tables to divs
- CSS for mobile (tablet, at least)
Database to do:
- Add note field to letter & review? (look at Richard's "notes" in spreadsheet)
- Add fields to physical location - end up separating this from location??
- Collection name
- Collection ID number
- repository (ex. Bodlein Library)
- institution (ex. U of Oxford)
(we decide how to insert private collections)
- Change to real NULL on db for values that are blank
- Query builder based on non-empty fields?
- 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
Fall 2015 major to dos:
- Connect source_dim to GCD and location_dim to GettyUsability tests with form & input - make sure everything is inserting into the db correctly and form is intuitive
- Input spreadsheet data - does Will have suggestions for this automatically or would it be easier to put people on the case?
- Usability tests with form & input - make sure everything is inserting into the db correctly and form is intuitive
- hire people - work with them to input data
- Connect source_dim to GCD and location_dim to Getty
- Data entry for DVDs and Michigan images
- Data analysis - quantitative & qualitative (narrative abt interesting letters)
- Apply for grants:
- Collab Research - due Dec 9th 2015 --> arrange meeting with collaborators
- DH Implementation - due Feb 17, 2016
- Community/Public... - due June 2016
- Humanities Collections & Reference Resources - due July 2016
...
- Connect source_of_source table (as a "snowflake")
- Reverse engineer script to build diagram of database tables
- Include location_dim table for city, state, country data in while loop in getautoname.php file
- Constrain issue data by value entered in series name form in source autocomplete files
- Finish autocomplete integration in all forms
- Add page number to source table (if from an issue)
- Style forms
- make basic ER Diagram for San Diego
- Fix nested form issue
- Reconcile form interface fields with database attributes - process files
- Added mutable attribute tables to SQL script, models
- 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
- Object orient forms & processes
- Parameterize SQL queries to hinder SQL injection attacks
- Change "create new" links to buttons
As of 8/11/2015