Automated Data.world Catalog Scorecard
Every Monday, WebRun opens data.world, checks every dataset in the catalog, posts a scorecard to Slack showing new, updated, and stale datasets, and sends a direct Telegram alert naming any dataset missing an owner or documentation.
How do I track dataset health across my data.world catalog?
WebRun checks every dataset in your data.world catalog every Monday, and posts a scorecard to Slack showing new, updated, and stale datasets with a total count. It sends a direct Telegram alert naming any dataset missing an owner or documentation, so gaps in the catalog get claimed instead of sitting unnoticed.
- Catalog health is visible in one weekly scorecard
- Datasets missing an owner get named, not just counted
- Documentation gaps surface before they pile up
Built for Data teams managing a shared catalog · data governance leads · analytics teams using data.world
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
data.worldin a real browser with your saved login - no setup, no API keys. -
1
Data.world - check dataset health
data.world
WebRun opens Data.world to check dataset health. - Open data.world and check every dataset in the catalog
- Note which datasets are new, updated, or missing an owner
- Flag any dataset with no documentation or description
Done when This week's catalog health is captured for every dataset.
-
2
Slack - post the catalog scorecard
slack.com
WebRun opens Slack to post the catalog scorecard. - Post the weekly catalog scorecard with counts by status
- Group results by new, updated, and stale datasets
- Include the total dataset count for context
Done when The team channel has this week's catalog scorecard.
-
3
Telegram - alert on missing owners
telegram.org
WebRun opens Telegram to alert on missing owners. - Send a direct alert listing datasets with no owner or documentation
- Name each dataset so it is easy to claim
- Skip this step on weeks where every dataset is fully covered
Done when Any dataset missing an owner or documentation has been flagged.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does it assign an owner to a dataset automatically?
No. It only flags datasets missing an owner or documentation. Assigning an owner is left to your data team.
What counts as a stale dataset?
One with no updates or new documentation for a while, called out in the scorecard alongside new and recently updated datasets.
Will I get a Telegram alert every week?
Only when a dataset is missing an owner or documentation. Weeks where the catalog is fully covered skip that alert.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.