In August, we plan to release a series of improvements to our search page including:
We're investing in navigation enhancements across the site for community and enterprise users. This week, we plan to roll out a beta breadcrumbs feature to help you get back to your list views from your resource pages. This first beta release will include easy access to your organization page from metadata catalog resources, quick filters to navigate back to similar items in your catalog, and basic hierarchical navigation for things like tables and columns. Additional hierarchical navigation support is planned for the coming months.
Recently announced in a coming soon post, the new resource type search filter is now available on the search page for all users of the platform. This filter allows users to drill down to any supported resource type, including custom configured catalog types.
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/.
In the last few weeks, several minor bugs and enhancements have been made. Here are some notable ones:
Improved help text for tags, including on pressing “Enter” to add tags
Improved empty state messaging for adding contributors to a dataset
Consistent use of timestamps in alerts and notifications
Navigation tabs on various pages are now keyboard-navigable (left and right arrow keys) for ease of browsing and improved accessibility
“Share” button directly opens “Grant access” modal
Consistent use of display name in emails
Text truncation fixed for filter bars and the project workbench
Various layout, text, and navigational misalignments or inconsistencies
We are thrilled to announce the public release of a highly requested feature: Column Search. The main search page now provides result details that match against columns in your data.world datasets and projects as well as column metadata in your catalog. Look for the new column results banner above your search results.
Not exactly sure what you are looking for in your catalog or your resources library? Tired of clicking into individual items just to discover it's not what you thought it was? Look for the new information icon on list views to see additional contextual metadata about the items in the list without leaving your current view.
data.world not only supports metadata collection, but can also power federated queries of data sources such as Snowflake, BigQuery, SQL Server, and many others. Now in addition to our UI, you can use our API to manage these virtual connections and tables.
Head over to our API documentation to learn more about configuring virtual connections and adding virtual tables to your datasets with the public API.
🚨 Default behavior change coming next week 🚨
We have recently discovered that when executing queries, there are some cases where our DATETIME columns contain timezone information, and other cases where they do not. This is primarily an issue that arises with columns containing date/time information in uploaded files (we do not see this with live tables). We have decided to address this inconsistency. Starting next week, query result columns of type DATETIME will no longer contain timezone information, while columns of type DATETIMESTAMP will always contain timezone information.
The impact of this change shouldn’t be significant, and most users will see no change. However, if you have queries across ingested data which aggregate on DATETIME columns, or do DATE_ADD() style calculations, you may notice differences in your results depending on your current timezone.
If you are impacted by this change, here are some ways to clarify your intent w.r.t. timezones:
CAST the resulting column to a DATETIMESTAMP to force timezones, or DATETIME to strip timezones (documentation)AT_TIME_ZONE() to explicitly state your timezone (documentation)DATETIMESTAMP or DATETIME (documentation)Note: If timezone information is desired, but not defined, UTC is assumed.
Please contact support@data.world with any questions or concerns. As always, we’re happy to help.
data.world is very excited to announce our new deep brain integration.
Now data consumers simply need to think about what data they want, and data.world will return governed, curated data. It also supports cataloging of business terminology straight from subject matter experts.
When we originally envisioned the feature, our design inspiration was to provide an "easy button." However Jon Loyens, co-founder and CPO, famously then said "what if there was no button at all?"
A future release will support agile data governance workflows, such as data access approvals. Integration is quick and relatively painless, though upgrades require a bit of effort and minor outpatient surgery.
