Using Google Chrome Extension for Hoots
Important
The Hoots Chrome Extension is only available for Private instance and Single Tenant instance installations.
The Hoots Chrome Extension can be configured to work at the instance level only. When looking for a catalog resource that matches the URL to display a Hoot badge, the Hoots Chrome Extension looks across all organization on the data.world instance.
Important
Skip this task if you are planning to set up embedded hoots on specific data product pages.
Installing the Google Chrome Extension
Browse to https://chromewebstore.google.com/
Search and install the data.world chrome extension.
Once the extension is installed, find it in the list of your extensions and configure it by providing the link to your data.world instance. The extension can only work with one data.world instance at a time. To change the instance that the Hoots Extension for Google Chrome is monitoring, change the Instance URL in the Settings dialog of the Hoots Chrome Extension.
To stop using the Hoots chrome extension, simply remove it from your browser.
Setting up hoots
Configure the hoot for a resource in data.world. As long as the user has the Chrome plugin installed correctly and is browsing to a resource page for which a hoot is installed, they will see the hoot badge on the page.
Important
Certain tools may add prefixes to URLs as you browse through data product pages. If these altered URLs don't match the resource URL configured in data.world, the hoot badge may not be visible. If you face such issues, please contact data.world.
Using the Google Chrome Extension
Once the Chrome extension is installed and setup, when the user browses to a page where hoot is setup, they will see the hoot badge. The Hoot Badge informs users about the status of the data product derived from the catalog and other Sentries connected to the hoot. Use the available controls to move the hoot badge to a different location or to resize the badge. Note that the size and position are not remembered, so revisiting the page later or reloading the page will display the badge in its default position and size.
Click the Hoot Badge to see more details in the Hoot pop-up window. Only users with access to the catalog in data.world will be able to click the Hoot Badge and see more details about it. If the user does not have access to the specific resource in the data catalog, they will see a 404 page.
If a page has an embedded hoot and you are visiting the page from a browser which has the Chrome extension, the user will see duplicate hoot badges. It is highly recommended that you either set up embedded hoots or the Chrome plug-in and not both.
Common troubleshooting tasks
Issue: The Hoot badge does not displaying on the data resource page.
Solution: Make sure that Hoots Chrome Extension is installed and the Instance URL in the settings is set to the host name of your data.world instance.
If navigating to the data resource page that should match a resource in the catalog does not cause the Hoot badge to be displayed, please file a support ticket. Include the external URL of the resource as recorded in the catalog, the data product URL from Chrome where the Hoot badge is expected to display (but is not being displayed), and the instance URL from the Hoots Chrome Extension settings page.
Issue: The Hoot badge appears when I first load the data product web page, but then it goes away.
Solution: This behavior probably means that the Hoots Chrome Extension finds a match for the data product URL when the web page first loads, but then the URL in the browser changes, and the match is lost. The Hoots Chrome Extension expects an exact match between the URL in the browser and the external URL on the resource, unless special matching logic has been implemented to handle the way a data product modifies its URL due to user interaction or navigation.
If you encounter this behavior, please file a support ticket. Include the external URL of the resource as specified in the catalog, and examples (multiple examples is better than just one) of alternate URLs for the corresponding data product.