Operational Contexts allow for mapping between sets of Ed-Fi Descriptors. In practice, the Ed-Fi ETL internally runs calculations based on Ed-Fi-provided Descriptors. Therefore, if you have custom Descriptors in use in your source ODS, you'll need to map these custom Descriptors to the as-shipped Ed-Fi Descriptors in order for your data to be included in calculations.
The process outlined below shows how to create an operational context that will be recognized by the ETL process, and map custom Descriptors through this operational context.
Fully Custom Descriptors
Fully custom descriptors (i.e., wholly new descriptors created by extension to the ODS) are not supported in the ETL. You do not need to map these Descriptors as they have no equivalents in the as-shipped Ed-Fi technology.
The high-level steps are:
Step 1. Create the Operational Context
Note this script must be run as-is. The values provided below are used by the ETL code.
Step 2. Identify Descriptors that may need mapping
The below query will show you any Descriptors defined in a non-Ed-Fi namespace that are not currently mapped in the Dashboard Operational Context. These are all candidate Descriptors you should consider mapping. Note that not all Descriptors need to be mapped as not all Descriptors are used by the ETL process.
If the result of this query is empty, you have no more custom Descriptors that are unmapped in the Dashboard Operational Context.
Step 3. Add Descriptor mapping to the Operational Context
@edfi_code_value variables below, and replace the
@edfi_code_value. If you have more than one custom CodeValue to map to the same
@edfi_code_value, uncomment and use the
UNION ALL syntax on the subsequent lines.
Step 4. Repeat until all Descriptors are mapped
Go to Step 2 and repeat for any remaining values you want mapped.