SongKong Jaikoz

SongKong and Jaikoz Music Tagger Community Forum

Discogs "Only modify field if empty" not working properly

#1

I have Jaikoz configured to only write the composer tag from Discogs when the field is empty, but I have noticed that it writes the tag even when the field has value. Because of this, the field value from Musicbrainz is automatically overwritten every time I import data. I tried with some other fields like Producer and I get the same results. Even when Discogs is configured to modify the field only when empty, it writes the tag values from Discogs all the time. I also noticed that if I set the composer tag to ‘Never modify’ in Discogs, it will empty the value of the field when I import data from Discogs.

#2

Hi, I have replicated the problem, the issue is just with people role fields
Composer, Conductor, Remixere, DJMixer, Lyricist, Producer, Engineer.

What happens if Disocgs has a particular role i.e a composeroits clear out existing values, then checks whether allowed to add, this is why if you set to Never Modify you end up with empty field rather than unchanged field.

It clears out values to ensure we dont add same more than once, and copes with adding multiple composers. But unfortaunetly it shod be doing this check after deciding it can modify.

I am fixing this now, it will be in next release of Jaikoz that I expect to release within the next week.

#3

Thanks for checking on this.
I’ve also noticed that when pulling things like the composer from discogs, it only seems to add a single value even if the discogs page lists multiple composers (Musicbrainz works as expected). It also seems to sometimes add the same composer for all tracks even if individual tracks have different composers. Such as with the this album (I get Ron Wood as the sole composer on all tracks): https://www.discogs.com/release/6007899

#4

Discogs database is not as well structured as MusicBrainz, looks like there is an issue and have raised https://jthink.atlassian.net/browse/JAIKOZ-1224

#5

So the first issue is now fixed as part of Jaikoz 9.4.0 released today, please see http://blog.jthink.net/2018/12/jaikoz-940-release.html