p20 state core logical data model n.
Skip this Video
Loading SlideShow in 5 Seconds..
P20 State Core Logical Data Model PowerPoint Presentation
Download Presentation
P20 State Core Logical Data Model

P20 State Core Logical Data Model

156 Vues Download Presentation
Télécharger la présentation

P20 State Core Logical Data Model

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. P20 State CoreLogical Data Model September, 2010


  3. The P20 State Core Logical Data Model Developed as part of the Common Data Standards (CDS) adoption work with funding from the Gates Foundation Based on NCES handbook, NEDM v2.0, SIF v2.4, PESC, SHEEO State of State PS Data Systems report , and Common Data Standards v1.0 Includes early childhood, elementary and secondary, post-secondary, and workforce data (aka P20) and detailed maps to all 657 files states are required to submit to USED Designed to support dropout early warning intervention systems (DEWIS), positive behavior intervention systems (PBIS) and response to intervention (RTI) May be maintained and governed as a model by a joint task force of SIFA and PESC on behalf of CCSSO and SHEEO and their member states (to be determined). Intended for SEAs and to help guide the relationships, business rules, and entity factoring validate state maps to views of a common P-20 SLDS model including: source files with different and or non-existent start and end dates complex relationships between organizations people with multiple roles in multiple organizations including student-teacher linkage

  4. Directory - the core of the core, Org-Org Relationships Each level of an educational system share common attributes, or data points, that allow us to represent all levels as ‘Organizations’ without losing the business relationship. All can be represented as Organizations

  5. People and Roles, the Person – Org Relationship Each person shares common attributes, or data points, that allow us to represent all levels as ‘Persons.’ Each Person has one or more ‘roles.’

  6. The Person Organization Relationships

  7. ODS: Operational Data Store ODS represents the most current data that the State has ODS includes the most current view of some historical data (such as prior assessment data and enrollment records) ODS is a relational database A “record” is added for each Person.Org Relationship change event in the system. Other updates to entity.attributes edit records in ODS and update in EAV

  8. ODS – Conceptual Model

  9. ODS – Physical View of Logical Model (Partial)

  10. ODS – Physical View of Logical Model (Full)

  11. ODS – Organization

  12. ODS – Organization Indicators and Statistics

  13. ODS – Person

  14. ODS – Person [K12 Student]

  15. ODS – Person [K12 Staff]

  16. ODS – Location

  17. ODS – Assessment [K12 – SIF]

  18. ODS – Learning Standards [K12-SIF]

  19. ODS – Transcript [K12 SIF]

  20. ODS – Person-Org [K12 Student.Enrollment]

  21. ODS – Person-Org [K12 Student.Program]

  22. EAV: Entity Attribute Value EAV is the auditing schema for ODS All ODS data manipulation operations result in or are caused by an EAV record EAV is a “no edit” database. Records are added, not edited. A record is added for each change in Entity.Attribute value

  23. EAV: Logical Model

  24. RDS: Reporting Data Store The RDS is a view of the ODS as of a specific date The RDS can be an unchanging snapshot or can remain synchronized to changes in the ODS The RDS contains both granular and derived /aggregated attributes to support reporting The RDS is more of a “flat” “star schema” focused on facts of people and organization as of a specific dates

  25. The ODS populates each RDS ODS data is transformed and copied into RDS, time-stamping the data to allow that dataset to represent a specific point in time.

  26. Each RDS represents a particular “As of” Date

  27. K12 Official Reporting Data Store (RDS) - Logical

  28. Tying everything in the model together, “Data Set”.

  29. The model is built on PCG’s metadata methodology

  30. Data Model ETL Validation Reporting (Outputs) Policies Metadata Extensibility Usage Scenarios Data Sources The model addresses the complete SLDS system cycle 17 17

  31. Inman DW 2.0 – The Importance of Metadata