Skip to content

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

Merged
chasetmartin merged 2 commits into
well-inventory-csvfrom
cm-well-inventory-csv-field-update
Dec 17, 2025
Merged

NO TICKET: Update well inventory csv feature field names#307
chasetmartin merged 2 commits into
well-inventory-csvfrom
cm-well-inventory-csv-field-update

Conversation

@chasetmartin

@chasetmartin chasetmartin commented Dec 16, 2025

Copy link
Copy Markdown
Collaborator

Why

This PR addresses the following problem / context:

  • measuring_person and water_level_date_time field names were updated on the well inventory csv template to reduce user confusion and more easily differentiate the person performing the measurement from the field staff recorded at field event.

@jacob-a-brown jacob-a-brown left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These look good to me. On the backend we're going to need to ensure that the measuring_person is a participant in the field event (that's more of a note for me, I don't think it needs to change here).

This change should also go into the water level csv feature file.

@chasetmartin

Copy link
Copy Markdown
Collaborator Author

@jacob-a-brown @jirhiker @ksmuczynski I updated this feature PR after talking with Jacob to account for the fact that users are entering data into the csv template as timezone naive strings, which are mountain time (the time they record in the field), but the system should handle assigning the proper timezone offset and conversion for storage based on the date.

@chasetmartin chasetmartin merged commit 6f6009d into well-inventory-csv Dec 17, 2025
4 checks passed
@chasetmartin chasetmartin deleted the cm-well-inventory-csv-field-update branch December 17, 2025 16:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants