Currently, when a MarkUs course is created via a Canvas LTI launch, the start date and end date fields remain unpopulated. We need to automate the population of these fields.
By default, the system should apply a standard 4-month term duration. Dates should span from the first day of the starting month to the last day of the final month.
Example: For a Fall term starting in September, the range would be September 1st to December 31st.
Customization
Since different institutions may follow unique academic calendars, this logic should not be hardcoded into the LTI controller. Instead, the date calculation should be handled in the LtiConfig module.
Currently, when a MarkUs course is created via a Canvas LTI launch, the
start dateandend datefields remain unpopulated. We need to automate the population of these fields.By default, the system should apply a standard 4-month term duration. Dates should span from the first day of the starting month to the last day of the final month.
Example: For a Fall term starting in September, the range would be September 1st to December 31st.
Customization
Since different institutions may follow unique academic calendars, this logic should not be hardcoded into the LTI controller. Instead, the date calculation should be handled in the LtiConfig module.