You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As aexternal UserI want * "to be able to identify when a well has no associated aquifer as opposed to being unobserved/unchecked"so that I can appropriately use the data.
Additional Context
Aquifer 1143 was created as a dummy aquifer for the wells that have been checked but couldn't be correlated to any existing aquifers. However, it may mislead users and assume 1143 is a real aquifer. To eliminate the confusion, it is better to replace 1143 with an explanation (text).
As per hydrogeologist explanation: Aquifer 1143 can't be replaced with blank because a blank for aquifer number means the source of this aquifer has not been checked.
Adding a flag as an option for if an aquifer has been checked
Checking all Aquifer 1143 and checking off the flags
Acceptance Criteria
Given I am in the well editing page, When a well has no aquifer number, then I should know whether it is unassigned or unobserved.
Given I have downloaded data from GWELLS when I examine the data, then I can tell which wells are assigned to an aquifer, have no assigned aquifer, or haven't been observed.
The text was updated successfully, but these errors were encountered:
QSu-2023
changed the title
Change of aquifer number field to allow both number and text entries
Change of aquifer number field to allow both number and text entries on the Well Editing age
Jul 25, 2024
QSu-2023
changed the title
Change of aquifer number field to allow both number and text entries on the Well Editing age
Change of aquifer number field to allow both number and text entries on the Well Editing page
Jul 25, 2024
As a external User I want * "to be able to identify when a well has no associated aquifer as opposed to being unobserved/unchecked"so that I can appropriately use the data.
Additional Context
Acceptance Criteria
The text was updated successfully, but these errors were encountered: