Enterprise & Vertical Reporting. Challenges and Solutions

Transcription

1 Enterprise & Vertical Reporting Challenges and Solutions

2 The Challenge: How do you design a real time data collection system that is scalable for states and districts that is easy to use and extendible for reporting?

3 Data Collection Challenges Data is in motion: Students are constantly enrolled and dropped, change courses and enter and exit programs. Districts/states need the ability to see information within minutes of entering, modifying, or deleting the data. The entire process should be invisible to users. Errors need to be corrected at the source for increased data accuracy.

4 In the Beginning

5 Stakeholder Challenges Project must have an executive sponsor or at least a data champion. Need to have staff dedicated to supporting the deployment should not just depend on the vendor to do it all. Project Manager-District/State and Vendor Create a project team to promote buy-in Conduct regular status meetings Create a project scope and stick to it. Scope changes can impact your production dates. Determine what documentation is needed up front.

6 How do districts give permission to vendors to pass and receive data is not the ODS? How does a district notify if they want to drop out of a data collection activity? Example Privacy Challenge

7 Key Considerations Determine version of the specification Don t keep switching vendors have their own development processes Other standards required? EdFi CEDS Create a SIF Profile Document Determine if you need extended elements Notify your SIS vendor! Communicate early and often Project Manager-District/State and Vendor Create a project team to promote buy-in Conduct regular status meetings

8 Basic Data Collection Components

9 Applications Student Information System SIF Agent REST API ODBC/CSV Student Identifiers [writeback] Assessments Multiple sources No SIF agents to dump data Other sources: Photos IEPs, AYPs, OMG

10 The Data Collection Process A SIF 2.x agent isn t always the best way to gather data to move data to an ODS Paradigm Shift Example: Food Service is a subscribing application What data do you need to collect? How do you get that data into an ODS?

11 Operational Data Store Gathering data via SIF can help normalize data Feed data to an ODS that is SIF aware Real Time data is always in motion Need a place/method for snapshots or historical data State reporting is date driven Importance of SIS vendor collaboration

12 Real time data is not enough in the education ecosystem. To make this data truly effective validation of the data is added to the mix. Gathering the relevant data from all of the various sources can be challenging. Entry/Exit Dates Photos Data Validation Challenges Attendance

13 Data Validation Process Create a SIF profile to document the Objects and elements you want to collect. Example Compare with data you currently collect [state level] Throw out the stuff you really don t need Determine mandatory and optional requirements Make sure the data you collect is clean Entry exit dates Grade codes LEA codes State codes Districts can mirror state data collection business rules

14 Data Error Handling There are different ways of handling errors: Staff can review a report and update their SIS Vendors can be asked to assist Key to data clean up is to correct the error in the SIS so data changes can flow to the ODS Create a best practices document for your users. What errors are common problems? Can be free form fields or data entry in field that are not validated by the vendor

15 What do you want to get out of it? User Reports Can be created with existing tools using data from ODS Create a template or requirements document for the creation of new and existing reports Meet with your stakeholders to determine their expectations Know the data source

16 Example: EIS

17

18

19

20 What do you want to get out of it? Portal Access to Instructional applications Single-Signon Identity management

21 Example 2: Illinois Shared Learning Environment [ISLE] Backend Interfaces & Services Tenants (School Districts) Data Collection and Validation) End-User Facing Interfaces Tenants (School Districts)

22 IlliniCloud Acting as a K12 federation operator and service provider, the IlliniCloud established three foundational services for the K12 community: Data Services Identity Services Presentation / Portal Services Lowering the Bar for Adoption: services require little to no modification of existing data and identity processes in the districts

23 incommon Google 4 Edu Other Service Providers School District Users/Orgs Trust 3 rd Party Service Providers & Other Federations Workforce Development Users/Orgs Federated Central Service School District Metadata Proxy IDP/SP Non-School District Metadata SAML 2.0 OAuth OpenID Read-Only Query Functionality Authentication Delegation to Authoritative Source Trust Native Directory Interface Districts (1.. N) using Active Directory Districts (1.. N) using edirectory Districts (1.. N) using LDAP/Kerberos

24 InCommon Federation SP Metadata SP Google for Ed SP SP Discovery Ed SuccessNet Any SP via SAML SP Publish Subscribe External Federations & Service Providers K12 Service Providers IDP IlliniCloud K12 Federation Metadata SP SP Single Sign On (SSO) Enabled Custom State Applications SP Custom District Applications K12 District X K12 District Y K12 District Z Local K12 Identity Services Directory Authoritative Directory Source AD LDAP Kerberos edirectory Key SSO = Single Sign On SP = Service Providers

25 General Purpose Login Process Tenant Portal-Manager Controls Portal Skin Customizations Content Customizations to User Roles Isle Apps District Apps EC/PK Apps My Page Tab Bar Illinois Open Education Resource Search Educator Dashboard Isle Apps Tenant Apps Office Apps My Page Tab Bar Isle Apps District Apps Admin Tools My Page Tab Bar Isle Apps Grade 8 Apps Office Apps Student@usd116.org My Page Tab Bar Illinois Open Education Resource Search Educator Dashboard

26 SIF 3 Data Collection Challenges