Clean up signal studies, evaluations, and request statuses

[ChristinaTremel]

Location Status

Knack object: locations Field: Location Status

• Existing to Update
  • [x] Not recommended -> Rename to Signal Not Recommended
    • Add Signal Not Recommended status
    • Update records with the Not Recommended status to Signal Not Recommended
    • Remove Not Recommended Status
• Add Statuses
  • [x] Under Evaluation
  • [x] Void
  • [x] Signal Recommended
• Delete Statuses
  • [ ] Recently Received 113
    • Change x records with this status to Under Evaluation
      • Any of these that are requests for PHBs can be archived, but that might be something that needs to happen later
  • [ ] Recommended (funded) 6
    • Change x records with this status to Signal Recommended
  • [ ] Recommended (needs funding) 38
    • Change x records with this status to Signal Recommended

Request Status

Knack object: signal_requests Field: REQUEST_STATUS

• Add Statuses
  • [x] SELECTED FOR STUDY
• Delete Statuses
  • [ ] CONSTRUCTED 24
    • Change x records with this status to SELECTED FOR STUDY
  • [ ] CONSTRUCTION 4
    • Change x records with this status to SELECTED FOR STUDY
  • [ ] DESIGN 2
    • Change x records with this status to SELECTED FOR STUDY
  • [ ] INELIGIBLE 113
    • Change x records with this status to ARCHIVED
  • [ ] NOT RECOMMENDED 113
    • Change x records with this status to SELECTED FOR STUDY
  • [x] ON FLASH 0
  • [x] PENDING_TAKEOVER 0
  • [ ] RECENTLY RECEIVED 142
    • Change x records with this status to UNDER EVALUATION
  • [ ] RECOMMENDED 90
    • Change x records with this status to SELECTED FOR STUDY
  • [ ] RECOMMENDED - NO FUNDING 4
    • Change x records with this status to SELECTED FOR STUDY
  • [ ] REMOVED_PERMANENTLY 3
    • Change x records with this status to ARCHIVED
  • [x] REMOVED_TEMPORARILY 0
  • [ ] TURNED_ON 110
    • Change x records with this status to SELECTED FOR STUDY
  • [x] UKNOWN - misspelled..keep? 0

Study Status

Knack object: studies Field: STUDY_STATUS

• Delete Statuses
  • [ ] NEW 10
    • Change x records with this status to UNASSIGNED
  • [ ] ASSIGNED 2
    • Change x records with this status to IN PROGRESS
  • [ ] DATA COLLECTION 3
    • Change x records with this status to IN PROGRESS
  • [x] FINAL/SIGNED SEAL 0

Study Outcomes

Knack object: studies Field: STUDY_OUTCOME

• Existing to Update
  • [x] RECOMMENDED -> Rename to Signal RECOMMENDED
  • [x] NOT RECOMMENDED -> Rename to Signal NOT RECOMMENDED

Originally posted by @ChristinaTremel in https://github.com/cityofaustin/atd-data-tech/issues/13719#issuecomment-1919480238

[ChrispinP]

Location Status Simple had a duplicate conditional rule and an overwriting rule that I corrected.

If Recommended (needs funding) is removed, these source & display rules for the City of Austin Signal Projects table need to be updated. https://builder.knack.com/atd/amd/pages/scene_1643/views/view_4114/table/source

• [ ] Note from Christina - Location Status filter can be updated to Signal Recommended

For Request Status, this Constructed filter would need to change or be removed. https://builder.knack.com/atd/amd/pages/scene_22/views/view_39/table/settings

• [ ] Note from Christina - Asking Andres if this table needs to be filtered. Thinking about just filtering out the Archived request statuses or adding a filter menu to filter down by status (with the new statuses)

Request Status <> Signal Status connections

• Request Status is pulling in a connected Signal Status value from Signal Status field_491 from Signals object, this is overwriting the Request Status values making the field pointless. If that connected value is blank, Request Status is set to another mc field called REQUEST_STATUS_PRE_CON field_220 which makes it or Signal Status the determining fields. So even if Request Status values are set on the front end, they are constantly overridden with the two conditional rules. There is also an old SIGNAL_STATUS_PREVIOUS field_1680 that is not being used that could be deleted.

• SELECTED FOR STUDY value has been added to both Request Status & REQUEST_STATUS_PRE_CON for now.

• ON FLASH, PENDING_TAKEOVER, REMOVED_TEMPORARILY, & UNKNOWN status removed from both Request Status & REQUEST_STATUS_PRE_CON but they still exist in Signal Status. To prevent records from taking up the Request Statuses we are deleting, they would need to also be removed from Signal Status or not depend and get set to its value. The PRE_CON field is currently used for front end form entry, PHB Study Details, Signal Request Report, PHB Request Ranking, Traffic Signal Bus Stops, PHB Bus Stops, and Traffic Signal Request Ranking and would need to be renamed or replaced.

All items completed are checked above. Any items not checked have records or dependencies that must be addressed before removing. I added the record count next to each item that will need to be updated to a new status.

During my work, I found additional blank page rules here that need to be corrected: https://builder.knack.com/atd/amd/pages/scene_18/rules