Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
When you set up a well initially, you can put in the current pump intake setting. Is there a way to revise the entry or add this info later when you get the data or the pump has been moved? We can't find how to do this. Thanks
Comments
Comment #2
robertwb CreditAttribution: robertwb commentedErinn - is this a per-well setting I presume?
Comment #3
robertwb CreditAttribution: robertwb commentedMarking this as critical since defining well pump setting is needed for technical evaluations.
Comment #4
c_thomas CreditAttribution: c_thomas commentedErinn - You are able to edit the Pump Setting on the Well Construction page for all wells currently. The Pump Setting field is in the first table (Pump Settings), where you can click the pencil button to edit/change an existing pump setting or the + sign to add one that doesn't exist.
Example Well Construction Page: dh/?q=gwp-well-dash-construction/1126
If this is not the Pump Setting that you mean or would like this in a different location for ease of use, let us know.
Comment #5
jkleiner CreditAttribution: jkleiner commentedChecking back on this. I think we ned confirmation, but it looks like you all need to be able to add individual well limits to a given permit and currently are unable to do so. Please confirm and we will get cracking.
Comment #6
jkleiner CreditAttribution: jkleiner commentedMP since we will need this feature for both wells and intakes.
Comment #7
robertwb CreditAttribution: robertwb commentedBumping this so we can get feedback from Erinn on #2 -- do we need to be able to set this per well? Or do we just need a single limit attached to the permit?
Comment #8
robertwb CreditAttribution: robertwb commentedComment #9
robertwb CreditAttribution: robertwb commentedErinn - we added the ability to set max pump setting to the "Construction" page a while back and I think that we discussed this on another issue, but I just wanted to verify before I close this out -- tentatively marked as fixed -- please re-open if that is not the case.