Beta: Sensitive Data Discovery

Business context

A key aspect of data compliance is knowing where sensitive data lives and applying classifications that relate to policies that inform business processes for proper tracking and management. Identifying sensitive data, applying these policies, and reporting on this information can be an extremely time consuming and error-prone task if attempted manually.

data.world’s Sensitive Data Discovery automates discovery and classification, making it easier for enterprise customers to identify sensitive data and take action on it within the catalog.

Capabilities

Scan – Use advanced machine learning to identify sensitive data types like email addresses, names, ID numbers, locations, protected health information, and 40+ additional data types identifiable out of the box.

Classify – Apply policy classifications, tags, and statuses such as Restricted, Personal Information, US Only, etc. These classifications help maintain the integrity and confidentiality of your data. They are driven by your scan results and other metadata, as dictated by your unique business logic and terminology.

Take Action – Report and audit sensitive data types and policy classifications across your data landscape, understand how it changes over time, and drive better compliance and governance in your organization.

Integrate – Leverage Sensitive Data Discovery metadata as part of your broader metadata orchestration strategy with APIs and bulk export. Our open and extensible platform makes it easy to plug in your broader ecosystem of additional Sensitive Data Discovery tools and platforms for even greater governance capabilities.

Screenshots

Resource page example

Search results example

If you are an existing data.world customer and would like to be included in the private beta, reach out to your Client Success Director for more information.

Interactive lineage items

For customers leveraging data artifact lineage, the resource items are now interactive. You can click through the icons to view the respective resource pages.

🚨 Default Behavior Change: PATCH API endpoints 🚨

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.


Existing Merge Behavior

Lists are merged with existing values on PATCH requests

  1. A dataset has tags: [tag A , tag B
  2. A PATCH request is sent to /datasets/democorp/my-example-dataset with body: { "tags": [ "tag C", "tag D" ]  }
  3. The dataset is updated to reflect tags: [ tag A, tag B, tag C ,tag D]
  4. A PATCH request is sent to /datasets/democorp/my-example-dataset with payload: { "tags": []  }
  5. No change is applied and the tags remain: [ tag A, tag B, tag C ,tag D]


New Replace Behavior

Lists replace existing values on PATCH requests

  1. A dataset has tags: [tag A , tag B
  2. A PATCH request is sent to /datasets/democorp/my-example-dataset with body: { "tags": [ "tag C", "tag D" ]  }
  3. The dataset is now updated to have tags: [ tag C ,tag D].  tag A and tag B have been removed.
  4. I send a PATCH request to /datasets/democorp/my-example-dataset with body: { "tags": []  }
  5. The dataset has been updated to remove all tags.


Why we are making this change

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.

Advanced Search Builder + New All Results Tab

This week, our search page got a face lift and we unveiled new tools for searching on data.world.

Explore data.world's rich advanced search syntax with the Search Builder tool on our main search page. This friendly form helps you construct more complex searches with multiple filters, logical operators, categories, and custom metadata fields. The Search Builder can be accessed by selecting the "Advanced" option above the filters list on the main search page.

This release also includes changes to our main search page. You'll notice a new layout on the All Results tab that shows the top 3 search hits by type for your term. This tab now shows more results per page and gives users a high level overview of the types of resources they can find on the platform. Hover over the circular "i" icon for more details about the result. More targeted results can be viewed on the Resources tab. You'll also notice changes to the category tabs at the top of the page. Resources, Organizations & People, Comments, and Columns each have their own tailored search experience.

The new search experience is available today for select users and will be available for all users early next week.

Beta: Postgres Proxy

We're happy to announce the beta release of our new Postgres Proxy support. Our goal is to allow any BI and data science tools which support PostgreSQL, to connect to directly with data.world. No 3rd party integration support required!

data.world provides a federated engine to query data from multiple data systems simultaneously, at the source. By using Postgres Proxy, it’s now easier than ever to extend these capabilities to your favorite analysis tools for quickly accessing and creating value from data.

To connect to data.world using the proxy, simply create a new PostgreSQL connection, configured as follows:

host: postgres.data.world
port: 5432
user: {your data.world user id}
pass: {read/write token}
db:   agentid/datasetid

You can find your read/write token in the user settings. If you have any issues or questions, don't hesitate to reach out.

Note: for single tenant customers, set host to postgres.{site}.data.world.

Metrics update: July 28, 2021

For enterprise customers, updated metrics have been released today to your Usage and Governance Reporting (ddw-metrics-*) dataset to address some minor bugs and performance improvements.

Potential observable changes:

  • For both single-tenant and multi-tenant customers, some reports were not reflecting de-provisioned user accounts. With this fix, multi-tenant customers may find a slight increase in counts in Visits - Return Visitors - Daily, Visits - Return Visitor Days, Visits - Unique Visitor Days and Visits - Unique Visitors - Monthly now properly reflecting de-provisioned user accounts in addition to active user accounts. Single-tenant customers may find a slight increase in Visits - Unique Visitors Daily and Visits - Unique Visitor Days.
  • For multi-tenant customers, under certain circumstances some reports could duplicate-count users that were members of multiple sub-organizations. With this fix, you may find a slight decrease in counts in Membership - By Date, Visits - Adoption Daily and Visits - Avg Visits Weekly.

If you have any questions or concerns, please let us know at support@data.world or via your customer success representative.

Announcing new data.world Documentation Portal

We're thrilled to announce the release of our brand new documentation portal. We've remastered all our platform documentation content to make it easier to read, search, and navigate. You can now get all the answers you need in just one place!

These are some of the improvements and new navigation experiences you'll see  in our new portal:

- Home page menus

Use the top menus to navigate the documentation for specific product versions: Community docs for data.world community members and Enterprise docs, specifically written for our enterprise customers who have needs and use cases outside of the scope of our community users.

- Search improvements 

Search is one of the most important ways to find the information you need. So we’ve introduced a new search experience. When you enter a query, you’ll immediately see some suggestions. 

- Easier access to everything you need

Easy access to integrations gallery, API docs, and Grafo documentation.

Check it out at https://docs.data.world/.

Coming soon: Resource Type Search Filter

Next week, we will be releasing an update to the Search UI to include a new standard filter for Resource Type. This has been a much requested filter option to help users drill down into the specific resource types returned from search. This filter includes our common types like datasets, projects, and queries as well as custom types that are configured for your organization's catalog.

This change will also update the presentation order of the search filters as:
1. Resource Type
2. Owner
3. Status
4. Tag
5. Collection
6... Custom configured facets

DockerHub and metadata collector enhancement roundup

Our metadata collector (dwcc, aka the data.world Catalog Collector) is now available on DockerHub! Simply run docker pull datadotworld/dwcc:x.xx where x.xx is your desired version, and you're in business. It's that easy.

Other enhancements to the metadata collector:

  • Updated Domo collector to improve relationship modeling
  • Various Tableau & Manta collector fixes & enhancements
  • Denodo metadata collector support shifted to Denodo 8
  • --config-file option for metadata collector (Beta): We've heard your feedback on wanting a simplified way to manage the configurations for your metadata collectors. The config file will become the default way in the near future to set your parameters going forward. Lots more info on this coming soon! 
Show Previous EntriesShow Previous Entries