We're proud to announce a new metadata collector is now available for enterprise customer use -- Presto (distributed SQL query engine). Presto is a popular way to query data across a variety of different data sources with a single, optimized interface. Metadata collected includes database, schema, table, view, and column information.
Status indicators, which include helpful tooltip hints when you hover, are available in many parts of the application such as search and the newsfeed. They provide quick, at-a-glance visibility of the quality, certification, or governance status around data or analysis resources. They are now also available on organization profile pages as well.
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.
OPTION (ALT) + SHIFT + 0OPTION (ALT) + SHIFT + click conceptGra.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.
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:
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.
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:
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
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.
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"
}