<< Click to Display Table of Contents >> Navigation: Other Information > Considerations on Where to Store Data |
Multiple ways exist to store and report location-specific data (other than concentrations) thanks to the flexibility of EQuIS databases. Some possibilities are described here. Consider the following factors to determine what is best in each situation:
•specificity of the data (e.g., per sample, location, subfacility)
•formats used for loading data
•frequency of testing, as tables have different criteria for duplicate records
•Schemas applied to the database
•reporting practices (which reports are currently being used or are planned to be used)
•Data storage in a certain table may be less feasible if additional formats or reports (and therefore extra loading or reporting time) are involved.
If results are text-based (e.g., "TRUE" or "FALSE"), unit conversion or action levels may not work as expected; reports with Action Level Exceedance analyze numeric action levels.
The Database Schema page summarizes the types of data that each EQuIS module can store. Additional licensing, upgrading, or installation may be needed for some modules. For radiological data, see Radiological Data Management.
Common result and parameter tables are summarized below.
Record Type |
Sample-Test-Result |
Sample Parameter |
Location Parameter |
Data Tables |
DT_SAMPLE DT_TEST DT_RESULT |
DT_SAMPLE DT_SAMPLE_PARAMETER |
DT_LOCATION_PARAMETER |
Example of Standard Use |
Analytical data, such as concentration of Sodium |
Photoionization detector (PID) readings |
Legal subdivision (LSD) |
Format Example |
Any that load analytical data |
EQEDD |
EQEDD |
Reference Tables* |
RT_ANALYTIC_METHOD RT_ANALYTE |
RT_SAMPLE_PARAM_TYPE |
RT_LOCATION_PARAM_TYPE |
Unique Criteria for Incoming Records |
SYS_SAMPLE_CODE + Test Alternate Key (TAK) + DT_RESULT.CAS_RN (per sample + parameter + TAK fields) |
SYS_SAMPLE_CODE + PARAM_CODE (per sample + parameter) |
SYS_LOC_CODE + PARAM_CODE (per location + parameter) |
Reporting |
Most reports for Analytical Results (e.g. Analytical Results II), Statistics, and Action Level Exceedance (e.g. Action Level Exceedance II with Parameters) |
Analytical Results II with Location Parameters Sample Parameter reports, such as Sample Parameters (Extra Fields) |
Analytical Results with Sample Parameter (Table) Location Parameter reports, such as Location Parameters (Extra Fields) |
* - for new references like analytes or parameters
Storing test data in the DT_RESULT table will create the most flexible reporting opportunities. However, it may affect report conversion if the results are text-only. Separating queries by matrix can help avoid unit conversion errors. With text-only results, the following may be advantageous:
•Having a defined unit (e.g., 'Unitless')
•If using Method Analyte Groups, adding the new analyte(s) to a group and define the unit there.
•If not using Method Analyte Groups, double-check for any conversion errors with the Result > Unit parameter defined.
The DT_SAMPLE_PARAMETER and DT_LOCATION_PARAMETER options are limited in terms of how many results can be stored per sample or location. Consequently, any re-analyses would be difficult to store here. Action Level Exceedance reports are available for sample parameters and location parameters, but with fewer options than the Action Level Exceedance II reports for analytical values.
While EarthSoft Support can provide information on available options for specific data types, the final decision requires the users' professional judgment.
Copyright © 2023 EarthSoft, Inc • Modified: 01 Mar 2022