Get OhNo! for data entry control

One of the differences between a database and a spreadsheet is data checking. A spreadsheet allows almost any data to be entered in any cell. But databases do not allow records to be saved unless all data is the correct type, the value is within bounds, and that all required information is entered. Data checking eliminates typographical errors, forces the data to be recorded in a predictable way, and prevents unrealistic combinations of times and activities.

OhNo! applies eight rules to synthesis data before the record is saved. Each rule can be configured so that if bad data is entered, it is ignored, or a warning is produced, or the synthesis is blocked and cannot be saved (until corrected).

E1. Time and Activity sequence checks

This rule checks adjacent time and activity measurements to ensure that the times increase and activities decrease. For example: Start of Synthesis (SOS) has to occur before End of Synthesis (EOS), and the starting activity at SOS must be greater than the final product activity at EOS.

E2. Completeness

This rule checks that all required production data has been saved. The user can select which fields are required. Any number (or none) can be selected. If a data entry field on the Production form has been designated as ‘Required’ it appears with a pale yellow background.

E3. Activities require time and date (and vice versa)

For example, if an activity is recorded at SOS, then a time has to be recorded too (and vice versa).

E4. New data must be recorded with 24 hours of a synthesis

This rule checks for incorrect dates (example: 2/3/10 vs 3/2/10). It eliminates typing mistakes as well as common problems such as forgetting to increment the year in January.

E5. Dates must be after 1975

This rule checks for unrealistic dates. It also eliminates a common problem with all databases, namely date = null or date = 0.

E6. Irradiation time must be 0.5 to 2 half-lives

This rule checks for incorrect SOB and EOB times, especially irradiations that span midnight, AM/PM problems or data pairs that are accidentally entered on different days.

E7. Maximum time span 4 half-lives

This rule checks the earliest time and date for a synthesis, against the last one. If the time span is more than 4 half-lives, an error is raised.

E8. Data within range

This rule checks that all entered data is within user-defined upper and lower limits.