1 / 9

EDEN Best-Practice Sharing

EDEN Best-Practice Sharing. Oregon File Preparation Practices. EDEN File Preparation. Support tables Execute build procedure to import data Data Owner validation Single-click file creation. Support tables.

mtennyson
Télécharger la présentation

EDEN Best-Practice Sharing

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. EDEN Best-Practice Sharing Oregon File Preparation Practices

  2. EDEN File Preparation • Support tables • Execute build procedure to import data • Data Owner validation • Single-click file creation

  3. Support tables • Seven year-to-year support tables are maintained to support the Single-Click File Creation Report - contains all allowable reports DataMap – Defines submissionstructures for each reporting level

  4. Support Tables (cont.) DataMapInstTypCd – Defines the reporting level of the DataMap fields Submission - tracks data load/submission dates by year SubmissionData - Stores the level of report to generate, Header Information and File Name

  5. Support Tables (cont.) N[###] – Stores report data for Data Owner verification and file submission. N[###]Header – Stores the count of records submitted.

  6. 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_BuildN36 @EndYr='2006',@EffYr='2007' N[###] – Stores report data for Data Owner verification and file submission.

  7. 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/)

  8. 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_CreateSubmissionFile @EndYr='2006', @EffYr='2007',@tblNm='N36'

  9. 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 N36 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

More Related