At the core of Splashback is Pools, our relational database offering. Pools house datasets with a common purpose, and are also used to assign User Permissions to data.
We believe that data is best managed by those that either have a need, or better a passion, for having access to the information. There is a cost, but usually it is better to create a new Pool within a Tenant, rather than requesting data management from people with little interest in the data being managed. We do our best to make Splashback easy to learn, so new users can be taught how to use the system.
Splashback Data Pools support patterns where values change over time. Understanding the underlying structure will help you get the most out of the Splashback platform. The core structure and relationships are constrained to ensure that data cannot be corrupted, increasing the long-term accessibility of your data.
The core structure of Pool data is as follows:
- Samples - where (or what) is sampled and when.
- Sample Variants - sample subgroups that occurred at the time of sampling.
- Sample Values - the value of every parameter measured for each subgroup.
We then provide a collection of metadata that provide context for each data point:
Do not edit metadata properties unless the change applies to all previously collected samples.
Samples are the core that holds data related to a sample.
|datetime||Date + time the sample was collected.|
|string||Who collected the sample.|
|string||Any comments associated with the sample collection.|
A site contains information about where a sample was collected.
|string||Name of the site.|
|string||Location of the site.|
|string||Description of the site.|
|float||Latitude coordinate of the site.|
|float||Longitude coordinate of the site.|
|float||Northing coordinate of the site.|
|float||Easting coordinate of the site.|
When a sample is taken, it is usually part of a larger program or project. A different program may use the same site increasing the associated knowledge, while also permitting the separation of the data when required for reporting and compliance purposes. The program is also associated with the sample.
Included fields for variant value (if required), Date/Time and a Label. It is common to have a single variant value with only default information set. Usually used for more complex data collection scenarios. Deciding when to use sample variants can be tricky, and feel free to contact Splashback for assistance with this.
The Variant Type describes what is being varied when the different subsamples are being collected. It may be the depth of a soil or water sample. It may even be a duplicate sample, meaning nothing is varied.
Includes fields for the values for each parameter stored.
Every Value has a parameter that defines what is being quantified. The Parameter stores the attributes associate with the parameter such as name, units and shortname.
The laboratory details where the measurement was labeled, Can be 'field' or 'factory' when measurements are observed on site.
The sample method details, used to collect the sample.
The quality details associated with each value. This can be 'Good', 'Moderate' etc, but is better if standards, accreditations are cited for the analysis and collection of the sample (eg. NATA).