-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support multiple Schedule pages #21
Comments
Should we generalize this to more than two schedules? If so maybe Cam's idea to put the start/end dates in an array (or maybe an object) could work. Something like: morea_start_date: When detected would automatically generate three top-level folders called schedule_Section_001, schedule_Section_002, schedule_003 and the dropdown menu would be populated with the properties of morea_start_date. We can avoid having to add a flag in _config.yml to indicate multiple schedules. |
get_schedule_events() and set_due_dates() are going to get a little hacky or we have to make duplicate methods to enable getting the start/end dates for both schedules. Would it be better to have a flag in _config.yml that creates a second schedule that automatically shifts the start/end dates by +/- n days? |
I like the array idea a lot. I'm not sure if the syntax is:
or
As for the plus/minus idea, it's certainly a timesaver. I just worry that it is too inflexible. Maybe one section needs to deviate from a constant offset sometimes (due to illness or holidays or I dunno what)? |
I've made an initial implementation of multiple schedules and an example in the issue-021 branch. It wasn't necessary but for clarity and consistency, I thought it would be useful to define I didn't know how to handle modules with multiple sections for To use multiple sections first define the sections in
Then for any morea_start_date or morea_end_date add the dates for each section as a hash:
The keys for this are not checked against Try it out and let me know if this seems to address the issue adequately before I make a pull request and document it in docusaurus. |
We are trying the multiple schedules feature on https://courses.ics.hawaii.edu/ics314f23/ and so far no issues have been reported and it seems to serve the purpose. After the semester ends, I will write documentation and suggest merging into the current morea-framework branch. One issue to address is handling default settings in localstorage for clients using multiple MOREA sites |
Works like a charm for 314. Once @dport96 gets around to writing documentation and merging into the morea template repo, I'll close this. |
Currently, Morea does not have good support for courses in which different sections are taught on different days. A typical example is one section on MW and another on TTh. In this case, a single Schedule page is problematic since an assignment will be due on different days depending upon the section. In the past, we have tried:
To provide better support for courses with different sections on different days, Morea could provide a backwards-compatible option that enables multiple schedule pages. In this approach, there would be: a flag in the _config.yml file to enable multiple schedule pages (disabled by default or if missing from the config file). If the flag is present and enabled, then the "Schedule" link in the nav bar will be converted into a dropdown menu with two items. Each item links to a separate schedule page. One schedule page is populated with the module start/end dates and the experience start dates (as is done currently). The second schedule page is populated with module start/end dates and experience start dates as indicated by a morea_start_date2 field in the front matter.
Implementing this involves:
The text was updated successfully, but these errors were encountered: