...
- Create course sites in SmartSite using external Banner Data
- Course sites should be created within a certain time frame (e.g. 3 weeks before term starts, etc.)
- Course sites created should not overwrite existing course sites that had been previously created manually
- Add a certain subset of pages and respective tools to those course sites created, as specified by management
- Enable the ability for rosters to be dynamically generated from the course site (e.g. allow CourseManagementProvider to find members and fill in the rosters dynamically)
- Allow any number of courses sites to be created "on-demand". These are "white list" courses, and would need to be skipped by any future batching mechanisms.
- Allow any number of course sites to be excluded from being batched. This is a "black list" of courses.
- Allow for any number of existing course sites to be updated with a "providerId", so that rosters can be dynamic. This functionality essentially changes the manually created site to act as a provided one to allow members to be updated dynamically.
Functional
...
Specifications
The batching mechanism is a prerequisite for providers to be activated, only because the provider id can then be set and "read" by providers.
Batching is to be done via quartz, by setting a quartz job impl for a given time frame using chron job. Quartz allows us to trigger a job as an administrative user, and can be re-run several times over.
Overview of process and implementation
...