Skip to main content

Data Import Checks

To avoid uploading of corrupted or erroneous data, Splashback's data importer provides a range of checks.

tip

Before your first import check that you have a default Sample Variant Type set for the pool. If you have difficulty deciding on this please contact Splashback.

General metadata checks#

  • Sites: Check that you have the required sites for the import to the samples table .
  • Programs: Check that you have the required program(s) for the to the samples table.
  • Parameters: Check that you have the required parameters for the import to the SampleValues table.
  • Qualities: Check that you have the required qualities for the import to the SampleValues table.
  • Laboratories: Check that you have the required laboratories for the import to the SampleValues table.
  • Sampling Methods: Check that you have the required sampling methods for the import to the SampleValues table.

General lookup checks#

Governor will help you identify when lookups are missing, but it is nice when you get it right the first time. To do this make the following checks.

warning

Important - Check lookups are mapped correctly. If a lookup is mapped to the wrong item, it can create a lot of work.

  • If a sample is green, there has been no previous data imported for the sample. If this is true green is okay, but if you have already entered field data for example the sample event, it should be amber, and the data is not aligned, and should not be imported.
  • If a sample is amber, there has been a previous data import for the sample. If this is true amber is okay, but if you have already entered data for the sample event,the data should not be imported.
  • Green and amber variant checks are basically the same as for samples. For example, if the sample variant was a water depth, has this depth (and associated label) been measured before, if it has, it should be amber and if not it should be green.
  • Value duplicates are red as unintended duplicates are not permitted on Splashback. If duplicates are required (and the Splashback team encourages their use), a sample variant type can be created for duplicate samples.
  • Site Lookups: Check that you have the required site lookups for the import. The lookup code for the import should be kept in column B. If this is blank the site Location will be used in column A.
  • Program Lookups: Check that you have the required program lookup(s) for the import.
  • Parameter Lookups: Check that you have the required parameter lookups for the import.
  • Quality Lookups: Check that you have the required quality lookups for the import.
  • Laboratory Lookups: Check that you have the required laboratory lookups for the import.
  • Sampling Method Lookups: Check that you have the required sampling method lookups for the import.

Check imported data#

  • If a sample is green, there has been no previous data imported for the sample. If this is true green is okay, but if you have already entered field data for example the sample event, it should be amber, and the data is not aligned, and should not be imported.
  • If a sample is amber, there has been a previous data import for the sample. If this is true amber is okay, but if you have already entered data for the sample event,the data should not be imported.
  • Green and amber variant checks are basically the same as for samples. For example, if the sample variant was a water depth, has this depth (and associated label) been measured before, if it has, it should be amber and if not it should be green.
  • Value duplicates are red as unintended duplicates are not permitted on Splashback. If duplicates are required (and the Splashback team encourages their use), a sample variant type can be created for duplicate samples.