About Hoots

Hoots provide trust in the governance of the analysis resources. If a stakeholder sees the Hoot they know the resource is being monitored by the data team and they can quickly get a color-coded signal regarding the health of the analysis resources. Red = sick, Green = happy, Gray = neutral. These correspond with the Negative, Positive, and Neutral asset status available for catalog resources.

Business users: As data and analytics are being pushed to more and more rank-and-file employees, people with little to no data literacy are now expected to make sense of this information. The hoots provide the simplest, lowest cognitive load way for these users to know if they can trust a report. And if they have a question, they can see the Hoot as the icon for help and trust in data.

Data teams: Data teams have to be reactive as business needs for data change constantly. Business priorities and initiatives are fluid. Data teams also have to contend with the rise of "shadow BI" - people promoting alternate data to support their personal theories or agendas. The hoots are data teams' stamp of approval on a report, signaling to users that the information could be trusted.

As a business user or stakeholder, you need to quickly understand if the analysis resource is trustworthy and governed. I want to know quickly if there are any known issues, what the terms mean, and where I can find more information. Hoots help you trust and understand.

As a data team member, you need to quickly communicate known issues in your data pipeline that affect the status or health of an analysis resource. You also don’t want to have to answer the same questions over and over and want to spend your time doing more proactive work, rather than reacting to questions that the catalog could answer for the user.

Enable Hoots for a collection to activate them across all analysis resources within the source collection. To manage Hoots more selectively, create a dedicated collection with Hoots enabled and add only the specific analysis resources you want to include. This approach provides more granular control.

To display Hoots on web pages outside your source collections, enable them for business terms and their subtypes. Add the Hoots URL for each resource and include them in a collection that has Hoots enabled. When users visit the configured URL for a business term, the corresponding Hoot appears on that page.

Hoots can be made available to end users through a browser extension for Google Chrome and Microsoft Edge. Install the data.world browser extension for Google Chrome or Microsoft Edge. Post-installation, while on Google Chrome or Microsoft Edge, users will see the hoot when they navigate to BI and analysis resource pages (for example, Tableau Dashboards, PowerBI Reports, etc.) where hoot is set up in data.world.

To update a hoot’s status, change the status of its connected resource in the catalog. When the resource status changes, the hoot status automatically updates to reflect the latest state for users viewing the associated analysis product.

Following is a sample list of analysis resources for which hoots are available:

To display Hoots on web pages not associated with analysis resources, enable Hoots for business terms and their subtypes, and configure custom webpage links for them.