SAMIS Integration functionality
The SAMIS integration (or block) is a tool that gives staff the ability to manage SAMIS cohorts within their Moodle courses. Typical uses might include:
- Enrolling multiple SAMIS cohorts on to a single Moodle course
- Specifying a date when a SAMIS cohort should be unenrolled from a Moodle course. For example, you may want students studying a unit in semester 1 to have access to the relevant Moodle course until the end of semester 2.
Any changes that you have made within the SAMIS interface, such creation of mappings to amend Participant Lists within a Moodle course, will normally be updated within 24 hours during the Moodle-SAMIS synchronisation process.
Automated synchronisation between Moodle and SAMIS only takes place Sunday through to Thursday. This means that the student memberships associated with mappings created on a Friday or Saturday, will not be reflected in Moodle until the early hours of the following Monday morning. If there is a need to synchronise an individual course sooner however, the SAMIS block has a function that will enable this.
Cohort mappings are typically referred to as either default or bespoke.
- A default mapping is one that is applied automatically to a course, having been identified as the relevant SAMIS code for that unit. This means that if your Moodle course represents a SAMIS unit or programme (and has the relevant SAMIS code) that the corresponding cohort of students will be automatically enrolled - assuming they are correctly registered in SAMIS.
- A bespoke mapping however is user defined - enabling additional (non-default) cohorts to be added to the course.
Cohorts will generally be added or removed according to the relevant period slot code (start and end dates) listed in SAMIS, though the Technology Enhanced Learning Team may occasionally extend these periods slightly as staff have reported that setting an earlier start date and slightly later end date for the period acts as a useful buffer to cohort management.