Socrata Platform Release Notes: Webtrends, Axis Scaling, and World Travel (30 May 2017)

Webtrends Analytics

As you publish data for your citizens, some of the most common outputs tracked are various website analytics, such as page views, click-through rates, and new users. While Google Analytics has been the predominant web analytics tracker used on Socrata sites, there are other analytics tools that Administrators like you have asked about adding through the “Site Appearance” settings on your site.

Due to popular request, we have added a Webtrends tag field for those who rely on Webtrends to track website stats. You can find the new option under the General Settings section in Site Appearance.


Read this Knowledge Base article for more details on how the Site Appearance section works.


Automatic Axis Rescaling for Data Lens

As you explore a Data Lens page, you are able to click on aspects of a chart in one card, and the rest of the visualizations on the page will be filtered to the value selected. In some cases, notably with high-cardinality datasets, applying a filter can make the data in other charts difficult to interpret, because while the axis remains the same, the total values are much smaller.

Based on popular request and much interest, Data Lens now has a “Rescale Axis on Filter” option, which will allow you and your users to easily see smaller subsets of data automatically when filtering.


If the scaling doesn’t make sense for that particular filter, you can uncheck the “Rescale Axis on Filter” option and the chart axes on the page will rescale back to the full dataset values.

Read the Knowledge Base for more details on how Data Lens work.


Traveling Around The World This Summer? Take Socrata With You!

When looking at data from a country that is different from your home country, language is one of the most obvious differences you are likely to notice. But, there are a number of other more subtle differences in how data is formatted from country to country. To help users around the world use Socrata more easily, we’ve made some updates to how we handle different languages and data formats.

First, to help Administrators better manage their Socrata data platform, we’ve ensured that all Administrative pages are now fully translated into the language for the site. We also added translations for a couple of other pages that were previously only in English, such as the dataset nominations page and the dataset analytics pages.

Second, in a majority of European countries, CSV files are often formatted with a semicolon separator rather than a comma separator. To help users in those countries who download data from Socrata and want to easily open the file in Excel, we’ve now added a new download option “CSV for Excel (Europe)” which provides a .csv file with semicolon separators.

And finally, there are many countries where a “.” is used as the thousands separator and a “,” is used as the decimal separator, for example 1.234,56. If a dataset on Socrata has that number formatting set for a number, percent, or money data column, we now preserve the format in the “CSV for Excel” and “CSV for Excel (Europe)” exports.

Keep an eye out for some more international updates soon!


Small Updates & Bug Fixes

  • New visualization experience:
    • Fixed an issue where grouping on a timeline chart caused an error in displaying the chart.
    • Sometimes filtering on categorical data (text data) was leading to the incorrect filter. This is now resolved.
    • In the table below the chart, money data types now respect the column alignment specified in the column metadata. For example, if you change the alignment from right to left, the table below the viz will respect that.
    • An issue where an additional non-relevant field was displaying in a flyout is now fixed.
    • When you are editing a map, as you zoom or move around on the map itself, you will now be notified that when you save that view of the map will be preserved in the final, saved version.
    • The row label capitalization is now respected in the table pager that appears below the visualization.
    • On a bar chart, if you have wordy labels on the y-axis you can now move the y-axis to the right and left to make more or less space for your label text before it turns into an ellipsis (…).
  • Primer:
    • When a Date & Time data type are used, the date and time displayed in the table on Primer now always displays the same date and time as in the traditional grid view no matter what timezone is used.
    • With very large datasets, sometimes the Primer page would display a 502 error. This should now happen less frequently.
    • The “more” option on Primer’s button menu is now visible on mobile devices.
  • Datasets and filters:
    • On a few datasets, filtering through the filter sidebar was not working. This is now resolved.
    • Maps based with multiple filtered data sources now correctly show all data sources on the map.
    • Fixed an issue where a dataset was unable to be published from a working copy.
    • Unfortunately users were sometimes unable to properly filter, or remove an existing filter, on charts. This issue has been resolved and filtering is working as expected.
    • Occasionally a user was unable to transfer ownership of a dataset. This is now fixed.
  • If a plain text column in a tabular dataset had a large number of unique values, users were temporarily unable to create cards for that column on a Data Lens page. This has been fixed.
  • Occasionally users were unable to download non-data files. This issue has been resolved.
  • Accessibility improvements were made to some to the Administrative and profile pages, Perspectives, the navigation menu bar, and PDF downloads.
  • Dates for related views and dates in the catalog are no longer appearing in English when the language for the site is set to Catalan.
  • Occasionally when searching on an embedded map, removing the search did not return the map to the original view. This is now fixed.
  • Fixed an issues where after re-ordering custom metadata fields, sometimes when deleting a field the wrong field would be deleted.


Check out our other Product News, and give us a shout at with questions or ideas.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request



Article is closed for comments.