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/.

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

On Thursday, June 10, we will be deploying a major update to data.world Enterprise Data Catalog customer Usage and Governance Reporting, which is delivered to the ddw-metrics-* dataset in your catalog.

These changes have focused on performance optimizations, increased consistency, some additional columns, and some new tables/reports. Some columns have been renamed to order to achieve consistent use and definitions.

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

Multi-tenant change log

Single-tenant change log (private sites & private installs)

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! 

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

Need some quick feedback on your collaborative modeling project? Want to share your graphical view of the world with your customers or your team?

You can now share your Gra.fo model documents without requiring your audience to have a Gra.fo account or an individual invitation. Use the "Get link" option of the share menu to grant read-only access to your document to anyone you've shared the link with. 

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

1. CAST the resulting column to a DATETIMESTAMP to force timezones, or DATETIME to strip timezones (documentation)
2. Use AT_TIME_ZONE() to explicitly state your timezone (documentation)
3. Ensure that the table column type is set to be of type 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.

Head over the Gra.fo API Documentation to learn more about how to use the Gra.fo public API to export your model as TTL or OWL. The export API is designed for use with build scripts, version control tools, integrations, or to upload your model into other tools, like data.world.

Fun fact: Ever wonder why our adorable mascot, Sparkle, is an OWL? Now you know!

Looking for the API Documentation? We've added a link to the user menu in Gra.fo:

Gra.fo supports several additional export formats from the document page. These options can be found under the File menu.

Here is a roundup of some of the key features we released last month, February 2021 -- Looker metadata support, custom metadata field default edit behavior improvements, Gra.fo enhancements, and dataset sync webhook notifications.