Open Expenditures 101
Schema and Examples
Welcome to Socrata's Open Expenditures experience. This page is designed to provide documentation that will help your team better understand the Open Expenditures application, and how you'll need to structure your data so that the application can read and display information in meaningful ways.
This page includes:
- Understanding Schemas
- Schema Documentation
- Customer Examples
- Additional Resources
Understanding the Schemas
There are two schemas we will cover: Open Expenditures requires one dataset detailing expenditures information ("The Expenditures Dataset") to function and recommends one dataset detailing vendor or recipient information ("The Vendor Dataset") to inform constituents about which organizations receive payment.
The schemas themselves are linked below. Within the schema documentation, you'll find three field types:
- Required Fields: These fields are required by Open Expenditures to function. Think of these as the data that you simply could not report spending without. For example, a payment date or an amount paid.
- Recommended Fields: These fields are not required, but including them will allow users to see a richer picture of your spending information. For example, a description for each expense or a transaction number.
- Optional Fields: These fields are useful for analysts or power-users accessing the information, or for adding a deeper level of hierarchy. For example, payment method or additional classifications of department hierarchy at which the expense was made.
For the full documentation of the Open Expenditures schema, select the link below:
Below are examples of actual customers' Open Expenditures implementations, from both the application-level as well as the data-level. Use the below examples to explore how the data is structured and how it is displayed in the final version of the application.