Skip to content

NO TICKET: Update well inventory csv feature field names #307

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
chasetmartin merged 2 commits into from
Dec 17, 2025
Merged

NO TICKET: Update well inventory csv feature field names #307

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f137c91
fix: update measuing_person and date_time field names in water level …
chasetmartin Dec 16, 2025
65cdd83
feat: update date time timezone handling in well inventory feature
chasetmartin Dec 16, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 8 additions & 4 deletions tests/features/well-inventory-csv.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,6 @@ Feature: Bulk upload well inventory from CSV
| elevation_method |
| measuring_point_height_ft |
And each "well_name_point_id" value is unique per row
And "date_time" values are valid ISO 8601 timestamps with timezone offsets (e.g. "2025-02-15T10:30:00-08:00")
And the CSV includes optional fields when available:
| optional field name |
| field_staff_2 |
Expand Down Expand Up @@ -125,20 +124,25 @@ Feature: Bulk upload well inventory from CSV
| sample_possible |
And the csv includes optional water level entry fields when available:
| water_level_entry fields |
| sampler |
| measuring_person |
| sample_method |
| measurement_date_time |
| water_level_date_time |
| mp_height |
| level_status |
| depth_to_water_ft |
| data_quality |
| water_level_notes |
And the required "date_time" values are valid ISO 8601 timezone-naive datetime strings (e.g. "2025-02-15T10:30:00")
And the optional "water_level_date_time" values are valid ISO 8601 timezone-naive datetime strings (e.g. "2025-02-15T10:30:00") when provided

# And all optional lexicon fields contain valid lexicon values when provided
# And all optional numeric fields contain valid numeric values when provided
# And all optional date fields contain valid ISO 8601 timestamps when provided

When I upload the file to the bulk upload endpoint
Then the system returns a 201 Created status code
# assumes users are entering datetimes as Mountain Time becuase location is restricted to New Mexico
Then all datetime objects are assigned the correct Mountain Time timezone offset based on the date value.
And the system returns a 201 Created status code
And the system should return a response in JSON format
# And null values in the response are represented as JSON null
And the response includes a summary containing:
Expand Down
Loading