Change Details

Once the new scheduler pattern is deployed. We'll need to align the origin_visit_status data records to actually have their type filled in. That means: - modify the schema to add the visit_type column - sql file to migrate the data from origin_visit to origin_visit_status - Check impacts on storage clients (i.e. loaders, if any, that might have already been dealt with)

Once the new scheduler pattern is deployed. We'll need to align the origin_visit_status data records to actually have their type filled in. That means: - modify the schema to add the visit_type column - sql file to migrate the data from origin_visit to origin_visit_status - ~~Check impacts on storage clients (i.e. loaders, if any, that might have already been dealt with) ~ (already dealt with indeed)

Once the new scheduler pattern is deployed. We'll need to align the origin_visit_status data records to actually have their type filled in. That means: - modify the schema to add the visit_type column - sql file to migrate the data from origin_visit to origin_visit_status - ~~Check impacts on storage clients (i.e. loaders, if any, that might have already been dealt with) ~ (already dealt with indeed)