Have you ever need to create a 7-day trailing average in order to smooth out a graph? How about compare a value to the same value in the previous row?

Windowed aggregations are a powerful way to perform complex analysis, such as this, without leaving the comfort of the SQL. These functions operate on a defined group, or "window", of rows to return an aggregated value for each row. Window aggregations are supported for both uploaded tabular data, as well as live tables (where support exists in the connected database).

Note: this feature is currently in Beta. Please contact support with any issues.

Keep your eyes open for an exciting new feature in upcoming enterprise releases.
Soon, our standard search behavior will be expanded to include custom metadata associated with your catalog resources. This feature will enable users to execute generic searches such as "Smith" and find resources where "Jane Smith" is listed as "Steward" (a custom metadata property) for a given resource. This feature will be accessible to enterprise customers and will include public API support.

Today we released a new filter group for the search page. Customers are using collections to group and organize the items within their catalog. Users can now filter their search results based on the catalog collection an item belongs to.
This feature is visible to enterprise customers.

Head over to our api documentation to learn more about the new API endpoints we've added in support of collection management.

You can now create and manage collections from the public API to help build automation pipelines and integrations around your enterprise data catalog.

Our interactive docs allow you to test requests right from the browser.

 🚨 Default behavior change coming soon! 🚨

data.world offers the ability to define custom metadata fields on resources like datasets, projects, glossary terms, dashboards, and metadata tables. Custom metadata field types include free text fields, drop-down fields, and multi-select hierarchical fields.

To provide a focused user experience while editing custom metadata, each field had a configuration option to either show the field during the editing process, or else put the field behind a drop-down, requiring a user to find the field in the drop-down before setting its value. The default behavior was to hide the field in the "Add new field" drop-down (pictured below), unless it was flagged as a primary field.

While we typically avoid changing the default behavior of features with widespread adoption, conversations with customers has led us to flipping the default — all fields will show up during the editing experience, unless they are now flagged a secondary field. Only if they are considered a secondary field will they ever be behind the "Add new field" drop down.

The benefit of this change is that users will more easily see all the fields available to edit or provide crowdsourced suggestions for, including fields that are empty and don't have a value set yet.

The edit experience, along with the "Add new field" drop down, in action:

Bottom line - this will result in more fields showing up by default when you click Edit (they won't be hidden under the 'Add new field' drop-down) - unless you mark them as secondary in your metadata configuration (which will hide them under the drop-down).

If you have any concerns or questions on how to implement the secondary setting, including if you'd like to implement it proactively prior to the feature being rolled out, please reach out to your customer success representative or support@data.world and we'd be happy to assist!

Find what you are looking for from anywhere in the application.
Look for new resource types added to the autosuggest feature of the main search bar! Queries and metadata resources, such as glossary terms and analysis records, have been added to the top level search bar. You can now search for these resources from any page with the search bar header. This feature previously supported dataset, project, and user search. This feature is live for community and enterprise users.

Here is a roundup of some of the key features we released last month, December 2020 -- collection crowdsourced suggestions, new metadata and search API endpoints, and a recap on search improvements.

Look for this new feature in upcoming data.world releases!

Here's a sneak peek of what to expect:

We are updating the way we present contributors and visibility for datasets and projects. Currently, we have a top level Access tab that controls individual access, and a Visibility section in the Settings tab that controls whether the dataset/project is open, private, or discoverable to the community. To minimize confusion and complexity, we are combining and redesigning these settings into a single pane of glass to simplify understanding and control of “who can see this resource."

This is how the experience will look from a data consumer's perspective:

This is now the experience will look from an admin's perspective:

Relevant data partners now appear at the top of some search results as featured results, making it easier to find high-quality, reliable datasets in search. Featured results are disabled for private installs.

If you’re interested in learning more about how we help teams find the right data vendors for their projects, drop us a line at concierge@data.world.

Look for this new feature in upcoming data.world releases!

Here's a sneak peek of what to expect:

You'll soon see a new banner above your search results highlighting the number of matched column results for your query. You can navigate to your column results either by clicking the banner or using the result type dropdown below the search bar.

Column search surfaces tables within datasets or projects that contain matched columns, and individual column records defined in your metadata catalog. This feature will be available for data.world enterprise and community users.