Skip to main content

Sample Data

Splashback supports the storage of temporal data, that is, datasets where values change over time. Our tools make it easy to analyse and monitor change in your data.

Data Pools#

In Splashback, data is organised into Pools. Pools are collections of Samples. Samples make access management simple and help you keep your data organised. We recommend keeping separate pools for separate projects and applications.

We belive data is best managed by those who use that data. By keeping data organised in pools according to project, management of data can be performed by users most familiar with that data at a project or application specific level. This facilitates better data managment practices and provides intuitive lines of accountability.


Samples are the units of data

The core structure of Sample 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:

Samples are the core that holds data related to a sample.

dateTimedatetimeDate + time the sample was collected.
takenBystringWho collected the sample.
commentsstringAny comments associated with the sample collection.

Sample Variants#

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.

Sample Variant Types#

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.

Sample Values#

Includes fields for the values for each parameter stored.