Skip to main content

An overview of the Hoot Admin space and Hoot pop-up window

In this walk-through we will introduce you to the various elements of the Hoot Admin space.

In the next walk-through we will introduce you to the various elements of the Hoot pop-up window which appears when a user clicks the Hoot badge. The Hoot pop-up window dynamically presents the resource details from the catalog, such as related resources and business glossary terms. It also displays any FAQs or custom messages that the Hoots administrator has added to the hoot.

sample_hoot.png

For best experience open this walk-through in full screen mode.

An overview of setting up and using hoots and Sentries

  1. First, plan how you want to use hoots and Sentries:

    1. Identify the resources in the catalog for which you want to create hoots.

    2. Decide if you want to inform users only based on catalog status or from other items in the data pipeline. Based on this decision, you will create additional Sentries and dbt jobs and monitors (if you use DBT).

  2. Create a hoot from the resource page in the catalog. A hoot gets created and shows in Hoots list in the Hoot Admin. A Sentry for the hoot is automatically created.

  3. Embed the hoot in the data product for which you built it. Skip this step, if you plan to make the hoots available to users using the Chrome Extension.

  4. Change the status of the resource which automatically changes the status of the hoot. Alternatively, change the status of the hoot manually from the Hoot page to temporarily over ride the automatic status set by the catalog.

  5. Create additional Sentries and attach to the hoot to influence the hoot status.

  6. If you use DBT, create and dbt jobs and monitors.

  7. When user uses the dashboard, let us say in Tableau, they will see the Hoot displaying the status. The end-user does not have to be logged in to see the Hoot badge and status. However, they will need to login if they want to see the Hoot pop-up (For example terms, metrics, and other metadata). This is because the system has to identify the user to understand if they have view permissions on the metadata records of the resource.

In this section: