Ed-Fi Terms

This page contains guidance related to Ed-Fi-specific terms.

Ed-Fi Term List

Ed-Fi Alliance Community

Ed-Fi Alliance Community. Capitalized as shown. Community on second use.
Ed-Fi Alliance Slack channels. Capitalized as shown. Plural "channels." Slack on second use.
Ed-Fi Tracker. Notably not ~~Ed-Fi Issue Tracker~~ or ~~Ed-Fi Jira~~. It is okay to use "Ed-Fi Tracker, a Jira-based system" in material for a tech-adjacent audience who may not be familiar with the Ed-Fi instance.
Ed-Fi Exchange. Capitalized as shown.
Ed-Fi Alliance Success. The one stop for all support to help with a successful implementation.

Ed-Fi Technology Suite and its Contents

Ed-Fi Data Standard. Capitalized as shown. Notably not ~~Ed-Fi Core~~ or ~~Ed-Fi Core Data Standard~~.
Ed-Fi ODS / API Platform. Capitalized as shown. Consists of the APIs published by the Alliance (and subordinately, the ODS database), including the surface of the ODS / API. In other words, the product includes the ODS / API + other Ed-Fi API specifications. When describing the individual components, it's okay to use ODS or API without a qualifier if the context is clear – or use formulations such as "...the Ed-Fi API..." or "...the Ed-Fi ODS..." if context or differentiation is useful. Note, the future Ed-Fi ODS will not have the same form as originally designed. Most contexts will have emphasis on the API with no need to mention the ODS.
Ed-Fi Technology Suite. As shown. "Technology Suite" on second use. Not ~~Ed-Fi Technical Suite~~, which has been deprecated.
Ed-Fi Tools collection. Capitalized as shown (n.b. lower-case "collection"). Ed-Fi Tools on second use, and optional for first use when the context is clear. Ed-Fi Tools are not a suite or a formal set of products, they're an evolving set of supporting technologies and resources. So, formulations such as collection of Ed-Fi Tools is appropriate if that sounds more natural.

Ed-Fi Tools Collection Contents

This page: