Open talllguy opened 5 years ago
@talllguy, sure, we can add a lifecycle field. Let me know when you want to add it, and we can update the scripts/schema in production.
@johnshiu Great. I included a proposal for it in the meeting invite for tomorrow to discuss the other status/tracker we're proposing in the SWMFAC widget scope with some overlaps here.
I reviewed the Excel document, and here are some initial thoughts/questions that we can discuss tomorrow.
Great, I wish you had been on the first call yesterday but it started as more of a widget-scope session.
Widget function is my assumption but that could also be done directly. We know that there is some list of assignments that lives outside of the database. This would aim to bring that back in.
I regret not adding the ETL paths to the proposal. 😃
Interesting idea! I like the thought of a simple SWMFAC for Inspection feature too because it could be filtered in each map. I also have been thinking we could improve performance by switching to map services if they're only using the web map for getting to an inspection. Feature services are slow. That could be another day though.
The purpose is threefold: 1) track the obvious whether it has been inspected or not. 2) track whether a condition that made it not-inspectable in the past is now cleared or not. They want to track if consultants verify that a proposed BMP is still proposed. Right now there is no method to track that. 3) track when something is not inspectable rather than assuming no logged inspections = not inspected. If it wasn't accessible they want to know that.
The lifecycle does not sync. It is just for ETL. The FIELD Insp Status should probably not update NPDES until it is finalized, in that case where something is deleted.
also 7. We got into this a little the other day. It seems that there isn't a solid "season" but rather an ongoing operation. Something we want to discuss in more detail. We thought it would just be what it is, and the last record would be added. 1:M approach is more normalized but may handle syncing not being in sync with an assumed season. I do think there'd be sometimes where they'd want to know the previous inspection status more than one iteration in the past.
@talllguy, when you finish any remaining updates to the schema Excel document, please let me know and send it over. I can get started on the schema changes and ETL scripts.
We've been using the FIRM field on the inspection FC to track the inspection lifecycle, e.g. submitted, deleted, etc.
In March 2019, we discussed adding a 'status' tracker field (see email below). I propose that we call that field a lifecycle tracker because there is another status field that is also in the queue.
Let's discuss the field values to add here.