Single Event
With Conflict
With Exceptions
With Appointments
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. |
Explanation of Standard Event Types
Sessions (Lecture, tutorials, etc.) - most popular one, used for synchronising with Paradigm
Meetings
Exams
Student bookings
Auditions
Explanation of Standard Event Attributes (Fields)
Take the most popular event type - Session as an example, please see the following common attributes:Overview
Now that you have created users, added new resources, and time Periods in RAPLA, its now time for you to create sessions or events. Creating events in RAPLA can be relatively straightforward if you are already familiar with the interface and you have experimented with the look and feel of the environment. This knowledge article will guide you with the basics of creating sessions or events in RAPLA, the possible functionalities you can use which could be relevant to your business or institution (Exceptions, Appointments, Groups and Class – which will be discussed further in the Advanced section of this documentation), and how to deal with conflicts.
Event Types
NOTE: The event types mentioned below are the default event types we’ve configured for your RAPLA application. These are highly customisable. Please feel free to raise a ticket or contact our Support Team if you have any questions or clarifications on the event types mentioned below.
Student Booking | |
Generic Meeting | |
Generic Event | |
Paradigm Session |
Paradigm Session Required Fields
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). |
WorkflowWorkflow
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. |
How to create a single event on
RaplaRAPLA
You will use the left mouse (drag and drop) to mark the time period for the specific appointment you want to. The marked rows are highlighted in pale blue (as below).
Right click a new context menu appears, then select the suitable event type, ranging from a session, generic event, meeting or student booking. In the below instance, it is an example of creating a new Event (Paradigm Session). Note there are three sections:
The upper section: confirm the Event type you want to create, fill out these fields that are critical for integration between Rapla RAPLA and Paradigm: Unit Codes (E.g. FIT9130), Unit Name, Campus (if applicable), Delivery mode, Department.
The middle section shows the detail of the appointment: you will need to fill out the start and end date, select whether it is a single event or recurring one. You can even exclude public holidays or semester breaks if applicable (Refer to below scenario 2).
The bottom section shows the resources you want to allocate to, add the resources from the left hand side to the right section by either double clicking or click on the resource and go to click Add button
Click on
Save button.
Expand | ||
---|---|---|
| ||
This is one of magics that Rapla RAPLA will show you next... While you follow the above steps of creating events/appointment, when you reach to the bottom section - resource allocations. Rapla RAPLA tells you the available resource by having a green icon at front. The red cross icon means the resource has been taken for another event. So you should try to avoid allocating it again. |
Expand | ||
---|---|---|
| ||
|
You should follow the instruction of Scenario 2 to create a recurring events first (i.e.appointment 1)
After you added the exception date for the first appointment (as per the below image: Exceptions showing 1 in red)
Click on New button under the Appointments section to create a 'No repeating' event (i.e. appointment 2)
At Resource Allocation section, you need to assign resources (e.g. staff, rooms) to each appointment individually.
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.
Resources have been color coded and allocated to
Appointment 1 and Appointment 2.
Introduction to RAPLA | 1. Install RAPLA | 2. Get Familiar with the RAPLA User Interface | 3. Create Users | 4. Add Resources: Facility, Equipment, Staff | 5. Create Time Periods | 6. Create Sessions or Events | 7. Publish RAPLA | 8. Synchronise Sessions to Paradigm