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.
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:
--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! The data.world catalog collector (dwcc) version 2.25 and newer now includes enhanced collection of Tableau metadata, leveraging the Tableau Metadata API. For maximum available metadata, it is recommended you use Tableau user credentials with admin level permissions. The latest version of the collector is also included automatically if using Connection Manager.
New metadata includes expanded information from datasources, databases, fields, metrics, and many more inter-object relationships.
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
Looking for a quick definition in your glossary? Want to see your full glossary in one view? The Glossary overview has been updated to include inline descriptions for your terms. Click on a term to view additional details and metadata.
One of the most powerful features of the data.world catalog is the ability to enrich your catalog resources with custom metadata that's unique to your business.
We are pleased to announce that we've rolled out the first of several improvements to support search matches on custom metadata fields for your catalog resources.
This improvement expands the fields we match against for free text searches to include any custom metadata fields you have configured in your catalog as text or selection fields. This feature empowers your end users to search for resources by the terminology and categorizations that mean the most to your business.
In the example above, verified by and data steward are custom metadata fields defined in our catalog for tables. A search for sarah smart now yields matches where she is listed as the data steward or the person who has verified the data, in addition to any existing matching fields like owner.
Tip: You can perform more precise searches against custom metadata fields with our advanced search syntax. In the example above, a search for
metadata:"data steward:sarah smart"will return filtered results where Sarah Smart is listed as the Data Steward.
Look for upcoming releases to further support boolean and IRI-based metadata searches.
🚨 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.
