Modeled for longitudinal storage and reporting of P-20W data, the Common Education Data Standards (CEDS) Data Warehouse implements star schema data warehouse normalization techniques for improved query performance.
Home Page: https://github.com/CEDStandards/CEDS-Data-Warehouse
License: Apache License 2.0
Describe the bug
The README for this repo tells users to create the CEDS Elements database by running a script that is no longer in the Data Warehouse repo. Instead, it appears users must clone the CEDS-Elements repo and create that database before finished the CEDS DW set up.
To Reproduce
The database is empty by default. Proceed with the following instructions to load CEDS Element metadata and CEDS Option Set values into the Dimension tables.
Open the Create CEDS Elements V11.0.0.0 document at /src/dimension-data/CEDS-Elements-V11.0.0.0
Connect to the server on which you created the CEDS Version 11.0.0.0 instance
Run the script. This will create the CEDS-Elements-V11.0.0.0 Database
Expected behavior
The README should be accurate to the steps.
This is for capturing needs not currently supported by the CEDS model. Please do not send or share actual data as examples in this issue or in attachments.
Author(s)
Duane Brown
Authoring Organization(s)
CEDS
Email Address
[email protected]
Use Case Title
Double check that all Junk Dimension tables are being populated.
Use Case Overview
It appears the following are Junk Dimensions but are not part of the Junk Dimension population script:
DimTitleIStatuses
DimReponsibleOrganization Types
DimPsFamilyStatuses
DimPsCourseStatuses
DimPsCitizenshipStatuses
DimK12OrganizationStatuses
DimIncidentBehaviors
Correct these and check for any others.
Pull Request Number(s) (If applicable)
Use Case Background
Provide information related to why these changes/additions are needed.
Components Affected
Delete everything from the list below except the components affected:
CEDS Integrated Data Store (complete IDS Design Overview Table)
CEDS Data Warehouse (complete DW Design Overview Table)
CEDS Data Migrations (complete Data Migration Impact Analysis Table)
CEDS Element Gap Analysis
Provide link to CEDS Align Map or Connection.
INTEGRATED DATA STORE DESIGN OVERVIEW
Description of Proposed Changes
Provide a concise description of the proposed changes.
As-Is Diagram
Add as an attachment in this issue.
Proposed To-Be Diagram
Add as an attachment in this issue.
DATA WAREHOUSE DESIGN OVERVIEW (Includes Dim, Fact, and Report tables)
Description of Proposed Changes
Provide a concise description of the proposed changes.
As-Is Diagram
Add as an attachment in this issue.
Proposed To-Be Diagram
Add as an attachment in this issue.
DATA MIGRATION IMPACT ANALYSIS
Description of Proposed Changes
Provide a concise description of the proposed changes.
New Business Rule
Provide a concise and comprehensive description of the new business rule.
Existing Business Rule
Provide a concise and comprehensive description of the existing business rule.
Changed Business Rule
Provide a concise and comprehensive description of the changes to be made to the business rule.
SELECT DISTINCT t.Name, t.XMLName, t.GlobalID, c.Code, c.Description, c.CodeDefinition, NULL, NULL
FROM CEDS.dbo.Term t
JOIN CEDS.dbo.TermxCodeSet tcs
ON t.TermID = tcs.TermID
JOIN CEDS.dbo.CodeSet cs
ON tcs.CodeSetID = cs.CodeSetID
JOIN CEDS.dbo.CodeSetxCode csxc
ON cs.CodeSetID = csxc.CodeSetID
JOIN CEDS.dbo.Code c
ON csxc.CodeID = c.CodeID
WHERE t.Version = @CEDSVersion
AND t.HasCodeSet = '1'
refers to a non-existent CEDS database. These should probably all be references to the CEDS domain in the current database:
SELECT DISTINCT t.Name, t.XMLName, t.GlobalID, c.Code, c.Description, c.CodeDefinition, NULL, NULL
FROM CEDS.Term t
JOIN CEDS.TermxCodeSet tcs
ON t.TermID = tcs.TermID
JOIN CEDS.CodeSet cs
ON tcs.CodeSetID = cs.CodeSetID
JOIN CEDS.CodeSetxCode csxc
ON cs.CodeSetID = csxc.CodeSetID
JOIN CEDS.Code c
ON csxc.CodeID = c.CodeID
WHERE t.Version = @CEDSVersion
AND t.HasCodeSet = '1'
This is for capturing needs not currently supported by the CEDS model. Please do not send or share actual data as examples in this issue or in attachments.
Author(s)
Kim Carlson
Authoring Organization(s)
South Dakota Department of Education
Email Address
[email protected]
Use Case Title
Provide a concise description that defines the use case.
Update FactPSStudentEnrollments grain information to include the DimPSInstitutionStatus as a BK
Use Case Overview
Provide a concise, high-level description of the actions of the use case. While being concise, the description should cover all possible actions for the use case.
South Dakota Department of Education is using National Student Clearinghouse data to populate FactPsStudentEnrollments table. We are not a P20W SLDS which means we do not have access to Post-Secondary data other than what we receive from NSCH through the StudentTracker data file.
South Dakota does not have data to correctly map Academic Term Designator so it was mapped to MISSING.
We are experiencing post-secondary schools that are changing their institution status during the school year. In this case, they went from a 2 year school to a 4 year school. When we did a little digging, it does seem like the school changed from a 2 year to 4 year school.
Pull Request Number(s) (If applicable)
Use Case Background
Provide information related to why these changes/additions are needed.
This is causing discard because FactPsStudentEnrollments is seeing this as a duplicate. SD doesn't want to form some business logic to pick an enrollment since both cases are correct.
Components Affected
Delete everything from the list below except the components affected:
CEDS Data Warehouse (complete DW Design Overview Table)
No DDL in the model should be affected. Only the Bus Architecture documentation that designates the Grain/BK for the table.
This is for capturing needs not currently supported by the CEDS model. Please do not send or share actual data as examples in this issue or in attachments.
Author(s)
Duane Brown
Authoring Organization(s)
CEDS Team & Data Warehouse Expansion Project Workgroup
Email Address
[email protected]
Use Case Title
Provide a concise description that defines the use case.
Enhancements from the Data Warehouse Expansion Project V9.1.0.0
Use Case Overview
This update includes the following changes to the Warehouse (Note: Additional documentation is provided in the release):
Pull Request Number(s) (If applicable)
Use Case Background
The new fact and dimension tables are being created to support the work done through the CEDS Data Warehouse Expansion Project. The column name changes/updates are done to create better consistency and alignment with the actual CEDS element technical names.
This is for capturing needs not currently supported by the CEDS model. Please do not send or share actual data as examples in this issue or in attachments.
Author(s)
Johnny Cunningham
Authoring Organization(s)
CEDS
Email Address
[email protected]
Remove deprecated IDS Id columns from staging tables
Use Case Overview
The columns are no longer used by the migration process and add confusion for anyone using those staging tables.
Pull Request Number(s) (If applicable)
Use Case Background
Provide information related to why these changes/additions are needed.
Components Affected
Delete everything from the list below except the components affected:
CEDS Data Warehouse (complete DW Design Overview Table)
DATA WAREHOUSE DESIGN OVERVIEW (Includes Dim, Fact, and Report tables)
Remove the following columns from the defined staging tables
This is for capturing needs not currently supported by the CEDS model. Please do not send or share actual data as examples in this issue or in attachments.
Author(s)
Duane Brown
Authoring Organization(s)
CEDS / Mississippi
Email Address
[email protected]
Use Case Title
Create Fact tables to house K12 Calendar Data (Session & Date Level)
Use Case Overview
Create two Fact tables, one that will contain K12 Calendar data at the session level and another that will contain K12 Calendar Data at the day (date) level.
Pull Request Number(s) (If applicable)
Use Case Background
Needed for tracking calendar information in an SEA. Used for determining days of instruction for funding.
As SEAs continue to use the CEDS DW and build new applications on top of the warehouse, they will need a way for those applications and downstream tools to know what version of the CEDS DW they are utilizing. The came from a request of several states involved with Generate as this table would allow Generate to read the version and display it on the screen.
This is for capturing needs not currently supported by the CEDS model. Please do not send or share actual data as examples in this issue or in attachments.
Author(s)
Duane Brown
Authoring Organization(s)
CEDS
Email Address
[email protected]
Use Case Title
Add additional fields to DimAttendances and correct naming of existing columns
Use Case Overview
The existing DimAttendances table contains 3 fields related to "Absenteeism". These are remnants from the Generate Data Warehouse for EDFacts reporting. These will be replaced with the correct CEDS element names. In addition, the remaining attendance status elements in CEDS need to be added to accurately report on daily attendance through FactK12StudentDailyAttendances.
Pull Request Number(s) (If applicable)
Describe the bug
The dimension table population script, Junk-Table-Dimension-Population swapped the values for AssessmentRegistrationCompletionStatus and AssessmentRegistrationParticipationIndicator when populating RDS.DimAssessmentRegistrations.
To Reproduce
N/A
This is for capturing needs not currently supported by the CEDS model. Please do not send or share actual data as examples in this issue or in attachments.
Author(s)
Deborah Donovan
Authoring Organization(s)
Mississippi Department of Education
Email Address
[email protected]
Use Case Title
Add PersonIdentifierSSN to DimPeople
Use Case Overview
We need to capture SSN as an identifier type for people
Pull Request Number(s) (If applicable)
n/a
Use Case Background
Need to extend for this additional identifier type
Components Affected
Delete everything from the list below except the components affected:
CEDS Data Warehouse (complete DW Design Overview Table)
CEDS Data Warehouse Parquet (complete DW Parquet Design Overview Table)
DATA WAREHOUSE DESIGN OVERVIEW (Includes Dim, Fact, and Report tables)
This is for capturing needs not currently supported by the CEDS model. Please do not send or share actual data as examples in this issue or in attachments.
Author(s)
Duane Brown
Authoring Organization(s)
CEDS
Email Address
Use Case Title
Follow architecture similar to K12 for DimAeDemographics and the FactAeStudentEnrollments
Use Case Overview
For the FactK12StudentEnrollments, items like Economic Disadvantage and Military Connected are separated in multiple Dimension tables. Recommend doing the same with FactAEStudentEnrollments and removing items from DimAeDemographics in favor of more dimension tables and the reuse of existing dimension tables that contain this data.
Pull Request Number(s) (If applicable)
Use Case Background
Provide information related to why these changes/additions are needed.
Components Affected
Delete everything from the list below except the components affected:
CEDS Integrated Data Store (complete IDS Design Overview Table)
CEDS Data Warehouse (complete DW Design Overview Table)
CEDS Data Migrations (complete Data Migration Impact Analysis Table)
CEDS Element Gap Analysis
Provide link to CEDS Align Map or Connection.
INTEGRATED DATA STORE DESIGN OVERVIEW
Description of Proposed Changes
Provide a concise description of the proposed changes.
As-Is Diagram
Add as an attachment in this issue.
Proposed To-Be Diagram
Add as an attachment in this issue.
DATA WAREHOUSE DESIGN OVERVIEW (Includes Dim, Fact, and Report tables)
Description of Proposed Changes
Provide a concise description of the proposed changes.
As-Is Diagram
Add as an attachment in this issue.
Proposed To-Be Diagram
Add as an attachment in this issue.
DATA MIGRATION IMPACT ANALYSIS
Description of Proposed Changes
Provide a concise description of the proposed changes.
New Business Rule
Provide a concise and comprehensive description of the new business rule.
Existing Business Rule
Provide a concise and comprehensive description of the existing business rule.
Changed Business Rule
Provide a concise and comprehensive description of the changes to be made to the business rule.
This is for capturing needs not currently supported by the CEDS model. Please do not send or share actual data as examples in this issue or in attachments.
Author(s)
Nathan Clinton
Authoring Organization(s)
CEDS
Email Address
[email protected]
Use Case Title
Add default values to all junk dimension table columns to allow for the easy, consistent addition of new columns
Use Case Overview
Adding new columns to tables can be difficult if the new columns a NOT NULL. Adding a default value constraint to these new columns solves this problem. To remain consistent, we should set all Junk dimension column defaults to 'MISSING'.
Pull Request Number(s) (If applicable)
This is for capturing needs not currently supported by the CEDS model. Please do not send or share actual data as examples in this issue or in attachments.
Author(s)
Richard Heck
Authoring Organization(s)
Otis Educational Systems
Email Address
[email protected]
Use Case Title
Request to add additional columns to support the grain for the DimCredentials table
Use Case Overview
For the DimCredentials table, we will need to have the Credential Identifier and Credential Identifier System elements added to support the grain.
Use Case Background
Changes are required to support the business key/grain for populating data in the table.
Components Affected
CEDS Data Warehouse (complete DW Design Overview Table)
DATA WAREHOUSE DESIGN OVERVIEW (Includes Dim, Fact, and Report tables)
Description of Proposed Changes
Add Credential Identifier and Credential Identifier System columns to the DimCredentials table
Author(s)
Mike Reynolds
Authoring Organization(s)
Cedar Labs, LLC
Email Address
[email protected]
Use Case Title
"Data Lake"-friendly schema for CEDS Data Warehouse
Use Case Overview
We are working with a client that wants to take advantage of a modern cloud infrastructure, and we'd like to take the CEDS DW into the cloud.
Pull Request Number(s) (If applicable)
Use Case Background
The current requirement to use MS SQLServer is overly prescriptive - especially for cloud environments. It would be nice to have a more open alternative for large implementations that can take advantage of modern scalable architectures.
Components Affected
CEDS Data Warehouse
CEDS Data Warehouse (complete DW Design Overview Table)
TBD
DATA WAREHOUSE DESIGN OVERVIEW (Includes Dim, Fact, and Report tables)
Description of Proposed Changes
Provide a concise description of the proposed changes.
As-Is Diagram
Add as an attachment in this issue.
Proposed To-Be Diagram
Add as an attachment in this issue.
This is for capturing needs not currently supported by the CEDS model. Please do not send or share actual data as examples in this issue or in attachments.
Author(s)
Richard Heck
Authoring Organization(s)
Otis Educational Systems
Email Address
[email protected]
Use Case Title
Request for Grain information for Dim/Fact tables
Use Case Overview
When loading data to the CEDS DW, it will be useful to have the grain information for each of the table to understand how to populate the objects.
Pull Request Number(s) (If applicable)
Use Case Background
N/A
Components Affected
CEDS Data Warehouse (complete DW Design Overview Table)
CEDS Element Gap Analysis
N/A
DATA WAREHOUSE DESIGN OVERVIEW (Includes Dim, Fact, and Report tables)
Description of Proposed Changes
Requesting a list of the columns (Business Key) for each table that make up the grain.
This is for capturing needs not currently supported by the CEDS model. Please do not send or share actual data as examples in this issue or in attachments.
Author(s)
Drew Bennett-Stein
Authoring Organization(s)
State of Vermont
Email Address
[email protected]
Use Case Title
Extend ExitOrWithdrawalType to nvarchar(max)
Use Case Overview
Loading ExitOrWithdrawalType
Pull Request Number(s) (If applicable)
Use Case Background
Unable to load ExitOrWithdrawalType with Description from RefExitOrWithdrawalType.
Components Affected
Delete everything from the list below except the components affected:
CEDS Integrated Data Store (complete IDS Design Overview Table)
K12StudentEnrollment RefExitOrWithdrawalType
CEDS Data Warehouse (complete DW Design Overview Table)
K12Enrollment ExitOrWithdrawalType
CEDS Data Migrations (complete Data Migration Impact Analysis Table)
The proposed changes in the ExitOrWithdrawalType do not directly impact the current data migration strategies or processes. However, ongoing monitoring will be required to ensure compatibility with future data migrations
CEDS Element Gap Analysis
A thorough review indicates no immediate gaps in the CEDS elements concerning the ExitOrWithdrawalType. Future assessments should be conducted to maintain alignment with evolving educational data standards and requirements.
INTEGRATED DATA STORE DESIGN OVERVIEW
Description of Proposed Changes
Enhancements to the K12StudentEnrollment.RefExitOrWithdrawalType to support extended character limits and incorporate descriptive metadata.
As-Is Diagram
Current design limits character input and lacks detailed descriptors.
DATA WAREHOUSE DESIGN OVERVIEW (Includes Dim, Fact, and Report tables)
DATA MIGRATION IMPACT ANALYSIS
Description of Proposed Changes
Adjustments to the data migration protocols to accommodate the expanded data type and ensure seamless integration with existing datasets.
New Business Rule
Implement validation checks for extended ExitOrWithdrawalType data during migration.
Existing Business Rule
Maintain current data integrity checks, with added focus on the extended data fields.
Changed Business Rule
Update transformation rules to align with the expanded data type for ExitOrWithdrawalType.
This is for capturing needs not currently supported by the CEDS model. Please do not send or share actual data as examples in this issue or in attachments.
Author(s)
Ben Silberglitt and Tori Ryan
Authoring Organization(s)
Cedar Labs and Maine DOE
Email Address
[email protected] [email protected]
Use Case Title
Graduation Data Warehouse working group
Use Case Overview
Maine would like to leverage the CEDS DW to support public-facing reporting around graduation outcomes. Currently, Maine's reporting on this domain includes some data that the CEDS DW data schema is not equipped to handle. For example, graduation outcomes are broken out into 4yr, 5yr, and 6yr cohorts. Also, outcomes are tracked by graduation, continuing, dropout, and unknown. Maine and Cedar Labs consulted with AEM, and it sounds like a new fact table will be the best approach. We'd like to form a working group with any and all interested parties, to determine what schema this fact table should have, to serve as many needs as possible.
Pull Request Number(s) (If applicable)
N/A
Use Case Background
See use case overview above
Components Affected
CEDS Data Warehouse (complete DW Design Overview Table)
CEDS Data Migrations (complete Data Migration Impact Analysis Table)
CEDS Element Gap Analysis
Provide link to CEDS Align Map or Connection.
INTEGRATED DATA STORE DESIGN OVERVIEW
Description of Proposed Changes
Provide a concise description of the proposed changes.
As-Is Diagram
Add as an attachment in this issue.
Proposed To-Be Diagram
Add as an attachment in this issue.
DATA WAREHOUSE DESIGN OVERVIEW (Includes Dim, Fact, and Report tables)
Description of Proposed Changes
Provide a concise description of the proposed changes.
As-Is Diagram
Add as an attachment in this issue.
Proposed To-Be Diagram
Add as an attachment in this issue.
DATA MIGRATION IMPACT ANALYSIS
Description of Proposed Changes
Provide a concise description of the proposed changes.
New Business Rule
Provide a concise and comprehensive description of the new business rule.
Existing Business Rule
Provide a concise and comprehensive description of the existing business rule.
Changed Business Rule
Provide a concise and comprehensive description of the changes to be made to the business rule.
Describe the bug
Column names are misspelled in the following tables:
In FactK12StudentAssessmentResultAggregates, all columns that begin with "StandarDeviation..." need to corrected to "StandardDeviation..."
In BridgeK12StudentAssessmentAccommodations, the PK of the table should be "BridgeK12StudentAssessmentAccommodationId" instead of "FactK12StudentAssessmentAccommodationId"
Author(s): Drew Bennett-Stein
Authoring Organization(s): State of Vermont, Agency of Education
Email Address: [email protected]
Use Case Title: Integration of Attendance Status and Truancy Data into CEDS Data Warehouse
Use Case Overview:
This use case proposes the integration of detailed attendance status (excused/unexcused) and truancy data into the CEDS Data Warehouse. This includes the addition of new tables such as DimAttendanceStatuses and modifications to existing tables like FactK12StudentAttendanceRates or FactK12StudentDailyAttendances for capturing the number of unexcused absences.
Pull Request Number(s) (If applicable): [To be filled after initiating the pull request]
Use Case Background:
The current CEDS Data Warehouse model lacks specific data points for Attendance Status (excused/unexcused) and does not include a field for 'NumberofDaysUnexcused' in the RoleAttendance section. This data is vital for analyzing attendance patterns and addressing issues like truancy effectively.
Components Affected:
CEDS Data Warehouse (complete DW Design Overview Table)
INTEGRATED DATA STORE DESIGN OVERVIEW
Description of Proposed Changes:
The proposal is to add a new table, DimAttendanceStatuses, for detailed attendance statuses, and to enhance existing tables to capture 'NumberofDaysUnexcused'.
As-Is Diagram: [Attachment Required]
Proposed To-Be Diagram: [Attachment Required]
DATA WAREHOUSE DESIGN OVERVIEW (Includes Dim, Fact, and Report tables)
Description of Proposed Changes:
Addition of DimAttendanceStatuses table and modifications to FactK12StudentAttendanceRates or FactK12StudentDailyAttendances to include unexcused absences data.
As-Is Diagram: [Attachment Required]
Proposed To-Be Diagram: [Attachment Required]
DATA MIGRATION IMPACT ANALYSIS
Description of Proposed Changes:
Introduction of new data points for attendance status and truancy.
New Business Rule:
Capture and store detailed attendance status (excused/unexcused).
Record 'NumberofDaysUnexcused' for each student.
Existing Business Rule:
[Describe the current business rules regarding attendance data management]
Changed Business Rule:
Enhancement of the existing business rule to include detailed attendance statuses and truancy data.
This is for capturing needs not currently supported by the CEDS model. Please do not send or share actual data as examples in this issue or in attachments.
Author(s)
CEDS
Authoring Organization(s)
CEDS
Email Address
[email protected]
Use Case Title
Add OPEID to DimPsInstitutions and make IPEDS Identifier Nullable
Use Case Overview
Add a new column to DimPSInstitutions - see ticket CEDStandards/CEDS-Elements#638
Pull Request Number(s) (If applicable)
Use Case Background
Provide information related to why these changes/additions are needed.
Components Affected
Delete everything from the list below except the components affected:
CEDS Integrated Data Store (complete IDS Design Overview Table)
CEDS Data Warehouse (complete DW Design Overview Table)
CEDS Data Migrations (complete Data Migration Impact Analysis Table)
CEDS Element Gap Analysis
Provide link to CEDS Align Map or Connection.
INTEGRATED DATA STORE DESIGN OVERVIEW
Description of Proposed Changes
Provide a concise description of the proposed changes.
As-Is Diagram
Add as an attachment in this issue.
Proposed To-Be Diagram
Add as an attachment in this issue.
DATA WAREHOUSE DESIGN OVERVIEW (Includes Dim, Fact, and Report tables)
Description of Proposed Changes
Provide a concise description of the proposed changes.
As-Is Diagram
Add as an attachment in this issue.
Proposed To-Be Diagram
Add as an attachment in this issue.
DATA MIGRATION IMPACT ANALYSIS
Description of Proposed Changes
Provide a concise description of the proposed changes.
New Business Rule
Provide a concise and comprehensive description of the new business rule.
Existing Business Rule
Provide a concise and comprehensive description of the existing business rule.
Changed Business Rule
Provide a concise and comprehensive description of the changes to be made to the business rule.
Describe the bug
The seed data for VirtualIndicatorCode/Description in [DimPsInstitutionStatuses] is different than the Element definition on the website.
To Reproduce
SELECT distinct
[VirtualIndicatorCode]
,[VirtualIndicatorDescription]
FROM [CEDS-Data-Warehouse-V10-0-0-0].[RDS].[DimPsInstitutionStatuses]
--Compare these values to the extended properties element
https://ceds.ed.gov/CEDSElementDetails.aspx?TermId=18167
Expected behavior
The [CEDS-Data-Warehouse-V10-0-0-0].[RDS].[DimPsInstitutionStatuses] seed data should have Yes/No/Missing(?) values like the element on the site instead of the current values.
Screenshots
If applicable, add screenshots to help explain your problem.
This is for capturing needs not currently supported by the CEDS model. Please do not send or share actual data as examples in this issue or in attachments.
Author(s)
Nathan Clinton
Authoring Organization(s)
Center for the Integration of IDEA Data (CIID)
Email Address
[email protected]
Use Case Title
Provide a concise description that defines the use case.
Update the CEDS Data Warehouse to include changes required for Generate
Use Case Overview
Provide a concise, high-level description of the actions of the use case. While being concise, the description should cover all possible actions for the use case.
Implement federal EDFacts reporting changes required by Generate and to fully align to CEDS data elements names.
Pull Request Number(s) (If applicable)
Use Case Background
Provide information related to why these changes/additions are needed.
Data warehouse changes determined after implementing the OSC version of the CEDS Data Warehouse V9 submitted by CEPI in Michigan.
Components Affected
Delete everything from the list below except the components affected:
CEDS Data Warehouse (complete DW Design Overview Table)
CEDS Element Gap Analysis
Provide link to CEDS Align Map or Connection.
DATA WAREHOUSE DESIGN OVERVIEW (Includes Dim, Fact, and Report tables)
Description of Proposed Changes
Provide a concise description of the proposed changes.
See docs\Version 8.0.0.0 to Version 9.0.0.0 Comparison.xlsx
This is for capturing needs not currently supported by the CEDS model. Please do not send or share actual data as examples in this issue or in attachments.
Author(s)
Duane Brown
Authoring Organization(s)
CEDS
Email Address
[email protected]
Use Case Title
Add the DimTitleIIIStatuses table to the FactK12ProgramParticipations
Use Case Overview
This is for tracking Title III statuses of a student who is enrolled in any program. The specific use case need is for tracking the Title III Accountability Progress Status of a student who is enrolled in a Title III language instruction educational program for EDFacts file specification 211.
Pull Request Number(s) (If applicable)
Use Case Background
Provide information related to why these changes/additions are needed.
Components Affected
Delete everything from the list below except the components affected:
CEDS Integrated Data Store (complete IDS Design Overview Table)
CEDS Data Warehouse (complete DW Design Overview Table)
CEDS Data Migrations (complete Data Migration Impact Analysis Table)
CEDS Element Gap Analysis
Provide link to CEDS Align Map or Connection.
INTEGRATED DATA STORE DESIGN OVERVIEW
Description of Proposed Changes
Provide a concise description of the proposed changes.
As-Is Diagram
Add as an attachment in this issue.
Proposed To-Be Diagram
Add as an attachment in this issue.
DATA WAREHOUSE DESIGN OVERVIEW (Includes Dim, Fact, and Report tables)
Description of Proposed Changes
Provide a concise description of the proposed changes.
As-Is Diagram
Add as an attachment in this issue.
Proposed To-Be Diagram
Add as an attachment in this issue.
DATA MIGRATION IMPACT ANALYSIS
Description of Proposed Changes
Provide a concise description of the proposed changes.
New Business Rule
Provide a concise and comprehensive description of the new business rule.
Existing Business Rule
Provide a concise and comprehensive description of the existing business rule.
Changed Business Rule
Provide a concise and comprehensive description of the changes to be made to the business rule.
This is for capturing needs not currently supported by the CEDS model. Please do not send or share actual data as examples in this issue or in attachments.
Author(s)
Nathan Clinton
Authoring Organization(s)
Mississippi Department of Education
Michigan Center for Education and Performance Information
Email Address
[email protected]
Use Case Title
Provide a concise description that defines the use case.
SEAs need student addresses tied to enrollment data
Use Case Overview
Provide a concise, high-level description of the actions of the use case. While being concise, the description should cover all possible actions for the use case.
Add a bridge table connected to FactK12StudentEnrollments that captures 1-to-many addresses for a student.
Pull Request Number(s) (If applicable)
Use Case Background
Provide information related to why these changes/additions are needed.
Student addresses are needed for location analysis by both Michigan and Mississippi.
Components Affected
CEDS Data Warehouse (complete DW Design Overview Table)
Add a new table named RDS.BridgeK12StudentEnrollmentPersonAddresses
This is for capturing needs not currently supported by the CEDS model. Please do not send or share actual data as examples in this issue or in attachments.
Author(s)
Duane Brown
Authoring Organization(s)
CEDS
Email Address
Use Case Title
Add Dates to DimK12Courses
Use Case Overview
DimK12Courses is a slowly changing Dimension. Add RecordStartDateTime and RecordEndDateTime to this table.
Additionally, add CourseBeginDate and CourseEndDate to the table to represent information about the course being offered. These will not be used as record management, but will instead be metadata about whether or not the course can be offered/whether it can exist in a school catalogue.
This is for capturing needs not currently supported by the CEDS model. Please do not send or share actual data as examples in this issue or in attachments.
Author(s)
Duane Brown
Authoring Organization(s)
CEDS
Email Address
[email protected]
Use Case Title
Release Data Warehouse scripts in lower version of SQL. Change the compatibility level to less than 150 (2019). Perhaps in the 2012 or 2016 range.
Use Case Overview
Current release script requires SQL Server Management Studio 2019. Change the compatibility level to less than 150 (2019). Perhaps in the 2012 or 2016 range.
This is for capturing needs not currently supported by the CEDS model. Please do not send or share actual data as examples in this issue or in attachments.
Author(s)
Lakshmana Kommuri
Authoring Organization(s)
CEPI - State Of Michigan
Email Address
[email protected]
Use Case Title
Add CountDateId as a foreign key reference to DimDates to several Fact tables.
Use Case Overview
CountDateId is needed to populate bridge tables for three Fact tables.
Pull Request Number(s) (If applicable)
Use Case Background
A specific point-in-time date is needed to capture the appropriate details from the staging for the associated Fact records in order to fill the bridge tables.
Components Affected
CEDS Data Warehouse (complete DW Design Overview Table)
CEDS Data Migrations (complete Data Migration Impact Analysis Table)
DATA WAREHOUSE DESIGN OVERVIEW (Includes Dim, Fact, and Report tables)
Description of Proposed Changes
DATA MIGRATION IMPACT ANALYSIS
Description of Proposed Changes
Update the Staging-to-RDS data migration scripts to populate necessary bridge tables related to FactK12StudentEnrollments, FactPsStudentAcademicRecords, and FactSpecialEducation by using the new CountDateId fields to select the correct point-in-time data from the Staging tables.
This is for capturing needs not currently supported by the CEDS model. Please do not send or share actual data as examples in this issue or in attachments.
Author(s)
Nathan Clinton
Authoring Organization(s)
CEPI
Email Address
[email protected]
Use Case Title
Provide a concise description that defines the use case.
Add fact and dimension tables to support robust staff reporting and analytics.
Use Case Overview
Provide a concise, high-level description of the actions of the use case. While being concise, the description should cover all possible actions for the use case.
Pull Request Number(s) (If applicable)
Use Case Background
Provide information related to why these changes/additions are needed.
Components Affected
Delete everything from the list below except the components affected:
CEDS Integrated Data Store (complete IDS Design Overview Table)
CEDS Data Warehouse (complete DW Design Overview Table)
CEDS Data Migrations (complete Data Migration Impact Analysis Table)
CEDS Element Gap Analysis
Provide link to CEDS Align Map or Connection.
INTEGRATED DATA STORE DESIGN OVERVIEW
Description of Proposed Changes
Provide a concise description of the proposed changes.
As-Is Diagram
Add as an attachment in this issue.
Proposed To-Be Diagram
Add as an attachment in this issue.
DATA WAREHOUSE DESIGN OVERVIEW (Includes Dim, Fact, and Report tables)
Description of Proposed Changes
Provide a concise description of the proposed changes.
As-Is Diagram
Add as an attachment in this issue.
Proposed To-Be Diagram
Add as an attachment in this issue.
DATA MIGRATION IMPACT ANALYSIS
Description of Proposed Changes
Provide a concise description of the proposed changes.
New Business Rule
Provide a concise and comprehensive description of the new business rule.
Existing Business Rule
Provide a concise and comprehensive description of the existing business rule.
Changed Business Rule
Provide a concise and comprehensive description of the changes to be made to the business rule.
This is for capturing needs not currently supported by the CEDS model. Please do not send or share actual data as examples in this issue or in attachments.
Author(s)
Nathan Clinton
Duane Brown
Authoring Organization(s)
Mississippi Department of Education
Email Address
[email protected]
[email protected]
Use Case Title
Provide a concise description that defines the use case.
Use Case Overview
Provide a concise, high-level description of the actions of the use case. While being concise, the description should cover all possible actions for the use case.
Pull Request Number(s) (If applicable)
Use Case Background
Provide information related to why these changes/additions are needed.
Mississippi is going to populate these two fact tables, but currently does not have the infrastructure to do so.
Describe the bug
There is a missing record in DimRaces for HispanicOrLatinoEthnicity. This record should be created when running the Junk Table Population Script.
This is for capturing needs not currently supported by the CEDS model. Please do not send or share actual data as examples in this issue or in attachments.
Author(s)
Johnny Cunningham
Authoring Organization(s)
CEDS
Email Address
[email protected]
Use Case Title
Add Assessment Score Metric types to Staging.AssessmentResult
Use Case Overview
This is a complementary ticket to Ticket #43 as well as the changes to RDS.FactK12StudentAssessments in v11.
Pull Request Number(s) (If applicable)
Use Case Background
Adding the individual Score Metric types will simplify the loading of the Staging.AssessmentResult table by providing the individual Score Metric types as well as the Standard Error for each Assessment rather than having to load multiple rows per student per assessment.
Components Affected
Delete everything from the list below except the components affected:
CEDS Data Warehouse (complete DW Design Overview Table)
CEDS Data Migrations (complete Data Migration Impact Analysis Table)
CEDS Element Gap Analysis
Provide link to CEDS Align Map or Connection.
DATA WAREHOUSE DESIGN OVERVIEW (Includes Dim, Fact, and Report tables)
Description of Proposed Changes
Add the individual Score Metric types and the standard error for each to Staging.AssessmentResult
AssessmentResultScoreValueRawScore (nvarchar(35), null)
AssessmentResultScoreValueStandardErrorRawScore (nvarchar(35), null)
AssessmentResultScoreValueScaleScore (nvarchar(35), null)
AssessmentResultScoreValueStandardErrorScaleScore (nvarchar(35), null)
AssessmentResultScoreValuePercentile (nvarchar(35), null)
AssessmentResultScoreValueStandardErrorPercentile (nvarchar(35), null)
AssessmentResultScoreValueTScore (nvarchar(35), null)
AssessmentResultScoreValueStandardErrorTScore (nvarchar(35), null)
AssessmentResultScoreValueZScore (nvarchar(35), null)
AssessmentResultScoreValueStandardErrorZScore (nvarchar(35), null)
AssessmentResultScoreValueACTScore (nvarchar(35), null)
AssessmentResultScoreValueStandardErrorACTScore (nvarchar(35), null)
AssessmentResultScoreValueACTSuperScore (nvarchar(35), null)
AssessmentResultScoreValueStandardErrorACTSuperScore (nvarchar(35), null)
AssessmentResultScoreValueSATScore (nvarchar(35), null)
AssessmentResultScoreValueStandardErrorSATScore (nvarchar(35), null)
DATA MIGRATION IMPACT ANALYSIS
Description of Proposed Changes
Update the Staging-to-RDS data migration scripts for Assessments to use the individual Score Metric values.
Describe the bug
The fields below are not part of the junk table population script, and therefore the data is not available in the DIM table.
IdeaInterimRemovalReasonEdFactsCode
DisciplineReasonCode
DisciplineReasonDescription
IncidentInjuryTypeCode
IncidentInjuryTypeDescription
This is for capturing needs not currently supported by the CEDS model. Please do not send or share actual data as examples in this issue or in attachments.
Author(s)
Duane Brown
Authoring Organization(s)
CEDS
Email Address
[email protected]
Use Case Title
Add Primary Assignment Indicator to the Data Warehouse
Use Case Overview
Add the CEDS element Primary Assignment Indicator to the Staging.StaffAssignment table. Additionally, add the element to the Dimension table it is applicable to.
Describe the bug
In the table FactK12StudentCounts, the column name "K12StudentId" should be a Foreign Key (FK) reference to the DimK12Students table.
To Reproduce
Steps to reproduce the behavior:
Go to RDS.FactK12StudentCounts and expand the columns and find the K12StudentId column.
Expected behavior
Change the K12StudentId to an FK referring back to the DimK12Students table.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
This is for capturing needs not currently supported by the CEDS model. Please do not send or share actual data as examples in this issue or in attachments.
Author(s)
Kim Carlson
Authoring Organization(s)
South Dakota Department of Education
Email Address
[email protected]
Use Case Title
Add score metrics to FactK12StudentAssessments
Use Case Overview
There are two requests for this issue...
(1) South Dakota is requesting a new metric column is added to FactK12StudentAssessments. It would be called AssessmentResultScoreValueACTSuperScore and be a (nvarchar(35), null).
(2) South Dakota is also requesting these metrics be added into FactK12StudentAssessments with the CEDS release if possible. These metrics were provided to South Dakota as possible additional metrics that could be added. One thing, for AssessmentResultScoreStandardErrorRawScore can the word value be added to be consistent with the other metric naming conventions?
• AssessmentResultScoreValueStandardErrorRawScore (nvarchar(35), null)
• AssessmentResultScoreValueStandardErrorScaleScore (nvarchar(35), null)
• AssessmentResultScoreValueStandardErrorPercentile (nvarchar(35), null)
• AssessmentResultScoreValueStandardErrorTScore (nvarchar(35), null)
• AssessmentResultScoreValueStandardErrorZScore (nvarchar(35), null)
• AssessmentResultScoreValueStandardErrorACTScore (nvarchar(35), null)
• AssessmentResultScoreValueStandardErrorSATScore (nvarchar(35), null)
Pull Request Number(s) (If applicable)
Use Case Background
Provide information related to why these changes/additions are needed.
These changes are needed so we can include standard error in the assessment table. We also need a new metric for ACT super score. South Dakota had a meeting with Nathan and Duane requesting this an additional metric since super score can be different than ACT scores.
Components Affected
Delete everything from the list below except the components affected:
FactK12StudentAssessments is what is affected. I'm not sure if it impacts both CEDS IDS and CEDS Data Warehouse?
CEDS Integrated Data Store (complete IDS Design Overview Table)
CEDS Data Warehouse (complete DW Design Overview Table)
CEDS Element Gap Analysis
Provide link to CEDS Align Map or Connection.
INTEGRATED DATA STORE DESIGN OVERVIEW
Description of Proposed Changes
Provide a concise description of the proposed changes.
As-Is Diagram
Add as an attachment in this issue.
Proposed To-Be Diagram
Add as an attachment in this issue.
DATA WAREHOUSE DESIGN OVERVIEW (Includes Dim, Fact, and Report tables)
Description of Proposed Changes
Provide a concise description of the proposed changes.
As-Is Diagram
Add as an attachment in this issue.
Proposed To-Be Diagram
Add as an attachment in this issue.
DATA MIGRATION IMPACT ANALYSIS
Description of Proposed Changes
Provide a concise description of the proposed changes.
New Business Rule
Provide a concise and comprehensive description of the new business rule.
Existing Business Rule
Provide a concise and comprehensive description of the existing business rule.
Changed Business Rule
Provide a concise and comprehensive description of the changes to be made to the business rule.
This is for capturing needs not currently supported by the CEDS model. Please do not send or share actual data as examples in this issue or in attachments.
Author(s)
Lakshmana Kommuri
Authoring Organization(s)
CEPI - State Of Michigan
Email Address
[email protected]
Use Case Title
Restructure DimPersonAddresses to link into facts via Bridge tables
Use Case Overview
DimAddresses is currently bound to the context of K12 Students because of the inclusion of AddressTypeForLearnerOrFamily. Also, there is currently no way to track multiple addresses for a student. This proposal recommends:
Pull Request Number(s) (If applicable)
Use Case Background
CEPI needs to track multiple addresses for Students as well as addresses for staff. The data warehouse model currently doesn't support this.
Components Affected
Delete everything from the list below except the components affected:
CEDS Data Warehouse (complete DW Design Overview Table)
CEDS Data Migrations (complete Data Migration Impact Analysis Table)
DATA WAREHOUSE DESIGN OVERVIEW (Includes Dim, Fact, and Report tables)
For DimPersonAddresses
Create a new bridge table named BridgeK12StudentEnrollmentPersonAddresses. It will include
Create a new bridge table named BridgeK12StudentEconomicDisadvantagePersonAddresses. It will include
As-Is Diagram
Proposed To-Be Diagram
DATA MIGRATION IMPACT ANALYSIS
Description of Proposed Changes
The script to move data from the Staging tables to FactK12StudentEnrollments need additional SQL code to populate BridgeK12StudentEnrollmentPersonAddresses.
This is for capturing needs not currently supported by the CEDS model. Please do not send or share actual data as examples in this issue or in attachments.
Author(s)
Johnny Cunningham
Authoring Organization(s)
CEDS
Email Address
[email protected]
Use Case Title
Provide a concise description that defines the use case.
Add individual program statuses to FactK12StudentAssessments
Use Case Overview
Provide a concise, high-level description of the actions of the use case. While being concise, the description should cover all possible actions for the use case.
Version 11 of the data warehouse broke DimK12Demographics into individual dimensions. This task will add programs Homelessness, Economically Disadvantaged, English Learner, Migrant, and Military Connected from the old DimK12Demographics dimension as well as support for Foster Care, Immigrant, and Title I statuses in FactK12StudentAssessments.
Pull Request Number(s) (If applicable)
Use Case Background
Provide information related to why these changes/additions are needed.
This change is required to track a students program participation through Assessments
Components Affected
Delete everything from the list below except the components affected:
CEDS Data Warehouse (complete DW Design Overview Table)*
CEDS Data Migrations (complete Data Migration Impact Analysis Table)*
DATA WAREHOUSE DESIGN OVERVIEW (Includes Dim, Fact, and Report tables)
Description of Proposed Changes
DATA MIGRATION IMPACT ANALYSIS
Description of Proposed Changes
Update the Staging-to-RDS data migration scripts for Assessments to populate the new program status IDs by joining to the appropriate dimension views.
This is for capturing needs not currently supported by the CEDS model. Please do not send or share actual data as examples in this issue or in attachments.
Author(s)
Duane Brown
Authoring Organization(s)
CEDS
CEDS Data Warehouse Expansion Process Workgroup
Email Address
[email protected]
Use Case Title
Expand the Data Warehouse in the Area of Finance
Use Case Overview
The CEDS Data Warehouse Expansion Process Workgroup met from November 2021 through August 2022 and is proposing the addition of three new Fact tables and several new dimension tables to the Data Warehouse The proposed expansion timing will be aligned with the approval of several new elements and updates to existing elements within CEDS which can be found in this Elements use case ticket: CEDStandards/CEDS-Elements#493
Components Affected
CEDS Data Warehouse (complete DW Design Overview Table)
DATA WAREHOUSE DESIGN OVERVIEW (Includes Dim, Fact, and Report tables)
Describe the bug
The Map field for HighSchoolDiplomaType in RDS.vwDimK12AcademicAwardStatuses has an incorrect field name. It is currently named SexMap, but it should be HighSchoolDiplomaTypeMap.
This is for capturing needs not currently supported by the CEDS model. Please do not send or share actual data as examples in this issue or in attachments.
Author(s)
Lakshmana Kommuri
Authoring Organization(s)
CEPI - State Of Michigan
Email Address
[email protected]
Use Case Title
Add SchoolYearId and PsDemographicId as Foreign Key to FactPsStudentAcademicAwards
Use Case Overview
SchoolYearId and PsDemographicId is needed to populate the Fact table - FactPsStudentAcademicAwards
Use Case Background
CEPI needs SchoolYearId and PsDemographicId data to be available in FactPsStudentAcademicAwards.
Components Affected
CEDS Data Warehouse (complete DW Design Overview Table)
CEDS Data Migrations (complete Data Migration Impact Analysis Table)
DATA WAREHOUSE DESIGN OVERVIEW (Includes Dim, Fact, and Report tables)
Description of Proposed Changes
DATA MIGRATION IMPACT ANALYSIS
Description of Proposed Changes
Update the Staging-to-RDS data migration scripts to populate the new SchoolYearId and PsDemographicId fields by joining to DimSchoolYears and vwDimPsDemographics respectively.
Describe the bug
The population of the DimProgramTypes table is wrong. It is populating over 20,000 options and should only be 41 options from the Program Type table.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Populate only the 41 options from the Program Type element in this table.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
This is for capturing needs not currently supported by the CEDS model. Please do not send or share actual data as examples in this issue or in attachments.
Author(s)
Nathan Clinton
Authoring Organization(s)
AEM Center
Email Address
[email protected]
Use Case Title
Provide a concise description that defines the use case.
Add dimensional model for Accessible Education Materials reporting
Use Case Overview
Provide a concise, high-level description of the actions of the use case. While being concise, the description should cover all possible actions for the use case.
The AEM Center is working with CEDS to identify elements and a reporting data structure to support reporting and analysis needs around accessible education materials that currently does not exist in the domain.
Pull Request Number(s) (If applicable)
Use Case Background
Provide information related to why these changes/additions are needed.
This is for capturing needs not currently supported by the CEDS model. Please do not send or share actual data as examples in this issue or in attachments.
Author(s)
Duane Brown
Authoring Organization(s)
CEDS
Email Address
Use Case Title
Add New Fact Table and Dimension Tables related to Salary Schedule
Use Case Overview
This proposal is to add a new fact to the Data Warehouse to store Salary Schedules. This is related to Elements ticket 428 (CEDStandards/CEDS-Elements#428)
Pull Request Number(s) (If applicable)
Use Case Background
Mississippi needs to capture/store/and report salary schedule data from their LEAs.
This is for capturing needs not currently supported by the CEDS model. Please do not send or share actual data as examples in this issue or in attachments.
Author(s)
Nathan Clinton
Authoring Organization(s)
Center for the Integration of IDEA Data -- CIID
Email Address
[email protected]
Use Case Title
Remove unused functions from Staging schema
Use Case Overview
There are several functions currently in the Staging schema that refer to CEDS IDS reference tables (Ref tables). These will not function without a fully integrated IDS installed in the same database, plus they are no longer necessary. They should be removed.
Pull Request Number(s) (If applicable)
#37
Use Case Background
These functions were created to support legacy Staging-to-IDS data migrations, which are no longer used or supported.
DATA WAREHOUSE DESIGN OVERVIEW (Includes Dim, Fact, and Report tables)
Description of Proposed Changes
Remove the following SQL functions
This is for capturing needs not currently supported by the CEDS model. Please do not send or share actual data as examples in this issue or in attachments.
Author(s)
Lakshmana Kommuri
Authoring Organization(s)
CEPI - State Of Michigan
Email Address
[email protected]
Use Case Title
Add TitleIStatusId to FactK12StudentEnrollments
Use Case Overview
CEPI needed Title I Status data available in FactK12StudentEnrollments.
Components Affected
Delete everything from the list below except the components affected:
CEDS Data Warehouse (complete DW Design Overview Table)
CEDS Data Migrations (complete Data Migration Impact Analysis Table)
DATA WAREHOUSE DESIGN OVERVIEW (Includes Dim, Fact, and Report tables)
Description of Proposed Changes
DATA MIGRATION IMPACT ANALYSIS
Description of Proposed Changes
Update the Staging-to-RDS data migration scripts to populate the new TitleIStatusId field by joining to vwDimTitleIStatuses.
Describe the bug
Two options within RDS.DimK12OrganizationStatuses, "YesReportingOffenses" and "YesNoReportedOffenses" are set to the EDFacts values of "YESWITHREP" and "YESWOREP" respectively. These should be updated to the CEDS codes.
Here is how these data are fixed for Generate instances:
update RDS.DimK12OrganizationStatuses
set GunFreeSchoolsActReportingStatusCode = 'YesReportingOffenses'
where GunFreeSchoolsActReportingStatusCode = 'YESWITHREP'
update RDS.DimK12OrganizationStatuses
set GunFreeSchoolsActReportingStatusCode = 'YesNoReportedOffenses'
where GunFreeSchoolsActReportingStatusCode = 'YESWOREP'
This is for capturing needs not currently supported by the CEDS model. Please do not send or share actual data as examples in this issue or in attachments.
Author(s)
Deborah Donovan
Authoring Organization(s)
Mississippi Department of Education
Email Address
[email protected]
Use Case Title
Create new table to link People and Addresses
Use Case Overview
We would like to be able to link a person (student and staff in particular) with all of their associated addresses, including mailing and physical addresses. There is not currently a way to link this data together for all use cases using existing tables.
Pull Request Number(s) (If applicable)
N/A
Use Case Background
See overview above. For example, we want to display the mailing and physical addresses for all students. Currently, there is no link available.
Components Affected
Delete everything from the list below except the components affected:
CEDS Data Warehouse (complete DW Design Overview Table)
CEDS Data Warehouse Parquet (complete DW Parquet Design Overview Table)
DATA WAREHOUSE DESIGN OVERVIEW (Includes Dim, Fact, and Report tables)
This is for capturing needs not currently supported by the CEDS model. Please do not send or share actual data as examples in this issue or in attachments.
Author(s)
Johnny Cunningham
Authoring Organization(s)
CEDS
Email address
[email protected]
Use Case Title
Provide a concise description that defines the use case.
Add GradeLevelId to FactK12StudentAttendanceRates
Use Case Description
List the proposed element name(s), definition(s), and/or option set(s).
Use Case Background
Provide information related to why these changes/additions are needed.
Location of Element in the Domain Entity Schema
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.