Bulk Importing

Bulk importing enables rapid data ingestion but requires adherence to specific rules. Ensure data accuracy and proper formatting to avoid errors.

General Guidelines
  • Columns with dropdown options are optional but recommended for accurate data linking.
  • Most fields are case-insensitive, except where noted (e.g., Assay linking). Values must match exactly (no partial matches unless specified).
  • Some options (e.g., Lithology, Alteration, QCSampleType, LandHoldingType) are defined at the project or company level by users.

Models with Point Geometry (PointSample, Archaeology, Field Observations, Structural Measurements, DrillCollar):
When importing geometry, if the field 'lat/northing' AND 'lon/easting' are selected on two different fields then the geometry will be set from these fields. If 'elevation' is selected as a dropdown on a field as well, this will be incorporated into the geometry, otherwise it is set to zero. If either 'lat/northing' or 'lon/easting' are not set, AND 'geometry' is set to a colum with text including 'POINT' e.g. POINT (515384.47 5283298.150), then geometry will be set from that field. If the POINT has 3 dimensions, e.g. POINT (515384.47 5283298.150 100), the incorporated elevation will be used, otherwise it will be set to zero. 

Model-Specific Import Rules

Assay-Related Models (PointSample, DrillSample, QAQC)

To link assay-related data to an assay:
  • Option 1: assay_name Column: Include a column with the assay name and select the assay_name dropdown in the software. The software links the data to the corresponding assay in the active project.
  • Option 2: Sample Name Matching: If no assay_name column is provided, the software attempts to link the sample to an assay with the same name in the active project.

Assay
  • The software attempts to link assays to PointSample, DrillSample, and QCSample instances by matching names.
  • Assay name matching is case-sensitive.

QCSample
  • Optional Column: sample_type.
  • Options: Defined at the company level (e.g., user-defined QCSampleType names).
  • Rules:
    • Values must match a QCSampleType name exactly (case-insensitive).
    • Unmatched values will not be set.

PointSample
  • Lithology and Alteration: Select lithology or alteration in a dropdown column to link to project-level Lithology or Alteration entries. Matches must be exact (e.g., "gran" will not match "granite"; "Granite" matches "granite").
  • Assay Linking: Follows the same rules as Assay-Related Models (see above).
  • Available Sample Types:
    • Soil
    • Rock Chip
    • Outcrop
    • Dump
    • Stream Sediment
    • BLEG
    • Other

DrillSample
  • Assay Linking: Identical to PointSample (see Assay-Related Models).
  • DrillCollar Linking: Use a bhid dropdown column to link to a DrillCollar. 
  • The name must match exactly (case-insensitive).

DrillLithology and DrillAlteration
  • Linking follows the same rules as PointSample for Lithology and Alteration.

DrillCollar
  • Optional Columns and Options:
    • hole_type: Diamond Core, Reverse Circulation, Direct Circulation, Percussion, Sonic, Trench, Other.
    • hole_status: Completed, Abandoned, Planned, In Progress.
    • hole_size: AQ, BQ, NQ, NQ2, HQ, HQ3, PQ, Other.

LandHolding
  • Optional Column: land_status.
  • Options: Defined at the company level (e.g., user-defined LandHoldingType names).
  • Rules:
    • Values must match a LandHoldingType name exactly (case-insensitive).
    • Unmatched values will not be set.

Structure and DrillStructure
  • Optional Column: feature_type.
  • Options:
    • Fault
    • Bedding
    • Foliation
    • Lineation
    • Shear Zone
    • Vein
    • Joint
    • Other

Archaeology
  • Optional Column: feature_type.
  • Options:
    • Cabin
    • Trash Dump
    • Collapsed Adit
    • Open Adit
    • Collapsed Shaft
    • Open Shaft
    • Other

FieldNote
  • Lithology and Alteration: Follows the same linking rules as PointSample.

Best Practices
  • Use dropdown options for better data integrity, even though they are optional.
  • Verify that all dropdown values match predefined options exactly, especially for case-sensitive fields like Assay names.
  • Use descriptive column names to avoid confusion (e.g., assay_name, sample_type).
  • Test imports with a small dataset to ensure correct linking before processing large datasets.