Data artifact lineage improvements continue as we introduce the ability to reset the lineage component viewport. For customers with large, complex data artifact lineage, we've heard that it can be difficult to reorient once you start exploring the visualization. With this new "Reset view" button, the view and zoom are immediately reset to the starting orientation.
Use the "None of the following" option in the Advanced Search Builder to exclude search results that match a specific value. This feature works with the logical NOT operator in our Advanced Search Syntax.
Expand and collapse controls are now available for the search filters sidebar to help you quickly locate available filtering options.
The Organization Profile Page is getting a facelift this week to offer more intuitive navigation, stronger support for custom catalog types, and richer discovery features.
Browse the Overview tab for quick links to different resource categories in your catalog. The quick link tiles will take you to a filtered presentation of the new Resources tab. This view operates much like the main search page with support for facets and advanced search syntax, all scoped to your organization's resources.
Searching for open data? Community organizations will now also have these search and filter options available on the new Resources tab.
Another neat feature for our customers leveraging data artifact lineage! In addition to being interactive, the resource items now display a summary card when hovering. You can preview metadata at a glance and click through to the collection, individual tags, or to the resource itself.
Updated metrics tables/reports have arrived on October 18, 2021! Some reports may take 24-48 hours to reflect the new data after deploy due to sync timing.
Data dictionary has been updated to reflect the latest updates as well.
Watch this month's Gra.fo Round Up to learn more about our recently released features!
Relationship arrows can now be repositioned with a drag and drop action.
Download a snapshot image of a concept and its immediate context.
The link to concept feature now includes rich image previews.
Link multiple Gra.fo documents together into one workspace. Separate complex models into subgraphs or extend reference documents that are used in multiple projects.
Most analysts trying to find answers to business questions aren’t searching for tables and columns directly. What they are actually looking for is contextual information that accelerates time to business impact for data. data.world Concept Cards will change the way data consumers access data by providing a unique search experience no other catalog provider does or can do without the backing of a knowledge graph.
Concept Cards are a feature on data.world’s near-term roadmap to help users discover related people, resources, and other supporting information we can obtain from the knowledge graph about a given search topic. If there are suggested actions that can be taken for the topic itself or for related resources, access to those actions is surfaced directly in the search results.
These cards become a jumping off point to browse and discover new things on the platform that share something in common with the search topic of interest. We see these Concept Cards as the first of many intelligent recommendations we can make by harnessing the power of the knowledge graph.
For customers leveraging data artifact lineage, the resource items are now interactive. You can click through the icons to view the respective resource pages.
Updated metrics tables/reports have arrived on September 16, 2021! Some reports may take 24-48 hours to reflect the new data after deploy due to sync timing.
New Tables (multi tenant & single tenant)
Updated Tables (multi tenant & single tenant)
Base platform data updates (single tenant only):
The data.world public API supports several options for programmatically making updates to resources on the platform. PATCH is a method for making partial updates to individual records, such as adding tags, changing a description, or modifying a title.
In the next two weeks, we will be making a change to the way PATCH endpoints modify list values. We outline these changes below.
tag A , tag B] PATCH request is sent to /datasets/democorp/my-example-dataset with body: { "tags": [ "tag C", "tag D" ] }tag A, tag B, tag C ,tag D]PATCH request is sent to /datasets/democorp/my-example-dataset with payload: { "tags": [] }tag A, tag B, tag C ,tag D]tag A , tag B] PATCH request is sent to /datasets/democorp/my-example-dataset with body: { "tags": [ "tag C", "tag D" ] }tag C ,tag D]. tag A and tag B have been removed.PATCH request to /datasets/democorp/my-example-dataset with body: { "tags": [] }Today, PATCH can be used to add, modify, or remove fields for all non-list values. With the current merge logic, items can only be appended to list values using PATCH. As a consequence, if you want to remove or reorder the items in a list, you must use the PUT method, which does not support partial updates and requires a full overwrite of the existing record. The new logic to overwrite list values will allow users to make partial updates to records that remove or modify the order of items in the list without needing to modify the entire record.
This new logic primarily impacts tags, file labels, collections, and multi-select custom metadata fields.
