Getting Started with Ed-Fi

Tool Search: Ed-Fi

What is Ed-Fi?

Ed-Fi is a data interchange standard and framework created by the Dell Foundation to allow K-12 educational institutions to consolidate and analyze data, and communicate this data with each other.  

The Ed-Fi ODS/API is a complex relational database that collects and stores data from multiple source systems and applications. The Core Student Data API standard describes a REST API surface that covers the core data domains typically managed by student information systems in K–12 education. These standards can be used to drive analysis of student performance, both alone and in combination with data from other systems.  

Infinite Campus is certified by the Ed-Fi Alliance. The core Ed-Fi solution provided by Infinite Campus is aligned to the certification requirements provided by the Ed-Fi Alliance. You can click here for more information on what versions and resources included in the core solution.

It's important to have a complete understanding of the Ed-Fi Technical Suite before implementing Ed-Fi. A district can utilize the Ed-Fi Tech Docs to assist with the implementation. There are also several technology companies offering an Ed-Fi solution for a fee that will assist with the hosting & implementation.

Additional Ed-Fi Information

Click here to expand...

Ed-Fi Feature Toggle

Ed-Fi is hidden behind a feature toggle. In order to un-hide and use Ed-Fi, districts must enter a support ticket to request Ed-Fi to be turned on. To implement Ed-Fi:

  1. Self-Implementation: Districts can perform the setup and implementation of Ed-Fi on their own. Note: It is up to the District to ensure the ODS is configured properly to accept Ed-Fi data. Infinite Campus Support does not have access to the Ed-Fi database and cannot provide assistance with ODS configuration.

Cost of Ed-Fi:

Cost to Districts: Infinite Campus does not charge to use the API for the Core Ed-Fi Resources. The District is responsible for any costs related to hosting the ODS and implementing Ed-Fi.

What Districts are responsible for: Ed-Fi implementation, ODS hosting & setup, and any other related costs.  

Ed-Fi Versions Supported by Infinite Campus

Infinite Campus supports the following Ed-Fi Data Standard and the Ed-Fi ODS/API Platform versions:

Suite
Ed-Fi Data Standard: 
Suite 3
Data Standard v4.0
Suite 3
Data Standard v3.3.1-b
Suite
Ed-Fi ODS/API Platform:
Suite 3
Ed-Fi ODS/API for Suite 3 v6.2
Suite 3
Ed-Fi ODS/API for Suite 3 v6.1
Suite 3
Ed-Fi ODS/API for Suite 3 v5.4

For more information on Ed-Fi versions, please see the Ed-Fi Tech Docs.

Ed-Fi Support:

A District must have an instance of Swagger implemented that Infinite Campus Support can have access to view data in the ODS. If Swagger is unavailable, Support will be unable to assist with data or Ed-Fi Resource-related issues.

Infinite Campus Support will provide assistance for the Ed-Fi Tools within the product: Ed-Fi Configuration, Ed-Fi Tools, Ed-Fi Reconciliation, and Ed-Fi Reports.

The following information is required when submitting a Support case:

  • Component = Ed-Fi
  • What version of Ed-Fi are you using: Examples 3.5, 3.6, etc.
  • Swagger Link: Provide the link to Swagger aligned to the ODS.
  • Description of the issue or question: If you are inquiring about an error message, a copy of the Error Message and JSON (if applicable) must be included.

Infinite Campus will not support the following:

  • Performance issues - If Ed-Fi is causing performance issues due to server or data setup, it is the District's responsibility to investigate and resolve any issues if they occur. You may contact Support to assist with issues, but there may be a fee associated. You will be notified before any work is completed by Infinite Campus if a fee will be incurred.
  • Connection/Setup & Security issues - It is up to the District to make sure the ODS is configured properly to accept the data. Infinite Campus Support does not have access to the Ed-Fi database and cannot provide assistance with ODS configuration.

Ed-Fi Resource data points & Descriptors: Ed-Fi has defined what the core instance of Ed-Fi is by requiring vendors to report a specific set of resources and data points within each of those resources. Infinite Campus is Ed-Fi Certified to the defined data points and only supports the core data defined by Ed-Fi. Infinite Campus will remain certified on major release versions but may not align to incremental versions that are released by Ed-Fi between major releases. If there are any questions or concerns about the resources or descriptors, please contact Ed-Fi directly. Infinite Campus does not support any extensions of resources or data points within resources. If a District chooses to add any/modify any descriptors, those will be available in the mapping tools.

Certificate Issues:  

  • Depending on the setup the District chooses to use, Certificate issues have been identified in the past. It is up to the District to find a Certificate that is allowed by Infinite Campus or use the Certificate Import tool to load any Certificate not used by Infinite Campus.

Sandbox vs Production

You cannot use the same Infinite Campus database to send to different Ed-Fi ODS’. If you start with an Ed-Fi Sandbox environment, you cannot connect your Infinite Campus Production Database to it to test data and then change the connection to a Production ODS. If you have connected your Infinite Campus Database to an ODS and then need to connect it to a new one, it is critical that the Ed-Fi tables in Campus be truncated of the old data from the first ODS. The tables that need to be cleared are the following:

  • edFiIdentityMapping
  • edFiIdentityMappingRoster

  • EdFiIdentityMappingAttendance

Data Setup & Configuration

Ed-Fi Setup

Users need to become familiar with the Campus Community documentation for Ed-Fi. When setting up Campus for the first time, the following steps need to be completed in order to configure and use Ed-Fi reporting:

State specific set-up options can be found by following the appropriate links in the State Specific Ed-Fi Information section.
  1. Ensure users have the appropriate Ed-Fi Tool Rights.
  2. Enable Ed-Fi via the Enable Ed-Fi system preference.
  3. Set up a valid Ed-Fi connection.
  4. Set all Resources to 'Off' and map the Ed-Fi Codes to Campus Codes via the Resource Preferences.
  5. Enter ID's for individuals.
  6. Toggle Resources to 'On' in Resource Preferences once all data setup is complete.
  7. Resync Ed-Fi Data (see the Recommended Sync Order section below for guidance on when to sync which resource).
  8. Note that some attributes that need to be reported to Ed-Fi are hidden. If a district wishes to map and report these attributes, then the attributes need to be un-hidden from the Custom Attribute Dictionary. See the Hidden Attributes section below for more information.

Data Set-Up

Having the proper data setup in Infinite Campus is critical to a successful Ed-Fi Implementation. It is important to review the requirements for each resource to understand how the data in Infinite Campus aligns to the end points in Ed-Fi. There may be additional data setup you need to complete in Campus in order to send data correctly. There is required data for each resource in order for the resource to send. If the required data is missing in Campus, the data will not send to Ed-Fi. See the Ed-Fi Configuration Section for the Data Resources logic.

In some states, attributes that need to be reported to Ed-Fi are hidden. If a district wishes to map and report these attributes, they need to be un-hidden from the Custom Attribute Dictionary. See the Hidden Attributes section below for more information.

Create an Ed-Fi Configuration

The Ed-Fi Admin tools will provide you with the OAuthURL/API URL, Client Key and Client Secret you will need to make a valid connection. A valid connection must be made to the ODS before data set up can continue. See the Ed-Fi Configuration article for more information: Ed-Fi Configuration

After a Connection has been created and saved, navigate to Resource Preferences and make sure that all Resources are toggled “OFF”. This will keep data from sending to the ODS until all data setup is completed and you are ready to send data to the ODS.

A new Configuration is needed for each school year.

Assign a Unique ID to Students & Staff

All students, staff and parents must be assigned a unique identifier in order to send data to the ODS. This unique identifier is used in Ed-Fi to link all related data to that person. Campus will auto-generate a unique ID for parents when the Student Parent Association is sent for the first time but the District will need to determine which ID they want to use for their Students and Staff. There are three options for Students and Staff:

  • Local Student/Staff Number
  • Student State ID/Staff State ID
  • Ed-Fi ID – a number assigned in the Ed-Fi ID field populated by the District. (This is mostly used in states where Ed-Fi is used for state reporting.)

Once an ID has been used for a Configuration, it should not be changed. If this option is changed after data has been sent, there is potential for data conflicts from Campus to the ODS. If the ID is changed after data has been sent and data clean-up is required, it may result in a fee if assistance from Infinite Campus is needed. See the Ed-Fi ID article for more information: Enter Ed-Fi IDs

Resource Preferences

Resource Preferences are used to determine which Resources are sent to Ed-Fi and allows you to map data in Campus to Ed-Fi to translate any Campus elements to Ed-Fi Resources. Not all data elements for an Ed-Fi resource are in the Resource Preferences, only data elements that require a mapping will appear. See the Resource Preferences for the version of Ed-Fi you are using for more information: Resource Preferences.

You are not required to turn on all of the resources in Ed-Fi in order to send data. It is important that you identify the use cases you are trying to solve with your Ed-Fi solution to determine in which resources you want to send data. Ed-Fi is a relational database system so there is dependent data that must be sent to Ed-Fi before additional resources can be sent. See the Dependency Flow Chart to see how resources are dependent of others: Dependency Flow Chart.

Loading Data into an ODS

Once data setup in Campus is complete and the Resource Preferences are set, you can begin to turn on Resources and sync data to the ODS. Local Education Agencies (LEA) Resource must be preloaded into the ODS in order for data to send. Contact Ed-Fi for assistance on this if needed.

The Resync tools must be used in order to load data for the first time to the ODS. Once the data has been successfully loaded into the ODS, data will automatically be sent to the ODS based on an UI or database trigger where data is changed and saved in Campus as long as there is a valid connection, the Resource Preference is ON, and there is not a data error that prevented the record from landing.

Schools must be sent first in order before any other resources. To send data, go to Resource Preferences and toggle the Resource you want to send to “ON”.

You can then use the Resync tool to select the resource you want to send. Once you select the resource and hit the Resync button, you will see records enter into the Event Queue. As records process, they will either land in the ODS or error and land in the Error log.

Since Ed-Fi is a relational database, it is important you verify the data from the selected resource successfully sent to the ODS before you select the next one. If the data errors, you will not be able to send any dependent resources until those errors are resolved.

After the Resync is complete, check the Error Log to see if any of the records did not send. Correct any data necessary to fix the error if there is one. Once all data for that resource is sent, you can move on to the next one.

Event Queue

The Event Queue tool holds all of the data events waiting to sync data from Infinite Campus to Ed-Fi. You can use the Event Queue to verify that data is properly triggered from a database change or a resync and that it is processing records to the ODS. See additional documentation in the Campus Community for more information on how the Event Queue works: Ed-Fi Event Queue.

Resync

The Resync tool allows you to manually sync data from Infinite Campus to Ed-Fi. Although Ed-Fi data is sent from Infinite Campus to Ed-Fi in real-time (transaction-based), instances where the connection is lost, records appear to have not sent, or other various instances may require you to manually request a resync of specific data.

The Resync tool can trigger a large amount of data, so it is recommended that you choose a limited set of schools and/or resources to resync at a time. Errors can also be overwhelming if you send a resync for a large data set. It is recommended that you send resources one at a time for individual schools when you are loading data for the first time.

See additional documentation in the Campus Community for more information on how the Resync tool works: Ed-Fi - Resync.

Error Log

Data syncing errors between Infinite Campus and Ed-Fi appear in the Error Log. From here, you can review each event error, including when it occurred, the name (person, school, calendar, etc.), what table was sending the data, what the old data was and what it was changed to, and why the error occurred. If an error occurs due to a data issue, find the proper data point in Campus and fix the data that caused the error. When the data is changed and saved, a new event will be triggered, and the data will attempt to resend to Ed-Fi. In most cases, it is not necessary to retry an error from the Error Log because correcting the data will trigger a new event and will either send successfully or error again. If you have identified the cause of an error, you should archive the error and then correct the data, wait for the event queue to process the record, and then check the Error Log again to see if it failed again. You will need to check the Error Log regularly to see if data is properly sending to Ed-Fi. You will want to monitor the Error Log because changing data in Campus triggers events for Ed-Fi.  

See additional documentation in the Campus Community for more information on how the Error Log works: Ed-Fi Error Log.

Delete Tool

The Delete Tool allows users to delete resource records from the Ed-Fi database for a specific resource ID, person, or set of people. This tool is useful for cleaning up duplicate records, removing erroneous data sent to Ed-Fi, and deleting orphan or erroneous records existing in the Ed-Fi ODS. Only resources active for the selected configuration are displayed in the Delete tool.

See additional documentation in the Campus Community for more information on how the Error Log works: Ed-Fi Delete Tool.

Ed-Fi Data Tool

The Ed-Fi Data tool allows users to compare student-related Ed-Fi resources with the data in Infinite Campus. To compare the data, a configuration and resource need to be selected. This tool can be used only for configurations on Ed-Fi versions 3.1 or higher. An Ed-Fi JSON for the selected resource can also be viewed using this tool.

See additional documentation in the Campus Community for more information on how the Ed-Fi Data tool works: Ed-Fi Data.

Troubleshooting Connection Issues

  1. Ensure the Ed-Fi Preferences is set to 'Yes' in System Administration > System Preferences.
  2. Make sure there is a valid connection.
  3. Make sure all students and staff have Ed-Fi IDs if the ID Preference is set to use that field for the Unique ID. This field can be blank if the Student/Staff Local ID or Student Staff State ID options are selected. If a student does not have an ID in the selected option, no data is sent for that person.
  4. Make sure the resource is set to active in Resource Preferences.


Additional Ed-Fi Tools

For more information, see the following articles per Ed-Fi tool:

State-Specific Ed-Fi Information

Recommended Resync Order - Core Ed-Fi

Click here to expand...

The Core Ed-Fi Recommended Resync Order has been moved to its own article: Recommended Resync Order and Dependency Flowchart (Core Ed-Fi v3.X)

Core Ed-Fi Dependency Flowchart

Click here to expand...

The Core Ed-Fi Dependency Flowchart has been moved to its own article: Recommended Resync Order and Dependency Flowchart (Core Ed-Fi v3.X)

Hidden Attributes

Click here to expand...

In some states, attributes that need to be reported to Ed-Fi are hidden. If a district wishes to map and report these attributes, they need to be un-hidden from the Custom Attribute Dictionary.

If an attribute that needs to be mapped is hidden, the following message displays when mapping the attribute in Resource Preferences. There are also attributes used in Ed-Fi that do not need to be mapped that may also be hidden, these fields need to be un-hidden as well.

For more information regarding Attributes, please refer to the Attribute Dictionary article.

Example of Hidden Attributes hidden.Hidden Attributes Example

In order to un-hide the attribute, navigate to System Administration > Custom > Attribute/Dictionary. Select the attribute that you want to report, un-mark the Hidden checkbox and then mark the Required checkbox. The attribute can then be turned on and/or mapped if desired.

 Image of Campus Attribute Detal with the Hide Checkbox Marked.Campus Attribute Detail