# ID3v2.3 TYER/TDAT now merged into one YEAR field formatted
**URL:** https://community.mp3tag.de/t/id3v2-3-tyer-tdat-now-merged-into-one-year-field-formatted/15097
**Category:** Support
**Created:** [October 11, 2013, 9:38am UTC](https://community.mp3tag.de/t/id3v2-3-tyer-tdat-now-merged-into-one-year-field-formatted/15097 "2013-10-11T09:38:12Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@mville](https://community.mp3tag.de/u/mville)
#### Post date: [October 11, 2013, 9:38am UTC](https://community.mp3tag.de/t/id3v2-3-tyer-tdat-now-merged-into-one-year-field-formatted/15097/1 "2013-10-11T09:38:12Z")
I am disappointed to see the following change in version 2.58:
CHG: reverted change: ID3v2.3 TYER/TDAT now merged into one YEAR field formatted as
YYYY-MM-DD (due to popular request).
Although I understand the need for this, why can't it be an option:
i.e. ID3v2.3 TYER/TDAT as per the specification as in version 2.57 and an option for users who wish to merge into one YEAR field formatted as YYYY-MM-DD?
---
### Author:  [@LyricsLover](https://community.mp3tag.de/u/LyricsLover)
#### Post date: [October 11, 2013, 8:20pm UTC](https://community.mp3tag.de/t/id3v2-3-tyer-tdat-now-merged-into-one-year-field-formatted/15097/2 "2013-10-11T20:20:16Z")
Something similar: [/t/15083/1](https://community.mp3tag.de/t/15083/1)
---
### Author:  [@system](https://community.mp3tag.de/u/system)
#### Post date: [February 9, 2026, 12:24pm UTC](https://community.mp3tag.de/t/id3v2-3-tyer-tdat-now-merged-into-one-year-field-formatted/15097/3 "2026-02-09T12:24:42Z")