For enterprise customers, the following updated metrics have been released to your Usage and Governance Reporting (ddw-metrics-*) dataset. This was noted as coming soon here.

Events - Pageviews - Last 90 Days: This table now includes all types of pageviews, whereas previously it was filtered to only include dataset and project views. In addition, the window has been extended from 30 to 90 days.

Events - Queries: This new table is a detailed audit of query events. This was previously already available for multi-tenant customers. Going forward, it will also be available for single-tenant or virtual private customers. More details are included in the data dictionary markdown file. 

Resources - Datasets: This table contains a new column called “notificationsEmail” which includes any additional email address associated with the notifications for the dataset, as set in the dataset settings.

Visits - New Users By Month: This table logic has been updated to be consistent with other metrics, namely Visits - Unique Visitors To Date and Visits - Unique Visitors - All Time List.

Check out recent UX improvements to Gra.fo, our visual knowledge graph modeling tool. 

1. To quickly zoom out to see the full graph, use the keyboard shortcut:
   OPTION (ALT) + SHIFT + 0
2. To zoom to a specific concept:
   OPTION (ALT) + SHIFT + click concept
3. You can now deeplink directly to a concept in the graph using the Copy link to concept option in the concept menu. Watch the video to see how we use this feature to move fluidly between a data.world catalog and Gra.fo.

Gra.fo is a companion product to data.world with a 30 day free trial of premium team features. Visit Gra.fo to learn more, or reach out to help@data.world.

Here is a roundup of some of the key features we released last month, January 2021 -- broader resource support for recently viewed resources and auto suggestions from the search bar, collection search filter/facet, collection management API, and enhanced SQL support for windowed aggregations.

We've been rolling out a series of features to make working with collections easier and more intuitive on data.world. In case you missed it, here a few recent collections related updates:

1. New Collection Management API
2. Quick Collection Creation
3. Editing Resource Collections
4. Filtering Collections In Search

Most recently, we've released bulk editing collections, which allows you to quickly manage a large number of resources by adding and removing them from collections with just a few clicks. 

Screenshot Walk-through

Using business terms as our example, we'll start off by clicking the "triple dot" menu and selecting "Edit multiple Business terms":

Select all the resources you want to edit:

Chose "Add to existing" to add the resources to an additional collection:

Review your changes:

After confirming, you'll see a message like this:

Quick Video Demo

This is a default behavior change that shows more metadata fields while in edit mode. This makes it easier to see the fields that are available for annotating, documenting, and governing catalog resources.

If you have any concerns or questions on how to manage field visibility, please reach out to your customer success representative or support@data.world and we'd be happy to assist!

For more information on this feature, see this Coming Soon post related to the change: https://whatsnew.data.world/coming-soon:-changes-to-custom-metadata-field-configurations-2UHSOA

The following update will only be available for Sites customers:

Managing data access requests takes a team - and data.world wants to make it easier for your data access request team, whether it be your data stewards, owners, or stakeholders, to make informed and timely decisions about each request.

Previously, each of the approving parties for a data access request would received a discrete, standalone email informing them of the data access request, including the customizable request access form details the user filled out.

Now, for Sites customers, we'll be sending out a single email to the approving parties, with the requesting user copied on the email.

This provides the requesting user a channel to engage further with the approving team, as well as a method for the approving team to communicate amongst themselves before rendering a decision about the request.

Real world example:

Let's say you have 3 administrators on the dataset, and a user requests access to the data. Previously, we'd send out 3 individual emails to each of the 3 administrators. Aside from the recipient, the emails are identical.

With our changes, we'll send out just a single email, but to 4 recipients: the 3 administrators, and the requesting user. Any of those users can reply-all, remove recipients, or add recipients in your preferred email client.

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.

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.

 🚨 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.