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!


Coming soon: Search support for custom metadata

Keep your eyes open for an exciting new feature in upcoming enterprise releases.
Soon, our standard search behavior will be expanded to include custom metadata associated with your catalog resources. This feature will enable users to execute generic searches such as "Smith" and find resources where "Jane Smith" is listed as "Steward" (a custom metadata property) for a given resource. This feature will be accessible to enterprise customers and will include public API support.

Coming Soon: Changes to custom metadata field configurations

 🚨 Default behavior change coming soon! 🚨

data.world offers the ability to define custom metadata fields on resources like datasets, projects, glossary terms, dashboards, and metadata tables. Custom metadata field types include free text fields, drop-down fields, and multi-select hierarchical fields.

To provide a focused user experience while editing custom metadata, each field had a configuration option to either show the field during the editing process, or else put the field behind a drop-down, requiring a user to find the field in the drop-down before setting its value. The default behavior was to hide the field in the "Add new field" drop-down (pictured below), unless it was flagged as a primary field.

While we typically avoid changing the default behavior of features with widespread adoption, conversations with customers has led us to flipping the default — all fields will show up during the editing experience, unless they are now flagged a secondary field. Only if they are considered a secondary field will they ever be behind the "Add new field" drop down.

The benefit of this change is that users will more easily see all the fields available to edit or provide crowdsourced suggestions for, including fields that are empty and don't have a value set yet.

The edit experience, along with the "Add new field" drop down, in action:

Bottom line - this will result in more fields showing up by default when you click Edit (they won't be hidden under the 'Add new field' drop-down) - unless you mark them as secondary in your metadata configuration (which will hide them under the drop-down).

If you have any concerns or questions on how to implement the secondary setting, including if you'd like to implement it proactively prior to the feature being rolled out, please reach out to your customer success representative or support@data.world and we'd be happy to assist!

Coming Soon: Access and ownership moved to Settings

Look for this new feature in upcoming data.world releases!

Here's a sneak peek of what to expect:

We are updating the way we present contributors and visibility for datasets and projects. Currently, we have a top level Access tab that controls individual access, and a Visibility section in the Settings tab that controls whether the dataset/project is open, private, or discoverable to the community. To minimize confusion and complexity, we are combining and redesigning these settings into a single pane of glass to simplify understanding and control of “who can see this resource."

This is how the experience will look from a data consumer's perspective:

This is now the experience will look from an admin's perspective:

Coming Soon: Column Search

Look for this new feature in upcoming data.world releases!

Here's a sneak peek of what to expect:

You'll soon see a new banner above your search results highlighting the number of matched column results for your query. You can navigate to your column results either by clicking the banner or using the result type dropdown below the search bar.

Column search surfaces tables within datasets or projects that contain matched columns, and individual column records defined in your metadata catalog. This feature will be available for data.world enterprise and community users.

Metadata management public APIs

We've added a full suite of metadata management endpoints to our public API!

If you need to build custom workflows, integrate with existing tool chains, or require additional flexibility in managing your catalog, head over to our API docs. We've added endpoints to manage glossary terms, analysis resources, data sources, tables, columns, and relationships.

Coming soon: Collection management APIs


New metadata collectors in private beta: Power BI and DBT

We're proud to announce that two new metadata collectors are now available for enterprise customer use in private beta -- Power BI (business intelligence and data visualization) and DBT (next-gen data transformation). Let us know if you'd like to get your hands on the early versions of these collectors.

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

What's new? We'll tell you!

Thank you for checking out the data.world Product - What's New changelog to learn about all the new and updated features hot off the presses. We wanted to have an interactive, rapidly and frequently updated newsfeed that reflects on data.world's continuous integration and continuous deployment approach -- where multiple product releases happen every week, and the product is constantly evolving.

As always, if you have questions or feedback feel free to reach out to us at support@data.world or your Customer Success Manager, and if you are looking for older release notes, you can click here.