Be notified of new releases
Create your free GitHub account today to subscribe to this repository for new releases and build software alongside 28 million developers.Sign up
- A status bar in the GUI now provides better insight into how far along your job has progressed and the pace at which its progressing.
- You no longer need to provide your app token as part of the authentication; you can simply keep your email and password.
- The date format of yyyy-MM-dd is now included as a default value in the advanced options when mapping your columns.
- Dates with commas now have improved support.
- Port jobs can once again be run to copy a dataset from a domain where a user does not have write access to a domain where a user does have write access. For example, if you wanted to copy a public-facing dataset from one site onto the site where you are a data publisher.
This release of DataSync updates the Port Job functionality to use a faster and more reliable code path. The UI remains unchanged.
To set up a new port job, go to File > New > Port Job. Full documentation available here: http://socrata.github.io/datasync/guides/setup-port-job.html
Note, new Port Jobs will port derived views as parent datasets.
This release of DataSync allows automated replacement of geospatial datasets (zipped shapefile, KML, KMZ, GeoJSON).
To create a new geospatial job, go to File > New > GIS Job. Full documentation available at http://socrata.github.io/datasync
Please note that the GIS job will completely replace the data in your existing dataset.
- When using DataSync in headless mode, the job ID is now logged to the console when the job begins, not when the job ends.
- Leading and trailing whitespace are now trimmed from domain names.
- Small time formatting bug fixed.
- The Trim Whitespace checkbox under Map Fields toggles whether your incoming data will be trimmed of whitespace.
- Setting a custom separator now re-evaluates the fields to be mapped.
- Empty fields in CSVs get converted to null instead of empty string ("").
- By default, comparisons between incoming data and server-side data will be whitespace sensitive
This release brings the ability to ignore bad data in your upload jobs, allowing the job to complete while setting aside any rows that contain errors. Checking the "Set aside errors" checkbox in the "Map fields" page enables that state.
As with other upload jobs, the status of the job can be monitored in the job status page. If the upload job completed (with partial success), a link to the CSV with bad data will be available in the job details page to download and inspect.
- Issue 106 - Map fields does not persist entries
- Missing fields dialog box does not present valid options.