Slc technology101 boston-sep2012

403 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
403
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Three structural groups – entities (core elements), descriptors (enums or codes which vary state to state) and assocations bwtn entities w/ attributes.
  • Slc technology101 boston-sep2012

    1. 1. SLC Technology 101Jason HoekstraTechnology Solutions Architect@jasonhoekstraUSMSGUEST PW: Ja8qb23 1
    2. 2. Agenda 2
    3. 3. Agenda• Technology Overview• Data Model Walkthrough• Security Overview• dev.slcedu.org Walkthrough• Hello World Sprint 3
    4. 4. TechnologyOverview 4
    5. 5. The SLC’s DatastoreSLC Technology offers a secure, multi-tenant data store. SLC Technology is aligned to CEDS usingthe open Ed-Fi XML model. Data ingestion and extraction methods are: Bulk XML, CSV, SIF ZISAdapters and Record-Level API’s SLC Technology Data Store Student Enrollment Student Achievement Student Biographical Teacher & Staff Education Data Data Data Association Data Organization Data School State Summative Race / Ethnicity Staff ID State Grade Local Benchmarks Free/Reduce Lunch Staff Location Region Course Class Formative Family Contacts Courses District Section End of Study Tests Programs/Services Sections Network Class Assignment Attendance School Official Transcripts Discipline Course Section 5
    6. 6. Making Tech Work Together Classroom tools Recommendation Engines Dashboard OER Repositories Learning Map Online Courseware Public Publisher Content Interactive Datastore API SLC Datastore State & Local Data Sources SEA/LEA Content State Data State/District LEA/School LEA/School LEA/School Educator Local Identity State LEA State/Local Local Warehouse SIS Assessment Gradebooks Instruction & Staff HR Directory Item Banks Item Banks Vendor Resources Systems Products Systems Content 6
    7. 7. Datastore Design Priorities 7
    8. 8. SLC Data Model 8
    9. 9. SLC Access MethodsThe SLC data store offers a variety methods to access data:• Today • Real-time REST API – either JSON or XML • Bulk data ingestion via Ed-Fi XML (zipped)• Future • CSV to Ed-Fi XML Convertor • Bulk data download (either full or delta) • SIF Adapter • API aggregate endpoints and consolidated views 9
    10. 10. SLI Entity FamiliesFamily groups are sets of entities with a logical relationship to each other.Collectively, they contain all entities, including associations and descriptorsfound in the Ed-Fi data model.The 6 SLI Entity Families 1. Education Organization Structure 2. Master Schedule 3. Academic Record 4. Assessment 5. Program & Cohort 6. Discipline 10
    11. 11. Education Organization Family*Diagram is for illustrative purposes only. Refer to technical documentation for full details. 11
    12. 12. Master Schedule Family*Diagram is for illustrative purposes only. Refer to technical documentation for full details. 12
    13. 13. Academic Record Family*Diagram is for illustrative purposes only. Refer to technical documentation for full details. 13
    14. 14. Assessment Family*Diagram is for illustrative purposes only. Refer to technical documentation for full details. 14
    15. 15. Discipline Family*Diagram is for illustrative purposes only. Refer to technical documentation for full details. 15
    16. 16. Program & Cohort Family*Diagram is for illustrative purposes only. Refer to technical documentation for full details. 16
    17. 17. SLC Security 17
    18. 18. Security Key Points• The district (LEA) owns data and grants permissions. • Sandbox: you control district and school access. • Production: district controls a.) entity access and b.) read/write permissions.• SLC provides a SSO experience to the district’s LDAP identity store (the SLC does not have passwords).• SLC sandbox provides sample identity store; SLC production assume user already logged in.• Teachers will have access to sections, classes and students they have a data relationship with 18
    19. 19. Sandbox OAuth Authentication Workflow 1 Client ID App Secret 2 Verif. Code 3 SLC Data 4 District Client Client ID Store Username Identity StoreApplication App Secret Password Verif. Code (via SAML) 6 5 Access Token Authenticated Successfully (via SAML)Note: To access data, the app needs a client ID and app secret from registration. 19
    20. 20. dev.slcedu.orgWalk Through 20
    21. 21. Hello World Sprint 21
    22. 22. What’s Next? 22
    23. 23. Case #1: Whole Student View CaseWhen teachers can see a student’s full biographical and performancehistory, they’ve got a serious head start toward understanding what eachstudent needs. But when records are inaccurate, incomplete, or don’t followstudents when they move, that complete picture is hidden. Educators wantapplications that enable them to see and use comprehensive studentinformation so classrooms feel more personal from day one.Applications DataDashboards StudentData Visualization Gradebook and AssessmentsReporting Attendance 23
    24. 24. Case #2: Open Source Utils / Wrappers• API Wrappers• Open Source Sample Apps• Be sure to tell us of your apps on the forums!!! 24
    25. 25. Case #3: Bounty Apps ($75,000 x 2) Student Data Aggregation Calculators Student Groupings Tool 25

    ×