}
		// Validate required string fields are non-empty
		locationName := strings.TrimSpace(record[0])
		if locationName == "" {
			return nil, fmt.Errorf("empty location_name in row %d", i+1)
		}
		directoryPath := strings.TrimSpace(record[2])
		if directoryPath == "" {
			return nil, fmt.Errorf("empty directory_path in row %d", i+1)

		dateRange := strings.TrimSpace(record[3])
		if dateRange == "" {
			return nil, fmt.Errorf("empty date_range in row %d", i+1)
		}

			LocationName:  record[0],

			LocationName:  locationName,

			DirectoryPath: record[2],
			DateRange:     record[3],

			DirectoryPath: directoryPath,
			DateRange:     dateRange,

## [2026-03-19] NOT NULL Constraint Validation in Bulk Import
Added empty-string validation for CSV fields in `bulkReadCSV()` (`tools/bulk_file_import.go`).

Audited all INSERT/UPDATE paths for NOT NULL constraint enforcement. Found one gap:
`record[3]` (DateRange → cluster name) was not validated for empty strings. Also added
validation for `record[0]` (location_name) and `record[2]` (directory_path) which would
cause downstream failures if empty.
**Changes:**
- `tools/bulk_file_import.go` — validate `location_name`, `directory_path`, and `date_range`
  CSV fields are non-empty (with TrimSpace) before building `bulkLocationData` structs