DoltHub is a place on the internet to share and collaborate on Dolt databases.

We built DoltHub because we thought it would be useful to interact with versioned SQL databases in familiar ways. For example, query public data on the web, or clone it down locally to inspect it in a SQL shell. Or fork a data repository to your DoltHub account, and make a contribution to an upstream dataset by submitting a pull request.

Today we are announcing another web management tool for Dolt repositories: Issues! This feature, now included on every DoltHub repository, allows users to file issues about that specific data and provide a more transparent log for data problems. Think missing rows or data sources, incorrect values, wrong column type, undesired schema restrictions... you name it!

Our DoltHub organization is currently running two data bounties. Read our blog post about data bounties here, or about our latest bounty to collect transparent hospital pricing data.

The first of our two bounties, Sourcing 2016 and 2020 Election Results, is running until February 14. The following screenshot is from this issue filed by our CEO Tim Sehn. This is a known issue with the data in the vote_tallies table that we've now formally preserved in metadata that is attached to our dataset. If someone resolves this, we can close the issue.

I asked Tim why we don't have this data already, and if anyone can acquire it. Here's the low down:

Navigating to DoltHub Issues

The concept of Issues is self explanatory, but navigating to it might not be. I've provided screenshots that show where to find the new feature. First, open the Issues tab in the repository navigation bar on the left:

Click on an issue and be routed to the issue page, like above. Or route to see all issues on a dedicated /issues route.

From this page you also have the option to create a new issue:

Our Next Steps

In the next couple weeks, I'll be making improvements to the Issues UI. This includes linking web queries directly into a new issue, cross referencing Pull Request and Issue ID's in their respective comment boxes, adding markdown to comments, and sorting Issue lists by Open or Closed. If there's anything else you'd like to see, come talk to me on Discord!

Your Next Steps

Start filing Issues on DoltHub repositories, and sign up for an account if you haven't yet. Keep an eye out for new issues in our active bounty repositories that you can help us close, and get paid for it!