You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Statically, based on the last added year in the configuration table. Year X in database corresponds to academic year X-(X+1). Year 2024 is September 2024-August 2025
Default route is determined based on method 1 and won't show the appropriate information after September if data were defined in the 8 first months of the year. Year may even not be defined in the configuration table.
Solution
One of the two methods should be implemented.
Either dynamically only: In this scenario, the available academic years for filtering are based on what's available in the data.
Either statically only. In this scenario we manually define when we want to change the academic year. It is probably the most flexible implementation. An alternative (hybrid) implementation is to only keep track of the current year and generate the filters based on what years are available in the data.
The text was updated successfully, but these errors were encountered:
If I want to do this statically, how does the current year's storage work? Because when an admin adds a new year, it shouldn't affect the current year of other users. Do I need to create a button for adding a new year and another button for moving on to the next year?
You can support adding a new year that is not the current one and let the admin select the current year in case of a static method. In all case, the current year should be determined using one method only.
Issue
Current year is currently determined using two different methods:
ictm-teaching/util.py
Line 4 in 56cfd84
ictm-teaching/db.py
Line 130 in 56cfd84
Default route is determined based on method 1 and won't show the appropriate information after September if data were defined in the 8 first months of the year. Year may even not be defined in the configuration table.
Solution
One of the two methods should be implemented.
The text was updated successfully, but these errors were encountered: