I still don"t see the:
https://www.discogs.com/release/35691010-Kasia-Lins-Obywatelka-KL
in the Albunack:
http://artist.albunack.net/4d7cc834-80b7-4e8c-90dc-08337090c04d.html
Albunack has been updated with latest data
Well you wouldn’t - the update hasnt completed yet.
How long does the dump/update take? No rush, I’m just curious about the process 
So it is a semi-automated process. Each stage is automated but we cannot do the whole thing in one go as we need to check the results since the external feeds of data can change causing issues, for example in 2024 there was six months where the monthly discogs data dump was broken, and twice a year MusicBrainz make changes to their database schema, then there are issues with having enough space for the ever increasing database (the largest part being the Acoustid part)
- Create New Database
- Import Discogs db
- Import MusicBrainz db
- Import Acoustid Database
- Create Acoustid Reports
- Create addtional tables based on data (e.g Albunack Ids)
- Create Search Index from database
- Deploy Search Index as WebService
So if everything ran fine the whole process would take one week, but this also depends on me being available after each stage to check the results, and this is not the case because I’m either away, asleep or busy working on something else.
1 Like
Update, Xmas got in the way but nearly done, should be complete in the next couple of days.
1 Like
Okay at last, now updated
Discogs Data 30/11/2025
MusicBrainz Data 12/12/2025
2 Likes
Thanks for doing that.
Why is the release:
https://musicbrainz.org/release/f8546f3e-f9bb-49e3-b264-ab55d4f3956a
from I believe 13.11 missing in the Albunack:
http://artist.albunack.net/4d7cc834-80b7-4e8c-90dc-08337090c04d.html ? Or do I have to look somewhere else?
There is a cache, because you have looked up that release before and it wasnt there then there is a empty value in the cache,but cached values expire, should sort itself out within a couple of weeks.
1 Like
Wanted to check things now running more smoothly, so now updated again.
Discogs Data 31/12/2025
MusicBrainz Data 03/01/2026
1 Like
sorry for being a pain in the a** but the album is still missing 
is there any way to invalidate or update the cache ? 
There is a way, but for individual releases you can access the actual MusicBrainz database with both SongKong and Jaikoz so that seems the easiest solution.
Are you using SongKong or Jaikoz?
I’m using SongKong
So you can use the Match to one Album task, enter the MusicBrainz Release ID and if not found in Albunack it will retrieve it from MusicBrainz.
Got it. TBH I already know the option and used it for some releases. One thing I noticed now: the Match To On Album task does not save folder.jpg. After the metadata gets saved to the files and i run fix songs for this release, then the folder.jpg is saved. Is this by design?
Since the update, I’ve noticed that the Grouping field which I have mapped to Genre on Discogs isn’t pulling anything through. Seems to work if you manually match to discogs but not if you run the main “autocorrect songs” menu item. I “think” it might be when it finds the Musicbrainz release and that has a discogs relation, but I’m not 100% sure. Everything else including my mapping of Discogs Style to the Genre field is working as expected.
Edit. Just manually matched to a discogs record and it didn’t pull through the genre to grouping.
Looks okay to me, can you give me a Discogs Release Id where this is happening.
I manually tagged a bunch. Next one I see, I’ll note it here for you.
OK here’s a bunch. Looks like they matched with musicbrainz and pulled through the discogs ID. None have pulled through the discogs genre which does exist:
https://www.discogs.com/release/15213018
https://www.discogs.com/release/15202839
https://www.discogs.com/release/10191391
https://www.discogs.com/release/18833698
https://www.discogs.com/release/19935067
I’ve also seen some pulling through to the wrong field, and even a weird one where the album artist and album artist sort had “alt.rock, indie…”!!