My initial read on this is that it could be considered major, but depending on what what we set to delineate between the two levels we may shift to minor. Please feel free to amend the list of tasks.

Problem/Motivation

Drillers/System providers often make minor amendments to GW-2 forms after initial submittal to VDH. These updates need to be reflected on the printable form, and also to synch properly with already created features in the well/facility/interval data tables.
A simple webform amendment is insufficient because it 1) won't be reflected in the GW-2, it would have to be an attachment, and 2) we do not currently have particularly robust update integration between webform and entities - although it works, it has only been tested sparsely and would likely involve some needed enhancements that would be time consuming.

Proposed resolution

  1. Create property widget pages to permit direct editing of properties.
  2. Create handler to log a submittal and/or time series records to mark the update request.
  3. Create permissions functions to lock records for editing after specified time period.
  4. Create new version of GW-2 printable form to use properties instead of Webform submittal component data.
  5. \

Remaining tasks

  1. Develop list of logical edit blocks for creating prop widget or editable views screens.
  2. Create property widget pages or editable Views to permit direct editing of properties by block.
  3. Update variable Vocabularies to enable more efficient creation of edit blocks and groupings

  4. Prop Section/eView #1

    Prop Section/eView #2

  5. Update variable Vocabularies to enable more efficient creation of edit blocks and groupings
  6. Develop page to act as launching screen for modification requests (may be integrated with printable form?)
  7. Create handler to log a submittal and/or time series records to mark the update request.
  8. Create permissions functions to lock records for editing after specified time period.
  9. Create new version of GW-2 printable form to use properties instead of Webform submittal component data.
  10. \

User interface changes

  • Entirely redone GW-2 printable form
  • Launching page to handle update requests
  • Add pages to permit logically grouped edits

API changes

n/a

Data model changes

n/a

Comments

robertwb created an issue. See original summary.

c_thomas’s picture

Issue summary: View changes
c_thomas’s picture

Issue summary: View changes
robertwb’s picture

Note - you may already know this, but you have 3 property edit widgets on the same edit page, and you can only have one single edit widget per page, or the group edit widget if you like. The limitation of the group edit widget is that you cannot include fields (like text comments), but all properties (propcode, propname, propvalue, startdate, enddate) are cool in the group widget. The single widget DOES allow proptext (and any other fields you attach). See the following for an example of the URL coding to enable a single page to edit any property in a group: http://deq2.bse.vt.edu/d.beta/?q=ows-registration-wsp_plan_locality-proj...

c_thomas’s picture

Thanks for that clarification. I do know that at the moment. I was monkeying around with things on Tuesday morning and just haven't been able to get back to it. Getting that cleaned up and working better is my goal today.

robertwb’s picture

Issue tags: +gw2