2016-08-25, 16:59
Vorbis comments have no official standard, but DATE, ORIGINALDATE, and YEAR seem to be the generally accepted tags.
Really Vorbis is more flexible then ID3, but media players don't seem to have made use of it. There is an arguement that says the way all tag processing is hard coded into Kodi is a limit, and that a user configurable meta model would be better, but that is not where we are. Optional fields, or one field meaning configurable things causes problems.
For your interest Kodi does not use SQL to do the sorting, it fetches all the data using queries without ORDER BY statements and then sorts the results set locally. So determining values for a date field to sort by could be done locally, but it is the local parsing of the data into objects and then sorting etc. that makes Kodi slow on large music collections. A "fancy SQL query" could be used to get a value from a variety of fileds, but I learned long ago avoiding null fields can save a lot of headaches.
Really Vorbis is more flexible then ID3, but media players don't seem to have made use of it. There is an arguement that says the way all tag processing is hard coded into Kodi is a limit, and that a user configurable meta model would be better, but that is not where we are. Optional fields, or one field meaning configurable things causes problems.
For your interest Kodi does not use SQL to do the sorting, it fetches all the data using queries without ORDER BY statements and then sorts the results set locally. So determining values for a date field to sort by could be done locally, but it is the local parsing of the data into objects and then sorting etc. that makes Kodi slow on large music collections. A "fancy SQL query" could be used to get a value from a variety of fileds, but I learned long ago avoiding null fields can save a lot of headaches.
