Automatically generated reports from MusicBrainz data. Daily reports use a locally replicated database; Top Editors, Edit Discussions and Top Voted Edits use the official database exports processed with GitHub Actions.
| Report | Schedule |
|---|---|
| Top Release Groups | Daily · 1:00 AM ET |
| Top Works | Daily · 1:15 AM ET |
| Duplicate Artists | Daily · 1:30 AM ET |
| Missing Cover Art | Daily · 1:45 AM ET |
| Artists Missing Basic Info | Daily · 2:00 AM ET |
| Top Editors | Weekly · Sunday morning |
| Edit Discussions | Weekly · Sunday morning |
| Top Voted Edits | Weekly · Sunday morning |
The Top Editors leaderboard also shows
latest-only totals for applied Release Group, Release, Artist and Work
creation edits for its current top 500 editors. These counts live in
TopEditors/contributions.json, are refreshed each weekly run, and are not
part of the historical rank/edit-count comparisons. Historic release-creation
edits are included.
Install the Artist Subscription Sync userscript to sync your MusicBrainz artist subscriptions for use in supported reports.
Currently supported:
- Duplicate Artists — show duplicate pairs where either artist is in your subscriptions.
- Artists Missing Basic Info — show only artists in your subscriptions.
The subscription list is stored locally in your browser. Re-sync from your MusicBrainz Artist Subscriptions page whenever you want to update it.
A big inspiration for setting up my own MusicBrainz server and reports was DontMindMe.
A few of his reports I especially like:
He has many more useful MusicBrainz reports as well, so definitely check out his page and projects.
Report data is generated automatically and published to GitHub Pages. Daily reports use the local MusicBrainz mirror; Top Editors, Edit Discussions and Top Voted Edits are built from official exports with GitHub Actions.
Thanks to majkinetor for the GitHub Actions processing idea.