Metrics update: Feb 25, 2021

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.

Gra.fo navigation and linking improvements

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.

Coming soon: Metrics update

An update is coming soon for the following metrics tables.

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.

New metadata collector in private beta: Looker

We're proud to announce a new metadata collector is now available for enterprise customer use in private beta -- Looker (business intelligence). Let us know if you'd like to get your hands on the early version of this collector.

As we get closer to general availability, we'll be releasing more information on these exciting expanded metadata and discovery capabilities!


February 2021 monthly product update

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.

Bulk editing collection resources

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


Now released: Changes to custom metadata field configurations

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

New Dataset Sync Notifications

data.world now sends 2 additional webhooks: Dataset Sync Failure and Dataset Sync Recovery Success

When a dataset within your org fails to sync, data.world will immediately send a webhook message to the configured URL with details about the failure, including error code and error messages from the downstream source.

With those sync failure details, you could configure a ticket to be created in your ticketing system, trigger an alert for a dev-ops team, or simply just make the team aware of the issue.

Natively, data.world will format the webhook payload to post messages in Slack when it recognizes the configured webhook is Slack, which is shown in the demo video below.

Demo


Screenshots


Technical Details

syncTask.status.success is triggered only after the recovery from a failure. 

Example payload, in JSON:

{
  "datasetid": "sync-demo",
  "event": {
    "type": "SUCCESS",
    "task": "state_table.csv",
    "created": "2021-02-04T06:37:06.936Z"
  },
  "eventType": "syncTask.status.success",
  "resourceUrl": "https://data.world/texas-whiskey/sync-demo/file/state_table.csv",
  "resourceType": "URL",
  "resourceOwner": "texas-whiskey"
}

 syncTask.status.failure is triggered on the first failure for that file. When it recovers, data.world will send one syncTask.status.success

Example payload, in JSON:

{
  "datasetid": "sync-demo",
  "event": {
    "type": "FAILURE",
    "task": "state_table.csv",
    "created": "2021-02-04T06:35:17.945Z",
    "error": "HTTP/1.1 404 Not Found"
  },
  "eventType": "syncTask.status.failure",
  "resourceUrl": "https://data.world/texas-whiskey/sync-demo/file/state_table.csv",
  "resourceType": "URL",
  "resourceOwner": "texas-whiskey"
}

Data access request email notifications

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.

Windowed aggregations (beta)

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.


Show Previous EntriesShow Previous Entries