Profile page improvements, enhanced custom metadata options, and more (April 13, 2020)

Administration & User Management

User Profile Page Improvements

  • Resolved an issue related to asset counts in the Profile page for "My Assets" and "Assets Shared to Me."

  • In the Profile page, users can now filter assets by Version, Asset Type, Audience, Tags and Category.

  • Users can now see which teams they are part of.

  • As a site Admin, while viewing somebody else’s profile, the Admin will be able to see the other User's access details along with their application tokens.

Catalog, Site Navigation & Metadata

Enhanced Custom Metadata Options

  • A new, optional custom metadata configuration feature allows site administrators to configure labels for otherwise obscure metadata values (such as codes) on a field-by-field basis. For example, a required metadata field called "Department Code" might use numerical codes to represent departments in an organization. Configuring meaningful labels (e.g. “Department of Information Technology”) for these values enables data publishers to quickly and easily make the appropriate selection when filling out metadata. More details scan be found in this support article. To have this optional feature enabled on your domain, please contact 

Data Interaction & Derived Views

Performance Improvements

  • Socrata has completed a ground-up rewrite of our data storage layer. This has enhanced response times, increased stability, and simplified how external users, applications and tools interact with your data. As of this release, all datasets are now powered by this new technology, which has already resulted in a 3-10x improvement in response time and up to 6x improvement in import time.


Updated User Roles

  • We have updated roles to better enable users to create and collaborate on Stories! Before this change, when a user added a collaborator to a Story, the person may not have had access unless they had the correct rights to create and edit Stories (specifically +perspectives roles).
    Now, when a Story is shared with a user, the user will be able to view and/or collaborate on that story even if this user does not have a role with permission to create and edit Stories. Note: We are not removing the +perspectives role, just making the publisher and editor roles more inclusive. For more information, read this article!

Curious about other areas of the platform? Visit our Performance or SCGC release notes for more! Or 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.