The Opportunity Project - Data Analysts Portal

CHALLENGE: Develop parent-friendly, scalable approaches to communicating data about public schools that drive insight and engagement—and meet the requirements of a recent federal law.
PROBLEM: The Every Student Succeeds Act—a landmark federal education law passed in 2015— requires states to make an estimated 2,107 data points about their public school systems accessible to parents. In response, states are looking to provide this information through digital “report cards.” These websites would give parents an interface for navigating important data about schools in their state, including per-student spending, test results, and more. Developing these will be a challenge: government tends to lack digital services expertise that would help ensure their solutions align with best practices around data visualization and human-centered design. The requirements of federal law and those around student privacy complicate the task, increasing the risk that parents end up with clunky tools that confuse rather than illuminate. 
WHY IS THE PROBLEM IMPORTANT:
The Every Student Succeeds Act has catalyzed nation-wide interest in new approaches to making data about schools transparent and accessible. A state-led wave of report card solutions is coming, one that will transform how families across the country learn about the schools in their neighborhood, and this is your opportunity to help shape a movement.

Access the Raw Education Data

The raw data is the source on which all the state level education report cards and dashboards have been built. Access it by clicking the link to the right to begin building and developing you own analyses and applications.  

For Developers and Data Scientists

The “endpoint” of a SODA API is simply a unique URL that represents an object or collection of objects. Every Socrata dataset, and even every individual data record, has its own endpoint. The endpoint is what you’ll point your HTTP client at to interact with data resources.
All resources are accessed through a common base path of /resource/ along with their dataset identifier. This paradigm holds true for every dataset in every SODA API. All datasets have a unique identifier - eight alphanumeric characters split into two four-character phrases by a dash. For example, ydr8-5enu is the identifier for the Building Permits. This identifier can then be appended to the /resource/ endpoint to construct the API endpoint.

API Access:

All requests should include an app token that identifies your application, and each application should have its own unique app token. A limited number of requests can be made without an app token, but they are subject to much lower throttling limits than request that do include one. With an app token, your application is guaranteed access to it's own pool of requests. If you don't have an app token yet, click the button to the right to sign up for one.
All communication with the API is done through HTTPS, and errors are communicated through HTTP response codes. Available response types include JSON, XML, and CSV, which are selectable by the "extension" (.json, etc.) on the API endpoint or through content-negotiation with HTTP Accepts headers.