Tags now support ampersands, apostrophes, and periods 🎉  

Search is a core feature of data.world and is consistently a focus of our improvement efforts. This month, we've rolled out improvements to result rankings on searches that contain more than one word. This improvement provides better rankings for results with titles that exactly match the submitted search as well as several other ranking and relevance improvements. These changes also provide better support for searches that contain special characters such as ampersands, dashes, underscores, and slashes.

Head over the Gra.fo API Documentation to learn more about how to use the Gra.fo public API to export your model as TTL or OWL. The export API is designed for use with build scripts, version control tools, integrations, or to upload your model into other tools, like data.world.

Fun fact: Ever wonder why our adorable mascot, Sparkle, is an OWL? Now you know!

Looking for the API Documentation? We've added a link to the user menu in Gra.fo:

Gra.fo supports several additional export formats from the document page. These options can be found under the File menu.

Here is a roundup of some of the key features we released last month, February 2021 -- Looker metadata support, custom metadata field default edit behavior improvements, Gra.fo enhancements, and dataset sync webhook notifications.

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.

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.

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!

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.

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"
}

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.