s2s workshops 2004

1
s2s workshops 2004

• DBA and transfer functionality
• Lost pupils and Messaging functionality
• Lost pupils best practice
• Please raise issues at appropriate times

2
2004 future functionality

• NAA (QCA)
• KS2/3 TA and SAT transfer
• Reduced CTF format
• KS3 English diagnostic data
• Welsh screens
• Police, Social Services, Health, Dental Service,
  Connexions

3
QCA
Sending school
Receiving School
1 upload file 6 delete file
2 Email
3 check data 4 download file 4a reject file
5 email file received 5a email file rejected
Secure Site
DfES
3 view files 4 download file
3 view files 4 download file
XXXXXX MMMMMMM
Sending LEA
Receiving LEA
Database for records without a destination
school XXXXXX or moved to an independent or
school outside England MMMMMMM
4
Handbooks

• School version
• Will be published and available through DfES
  publications
• LEA version on web only

5
Three types of LEA Role

• 1. Database Administrator (DBA) able to add and
  edit LEA users and schools
•  
• 2. Transfer Files able to transfer files,
  download copies of files sent to schools, produce
  reports, etc
•  
• 3. Lost Pupils able to search the lost pupils
  database and produce reports on lost pupils

6
Four types of LEA users

• 1. Database Administrator (DBA)
•  
• 2. Transfer Files
•  
• 3. Lost Pupils 
• 4. Transfer and Lost Pupils (2 and 3)

7
DBA

• Key role
• Maintaining users and schools
• ? Should schools be able to maintain own details
  on s2s

8
LEA Transfers

• PLASC, CTF, CFR, FSP and Exclusions
• Generic ZIP
• Admissions (2005)
• ? introduce user for each type/generic user

9
DBA

• Demonstration

10
Lost Pupils

• Database of disappeared pupils (XXXXXXX) and
  moved outside maintained schools (MMMMMMM)
• LEA can search and download
• Print a list or create a csv file of pupils
  uploaded by schools in the LEA

11
How to remove found pupils

• Check against PLASC in 2003 only 200 of 2000
  records were matched
• ? How to ensure schools that have uploaded a file
  request a download if destination becomes known
• ? How to ensure schools receiving a child ask LEA
  to look for CTF

12
Way forward

• Any extra functionality needed
• IRT database developments
• Processes in LEAs and across LEAs
• Access to other sources of information
• ? Can the secure messaging service provide a
  better way to track pupils than general emails.

13
Demonstration

• Lost pupils
• Messaging

14
New opportunities for s2s

• Sharing information with external agencies -
  following local protocols re data exchange

15
Examples of Agencies

• Health
• Connexions
• Social Services
• Police
• Dental Health
• QCA
• Software Houses

16
Examples of Data for Sharing

• Health to LEA of 2/3/4 yr olds
• LEA to Health list of pupils by school
• LEA to Dental Health list of pupils by school and
  specific year groups
• LEA to Social Services performance data for
  Children Looked After
• LEA to QCA Teacher Assessments for KS2 KS3
• NCER to LEA GCSE performance data
• School/LEA to Software house Schools data

17
Issues to be addressed

• Agencies would need a reference Agencies could
  be given Edubase references or a standard set
  which would be prefixed with your LEA number eg
• 8888 Health
• HLTH Health
• What happens when one LEA deals with multiples of
  the same Agency?
• Not a problem if one Agency deals with more than
  one Authority they only need the one reference
  and share this reference with other Authorities

18
Groups

• Local clusters
• 2 people from an LEA go into 2 groups or 1
• Real consultation use knowledge and expertise
  to develop a practical solution
• Problem has existed previously no national data
  or policy