Every Meeting

• Review issues with Done status
  • Close and move to Reviewed (assuming no follow-up work discovered during review)
• Review issues with Blocked status

Meeting: 2024-10-7

• Aquarius integration update (Craig, Katie)

  • Question wording update from Jacob
  • Need to review / update column aliases (#178)

• District Monitoring migration status (#188; Katie)

• Arcade research (#191; Sarah / John / Sam)

• Ticket #194: Changes to the survey and new battery type

Tasks to Get to Production

• Deploy Survey123 to field devices
  • Upgrade field laptops to Windows 11
    • Complete except for one machine that doesn't support Windows 11
      • Running Windows 10
      • Meets the current business need, because we're no longer using Windows Subsystem for Android
• Update data in Aquarius > import to geodatabase:
  • Measuring Points (target last week September)
  • Photos
  • New equipment / serial numbers
    • Several dozen items in coming month(s)
      • Equipment has arrived
      • Needs to be installed
    • Ideally, update District Monitoring spreadsheet > import to clean geodatabase before production
• Procedure for propagating Aquarius changes to geodatabase
  • Photos
  • New information migrated to Aquarius from District Monitoring spreadsheet
• Procedure for propagating survey data from geodatabase to Aquarius
  • Finish scripts (this week?)
  • Review surveys before sending to Aquarius
    • Discharges need to be reviewed in other software first
      • Possibly edited
      • Cannot be edited once it's loaded to Aquarius
      • Notify Katie that new discharge is available for review (#186)
• *** Move District Monitoring spreadsheet to geodatabase ***
  • What is required?
  • How do we do this?
    • Sarah working on Workforce proof-of-concept
  • Some of the spreadsheet data is moving to native Aquarius
• Training
  • Slow rollout?
• See Future section below for survey update related questions

On Hold

• #96 Continue reviewing as a group
  • Workflow diagram annotated with where we left off

Future

Production Updates to Survey / Data

• Continue discussion about workflow / automation for "republishing" survey when something changes:
  • Survey will need to be modified by GIS staff and republished from Survey123 Connect application under these circumstances
    • New field added to database
    • Domain updated in the database
    • Question in the survey needs to be reworded or modified
  • When a new location gets added or modified in the database the following changes will need to occur:
    • Measuring Point (CSV) to be updated via a manual upload or updated with a script
    • Photos for the location to be added manually via a survey or copied over with a script

Questions

Currently:

• What is the human workflow for making changes to the source data
  • E.g. Field user finds MP is underwater so new, higher MP needs to be established
    • Who tells who what?
    • How does the new MP get created?
    • When does Aquarius get updated?

Once the survey / geodatabase is in production, we will have new dependencies because the people / system for changing the source data will probably be different than those for republishing the survey:

• How does the survey publisher know that something has changed, such that the survey needs to be republished?
• By what mechanisms do the notification and republishing happen (e.g. manual, manually-triggered automation, full automation)?
• What do Survey123 users need to do when an update has been made?
  • "Structural" - E.g. new Measuring Point (i.e. new CSV)
  • "Data" - E.g. updated Data Logger Serial Number