Difference between revisions of "Getting started"

From CuraWiki
Jump to navigation Jump to search
 
(35 intermediate revisions by the same user not shown)
Line 1: Line 1:
If you have not installed, please see the [[installation]] page. Otherwise read this one blah blah blah. <br> <br>
+
This page is designed to help teachers and admin staff get to grips with Cura, rather than being a guide to installing and configuring Cura. For configuration, either see the '''[[::Category:Configuration|configuration]]''' category or download the setup document from the '''[[training guides]]''' page. <br> <br>
  
=Creating an admin account=
+
==Introduction==
  
Before creating your admin account, you should download an authenticator. You will need this to log in to Cura in the future, as will all other users. There are many free authenticators available, including one created by Google. If you want to use the Google authenticator, you can find instructions for it '''[https://support.google.com/accounts/answer/1066447?hl=en <span style="color:#ff8800"> on this webpage</span>]'''. <br> <br>
+
Cura is a piece of software designed to manage child protection within schools; you can record low to high level concerns about pupils' welfare and those concerns will automatically be forwarded to another member of staff to be reviewed. A concern could be anything that worries you, even if it seems minor. It is lower level issues that become critical when trying to establishing the start point should a serious child protection situation arise. <br> <br>
  
Once you have installed Cura and have access to an authenticator, you will need to begin creating user accounts. The first account you need to create is the admin account. Go to the Cura homepage, and click the "Register" link at the top right of the page. <br> <br>
+
Cura uses a simple interface that has been designed so that it can be used by school staff to record the relevant details into a secure database. All the subsequent analysis and reporting is completed by the software, so that it requires a minimum of staff time. <br> <br>
  
[[Image:loginscreen.jpg]] <br> <br>
+
==Logging in==
  
You will then need to enter the details for the admin account. '''Please call the account "admin" - this is a strong convention.''' You will also need to enter an email address and password. Once done, you will be given a QR code - scan this with your phone/mobile device or enter the 20 character code into an authenticator. You will need this to log in to Cura and you will not be given another QR code, unless you '''[[delete the admin account]]'''. <br> <br>
+
Cura is a web based application, so you will need to go your school's Cura web page on-line to log in. Someone in school (typically your network manager) will be able to give you the web page address. You will then see the Cura log in page. <br> <br>
  
=Giving yourself permissions=
+
If you are a SIMS user then you can use your SIMS username and SIMS password. <br> <br>
  
Log in to Cura using your admin account and you will be taken to the Users page. From here, you can update permissions, set affinities or reset other users' secret codes. <br> <br>
+
Cura uses two factor authentication, which means you will need a PIN number as well as a username and password in order to log in. To get your PIN number you will need to download an authenticator, which is an app for your phone or tablet. There are several different authenticators available for free via the Play Store or App Store, any of them will work. You should download the authenticator '''before''' attempting to log in. <br> <br>
  
[[Image:adminperms.jpg|right|thumb|The permissions needed by the admin user]]
+
Once you have an authenticator, enter your username and password and click the '''Login''' button. You will then be shown a QR code - scan this with your authenticator or type the 20 digit number into your phone. Your device will then generate a PIN number for you, which lasts 60 seconds. After 60 seconds, the old PIN number will expire and be replaced by a new PIN. <br> <br>
  
Select the admin user using the tickbox on the left of the page, then click the "Open" button at the top right. This will open the permissions window. You should select the following options: <br> <br>
+
==Clearance and severity==
  
*Account manager
+
Staff can record a concern about any child in the school, not just those that they teach or have pastoral responsibility for. Whenever somebody records a concern, they will need to choose a clearance level and a severity level. <br> <br>
*Data importer
 
*Resource manager <br> <br>
 
  
Then click the "Save" button at the bottom of the window. This will update your permissions - now refresh your browser. <br> <br>
+
'''Clearance''' <br>
 +
The clearance level is used to denote how sensitive you think the concern is, and defines which staff members are able to view the information that you record. For example, a pupil who is normally well presented and punctual turns up to school late and looking scruffy. There is no harm in any other staff members knowing about this so you would set a low clearance level (clearance and severity range from 1 to 5). However if a pupil discloses to you that they are being abused at home, then the information is highly sensitive and you should set a high clearance level. <br> <br>
  
=Creating users for staff=
+
'''Severity''' <br>
 +
The severity level indicates how alarming the concern is, and Cura will use this to decide which staff member is going to review the information that you record. For example, form tutors might be responsible for reviewing incidents of severity 1, whereas the child protection officer might be responsible for reviewing incidents of severity 5. The exact structure is decided by your school and you may not know which members of staff are responsible for each severity level. <br>
 +
Use your own discretion - the more worried you are, the higher you should set the severity level. The concern will be reviewed by another member of staff who may change the severity level at a later date so follow your instincts. <br> <br>
  
To import staff into Cura, you will need the staff members' details in an xml file. This file is then imported into Cura, which will create user accounts for all of the staff in that file. <br> <br>
+
==Reviewing information==
  
==Obtaining an XML file of staff details==
+
Cura expects concerns to be reviewed within 48 hours. Any concerns that take longer than this to be given some sort of outcome (arranging a meeting to discuss the concern is regarding as an outcome) will be flagged as late. If you are responsible for reviewing the concerns of staff, then you should check Cura regularly to make sure that you are reviewing concerns in a timely manner. After a staff member has recorded a concern, they will be able to see whether or not it has been actioned. <br> <br>
===If you have SIMS===
 
  
If you use the SIMS database, then you can download this report format: [http://www.tascsoftware.co.uk/wiki/CURA/files/Stafflist.RptDef  SIMS staff report].
+
[[Category:Usage]]
 
 
You will need to import this report into SIMS, then run it. Once you have run the report, you will need to give it a name and format. Choose any name you like, followed by <br>
 
 
 
.staff.xml
 
 
 
So if you wanted to call your report "MyReport", you would name the report "MyReport.staff.xml". You will also need to choose a format - select XML. <br> <br>
 
 
 
[[Image:SIMSexport.jpg]] <br> <br>
 
 
 
===If you do not have SIMS===
 
 
 
*ID
 
*Email address
 
*Title
 
*Forename
 
*Surname
 
*Photo
 
 
 
==Importing the staff details file==
 
 
 
=Setting permissions=
 
 
 
=Affinities=
 
 
 
=System settings=
 
 
 
[[Category:Configuration]]
 

Latest revision as of 13:36, 17 August 2016

This page is designed to help teachers and admin staff get to grips with Cura, rather than being a guide to installing and configuring Cura. For configuration, either see the [[::Category:Configuration|configuration]] category or download the setup document from the training guides page.

Introduction

Cura is a piece of software designed to manage child protection within schools; you can record low to high level concerns about pupils' welfare and those concerns will automatically be forwarded to another member of staff to be reviewed. A concern could be anything that worries you, even if it seems minor. It is lower level issues that become critical when trying to establishing the start point should a serious child protection situation arise.

Cura uses a simple interface that has been designed so that it can be used by school staff to record the relevant details into a secure database. All the subsequent analysis and reporting is completed by the software, so that it requires a minimum of staff time.

Logging in

Cura is a web based application, so you will need to go your school's Cura web page on-line to log in. Someone in school (typically your network manager) will be able to give you the web page address. You will then see the Cura log in page.

If you are a SIMS user then you can use your SIMS username and SIMS password.

Cura uses two factor authentication, which means you will need a PIN number as well as a username and password in order to log in. To get your PIN number you will need to download an authenticator, which is an app for your phone or tablet. There are several different authenticators available for free via the Play Store or App Store, any of them will work. You should download the authenticator before attempting to log in.

Once you have an authenticator, enter your username and password and click the Login button. You will then be shown a QR code - scan this with your authenticator or type the 20 digit number into your phone. Your device will then generate a PIN number for you, which lasts 60 seconds. After 60 seconds, the old PIN number will expire and be replaced by a new PIN.

Clearance and severity

Staff can record a concern about any child in the school, not just those that they teach or have pastoral responsibility for. Whenever somebody records a concern, they will need to choose a clearance level and a severity level.

Clearance
The clearance level is used to denote how sensitive you think the concern is, and defines which staff members are able to view the information that you record. For example, a pupil who is normally well presented and punctual turns up to school late and looking scruffy. There is no harm in any other staff members knowing about this so you would set a low clearance level (clearance and severity range from 1 to 5). However if a pupil discloses to you that they are being abused at home, then the information is highly sensitive and you should set a high clearance level.

Severity
The severity level indicates how alarming the concern is, and Cura will use this to decide which staff member is going to review the information that you record. For example, form tutors might be responsible for reviewing incidents of severity 1, whereas the child protection officer might be responsible for reviewing incidents of severity 5. The exact structure is decided by your school and you may not know which members of staff are responsible for each severity level.
Use your own discretion - the more worried you are, the higher you should set the severity level. The concern will be reviewed by another member of staff who may change the severity level at a later date so follow your instincts.

Reviewing information

Cura expects concerns to be reviewed within 48 hours. Any concerns that take longer than this to be given some sort of outcome (arranging a meeting to discuss the concern is regarding as an outcome) will be flagged as late. If you are responsible for reviewing the concerns of staff, then you should check Cura regularly to make sure that you are reviewing concerns in a timely manner. After a staff member has recorded a concern, they will be able to see whether or not it has been actioned.