Android Core Logging Application Keith Schneider Introduction The Core Logging application is part of a software suite that is designed to enable geologic to be logged and disseminated as quickly as possible. The ability to log straight to a digital format with the Core Logging application has been field tested and proven to increase the rate of data collection while concurrently providing data validation. The application provides real time data quality control that is coupled with data validation. With an intuitive and user centric interface that makes every effort possible to provide an environment that enables professionals to record and access data, while minimizing redundant efforts. Features Real-time Quality Control Integrated photos with annotation capabilities Bar-code scanning for laboratory samples Alternative interfaces for specific tasks File transfer via Wi-Fi, Bluetooth, USB and SD Card Customizable Lookup tables Extensible User Interface design Integration with existing data frameworks UI Design and Usability The individual components of the user interface where designed to allow features to be added to components without modifying existing code. This follows from a component based model for individual user controls that can interface with the existing model-view-controller paradigm. The user interface design was designed to be adaptable for the clients specific needs. Each client or project carries with it specific needs and a unique data structure, and often fundamentally different methods of data collection. The application was designed to accommodate these needs. Controls such as text fields, lookups, and validated numerical fields have been constructed such that they can be reused in multiple contexts with out the need to recode. Through testing and user feedback the design has changed to accommodate use in varied lighting conditions including direct sunlight. Real Time Data Integrity and Quality Control Validation of the input data should be accomplished as close to real time as possible, this information should be presented to the user in a highly visible but non-intrusive manner. Quality control routines should not impede work flow, or cause undo frustration. When possible the program should offer potential solutions, and should provide links to documentation that explains why the input data is in violation of the data-integrity rules. If possible the controls should be designed such that inputting invalid data is either impossible or unlikely. Overview of System Design Controls Controls are built upon a common interface that contains both the control component, and QC code that is particular to that type of control, or data field. This allows for the control itself and the code to vary independently and promotes reuse. Each control has a reference to it parents data structure and registers as an observer to be notified of specific changes in the structure. Parent Views The parent views consist of two major visual components. A navigational component which allows for navigation through the data structure. And a view consisting of the various controls necessary to make modifications to the actual data. The parent view also contains data QC components that can check the data set as a whole for validation errors that can only be found in context. Validation errors can then be forwarded to the appropriate controls to notify the user, that the data need further attention. The Model The database is based on the Open-Source SQLite3 format, and contains the recorded data. Queried data is accessed through a custom pointer class that navigates the data structure, performs updates to the data, and notifies registered listeners of changes. The model itself contains some inherent QC that enforces validation for critical information to prevent the dataset from being corrupted.