Objective
...
You have already read Introduction to Rapla
You have already installed Rapla as per Accessing Rapla
You have a valid Rapla user account
Key terms and concepts
| Info |
|---|
NoteBoth admin and non-admin user privileges are able to create events in Rapla. Only admin users can edit events created by other users. |
| Note |
|---|
Be advisedThe user needs to make sure they are not highlighting anything on the left-hand side of the menu bar. This can cause Rapla to think that you are creating any events against that resource. Hence, you might see a warning message. |
...
| Warning |
|---|
WarningParadigm makes an important assumption that ALL sessions where the Session Class is not set are compulsory enrolments. The user |
The Session Class is used to limit what a user may select when enrolling into sessions. The restrictions work in two layers
...
The use of Session Class simplifies the process of selecting a suitable, non-clashing set of sessions. It is especially useful when there is a need to define a pairing or set of sessions consisting of multiple Session Groups where you want to enforce predefined session enrolment combinations. Session class number starts at 1, it increments by 1. Session class number defines a set of sessions across multiple session groups.
Session Group
| Info |
|---|
NoteWhen the Session Class is set but the Session Group is blank, then the Paradigm will assume there is an implicit Session Group of 1. |
The Session Group is used there there are multiple Session Types associated with the same Scheduled Unit. Assigning a Session Group will visually group the sessions when viewed from within Paradigm. When used together with Session Class it is possible to prevent users from enrolling into more than one session from each defined Session Group. Examples of common session group types include lectures, tutorials and and workshops. The Session Group field should start at 1 and be incremented by 1 as required.
...