Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Objective

...

Key terms and concepts

Info

Note

Both 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 advised

The 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.

Explanation of Standard Event Types

...

Field Name

Description

Unit Name

The name of the unit offers by the Institution. The same one matches the record in Paradigm.

Unit Code

The unit code offers by the Institution. The same one matches the record in Paradigm.

Session Type

Subject to each institution to define their session type (e.g. class, tutorial, lecture)

Campus

Subject to each institution to define their campus (e.g. Melbourne, Sydney)

Minimum Participants

The minimum number of participants for running the session (e.g. 5)

Maximum Participants

The maximum number of participants for running the session

Faculty/Department

Subject to each institution to define their faculty/department (e.g. Faculty of Art)

Session Group ID (Group number)

A group of sessions from which a selection is made during the enrolment (aka. it is an enrolment choice).

Session Seq ID (Class number)

A set of students who attend the same session together under one scheduled unit (Lecture).

Session Group and Session Class

Info

Note

It is up to each provider or institution to allocate an appropriate ID

...

Do not change

...

Session Seq ID

...

when populating the Session Class or Session Group fields.

Note

Be Advised

Carefully consider the following definitions to determine if your institution requires the use of the session group and class fields. If these features are not required then it is appropriate to leave the field(s) in blank.

Session Class (or session sequence ID)

Warning

Warning

Paradigm makes an important assumption that ALL sessions where the Session Class is not set are compulsory enrolments.

The Session Class is used to limit what a user may select when enrolling into sessions. The restrictions work in two layers

  1. Selecting a Session Class will also select all other sessions that share the same Session Class value

  2. When a Session Group AND a Session Class are both set, then the user must select one and only one session, from each group

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.

We recommend starting the Session Class value with the digit 1 increment it by 1 for each new Session Class.

Session Group

Info

Note

When the Session Class is set but the Session Group is blank, then the Paradigm will assume there is an implicit Session Group value of 1.

The Session Group is used when 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.

We recommend starting the Session Group value with the digit 1 increment it by 1 for each new Session Group.

Workflow

How to create a single event on Rapla

...

Expand
titleScenario 3: Creating repeating events along with an once-off event
  1. You should follow the instruction of Scenario 2 to create a recurring events first (i.e.appointment 1)

  2. After you added the exception date for the first appointment (as per the below image: Exceptions showing 1 in red)

  3. Click on New button under the Appointments section to create a 'No repeating' event (i.e. appointment 2)

4. At Resource Allocation section, you need to assign resources (e.g. staff, rooms) to each appointment individually.

5. Currently all resources have been set to every appoint, you can change it by click on 'Every appointment'. It opens up more options to each appointment.

 6. Resources have been color coded and allocated to Appointment 1 and Appointment 2.

Image RemovedImage Added

Further Reading

...