Managing Hoots
Important
Only users with the Organization Administrator privilege can manage hoots and BB Bots.
Hoots are the main feature that the data product users interact with. They have a 1:1 relationship with the cataloged resource. When a user clicks on a Hoot badge in their BI dashboards, a Hoot details page pops up. This small page provides the end-user with more information (link to the catalog, lineage, related glossary terms, etc).
The badge is an embeddable web object that can be added to any data product (for example, Tableau Dashboards, Power BI Reports, etc.) that allows tiled or floating web objects.
Creating hoots
To create a hoot:
Browse to the resource for which you want to configure the hoot.
Check if the Resource has a status. If not, you must consider setting a Status as the status of the resource in the catalog determines the status of the hoot.
From the Settings tab, go to the Hoots section. Click the Configure Hoot button.
A hoot is automatically created for the resource and the hoot details page opens. The hoot has the same status as the resource. A corresponding BB Bot also gets created for the hoot.
Important
If the resource does not have a status configured, the hoot is created with a Sad status (yellow color).
Click the Manage tag button to assign tags to the hoot. From the Manage tag window, select an existing tag or type in a new tag name and assign it to the hoot.
Click the Preview button to see a preview of the Hoot on a web page.
Click the View in data.world button to go back to the resource in data.world.
Embedding hoots in the data product
To embed the hoot:
From the Hoot details page, copy the Hoot URL or the Markdown for the hoot. The selection will depend on what is supported by the application where you are embedding the hoot.
Go the application where you want to embed the hoots and follow the instructions of the application to add the Hoot using markdown or using an embeddable URL.
Disabling and enabling hoots
Disable a hoot if you want to stop using it temporarily. Once disabled, the Hoot badge will show the disabled status on the pages where you have embedded the hoot.
To disable a hoot:
In the Hoots Admin, browse to the Hoots list.
Locate the hoot you want to disable. Click the hoot to open the Hoot details page.
Click the Edit button.
In the Edit Hoot window, click the Disable hoot boot. Click Save.
The Hoot details page now indicates that the hoot is disabled. Simply click the Enable button to re-enable the Hoot.
To see the list all disabled hoots, change the filter on Hoots list page to Disabled.
Connecting BB Bots to a hoot
To connect BB Bots with a hoot:
On the Hoot details page, click the Connect Hoot button available in the right sidebar.
In the Connect Hoots window, select the BB Bots for the hoot. Click the Update Hoot button.
Influencing the status of hoots
There are different ways in which the hoot status can changes:
When the status of resource is changed in the catalog. Anytime the status of the connected resource is changed in the catalog, the hoot status changes immediately to reflect the latest status to the users of the data product where the hoots are embedded.
When the status of hoot is changed manually from Hoot Admin app. A hoot admin can decide to intervene in the automatic updates to intentionally inform the data product users about a status that is not reflected by the automated updates. For example, when a hoot a sick and all the issues are resolved, it might take for the automated process to be informed about the latest happy status. In such cases, the hoot admin can change the status to Happy manually so that the data product users can start using the dashboards with confidence. The manual chages are over written as soon as their an automatic update received from the data source.
When you have other BB bots connected with the hoot and their status changes. When there are other BB Bots connected with the hoot - the most severe status takes effect.
Table 1.Action
BB Bot 1 status
BB Bot 2 status
Hoot status
A new hoot with two connected BB Bots are set and the status for all is Happy
Result:
Hoot is Happy
The status of BB Bot 2 changes to Sick automatically.
Result:
Hoot becomes Sick.
The status of BB Bot 1 changes to Sad automatically.
Result:
Hoot stays Sick as that is the most severe status.
Hoot admin manually over writes the status of the hoot to be Happy
Result:
Hoot becomes Happy because of manual over-write.
The status of BB Bot 1 changes to Sad automatically.
Result:
The manual over-write is removed because of new status update on BB Bot 1.
Hoot becomes Sick because that is the most severe status derived from connected bots.