Upload
danielle-parker
View
217
Download
0
Tags:
Embed Size (px)
Citation preview
1
SP3.0 Supporting Students
with Information
Ivan Webb2005
2
Background
3
Basic assumptions
1. Key outcomes success and well-being
2. Requires knowledge
3. It is everyone’s job to– Know what is happening
– Work with others to improve what is happening
– Make it easier for the next person to do well
4. And it is the school’s job to make this easier!!
4
Core tasks
Management: • Working with people on ‘the
system’• Strategy = ‘easier first’Operations – everyone’s job1. Know what is happening2. Work with others to improve what
is happening3. Make it easier for the next person
5
Support CycleStudent Support
Information(tools)
Success & Well-being
help ensure
reduce needfor
Improve what is happening
aim
Make it easier for the next person
strategy
inform
6
Supporting Activities: SP3.0
Collecting dataProcessing data informationMonitoring knowledgeResponding planning,
coordinating, informing, contacting, implementing …
Managing documentation
7
Quality of data
Depends on many factors• Currency• Accuracy• Completeness• Significance (meaning)• Usefulness (can be applied & is
timely)• Accessibility• …
8
Improving quality
To improve the quality of the data1. use the data extensively and widely2. engage others with the data in
– gathering– entry– organizing– presenting – considering
9
Today’s Agenda
Qs: What’s working, what’s not and what else?
1. Stories (experiences) to share 2. Integration into school practices3. How are you measuring your progress?4. Histories wrt. other data5. Performance ratings – what’s happening?6. ‘Clever’ coding easier and better7. Information for midyear reporting 8. Controlling access
10
Agenda items (cont.)
9. New in 3.0 10. The future: Version 3.0 & the
DoE11. Language & confidentiality
11
Progress – think first
TO TOP THINGS RIGHT OFF, VINCENT NOW FOUND THAT HIS SIGHT WAS GOING
12
1. Stories to share
Illustrations of• What’s working• What’s not• What else• Insights – ‘things we didn’t know’
13
2. Integration
New or improved:• Awareness• Practices • Terminology• Roles• Documentation• Relationships
14
3. Measuring progress
How do you know its worth the effort?
•
15
4. Histories
A common initial confusionBasic idea snapshot – quick readKey ‘events’ in the (educational) life
of the studentNot just events (incidents, actions)
16
5. Performance Ratings
What’s happening and why?• Categories?• Possibilities?• Integration?
17
6. ‘Clever’ coding
What’s working? •
18
7. Informing Midyear reporting
What’s in the pipeline?•
19
8. Controlling access
• Best done at the folder/report level• Options: discuss with tech support• Read access
– expand slowly, – risks include duty of care
• Write access – be conservative, risks to data quality
Current practices and experiences?
20
9. New in 3.0
• Three views – same data– Support, incidents and monitoring
• Hyperlinking• Fast entry / update /checking• Quick search incidents and actions• Time and place• Contacts
21
Three Views
Go straight to the view you need• Incidents• Support• Monitoring (high support students)
Example
22
Hyperlinking
Hyperlink to any document available thru the network
• Letters, IEPs, applications & reports • Programs on the internet• Rapid access and easy annotation !!, • Reveals/maps existing
documentation• Places sensitive info outside the
database!!Example
23
Linking to other data
• Folder setup – for easy ‘document management’
24
Linking to other data
• Student support files
25
Fast entry / checking
From Main Menu• Pluses
– Faster, easier (ideal for clerical staff)• Minuses
– Limited view – reduced monitoring– Removes entry from view of student– Can promote task over knowledge
Example
26
Search incidents & actions
New from Main Menu• Enter bit of text to find
– Incident description– Incident resolution– Support actions (description)
Example
27
Place and time
• Add a code at the begining of an incident, eg,
“N/1 defiance of duty teacher”• Run last report on report page
Example
28
Contacts
Associate contact details with students• Aides, family, back up• Work arrangements• Temporary
Example
29
10. SP3.0 and SIMS
Situation: negotiated engagementRecommendations1. Upgrade all current users to 3.02. Hold further development of 3.03. Identify and remove bugs4. Capture experiences, issues &
strategies for sharing with DoE5. Work to ensure full functionality in
DoE project
30
Technology and Databases
42
Knowledge & technology
Technology
We continually (co-)construct
and (co-)reconstruct our knowledge*
as we act and interact
Devices
embedded in
Activities
mediate
Practices
organized as utilize
* Knowledge is both situated & emergent