1. Central Arizona Phoenix LTER Center for Environmental Studies Arizona State University Data Entry Applications Peter McCartney (CAP) RDIFS Training Workshop Sevilleta LTER October 28-30, 2002

2. Central Arizona Phoenix LTER Center for Environmental Studies Arizona State University The Data Cycle RDBMS Storage ILSDFWEWFDSF FWEFSDFWE DIFJDISLDIJFS SDFSDFSDFSDIMLMKM FSMDSID MLSDIFMSLDFI SDFSDFSL LSIDFSLDFM JIJIJIJLSDIFS Sdfsdfsdfs dfsdfs 8989 sdfsdfsdsdfsd 90 sdfsdsd 4004 dfsdfsdfsdfsdfs dfsd Query Analysis QA/QC Data Entry DenormalizedNormalized Site, Type,Sample, date,taxon 1A, urb, 1,2/2/99, 145 1A, urb, 1, 2/2/99, 123 1A, ag, 2, 2/3/99, 145 …..1..A

3. Central Arizona Phoenix LTER Center for Environmental Studies Arizona State University Application Development Functionality –Differences in user needs and skills Performance –Number of users –Size of database –connectivity

4. Central Arizona Phoenix LTER Center for Environmental Studies Arizona State University Scale Single Tier –Desktop systems –Direct data access by application Two Tier –Client/server systems –Data access brokered by server Three Tier –Web database applications –Web application handles communication between client and server

5. Central Arizona Phoenix LTER Center for Environmental Studies Arizona State University Development modes Rapid Application Development –Environment with many built in objects for common data operations –Drag and drop programming –Usually interpreted language dependent on environment to run Native application programming interface –Far slower development cycle –Customizable at expense of manually coding interface elements

6. Central Arizona Phoenix LTER Center for Environmental Studies Arizona State University Forms based programming Used to develop entry,edit and query applications Forms –represent the interface between user and data –can be bound to tables or queries Controls –can be bound to attributes Events –Invoke actions on data through event scripts

7. Central Arizona Phoenix LTER Center for Environmental Studies Arizona State University Basic data entry form Create a form Bind to a parent entity Select controls and bind to each attribute –Text box, list box, checkbox, etc Set any QA/QC constraints or defaults for the controls Create unbound controls as needed to manipulate form (save, reset button, etc) Create event scripts for either the entire form or individual controls

8. Central Arizona Phoenix LTER Center for Environmental Studies Arizona State University

9. Central Arizona Phoenix LTER Center for Environmental Studies Arizona State University

10. Central Arizona Phoenix LTER Center for Environmental Studies Arizona State University

11. Central Arizona Phoenix LTER Center for Environmental Studies Arizona State University Forms for related information Create a form to edit the attributes of a related table. Bind the form to a query from that table where records are selected by the foreign key Create an event script in form #1 that alters and re-executes the query for form #2 each time the record pointer in form one moves.

12. Central Arizona Phoenix LTER Center for Environmental Studies Arizona State University

13. Central Arizona Phoenix LTER Center for Environmental Studies Arizona State University

14. Central Arizona Phoenix LTER Center for Environmental Studies Arizona State University Proofing reports Define query that will list data in groupings and order that matches entry sheets. Create report and arrange controls to print data in same order as paper forms. Bind report to query

15. Central Arizona Phoenix LTER Center for Environmental Studies Arizona State University Some Design Considerations Optimize entry speed and accuracy Match the sequence of entry with the order of information on the data sheets Find out whether data entry person prefers to enter codes directly or use pull downs Consider providing controls to help users shorten lengthy domain lists Consider a double entry system where duplicate entries are stored in a buffer and compared prior to entry.

16. Central Arizona Phoenix LTER Center for Environmental Studies Arizona State University Considerations for Web Forms HTTP (3 tier) –protocol is “stateless” -session used to store state information –Data exchange limited to response/request object –Eg. Cursor location, key values –Limited interface controls, offset by client script (javascript, jscript, vbscript) Applets/plugins (two tier) –More responsive –Maintains state –Requires software (JRE, plugin, database drivers, etc.)

17. Central Arizona Phoenix LTER Center for Environmental Studies Arizona State University Alternates to Forms Based Entry Bulk inserts –Bulk copy –Scripted inserts Tabular data XML data Application interfaces –Direct inserts/updates via an API