Core mishandles date tags in yyyy-mm format [Ticket In]

Support Metadata
1

This issue was already reported by Ken Lesniak on 08/2019.
Core mishandles date tags in yyyy-mm format

At least on Windows, the problem still exists.

Core: Windows Server 2016
ROON 1.7 (build 710)

If you specify a date file tag (for example YEAR or ORIGINALRELEASEDATE) and format it as yyyy-mm, ROON adds 01 for the day when it’s imported

This formats work as expected
yyyy
yyyy/mm
yyyy-mm-dd
yyyy/mm/dd

1 Like
2

Hi @Martin_Schneider,

We have a ticket open for this with our development team. I can’t provide any specific timeframes on when this will be addressed, but we’ll be sure to keep you updated once we have more info on this. Thanks!

3

I am a little late in answering :slight_smile:
Thanks for your efforts.

1 Like
4

Any news on this issue ?

This syntax results in the same behaviour as yyyy-mm for me

5

I found if you use the long form (e.g. “November 1974”) it works.
I’d prefer to be able to use yyyy-mm though.

1 Like