Census workbook upload should create Survey record if required [2020:H]
Issue #924
resolved
If the survey does not exist, provide feedback to the user that the record will be created when the upload is processed.
Comments (5)
-
reporter
-
@Brian Lewis ok. Anything that makes managing of this required new records every year is a good solution. The things is, Survey table (and some others like SurveyYearTeacherQual) require user input which is not ideal. Users will likely forget about these. We need a way to make this super simple. We have a working solution with SurveyYearTeacherQual I think. How about a procedure that would create the new records based on the previous record. So if previous record svyCensusDate is 2019-12-31 00:00:00.000 then on 2020-01-01 create the new survey record based on the previous one. In short, we don’t want to have to remember to create this record. A notification to the user in the UI with a place to create the record perhaps? But that opens up a vector for miss configuration. I’m open to ideas here but it has to be super simple, that’s the only requirement:)
-
reporter
- changed status to open
-
reporter
As a step towards this, the user cannot proceed with the census workbook rollover if the new survey year is not in place. That means the correct year is already in the workbook, and, the census date in the workbook comes from Survey table so is guaranteed to align with the value used to census load.
-
reporter
- changed status to resolved
- Log in to comment
There is a chicken-and-egg situation here with
#929: the census date used for age calculation is now drawn from the Survey table ( refreshed on the lists page). this means that the Survey record for the year must be in place when the workbook is refreshed ( ie all lists are refreshed through their database connections) , ideally before the workbook is distributed.In that case, we would not find the situation where the Survey record does not exist?