🚨 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!

Find what you are looking for from anywhere in the application.
Look for new resource types added to the autosuggest feature of the main search bar! Queries and metadata resources, such as glossary terms and analysis records, have been added to the top level search bar. You can now search for these resources from any page with the search bar header. This feature previously supported dataset, project, and user search. This feature is live for community and enterprise users.

Here is a roundup of some of the key features we released last month, December 2020 -- collection crowdsourced suggestions, new metadata and search API endpoints, and a recap on search improvements.

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:

Relevant data partners now appear at the top of some search results as featured results, making it easier to find high-quality, reliable datasets in search. Featured results are disabled for private installs.

If you’re interested in learning more about how we help teams find the right data vendors for their projects, drop us a line at concierge@data.world.

We recently added search as a feature of our public API.

These new endpoints support searching for datasets, projects, insights, queries, tables, collections, files, glossary terms, and analysis resources.

We offer two options:

• Simple Search: Simple text search with filtering support by owner and resource type
• Advanced Search: Supports complex searches including date ranges, tags, and custom resource types

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

Search is the primary way users look for data and analysis in data.world. Now it's even easier with simpler "status:" advanced search keyword, status tooltip hints that appear when you hover over a colored status indicator, full-text search on metadata tags, and the new Collections filter.

Here is a roundup of some of the key features we released in 2020, including search improvements, 'Collection' management UX enhancements, query log reporting, and more.

Windowed aggregations partition the results from a SQL query into groups in order to perform calculations across adjacent rows of the query result. You can read more about windowed aggregations and see examples of their usage on data.world in our SQL documentation.

Here is a list of all the new windowed functions with links to their reference pages:

• CUME_DIST
• DENSE_RANK
• FIRST_VALUE
• LAST_VALUE
• LEAD
• LAG
• NTH_VALUE
• NTILE
• PERCENT_RANK
• RANK
• ROW_NUMBER