EDEN BestPractice Sharing Oregon File Preparation Practices MIS

  • Slides: 9
Download presentation
EDEN Best-Practice Sharing Oregon File Preparation Practices MIS 2008 / Merging Two Data Collections:

EDEN Best-Practice Sharing Oregon File Preparation Practices MIS 2008 / Merging Two Data Collections: Lessons Learned from the CCD-EDEN Merger

EDEN File Preparation • • Support tables Execute build procedure to import data Data

EDEN File Preparation • • Support tables Execute build procedure to import data Data Owner validation Single-click file creation MIS 2008 / Merging Two Data Collections: Lessons Learned from the CCD-EDEN Merger 2

Support tables • Seven year-to-year support tables are maintained to support the Single-Click File

Support tables • Seven year-to-year support tables are maintained to support the Single-Click File Creation Report - contains allowable reports Data. Map – Defines submission structures for each reporting level MIS 2008 / Merging Two Data Collections: Lessons Learned from the CCD-EDEN Merger 3

Support Tables (cont. ) Data. Map. Inst. Typ. Cd – Defines the reporting level

Support Tables (cont. ) Data. Map. Inst. Typ. Cd – Defines the reporting level of the Data. Map fields Submission - tracks data load/submission dates by year Submission. Data - Stores the level of report to generate, Header Information and File Name MIS 2008 / Merging Two Data Collections: Lessons Learned from the CCD-EDEN Merger 4

Support Tables (cont. ) N[###] – Stores report data for Data Owner verification and

Support Tables (cont. ) N[###] – Stores report data for Data Owner verification and file submission. N[###]Header – Stores the count of records submitted. MIS 2008 / Merging Two Data Collections: Lessons Learned from the CCD-EDEN Merger 5

Execute build procedure to import data • Developer codes T-SQL build procedures to import

Execute build procedure to import data • Developer codes T-SQL build procedures to import data into the report load tables. Once the build procedures are coded and the Support Tables are in place then executing this procedure prepares data for verification and reporting. EXECUTE pr_Build. N 36 @End. Yr='2006', @Eff. Yr='2007' N[###] – Stores report data for Data Owner verification and file submission. MIS 2008 / Merging Two Data Collections: Lessons Learned from the CCD-EDEN Merger 6

Data Owner validation • Once the source data is imported into the year-to-year report

Data Owner validation • Once the source data is imported into the year-to-year report table, the Data Owner electronically validates that all counts are correct using Microsoft SQL 2005 Reporting Services—this step ensures that all data submitted is verified (http: //www. microsoft. com/sql/technologies/reporting/) MIS 2008 / Merging Two Data Collections: Lessons Learned from the CCD-EDEN Merger 7

Single-Click File Creation • Execute a single script to generate all submission files for

Single-Click File Creation • Execute a single script to generate all submission files for a report to a network location. These files are then ready to be uploaded through the EDEN application. EXECUTE pr_Create. Submission. File @End. Yr='2006', @Eff. Yr='2007', @tbl. Nm='N 36' MIS 2008 / Merging Two Data Collections: Lessons Learned from the CCD-EDEN Merger 8

Oregon EDEN Example Database • The Oregon Department of Education has created an example

Oregon EDEN Example Database • The Oregon Department of Education has created an example which creates a working database on a SQL Server 2005 local SQLEXPRESS instance. (This script can be modified to be installed on any SQL Server box. ) • This is a T-SQL script and should be run by a Database Administrator. • This script creates a database called “EDEN” with all Support Tables and Meta-Data necessary for EDEN submissions. • Contains one example build procedure with source table for creating the N 36 report. • Object definitions and instructions for how to do the example are included in the script. • Download the zipped T-SQL script at http: //www. ode. state. or. us/go/EDENexample MIS 2008 / Merging Two Data Collections: Lessons Learned from the CCD-EDEN Merger 9