provide blank forms to ODK Collect (or other OpenRosa clients),
accept finalized forms (submissions) from ODK Collect and manage collected data,
visualize the collected data using maps and simple graphs,
export data (e.g., as CSV files for spreadsheets, or as KML files for Google Earth), and
publish data to external systems (e.g., Google Spreadsheets or Google Fusion Tables).
ODK Aggregate can be deployed on Google’s App Engine, enabling users to quickly get running without facing the complexities of setting up their own scalable web service. ODK Aggregate can also be deployed locally on a Tomcat server (or any servlet 2.5-compatible web container) backed with a MySQL or PostgreSQL database server.
changed behavior: simple JSON publisher now POSTs an application/json entity body; added option for how to treat binary content. Incompatible change; see Upgrading section if you were using the Z-ALPHA JSON Server
changed representation: ODK Tabled storage schema has been revised. Incompatible change; see Upgrading section if you used your server to upload or download data to ODK Tables. Syncing with ODK Tables is broken in this release. Only v1.3.4 on Google AppEngine works with the ODK Tables alpha (we are in the middle of changing table schemas).
fix: file exports were not properly writing UTF-8 character sets.
fix: postgreSQL failures on some forms (column names must be less than 63 characters)
Upgrade Aggregate’s Google publishers to use the updated Oauth2 libraries (e.g., Google Fusion Tables, Google Spreadsheet). Publishing from Google Apps domains does not work (it never has). This required a significant rewrite of the publishers so please notify the ODK core team of bugs!