Overview
AAAAAThe session focuses on the areas within Paradigm where information is recorded that describes the student as a person, including demographic data, addresses, language competency, visa details, and government identifiers. Emphasis is placed on establishing sound data entry practices, including different approaches to answering the important question of what data should be recorded for each student.
Learning outcomes
Demonstrate the ability to create a complete student record
Differentiate between the different types of student addresses and their recommended usage
Distinguish the difference between a minimum system requirement, viable operational requirement, and a complete government record requirement
1. Student
recordsRecords
Duration: 60 minutes
Complexity:
| Status | ||||
|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
Before the academic progression of a student can be recorded within Paradigm, it is first necessary to create a record that describes the student as a person. The focus of this section is to outline the broad range of fields available for the provider to record such information. Special attention will be ascribed to specific sets of fields that are known to cause uncertainty during data entry including irregular names, addresses, and implications of incomplete data for government reporting.
We will also provide guidance on how users unfamiliar with the education sector may choose to resolve the question of what information should be recorded in Paradigm. Irrespective of the advice shared in this section, the provider retains discretion on how they wish to record data within our software.
Topics:
Student numbers
Student status codes
Coding irregular names
Field: Overseas Student
Section: International Students
Section: Entry Requirements
Section: HEIMS
Generating CHESSN
Checking CHESSN balances
Recording USI
Workflow 1, 3, 5 from https://silverband.atlassian.net/wiki/spaces/PKB/pages/985201/Student%2B-%2BSearch%2BAdd%2Band%2BEdit
Resource Links
2. Student Photos
Duration: 10 minutes
Complexity:
| Status | ||||
|---|---|---|---|---|
|
| Note |
|---|
BE ADVISED Allowing students or applicants to upload their own photos may result in inappropriate or undesired images being stored within Paradigm. The Paradigm end user license agreement End User License Agreement (EULA) indemnifies Silverband from responsibility for inappropriate or illegal content uploaded by a student, staff member, or applicant. |
Uploading photos of a student to their record within Paradigm offers many advantages including improving recall of a student, building empathy with students, and for use on system generated reports including the student ID card or class lists. Uploaded files will be automatically resized upon upload if we believe either the file size or dimensions will degrade site performance.
The uploading of student photos is a task performed from the Student Summary screen. Optionally, providers may allow applicants or students to upload photos on their own via the online application portal (applicants) or student portal (students).
Accepted images types: PNG, PJPG, JPG, JPEG, GIF, BMP, GD, GD2
Topics:
Workflow 2 from https://silverband.atlassian.net/wiki/spaces/PKB/pages/985201/Student%2B-%2BSearch%2BAdd%2Band%2BEdit
Resource Links
2. Student Addresses
Duration: 10 minutes
Complexity:
| Status | ||||
|---|---|---|---|---|
|
XXXXX
Topics:
Workflow 1-2 from Student - Edit Contact Info
Resource Links
TCSI Term Address definition https://www.tcsisupport.gov.au/glossary/glossaryterm/Term%20address
TCSI Residential Address definition https://www.tcsisupport.gov.au/glossary/glossaryterm/Residential%20address
2. Student Files
Duration: 20 minutes
Complexity:
| Status | ||||
|---|---|---|---|---|
|
|
Digital files regarding students may be uploaded to Paradigm and stored against a specific student record. Files uploaded in this way may be optionally described with additional meta-data fields and organised into categories to aid with future retrieval. This section will cover the various workflows relevant to uploading new files or managing existing records.
The formation of a single respository or source of truth for each student is a strongly recommended strategy for providers maintaining compliance with TESQA and HESA requirements.
Topics
Workflow 1-5 from Student Files
Resource Links
3. Review
Duration: 10 minutes
Complexity:
| Status | ||||
|---|---|---|---|---|
|
After delivering the main topics, there will be some spare time for open discussion. You can ask any questions you have during the training. We will discuss and confirm a date and time for the next training session.
Topics:
Open discussion including Q&A
Confirm schedule for next training session
Outline outcomes of next session
4. Extension
Duration: 90 minutes
The following tasks are recommended for users to complete at the conclusion of each training session to ensure that the content is understood and to establish familiarity with Paradigm terminology and its user interface.
Any records created during this section may be raised for review at the beginning of the next session to ensure that the data has been entered correctly, for example, meeting the relevant government reporting standard.
Tasks:
Create a domestic student record
Create an international student record
Create all three main types of addresses (residential, billing, and emergency)
Upload a student file
Upload a student image / photo
Generate a student card
OPTIONAL: Customise the sections on the Student Files screen
OPTIONAL: Create a helpdesk ticket to re-brand the student card