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)
Amy Powell Moman, Eric Marshall

Authoring Organization(s)
North Carolina Department of Public Instruction

Use Case Title
Add License Area Years Experience as an element to CEDS

Target Date Needed
ASAP

Use Case Description
North Carolina collects data on the years experience for each individual license area in addition to general years of teaching experience (Years Prior Teaching Experience – 000302)

Use Case Background
North Carolina is currently mapping existing state data to the CEDS IDS. As part of the process, North Carolina is identifying data elements that are not currently found in CEDS and would like to add these elements to CEDS. North Carolina is also working with eScholar to ensure needed elements are available in their schema.

Location of Element in the Domain Entity Schema
License Area Years Experience – K12/K12 Staff/Credential or License

Author(s)
Amy Powell Moman

Authoring Organization(s)
North Carolina Department of Public Instruction (NCDPI)

Email address
[email protected]

Use Case Title
Add new CEDS element for “Staff paid out of district”

Target Date Needed
ASAP

Use Case Description
NCDPI collects information to indicate if a staff member’s salary is paid from funds outside of the current school district where they are assigned. Currently this is a “Yes” or “No” indicator.

Use Case Background
NCDPI collects information to indicate if a staff member’s salary is paid from funds outside of the current school district where they are assigned. Currently this is a “Yes” or “No” indicator.

Location of Element in the Domain Entity Schema
?

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)
Andrea Hall

Authoring Organization(s)
CEDS / EDFacts

Email address
[email protected]

Use Case Title
Add elements for EDFacts reporting (File Specification 206)

Target Date Needed
ASAP

Use Case Description
EDFacts changed their data collection requirements for School Support and Improvement

EDFacts data group 842: revised definition; revised category configuration to include categories Comprehensive Support and Improvement, Targeted Support and Improvement and Additional Targeted Support and Improvement

Recommend adding 3 new elements and option sets:

1. Comprehensive Support and Improvement
   - Comprehensive Support and Improvement
   - Comprehensive Support and Improvement – Exit Status
   - Not Comprehensive Support and Improvement
2. Targeted Support and Improvement
   - Targeted Support and Improvement
   - Targeted Support and Improvement – Exit Status
   - Not Targeted Support and Improvement
3. Additional Targeted Support and Improvement
   - Additional Targeted Support and Improvement
   - Not Additional Targeted Support and Improvement

Use Case Background
These elements are required for EDFacts reporting

Location of Element in the Domain Entity Schema
K12 -> K12 School -> Accountability

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)
Amy Powell Moman

Authoring Organization(s)
North Carolina Department of Public Instruction (NCDPI)

Email Address
[email protected]

Use Case Title
Add a new CEDS elements to capture if and what schools close due to new school opening

Target Date Needed
ASAP

Use Case Background
When a new school opens, NCDPI collects information on if other schools are closing as a result of the school open and if so, what schools will close. Currently this is captured in two fields: “SCHOOL_CLOSINGS_DUE_TO_OPENING” and “LIST_OF_CLOSING_SCHOOLS”.

Use Case Description
When a new school opens, NCDPI collects information on if other schools are closing as a result of the school open and if so, what schools will close. Currently this is captured in two fields: “SCHOOL_CLOSINGS_DUE_TO_OPENING” is captured as “Yes” or “No”. “LIST_OF_CLOSING_SCHOOLS” is a text field.

Location of Element in the Domain Entity Schema
?

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)
PSLC DataShop

Authoring Organization(s)
Carnegie Mellon University

Use Case Title
The following elements support the mapping of DataShop data to CEDS.
CEDS_first_pass_090919-18OCT_response.xlsx

Target Date Needed
n/a

Use Case Description

Transaction Export Data:

Timezone - timezone
Dataset Level <= 100 chars - This element is variable and can allow for a hierarchical representation of the problems. In our transaction export, multiple columns of this type are allowed. A Dataset Level. An example of the correct use of this column heading is Level (Unit), where "Unit" is the dataset level title and the value in the column is the levelname (e.g., "Understanding Fractions"). The Level column should always be of the format Level (level_title). The level title must be ≤ 100 characters and consist of letters, numbers, dashes, underscores, and spaces. If a dataset level title is not included, it will become "Default". Multiple Level columns are OK. For additional description, see the level element in the Guide. In tutor-message format XML, level "title" is referred to as "type".
Total Num Hints integer - The total number of hints available for a problem.
Student Response Type <= 30 chars - ATTEMPT or HINT_REQUEST
Student Response Subtype <= 30 chars - polynomial (generally discreet values)
Tutor Response Type - RESULT or HINT_MSG
Feedback Classification <= 255 chars - A further classification of the outcome. See action_evaluation / classification in the Guide. Note that if Feedback Classification has a value, Feedback Text must have a value as well.
Feedback Text <= 65,535 chars - The body of a hint, success, or error message shown to the student.
Condition Name <= 80 chars - "A study/experimental condition. Must always be paired with Condition Type, even if a condition does not have a condition type. A describes a study condition, in the case that these data are being collected in the context of a research study."
Condition Type <= 255 chars - A condition classification. Must always be paired with Condition Name, even if a condition does not have a condition type. Multiple Condition Type columns are OK. If Condition Type is specified, Condition Name must have a value as well.

Student-Step Export Data:

Hints integer - Total number of hints requested by the student for the step. (<= Total Num Hints)
Condition <= 65,535 chars - The name and type of the condition the student is assigned to. In the case of a student assigned to multiple conditions (factors in a factorial design), condition names are separated by a comma and space. This differs from the transaction format, which optionally has "Condition Name" and "Condition Type" columns.
KC (model-name) <= 65,535 chars - (Only shown when the "Knowledge Components" option is selected.) Knowledge component(s) associated with the correct performance of this step. In the case of multiple KCs assigned to a single step, KC names are separated by two consecutive tildes ("~~").
Opportunity (model-name) integer - (Only shown when the "Knowledge Components" option is selected.) An opportunity is the first chance on a step for a student to demonstrate whether he or she has learned the associated knowledge component. Opportunity number is therefore a count that increases by one each time the student encounters a step with the listed knowledge component. In the case of multiple KCs assigned to a single step, opportunity number values are separated by two tildes ("~~") and are given in the same order as the KC names.
Predicted Error Rate (model-name) double - A hypothetical error rate based on the Additive Factor Model (AFM) algorithm. A value of "1" is a prediction that a student's first attempt will be an error (incorrect attempt or hint request); a value of "0" is a prediction that the student's first attempt will be correct. For specifics, see below "Predicted Error Rate" and how it's calculated. In the case of multiple KCs assigned to a single step, Datashop implements a compensatory sum across all of the KCs, thus a single value of predicted error rate is provided (i.e., the same predicted error rate for each KC assigned to a step). For more detail on Datashop's implementation for multi-skilled step, see Model Values page.

Use Case Background
A review of DataShop and CEDS schemas was conducted between Mike Komisin and Jim Goodell. Contact: [email protected]

Location of Element in the Domain Entity Schema

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)
Daniel Courtney

Authoring Organization(s)
National Defense University

Email address
[email protected]

Use Case Title
Update "Military Branch" Option Set to Include "SpaceForce - Space Force"

Target Date Needed
ASAP

Use Case Description
Update "Military Branch" Option Set to Include "SpaceForce - Space Force"

Use Case Background
With the signing of the National Defense Authorization Act for Fiscal Year 2020, the United States Space Force (USSF) became the sixth branch of the U.S. Armed Forces. This should be reflected in the next release of CEDS.

Location of Element in the Domain Entity Schema
GUID - 001640

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)
Amy Powell Moman

Authoring Organization(s)
North Carolina Department of Public Instruction (NCDPI)

Email address
[email protected]

Use Case Title
Add a new element to capture the current schools from which a new school’s population will come

Target Date Needed
ASAP

Use Case Description
When a new school is opening, NCDPI collects a list of the current schools from which the new school’s student population will come. Currently this is collected in a text field.

Use Case Background
When a new school is opening, NCDPI collects a list of the current schools from which the new school’s student population will come.

Location of Element in the Domain Entity Schema

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)
Amy Powell Moman

Authoring Organization(s)
North Carolina Department of Public Instruction (NCDPI)

Email Address
[email protected]

Use Case Title
Add additional options to Increased Learning Time Type (000164): Night school, Before School, After School

Target Date Needed
ASAP

Use Case Description
For reporting purposes and for student accounting, NCDPI is asking for the addition of “Night School” to be added to the option set of the CEDS element Increased Learning Time Type (000164).

Additionally, NCDPI considers before and after school program as separate types of programs and are often reported as such. The current option of “Before or After School” does not capture the distinction needed for reporting.

Use Case Background
For reporting purposes and for student accounting, NCDPI is asking for the addition of “Night School” to be added to the option set of the CEDS element Increased Learning Time Type (000164).

Additionally, NCDPI considers before and after school program as separate types of programs and are often reported as such. The current option of “Before or After School” does not capture the distinction needed for reporting.
Option set code purposed

1. Night School option: if a school offers a Night School program.
2. Before School option: if a school offers a Before School program.
3. After School option: if a school offers an After School program.

Location of Element in the Domain Entity Schema
K12 -> K12 School -> Institution Characteristics

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)
Beth Young

Email address
[email protected]

Use Case Title
Need for more technology/equipment elements (in schools and districts)

Use Case Description
CEDS needs to expand its elements regarding technology in schools and districts. The current COVID-19 crisis highlights the need for elements that can quickly ascertain the technology and equipment available at the school for instruction and support of home instruction. There are very few elements in CEDS that support this use case now, however, there are elements in Extend that come from the NCES Handbooks and the Forum’s Technology in Schools guide. Both of these are older projects and these elements should be reviewed before implementing in CEDS.

Current CEDS Elements:

There are several a few elements in the facilities section which cover Building Systems (https://ceds.ed.gov/CEDSElementDetails.aspx?TermxTopicId=47029) and Building Technology Wiring System Type (https://ceds.ed.gov/CEDSElementDetails.aspx?TermxTopicId=47030). There is also an element that looks at Integrated Technology Status (https://ceds.ed.gov/CEDSElementDetails.aspx?TermxTopicId=42896) of the district needed for federal reporting.

Current Extend Elements to be considered (full definitions and options sets in attachment):

Equipment Description
Equipment Mobility
Equipment Name
Equipment Purpose
Technology Equipment
Technology Equipment Networking
Technology Equipment Use Purpose
Computer Hardware
Computer Operating System Version
LAN Bandwidth Within the Building
IP Address
FTP Address
Software Application License Number
Software Application Type
Software Application Version and Release Number

Other Elements?

There may also be elements that are not listed here that need to be added. For example:

1. How is one-to-one equipment matched up and tracked when they are sent home with students? 2. What else gets sent home with students beyond a laptop and charger?
2. Wifi hotspots?
3. What else?

Technology Extend Elements.docx

Use Case Background
Most of these elements came from the Forum's Technology in Schools guide, the predecessor to the Forum Guide to Technology Management in Education: https://nces.ed.gov/forum/tec_intro.asp They were incorporated into the NCES Handbooks and then moved over to CEDS Extend.

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)
Amy Powell Moman

Authoring Organization(s)
North Carolina Department of Public Instruction

Email address
[email protected]

Use Case Title
Add “block” as a code set option to Session type (000254)

Target Date Needed
ASAP

Use Case Description
NCDPI collects the predominate school schedule type for all schools. The options are semester, block, and quarterly. While this element can map to CEDS element Session Type (000254) with a similar intent, an additional option of “Block” needs to be added for NCDPI’s purposes.

Use Case Background
NCDPI collects the predominate school schedule type for all schools. The options are semester, block, and quarterly. While this element can map to CEDS element Session Type (000254) with a similar intent, an additional option of “Block” needs to be added for NCDPI’s purposes.

Location of Element in the Domain Entity Schema
K12 -> K12 School -> Session

Author(s) Marlene Dorenkamp

Authoring Organization(s) Iowa Department of Education

Email address [email protected]

Use Case Title
K12Staff>Professional Development>Career Education Plan Type>An indication of whether a student completed an individualized guidance and counseling plan.

Target Date Needed NA

Use Case Description
List the proposed element name(s), definition(s), and/or option set(s).
K12Staff>Professional Development>Career Education Plan Type>An indication of whether a student completed an individualized guidance and counseling plan.

Use Case Background
Provide information related to why these changes/additions are needed.
This description relates to a students individualized guidance and counseling plan, but it is listed under K12 staff. This seems to be in the wrong domain. It should go to Elementary and Secondary K12>K12 Student domain entity.
Location of Element in the Domain Entity Schema
Elementary and Secondary K12>K12 Student domain entity.

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)
Nancy Copa

Authoring Organization(s)
AEM Corporation

Email address
[email protected]

Use Case Title
Update definition of Student of Support Service Type to support offerings

Target Date Needed

Use Case Description
Student Support Service Type
Type of related or ancillary services provided to a person or a group of persons within the formal educational system or offered by an outside agency which provides non-instructional services to support the general welfare of students. This includes physical and emotional health, the ability to select an appropriate course of study, admission to appropriate educational programs, and the ability to adjust to and remain in school through the completion of programs. In serving a student with an identified disability, related services include developmental, corrective, or supportive services required to ensure that the person benefits from special education.

Use Case Background
We propose adding the words “offered or” before "provided" in the definition and deleting “offered” before “by an outside agency”. This will capture the scenario at the school level where a support service type is offered by the school, but no one takes advantage of it. It would read:

Type of related or ancillary services offered or provided to a person or a group of persons within the formal educational system or by an outside agency which provides non-instructional services to support the general welfare of students. This includes physical and emotional health, the ability to select an appropriate course of study, admission to appropriate educational programs, and the ability to adjust to and remain in school through the completion of programs. In serving a student with an identified disability, related services include developmental, corrective, or supportive services required to ensure that the person benefits from special education.

We also propose adding a usage note for clarity that reads:
At the organization level, this element indicates the services offered to students. At the individual level, this element indicates the services received by students.

Location of Element in the Domain Entity Schema
K12 -> K12 School -> Institution Characteristics
K12 -> K12 Student -> Individualized Program
K12 -> K12 Student -> Individualized Program -> Services

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 Education Performance and Information (CEPI - Michigan)

Use Case Title
Provide a concise description that defines the use case.
CEPI has addresses (both fields) for postsecondary institutions that are larger than 40/30 characters (the sizes currently allotted). For future support, we recommend increasing both to 60 characters. You may want to consider increasing the size of Building Site Number to 60 as well.

Target Date Needed
We are implementing in a reporting project and will submit IDS changes to GitHub once the project is complete. No immediate need for reaction necessary.

Use Case Description
List the proposed element name(s), definition(s), and/or option set(s).
Some institutions are using the full name of the building to designate the "line 2" of their address, which we translate into Address Apartment Room or Suite Number. Some of these names are larger than 30 characters.

Location of Element in the Domain Entity Schema
Anywhere where "Address" is located.

Author(s)
Chelsea Waite

Authoring Organization(s)
Christensen Institute

Email address
[email protected]

Use Case Title
Add new element: Project Based Learning Type

Target Date Needed
Fall 2020

Use Case Description
Project-based Learning Indicator (NEW)
Definition: An indicator that an instructional model in which a student learns through answering complex questions or solving for real-world problems is implemented.

Option set:

• Yes | An instructional model in which a student learns through answering complex questions or solving for real-world problems is implemented.

• No | An instructional model in which a student learns through answering complex questions or solving for real-world problems is not implemented.

Project-based learning Type (NEW)
Definition: A type of instructional model in which a student learns through answering complex questions or solving for real-world problems.

Option set:

• Primarily Projects | Projects are a central approach to learning core content and skills, rather than added on as extra activities once core content is covered.

• Student-developed | Projects are developed by students with teacher advisement. Students are likely to be working on diverse project topics and goals.

• Teacher-developed | Projects are developed by teachers and executed by students.

• Other

Use Case Background
This need was identified through the Canopy project led by the Clayton Christensen Institute.

We propose adding two new elements: Project-Based Learning Indicator and Project-Based Learning Type. Project-based learning is a strategy teachers are using in the classroom and sometimes it is a strategy in place across an entire school. These two elements will allow schools to document both whether, and how, the strategy is being implemented, and in turn evaluate the effectiveness of the strategy.

NOTE: This element should be included in such a way that Project-Based Learning Type is able to ‘mark all that apply’ and not a single option per school or per course.

Location of Element in the Domain Entity Schema
Recommend:
K12 -> Course Section
K12 -> K12 Course
K12 -> K12 School -> Directory

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)
Amy Powell Moman

Authoring Organization(s)
North Carolina Department of Public Instruction

Email address
[email protected]

Use Case Title
Add "Regional Membership" and "Regional Membership identifier" as new CEDS Elements.

Target Date Needed
ASAP

Use Case Description
There are multiple regional membership assignments for LEAs and Charter Schools within NCDPI. A district’s regional membership is used for reporting as well as analysis. NCDPI is requesting a new element to record the regional membership assignment as well as a field that identifies the type of regional membership.

Use Case Background
There are multiple regional membership assignments for LEAs and Charter Schools within NCDPI. A district’s regional membership is used for reporting as well as analysis. For example, each district falls into one of eight State Board of Education regions. NCDPI Testing and Accountability Services have six main regions. There are also District and Regional support work that divides the state into regions as well. eScholar has an element of Regional Organization Code.

Location of Element in the Domain Entity Schema
?

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)
Amy Powell Moman

Authoring Organization(s)
North Carolina Department of Public Instruction

Email address
[email protected]

Use Case Title
Provide a concise description that defines the use case.

Target Date Needed
ASAP

Use Case Description
All schools under the auspices of the NC Department of Public Instruction are assigned a "school designation type" that coincides with funding as well as reporting. They are designated as either Charter, Federal, Laboratory, Public, Other, or Regional School. NCDPI is asking for this additional element, but not a particular pre-defined code set as schools are mostly likely not designated the same across states.

Use Case Background
All schools under the auspices of the NC Department of Public Instruction are assigned a "school designation type" that coincides with funding as well as reporting. They are designated as either Charter, Federal, Laboratory, Public, Other, or Regional School. NCDPI is asking for this additional element, but not a particular pre-defined code set as schools are mostly likely not designated the same across states.

Location of Element in the Domain Entity Schema
?

Author(s)
Chelsea Waite

Authoring Organization(s)
Christensen Institute

Email address
[email protected]

Use Case Title
Add new element: Student Support Service Eligibility

Target Date Needed
Fall 2020

Use Case Description
Student Support Service Eligibility (NEW)
Definition: The group of persons to whom related or ancillary services are offered within the formal educational system or by an outside agency which provides non-instructional services to support the general welfare of students.

Option set:

• All students | All students are eligible to receive support services, not just those for whom accommodations are traditionally reserved, e.g. students receiving aids and services under Section 504 of the Rehabilitation Act of 1973, as amended, or under the Individuals with Disabilities Education Act (IDEA) according to an Individualized Education Program (IEP), Individual Family Service Plan (IFSP), or service plan.

• Students with disability | Accommodations are reserved for students receiving aids and services under Section 504 of the Rehabilitation Act of 1973, as amended, or under the Individuals with Disabilities Education Act (IDEA) according to an Individualized Education Program (IEP), Individual Family Service Plan (IFSP), or service plan.

Use Case Background
This need was identified through the Canopy project led by the Clayton Christensen Institute.

We propose adding a new element: Student Support Service Eligibility. Many schools are taking steps to extend accommodations and supports traditionally reserved for students with disabilities, so that any student may take advantage of them. The addition of the Student Support Service Eligibility element will allow schools to specify whether support services are offered to all students, or a subset who meet the eligibility criteria.

Location of Element in the Domain Entity Schema
K12 -> K12 School -> Institution Characteristics
K12 -> K12 Student -> Individualized Program
K12 -> K12 Student -> Individualized Program -> Services

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)
Jim Goodell (wearing hat of IEEE Reusable Competency Definition standard workgroup chair)

Authoring Organization(s)
IEEE Learning Technology Standards Committee

Email address
[email protected]

Use Case Title
Provide a concise description that defines the use case.
Change element name "Competency Definition Node Name" to "Competency Definition Short Name"

Target Date Needed
2021

Use Case Description
List the proposed element name(s), definition(s), and/or option set(s).

1. Change existing element name "Competency Definition Node Name" (element id 001409 ) to "Competency Definition Short Name"
2. Change the definition to reflect the name and broader use: “Short name or label for the competency definition or its node in a competency framework.”

Use Case Background
Provide information related to why these changes/additions are needed.

The original use case for the element was narrowly defined for alternative/accessible pathways in a "learning map" (from alternative assessment consortium out of U. of Kansas). In practice this element is being used as a label for the competency definition object even when it is not part of a map or graph.

Location of Element in the Domain Entity Schema
Competencies -> Competency Definition

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)
Andrea Hall

Authoring Organization(s)
CEDS / EDFacts

Email address
[email protected]

Use Case Title
Add element "Achievement Status"

Target Date Needed
ASAP

Use Case Description
Element Name: Achievement Status
Element Definition: An indication of whether the students achieved the measure for career and technical education.
Element option set: ACHSTSCTEYES (Achieved); ACHSTSCTENO (Did not achieve)

Use Case Background
This element is needed to fulfill a new EDFacts reporting requirement for SY 2019-20 (FS217 - CTE Concentrators Program Quality).

Location of Element in the Domain Entity Schema
Career and Technical -> CTE Student -> Academic Record -> Academic Award

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 / Michigan
Use Case Title
Add Organization and Program Type to Support Early and Middle College

Target Date Needed
ASAP
Use Case Description
Michigan tracks schools that offer early and middle college to students. An example of National Definitions for this can be found here: http://mcnc.us/about/middle-early-college/ , but there are other examples as well of this type of Organization. An Early/Middle College is a school that exclusively offers early middle college to students. The need to track this type of Organization and to also track students in High School who are enrolled in a Program that allows them to participate in Early Middle College is needed. It would be beneficial to bring in other states that have similar offerings to come up with a standard definition across that will meet all of the needs.

Use Case Background
Provide information related to why these changes/additions are needed.

Location of Element in the Domain Entity Schema

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)
Andrea Hall

Authoring Organization(s)
CEDS / EDFacts

Email address
[email protected]

Use Case Title
Add Adult Education to Entry Grade Level

Target Date Needed
ASAP

Use Case Description
Value to be added to Entry Grade Level: AE (Adult Education).
The grade level of Adult Education (AE) is used for those LEAs and schools that provide adult education programs. If an LEA or school offers AE, then AE is required for reporting to EDFacts.

Use Case Background
For SY 19-20, EDFacts file specification 052 (Membership) requires states to report on students with a grade level of Adult Education (AE) if the state offers adult education programs. If the LEA is providing adult education, they are likely tracking it in their student information system with an enrollment and that would require they put a grade level and since they can’t use any of the grade levels currently in CEDS for that student, they would be going custom. The use case of Entry Grade level in the SIS is consistent with the use in EDFacts and Grades Offered.

Location of Element in the Domain Entity Schema
K12 -> K12 Student -> Enrollment

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 / EDFacts

Email address
[email protected]

Use Case Title
Add Single Management (non-profit) and Single Management (for-profit) to the Charter School Management Organization Type Element

Target Date Needed
ASAP

Use Case Description
EDFacts FS196 added two new options to Data Group 829 - Management organization type. These are:

1. Single Management (non-profit) - A non-profit organization that is not a CMO or EMO and that provides management services to one charter school.
2. Single Management (for-profit) - A for-profit entity that is not a CMO or EMO and that provides management services to one charter school.

EDFacts has also deprecated the option "Other - an organization that is not a CMO or EMO and that provides management services to one or more charter schools."

Recommend adding the following to the Charter School Management Organization Type element:
Description: Single Management (non-profit)
Definition: A non-profit organization that is not a CMO or EMO and that provides management services to one charter school.
Code: SMNP

Description: Single Management (for-profit)
Definition: A for-profit entity that is not a CMO or EMO and that provides management services to one charter school.
Code: SMFP

Recommend deprecating the option "Other Management Organization - An organization that is not a CMO or EMO and that provides management services to one or more charter schools." but retaining in the IDS for historical purposes.

Use Case Background
These elements are needed for required EDFacts reporting.

Location of Element in the Domain Entity Schema
K12 -> K12 School -> Directory -> Charter School Management Organization
K12 -> Organization -> Identification

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)
Andrea Hall

Authoring Organization(s)
CEDS / EDFacts

Email address
[email protected]

Use Case Title
Add element "State Appropriation Methods" to satisfy EDFacts reporting requirement

Target Date Needed
ASAP

Use Case Description
Element Name: State Appropriation Methods
Element Definition: Methods used to provide state appropriations to schools.
Element Option Set:
STEAPRDRCT - Direct from state. (Charter school receives allocations and appropriations directly from the state.)
STEAPRTHRULEA - Through local school district. (Charter school receives appropriations allocated by the state through the local school district with no local school district control on allocation of funds (e.g. passthrough allocations).
STEAPRALLOCLEA - Allocation by local school district. (Local school district receives appropriation of funds from state and allocates funding to charter school, local school district has similar decision making control on charter school’s use of funds as district has for traditional public schools (e.g. district operated charter school.)

Use Case Background
This element is needed to fulfill a new EDFacts reporting requirement for SY 19-20 (FS207 - State Appropriations for Charter Schools.)

Location of Element in the Domain Entity Schema
K12 -> K12 School -> Finance

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)
Andrea Hall

Authoring Organization(s)
CEDS/EDFacts

Email address
[email protected]

Use Case Title
Add new element: Major Racial and Ethnic Groups

Target Date Needed
ASAP

Use Case Description
For Accountability and Assessment data, EDFacts requires that states report on 11 major racial and ethnic subgroups. To accommodate this requirement, add a new element called "Major Racial and Ethnic Groups" with the following options:

MAN | American Indian \ Alaska Native \ Native American
MA | Asian
MAP | Asian \ Pacific Islander
MB | Black (not Hispanic) African American
MF | Filipino
MHN | Hispanic (not Puerto Rican)
MHL | Hispanic \ Latino
MM | Multicultural \ Multiethnic \ Multiracial \ other
MNP | Native Hawaiian \ other Pacific Islander \ Pacific Islander
MPR | Puerto Rican
MW | White (not Hispanic) \ Caucasian

Use Case Background
These elements are required for EDFacts reporting.

Location of Element in the Domain Entity Schema
K12 -> K12 Student -> Demographics

Author(s)
Credential Engine

Authoring Organization(s)
Credential Engine

Email address
[email protected] (issue submitter)
[email protected]

Use Case Title
Possible "Credential Definition Type" element

Target Date Needed
By 2021?

Use Case Description
List the proposed element name(s), definition(s), and/or option set(s).
See: https://docs.google.com/document/d/1ocGhpHXBsK8oYZ5wBqtvzrjJb2B5AIvH87bqTm5tquk/edit

CEDS currently doesn't have a specific controlled vocabulary for Credential Type. It has a "Credential Category" and "Credential Category System" but without even specifying the possible systems.

Use Case Background
Provide information related to why these changes/additions are needed.

The Credential Engine is considering adding a term based on a use case from New Jersey:

"The State of New Jersey is currently working towards mapping information over 1,000 credentials in their Eligible Training Provider List (ETPL) to publish to the Registry. While gathering the credential information and reviewing the types of credentials to be published, it was determined that a use case for an additional credential type needs to be explored; likely, other agencies, systems, and institutions will benefit from a credential type that meets this need as well."

CEDS currently doesn't have a specific controlled vocabulary for Credential Type. It has a "Credential Category" and "Credential Category System" but without even specifying the possible systems.

(See https://docs.google.com/document/d/1ocGhpHXBsK8oYZ5wBqtvzrjJb2B5AIvH87bqTm5tquk/edit
for more information about the Credential Engine context.)

Location of Element in the Domain Entity Schema

Author(s)
Amy Powell Moman

Authoring Organization(s)
North Carolina Department of Public Instruction (NCDPI)

Email address
[email protected]

Use Case Title
Add new CEDS element: “Student Uniform Required”

Target Date Needed
ASAP

Use Case Description
NCDPI collects if a school requires students to wear school uniforms and would like this element added. Currently, it is being collected as “Yes” or “No”.

Use Case Background
NCDPI collects if a school requires students to wear school uniforms and would like this element added. Currently, it is being collected as “Yes” or “No”.

Location of Element in the Domain Entity Schema
?

Describe the bug
The definition of the option description 'Grade 13' has a typo.

To Reproduce

1. Go to 'Elements -> View Domain Entity Schema'
2. Drill down to 'Assessments -> Assessment Registration'
3. Click on the element name 'Assessment Registration Grade Level To Be Assessed'
4. See error in Option set description for option 'Grade 13'

Expected behavior
'13is' should be separated by a space, e.g., '13 is'

Screenshots

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)
Amy Powell Moman

Authoring Organization(s)
North Carolina Department of Public Instruction

Email address
[email protected]

Use Case Title
Add “Primary School Program Type” as a CEDS element

Target Date Needed
ASAP

Use Case Description
NCDPI classifies individual schools into 5 primary school program types: Magnet, Hospital, Cooperative Innovative High School, Early College, and None. NC would like to ask the CEDS community if there is need for a new element to represents a school’s primary program type or if it NC specific?

Use Case Background
NCDPI classifies individual schools into 5 primary school program types: Magnet, Hospital, Cooperative Innovative High School, Early College, and None. This NC school program type could be mapped to the CEDS element program type (000225); however, Hospital, Cooperative Innovative High School, Early College would need to be added to the code set. In addition, NCDPI does not feel the CEDS element school program type is definitional the same as the primary school program type.

Location of Element in the Domain Entity Schema
K12 -> K12 School -> Directory

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)
Amy Powell Moman

Authoring Organization(s)
North Carolina Department of Public Instruction

Email address
[email protected]

Use Case Title
Request rewording of the definition of the CEDS element (000584) Cohort Graduation Year.

Target Date Needed
ASAP

Use Case Description
In current definition of the CEDS element (000584) Cohort Graduation Year, the word “cohort” has the potential to be interpreted differently than was intended. The current definition is: “The year the cohort graduated with a regular high school diploma.” It is ambiguous as to whether cohort here denotes a single student or the cohort to which the student belongs. NCDPI suggests the definition to be changed to: “The year students in the cohort graduated with a regular high school diploma” or something similar.

Use Case Background
In current definition of the CEDS element (000584) Cohort Graduation Year, the word “cohort” has the potential to be interpreted differently than was intended. The current definition is: “The year the cohort graduated with a regular high school diploma.” It is ambiguous as to whether cohort here denotes a single student or the cohort to which the student belongs. NCDPI suggests the definition to be changed to: “The year students in the cohort graduated with a regular high school diploma” or something similar.

Location of Element in the Domain Entity Schema
K12 -> K12 Student -> Enrollment
Postsecondary -> PS Student -> Demographic

Describe the bug
The URL in the definition for element 'County ANSI Code' is no longer valid. The correct URL is: https://www.census.gov/library/reference/code-lists/ansi.html#par_statelist

To Reproduce
Steps to reproduce the behavior:

1. Go to 'Elements > View Domain Entity Schema'
2. Leave Domain set to 'All'
3. Enter 'County ANSI Code' in the search field'
4. Click on any of the records returned ('County ANSI Code)'
5. Review the definition
6. Click on http://www.census.gov/geo/reference/codes/cou.html
7. See error

Expected behavior
The link will direct the user to the appropriate location of the county ANSI codes.

Author(s)
Amy Powell Moman

Authoring Organization(s)
North Carolina Department of Public Instruction (NCDPI)

Email address
[email protected]

Use Case Title
Add new CEDS element/code option for “Unlisted Phone Number”

Target Date Needed
ASAP

Use Case Description
NCDPI collects data on if a phone number for a contact is unlisted. This indictor is used when pulling contact information. It is currently stored in a nullable “Yes” or “No” field.

Use Case Background
NCDPI collects data on if a phone number for a contact is unlisted. This indictor is used when pulling contact information. It is currently stored in a nullable “Yes” or “No” field.

Location of Element in the Domain Entity Schema
?

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)
Daniel Courtney

Authoring Organization(s)
National Defense University

Email address
[email protected]

Use Case Title
Update "Military Active Student Indicator" Option Set

Target Date Needed
ASAP

Use Case Description
Update "Military Active Student Indicator" Option Set

Use Case Background
The current definition of the "Military Active Student Indicator" element is:

An indication that the student is currently serving on Active Duty, in the National Guard, or in the Reserve components of the United States military services

the current option set is:

NotActive - Not Active
Active - Active
Unknown - Unknown

There is no way to delineate whether a student is a member of the National Guard or a member of a Service's Reserve force with the current option set. Per U.S. Code Title 10 - Armed Forces >> Subtitle E - Reserve Components >> Part II - Personnel Generally >> Chapter 1209 - Active Duty, members of the Army National Guard and the Air National Guard are considered part of the reserve components (i.e. "Not Active"), yet they are nonetheless different from their Army Reserve and Air Force Reserve counterparts.

I am proposing that CEDS adds an additional value to the option set, "Guard - Guard", and that the existing option set value of "NotActive - Not Active" be changed to "Reserve - Reserve".

Location of Element in the Domain Entity Schema
GUID - 001577

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)
Andrea Hall

Authoring Organization(s)
CEDS

Email address
[email protected]

Use Case Title
Add element "Standard Occupational Classification" to Workforce Domain

Target Date Needed
ASAP

Use Case Description
The element currently exists in the Early Learning, K12, Postsecondary and Credentials domains, but is not included in the Workforce domain.

Use Case Background
This element is relevant to the Workforce domain by its definition: "A Bureau of Labor Statistics coding system for classifying occupations by work performed and, in some cases, on the skills, education and training needed to perform the work at a competent level. See http://www.bls.gov/soc/soc_structure_2010.pdf."

Location of Element in the Domain Entity Schema
Workforce -> Employment

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)
Jill Aurand

Authoring Organization(s)
Nebraska Department of Education

Use Case Title
Add "Full Time Equivalency" as an element to CEDS to track the percentage of a student's enrollment in a school.

Target Date Needed
Coincide with the release of FTE with Ed-Fi

Use Case Description
Nebraska utilizes an element called "FTE" or "Full Time Equivalency" to track a student's participation/ownership in an School/LEA. A student has to have greater than 50 FTE to be counted for certain EDFacts reporting. Other states may share a similar process.

Use Case Background
Nebraska will be working with Ed-Fi to add FTE to the Ed-Fi standard as well. CEDS and Ed-Fi will coordinate around the development of this element.

Location of Element in the Domain Entity Schema

Author(s)
Amy Powell Moman

Authoring Organization(s)
North Carolina Department of Public Instruction (NCDPI)

Email address
[email protected]

Use Case Title
Add new CEDS element: “Excluded from State Reporting”

Target Date Needed
ASAP

Use Case Description
Not all students, schools, and districts NCDPI collects data on are required to be reported on at the state level. NCDPI would like to add an additional element to capture this information. Currently, this is collected as a “Yes” or “No” field.

Use Case Background
Not all students, schools, and districts NCDPI collects data on are required to be reported on at the state level. NCDPI would like to add an additional element to capture this information. Currently, this is collected as a “Yes” or “No” field.

Location of Element in the Domain Entity Schema
?

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 (EDFacts)
Email address

Use Case Title
dd School Psychologist and modification to Student Support Services Staff to K12 Staff Classification

Target Date Needed
ASAP
Use Case Description
EDFacts file specification FS059 has an additional K12 Staff Classification of School Psychologist and has adjusted the way that Student Support Services Staff is defined to remove psychology. CEDS needs to adjust to support this use case.

To the CEDS element K12 Staff Classification, add the following option set:
Description: School Psychologist
Definition: Professional staff member who provides direct and indirect support, including prevention and intervention, to evaluate and address student’s intellectual development, academic success, social-emotional learning, and mental and behavioral health.
Code: SchoolPsychologist

For the adjustment to support the removal of "psychologist" from the definition of Student Support Services Staff, two possible options:

1. Add a new option set called Student Support Services Staff Without Psychology and provide the EDFacts definition for this option set and retain the other option set of Student Support Services Staff for historical purposes.
2. Adjust the current definition of Student Support Services to remove all references to actual roles that staff play (e.g., speech pathology, coaches, etc.). By doing this, historically the definition could still include psychologist and going forward, the definition does not specify psychologist. The same CEDS element continues to be used in reporting to EDFacts for Student Support Services Staff. Context as to whether or not this included psychologists is removed. But prior to this change, it was not known if the Student Support Services Staff members was a psychologist or not since it was not specified.

Other ideas are welcome.

Use Case Background
To support EDFacts file specification FS059

Location of Element in the Domain Entity Schema
Option Set in the K12 Staff Classification element

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)
Andrea Hall

Authoring Organization(s)
CEDS / EDFacts

Email address
[email protected]

Use Case Title
New element needed for EDFacts reporting (File Specification 207)

Target Date Needed
ASAP

Use Case Description
New EDFacts report for SY 2019-20
EDFacts data group 845: How Charter Schools Receive State Appropriations

Recommend adding one new element and option set, noted below:

Element Name: State Appropriation Methods
Element Definition: Methods used to provide state appropriations to charter schools.
Element option set:

• STEAPRDRCT (Direct from State) Charter school receives allocations and appropriations directly from the state
• STEAPRTHRULEA (Through local school district) Charter school receives appropriations allocated by the state through the local school district with no local school district control on allocation of funds (e.g. passthrough allocations)

Use Case Background
This element is required for EDFacts reporting

Location of Element in the Domain Entity Schema
K12 -> K12 School -> Finance

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)
John W. Lovell

Authoring Organization(s)
Access 4 Learning

Email address
[email protected]

Use Case Title
Privacy Obligations Support

Target Date Needed
Reasonable and Prudent

Use Case Description
Contracts often require privacy of individuals be honored. A4L has published a Privacy Obligation Document (POD) definition used to describe an artefact derived from a paper contract which contains details of the parties involved, the data which can be transferred from one party to another, details of the technical benchmarks which must be adhered to (e.g. encryption levels) and details of any additional parties which may handle the data.

The document itself is comprised of 278 potential fields (some that repeat) many that reflect existing elements in CEDS such as those related to contacts. However, it also includes some truly technical concepts that may not be a good fit for CEDS. In order to, “List the proposed element name(s), definition(s), and/or option set(s),” I attached supporting documentation included a spreadsheet which enumerates all 278 fields. However, no attempt to map or reduce them has yet to be made.

Use Case Background
While this work was originated because of a request from Wyoming, it really found its legs with passage of the General Data Protection Regulation (GDPR). That European legislation gave us some common terms and requirements to better guide the work and we have tried to reflect it accurately. Published with the SIF Infrastructure Specification 3.3 the POD is currently being piloted in Massachusetts and we expect feedback from that endeavor to further clarify its mean and usage.

Location of Element in the Domain Entity Schema
Privacy is not currently an area in the DES.

Supporting Files
POD2CEDS.xlsx

PrivacyServices_3-3.pdf

Official Link

Author(s)
Chelsea Waite

Authoring Organization(s)
Christensen Institute

Email address
[email protected]

Use Case Title
Add new element: Course Level Approval

Target Date Needed
Fall 2020

Use Case Description
Course Level Approval Indicator (NEW)
Definition: An indicator that student participation in the course is based on school or program developed requirements for the course level characteristic.

Usage Note: This element is used in conjunction with Course Level Characteristic.

Option set:

• Yes | School or program developed requirements for the course level characteristic determine eligibility for student participation.

• No | There are no school or program developed requirements for the course level characteristic. All students are eligible for participation.

Use Case Background
This need was identified through the Canopy project led by the Clayton Christensen Institute.

We propose adding a new element: Course Level Approval Indicator. Many schools are taking steps to extend courses traditionally reserved for students meeting specific eligibility requirements, so that any student may take advantage of them. The addition of the Course Level Approval Indicator element will allow schools to specify whether these courses are offered to all students, or a subset who meet the eligibility criteria.

We also recommend adding Course Level Characteristic to the K12 -> K12 School -> Directory so that the two elements can work in tandem at the school level.

Location of Element in the Domain Entity Schema
Recommend:
Adult Education -> Course Section -> Course
Career and Technical -> Course
Career and Technical -> Course Section -> Course
K12 -> Course Section -> Course
K12 -> K12 Course
K12 -> K12 School -> Directory

Author(s)
Chelsea Waite

Authoring Organization(s)
Christensen Institute

Email address
[email protected]

Use Case Title
Add Other to Blended Learning Model Type

Target Date Needed
Fall 2020

Use Case Description
Blended Learning Model Type
Option set:

• Rotation Model | A model in which within a given course or subject, students rotate between learning modalities, at least one of which is online learning. Other modalities might include activities such as small-group or full-class instruction, group projects, individual tutoring, and pencil-and-paper assignments.

• Flex Model | A model in which online learning is the backbone of student learning, even if it directs students to offline activities at times. Students move on an individually customized, fluid schedule among learning modalities, and the teacher of record is on-site. The teacher-of-record or other adults provide face-to-face support on a flexible and adaptive as-needed basis through activities such as small-group instruction, group projects, and individual tutoring.

• A la carte Model | A model in which students take one or more courses entirely online with an online teacher of record and at the same time continue to have brick-and-mortar educational experiences. Students may take the online courses either on the brick-and-mortar campus or off-site. This differs from full-time online learning and the Enriched Virtual model because it is not a whole-school experience.

• Enriched Virtual Model | A whole-school experience in which within each course, students divide their time between attending a brick-and-mortar campus and learning remotely, off-site, using online delivery of content and instruction.

• Other | A model for implementing blended learning that does not fit the definition of the other blended learning model types.

Use Case Background
This need was identified through the Canopy project led by the Clayton Christensen Institute.

We propose adding Other to the option set. New models for implementing blended learning are emerging in schools. Adding an “other” category allows the user to indicate that blended learning is occurring, but using a model or format beyond the exhaustive list currently provided. Future analysis of alignment to this element could reveal future options for this element.

We also would like to ensure that this element is included in such a way that Blended Learning Model Type is able to ‘mark all that apply’ and not a single option per school or per course.

Location of Element in the Domain Entity Schema
Adult Education -> Course Section
Career and Technical -> Course Section
K12 -> Course Section
K12 -> K12 Course
K12 -> K12 School -> Directory

The U.S. Chamber of Commerce Foundation's T3 Innovation Network has a project (PP1) to map/crosswalk relevant data specifications in the education-to-work ecosystem from entities such as IMS Global, PESC, HR Open, Credential Engine and others.

These crosswalks use CEDS as a common spine (reference or intermediary standard) to which the other data specifications are directly mapped. In cooperation with CEDS, the project is maintaining a Google Sheet listing attributes found in the data specifications being crosswalk that currently do not exist in CEDS. That continuously evolving Google Sheet can be found here. Since the terms entered in the Google Sheet represent potential gaps in CEDS coverage, we thought the sheet would be useful to the CEDS community.

Stuart

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)
Amy Powell Moman, Eric Marshall

Authoring Organization(s)
North Carolina Department of Public Instruction

Use Case Title
Add License Effective Date as an element to CEDS

Target Date Needed
ASAP

Use Case Description
North Carolina collects data on the date that a license is issued as well as the date that the license becomes effective. Currently, CEDS only has a single date element (credential issuance date – 000070) to capture both.

Use Case Background
North Carolina is currently mapping existing state data to the CEDS IDS. As part of the process, North Carolina is identifying data elements that are not currently found in CEDS and would like to add these elements to CEDS. North Carolina is also working with eScholar to ensure needed elements are available in their schema.

Location of Element in the Domain Entity Schema
License Effective Data – K12/K12 Staff/Credential or License

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)
Michigan/CEDS
Use Case Title
Provide a concise description that defines the use case.

Target Date Needed

Use Case Description
Michigan separately tracks Transitional Housing and Shelters. Currently the CEDS Element Homeless Primary Nighttime Residence includes “Shelters, Transitional Housing, Awaiting Foster Care” in the “Shelters” option set. This is the aggregation that occurs for EDFacts reporting. We need Transitional Housing pulled out of that option set and/or need another way to track Shelters and Transitional Housing separately. Other stakeholders may need additional items in this EDFacts elements separated. Such as Unsheltered indicating the place where the student is unsheltered – car, park, campground, etc.). It would be good to have a workgroup look at how states are tracking this information and adjust the standard to allow for more granularity.

Use Case Background
Provide information related to why these changes/additions are needed.

Location of Element in the Domain Entity Schema

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)
Amy Powell Moman

Authoring Organization(s)
North Carolina Department of Public Instruction (NCDPI)

Email address
[email protected]

Use Case Title
Add “Share Space” and “Share Space Description” as new CEDS elements

Target Date Needed
ASAP

Use Case Description
NCDPI collects information on if a school shares facilities or space with another school. Currently this is captured in two fields: “Share Space” is captured as “Yes” or “No”. “Share Space Description” is a text field.

Use Case Background
NCDPI collects information on if a school shares a facilities or space with another school. Currently this is captured in two fields: “Share Space” and “Share Space Description”.

Location of Element in the Domain Entity Schema
Facilities?

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)
Amy Powell Moman

Authoring Organization(s)
North Carolina Department of Public Instruction

Email address
[email protected]

Use Case Title
Add “Approved Grade Levels” as a CEDS element

Target Date Needed
ASAP

Use Case Description
NCDPI stores both the current grade levels offered at a school as well as the grades the school is approved to enroll students. There is no current CEDS element to collect the grades a school is approved to offer.

Use Case Background
NCDPI stores both the current grade levels offered at a school as well as the grades the school is approved to enroll students. There is no current CEDS element to collect the grades a school is approved to offer. For example, a Charter School is approved to instruct students in grades 3 through 6. The first two years the school only enrolls students in grade 3 and then adds a grade the following years.

Location of Element in the Domain Entity Schema
K12 -> K12 School -> Directory

Author(s)
Beth Young and Kris Dunman, QIP representing working group (see below)

Authoring Organization(s)
National Forum on Education Statistics Exit Code Working Group

Use Case Title
Changes Needed to Exit or Withdrawal Type

Target Date Needed
ASAP, the working group is trying to decide if to wait for CEDS to review so it can be included in Forum Guide

Use Case Description
Exit or Withdrawal Type - this code set no longer matches the definition, or use, of this data element. There are several issues:
Definition = The circumstances under which the student exited from membership in an educational institution.

• options that are elsewhere in CEDS (ex. options that describe what type of school a student transfers) - also, only some school types listed
• options that are not reasons of withdrawals, (ex. Exited)
• options that no longer match federal reporting (ex. need to split up died and permanently incapacitated).

It is possible that the best decision will be to break this into separate elements

The detailed comments on the element and option set are included in attached documents. Please note, not all of the comments from working group members are in agreement with each other.
Forum SEA and LEA Comments on Exit Codes Taxonomy.docx
Forum SEA and LEA Comments on Exit Codes Taxonomy_text.docx

Use Case Background
The Forum is updating their 2006 Exit Code guide (links below) and as part of that work they look at the Exit code taxonomy currently in CEDS.
https://nces.ed.gov/forum/Exit_Codes_Working_Group.asp
https://nces.ed.gov/forum/pub_2006804.asp
Provide information related to why these changes/additions are needed.

Location of Element in the Domain Entity Schema
https://ceds.ed.gov/CEDSElementDetails.aspx?TermxTopicId=38752

Describe the bug
For version 8 the community member recommended and it was accepted via the public review process to use of "Program Participation Start Date" and "Program Participation Start Date" instead of duplicative elements "English Learner Entry Date" and "English Learner Exit Date" that are defined as dates the learner entered or exited "the English Learner program." This change supports the way dates are applied in the IDS and applications such as Generate.

However, in the release of version 8 only the change for "English Learner Entry Date" was made. The "K12 -> K12 Student -> English Learner -> English Learner Exit Date" is still there and existing Align maps and Connect connections still use it.

To Reproduce
Steps to reproduce the behavior:

1. See https://ceds.ed.gov/CEDSElementDetails.aspx?TermId=13562

Expected behavior

1. "K12 -> K12 Student -> English Learner -> English Learner Exit Date" should no longer be seen in the DES.
2. Any existing / previously mapped Align and Connect instances that used that TermTopixId should be remapped to the "K12 -> K12 Student -> English Learner -> Program Participation Exit Date"

Author(s)
Chelsea Waite

Authoring Organization(s)
Christensen Institute

Email address
[email protected]

Use Case Title
Add new element: Interdisciplinary Indicator

Target Date Needed
Fall 2020

Use Case Description
Interdisciplinary Indicator
Definition: An indicator that the course, projects, and/or learning activities develop knowledge and skills across multiple subject areas and highlight connections between subject area domains.

Option set:

• Yes | The course, projects, and/or learning activities develop knowledge and skills across multiple subject areas and highlight connections between subject area domains.

• No | The course, projects, and/or learning activities develop knowledge and skills in a single subject area.

Use Case Background
This need was identified through the Canopy project led by the Clayton Christensen Institute.

We propose adding a new element: Interdisciplinary Indicator. Interdisciplinary learning is a strategy schools are using in the classroom and sometimes for an entire school. This element will allow schools to identify where interdisciplinary learning is happening and in turn evaluate the effectiveness of the strategy.

Location of Element in the Domain Entity Schema
K12 -> Course Section
K12 -> K12 Course
K12 -> K12 School -> Directory

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)
Amy Powell Moman, Eric Marshall

Authoring Organization(s)
North Carolina Department of Public Instruction

Use Case Title
Add Program Entry Reason as an element to CEDS

Target Date Needed
ASAP

Use Case Description
North Carolina collects the entry reason for a student’s enrollment in various programs, such as Alternative Learning programs and Migrant Program.

Use Case Background
North Carolina is currently mapping existing state data to the CEDS IDS. As part of the process, North Carolina is identifying data elements that are not currently found in CEDS and would like to add these elements to CEDS. North Carolina is also working with eScholar to ensure needed elements are available in their schema.

Location of Element in the Domain Entity Schema
Program Entry Reason – K12/K12 Student/Program

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)
Joshua McGhee
Authoring Organization(s)
IMS Global Learning Consortium
Email address
[email protected]
Use Case Title
OneRoster 1.2 SourcedID

Target Date Needed
NA
Use Case Description
IMS OneRoster provides identifiers for all objects that are used to retain fidelity and promote interoperability between systems. Each OneRoster entity will contain a sourcedID. It is defined in the OneRoster Specification as:

"This is the GUID that SYSTEMS will refer to when making API calls, or when needing to identify an object. It is RECOMMENDED that systems are able to map whichever local ids (e.g. database key fields) they use to SourcedId"

For example, the User entity will have user.sourceID. This is in addition to the local identifiers, or the school system identifier and is used to promote interoperability between systems.

Use Case Background
As part of doing an align map between OneRoster's upcoming 1.2 release and CEDS.
Location of Element in the Domain Entity Schema
Multiple.