Merge pull request #19 from CEDStandards/feature/V10-release-candidate

Feature/v10 release candidate

.gitignore

@@ -4,3 +4,4 @@
 
 /res/Thumbs.db
 /res/Thumbs.db
+/.vs

Contributing.md

@@ -20,7 +20,7 @@ It is important to apply a consistent naming standard so users know what to
 expect when they use the data model.  Below are rules to use when creating objects
 in the database.
 
-* Use CEDS entity and element names when possible.
+* Use CEDS entity and technical element names when possible.
   * (Note: CEDS element names have parts to give full context when applicable. Name parts include entity, qualifier, property, and representation. See the naming conventions section in the CEDS Data Model Guide.)
   * A table name often includes the entity part and a column name often includes a property part. For example, in the IDS the "Name" column in the table “Financial Account” corresponds to the CEDS element "Financial Account Name."
 * Use Pascal Case for all objects.

Contributors.md

@@ -2,21 +2,13 @@
 
 Before CEPI, the [Center for the Integration of IDEA Data](https://ciidta.grads360.org/#program) (CIID), through a grant from the Office of Special Education, created the CEDS Data Warehouse with the development of [Generate](https://ciidta.grads360.org/#program/generate). Generate, an EDFacts reporting application, began by using the CEDS Integrated Data Store (IDS) to integrate data from multiple sources for EDFacts reporting but needed the ability to retrieve data quickly out of the system which prompted the first iteration of the CEDS Data Warehouse. For several years, under CIID through the Generate application, the CEDS Data Warehouse was field tested. The [Nevada Department of Education](http://www.doe.nv.gov/) was the pilot state for Generate and assisted in several iterations, updates, and enhancements to Generate. Their efforts, along with other states implementing Generate, helped the CIID team improve the CEDS Data Warehouse structure.
 
-In the next few years, CEDS will continue to work with stakeholders to find ways to bring the community together. The CEDS team is excited to continue to partner with you, the community, in this new era.
+Version 9.1.0.0 was updated primarily based on work done through the CEDS Data Warehouse Expansion Project (https://ceds.communities.ed.gov/#communities/ceds-osc/workgroups/ceds-dw-expansion)
+Contributions from [The Colorado Department of Education](https://www.cde.state.co.us/) and [Michigan's Center for Educational Performance and Infomration (CEPI)](https://www.michigan.gov/cepi/) resulted in additions and insight into the special education and adult education use cases. Additionally [Double Line](https://wearedoubleline.com/) assisted in the build out of the metadata tagging you will find in the dimension tables. Search the extended properties of the Dimension tables to find the associated CEDS element information. Numerous other stakeholders from state education agencies, local education agencies and the vendor community contributed through participation in meetings throughout the project and providing insight into the special education and adult education use cases that made up the scope of the project. It is the CEDS community of stakeholders that make all of this possible.
 
-This version of the CEDS Data Warehouse has been updated primarily based on work done through the CEDS Data Warehouse Expansion Project (https://ceds.communities.ed.gov/#communities/ceds-osc/workgroups/ceds-dw-expansion)
+Version 10.0.0.0 contains contributions from [Michigan's Center for Educational Performance and Infomration (CEPI)](https://www.michigan.gov/cepi/) as well as improved alignment to standard naming conventions and expansion of the metadata tagging in extended properties and increased population of the junk dimension tables. 
 
-We would like to thank the following organizations for their contributions in the release of the CEDS Data Warehouse V9.1.0.0
+CEDS is continuing to work with stakeholders to continue expansion of the Data Warehouse. The next version is expected to contain tables related to finace data with contributions from Maine, Missouri, and Michigan as well as many other stakeholders. The CEDS team is excited to continue to partner with you, the community, in this new era.
 
-[The Colorado Department of Education](https://www.cde.state.co.us/)
-[Michigan's Center for Educational Performance and Infomration (CEPI)](https://www.michigan.gov/cepi/) 
 
-These two education agencies provided extensive time to the build out of the model around their specific use cases providing subject matter experts when needed.
-
-[Double Line](https://wearedoubleline.com/)
-
-Double Line assisted in the build out of the metadata tagging you will find on the elements in the dimension tables. Search the extended properties of the Dimension tables and you will see the associated CEDS element information.
-
-Numerous other stakeholders from state education agencies, local education agencies and the vendor community contributed through participation in meetings throughout the project and providing insight into the special education and adult education use cases that made up the scope of the project. It is the CEDS community of stakeholders that make all of this possible.
 
 

README.md

@@ -9,19 +9,18 @@ Modeled for longitudinal storage and reporting of P-20W data, the Common Educati
 
 To create a new instance of the CEDS Data Warehouse on your SQL Server, perform the following steps.
 
-1. Open the database creation script at /src/ddl/CEDS-Data-Warehouse.sql using your preferred SQL client. 
+1. Open the database creation script at /src/ddl/CEDS-Data-Warehouse-V10.0.0.0.sql using your preferred SQL client. 
 2. Connect to the server on which you want to create the CEDS Data Warehouse instance.
-3. Find and replace the existing database name in the script (i.e. CEDS-Data-Warehouse-V9_1_0_0) with the database name of your choice.
-4. Run the script. 
-
-The database is empty by default.  Proceed with the following instructions to load CEDS Element metadata and CEDS Option Set values into the reference tables.
-1. Open the Create CEDS Element Tables V9.0.0.0 document at /src/dimension-data/Create-CEDS-Element-Tables-V9.0.0.0
-2. Connect to the server on which you created the CEDS Version 9.1.0.0 instance
-3. Find and replace the existing database name in the script (i.e. CEDS-Data-Warehouse-V9_1_0_0) with the name of your data warehouse instance.
-4. Run the script
-5. Open the Junk-Table-Dimension-Population-V9.1.0.0 document at /src/dimension-data/Junk-Table-Dimension-Population-V9.1.0.0
-6. Find and replace the existing database name in the script (i.e. CEDS-Data-Warehouse-V9_1_0_0) with the name of your data warehouse instance.
-7. Run the script
+3. Find and replace the existing database name in the script (i.e. CEDS-Data-Warehouse-V10-0-0-0) with the database name of your choice.
+4. Run the script. This will create the CEDS-Data-Warehouse-V10.0.0.0 database.
+
+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.
+1. Open the Create CEDS Elements V10.0.0.0 document at /src/dimension-data/CEDS-Elements-V10.0.0.0
+2. Connect to the server on which you created the CEDS Version 10.0.0.0 instance
+3. Run the script. This will create the CEDS-Elements-V10.0.0.0 Database
+4. Open the Junk-Table-Dimension-Population-V10.0.0.0 document at /src/dimension-data/Junk-Table-Dimension-Population-V10.0.0.0
+5. Find and replace the existing database name in the script (i.e. CEDS-Data-Warehouse-V10-0-0-0) with the name of your data warehouse instance.
+6. Run the script. This will populate the dimension tables in the CEDS Data Warehouse Version 10
 
 ## Contributing