certuna

> > Ah yes I'll fix this, there have been new additions to the codebase so my migration is outdated. > > Thank you so much! Looking forward to trying...

Yeah this should only happen during the scan, afterwards the non-album artists are cleaned up and the links disappear. https://github.com/navidrome/navidrome/pull/2583 fixes this by making all artists clickable, but isn't merged...

> ive got many errors while moving from 0.49.3 to 0.50.1 like the date formatting not being accepted (example: 10/09/2011) This is not a bug, your tags have incorrectly formatted...

Is this an issue with Navidrome or with the Spotify API?

I think this will probably have to wait (like many web UI features) until the migration to ReactAdmin v4.

Problem is that it is not clear cut what the ORIGINALRELEASEDATE field should hold: - the id3 standard says that the Original Release Date (the `TDOR` frame) of a track...

I believe this is officially the `TPUB` frame in id3v2.x, although MusicBrainz might write its own custom tag?

I'd say read both label and publisher, make it a multi-value field?

Looking into this - as with all text fields, id3v2.4 and Vorbis allow the label field to have multiple values. This in principle means this can't just be stored in...

Still relevant and valuable