Improved support for Schema.org
The Schema.org structured data standard is a global, collaborative effort to develop a shared and consistent “vocabulary” for web pages, which search engines and software applications use to better “understand” the content they are interacting with. Socrata has supported this standard for years as we’ve worked to bring open government data to the technologies that data consumers already use to discover data, including search engines like Google, Bing, and Yahoo.
Recently, we enhanced our support for the Schema.org standard by adding new behind-the-scenes metadata markup to improve search engines’ “understanding” of published data assets. This markup helps search engines understand the subject matter of published data, interpret data records themselves, and even determine when data assets are related to each other. We expect that these changes will also help to maximize the discoverability of Socrata-hosted data from within popular search engines.
For more information about the markup and standard, please visit http://schema.org/.
In-product Socrata Customer Center resources
Noticed something new on your user profile? We’ve recently added a focused set of “customer support” resources to help members of your site access education resources, explore the Socrata Customer Center, and submit support tickets with ease. We’ve already heard from customers that this widget is helping to guide users to helpful resources available to them - so if you have additional resources in mind, let us know!
Optimizing navigation for members of your site
When the global navigation bar was introduced last year to help Socrata Site Members navigate their sites more seamlessly, we received a great deal of positive feedback from users about the opportunity for consistent navigation and the ease with which they could now take key actions. However, some users were also confused when header interfaces “stacked” atop each other on certain pages, depending on the page and type of user.
As a result, and to improve all users’ awareness of their current context, we’ve adjusted when different navigation interfaces are experienced by different users:
- Site Members (i.e. users with roles) will now primarily experience the global navigation in addition to context-specific headers which appear on particular pages and surfaces (for asset management, site administration, etc). These users will now rarely experience your site's branded headers.
- Community Members (i.e. users without roles) will continue to see the branded header, typically configured by a Site Administrator to support exploration and discovery of data by members of the public.
Site Members will now primarily navigate using the grey global navigation.
Members of the public will continue to use the site’s branded header for navigation and discovery.
In the very near future, we will also be offering Site Administrators the ability to configure additional navigation links just for their Site Members, and will be adding the ability to switch between configured languages from within the global navigation. Stay tuned!
Version 1.9.1 of DataSync is now available
A new version of DataSync (1.9.1) has been released and is available for download here.
This new version comes with a number of updates:
- 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.
- When running a Port Job between two Socrata sites, the domain and credentials entered at the bottom of the GUI is now the destination site, as opposed to the site where the data is coming from.
Read the DataSync documentation for more details on how DataSync works.