Sounds great. I'm with RichG on this one.
Thanks as always.
DATE and YEAR tags
Re: DATE and YEAR tags
So it sounds like two album years will be enough, even if you wanted to use my suggested ORIGINAL YEAR field for Recorded Year. Are you saying in general terms we might need a track level DATE field as well, eg for jazz session date?
Re: DATE and YEAR tags
That may not be a bad idea also for best of compilation albums where each track is from a different year though ORIGINAL YEAR tag may also be used for each track in that instance.
Re: DATE and YEAR tags
Yes. It think I could take some advantage of a track level date. Below you can see an example of how I use TRACKGROUPHEADER to identify each session date and consequently grouping under that header the respective performers.musoware wrote:Are you saying in general terms we might need a track level DATE field as well, eg for jazz session date?
Re: DATE and YEAR tags
I think that works pretty well as it is using the track group header: I don't see having a separate date would enhance that at all unless you wanted to drive a query by session date - as you'd need a session location as well.
Re: DATE and YEAR tags
Exactly. I would still need to use the Group Header for the session location. I can live very well without that extra date although someone may find it useful to be able to follow a performer's career, for instance.musoware wrote:I think that works pretty well as it is using the track group header: I don't see having a separate date would enhance that at all unless you wanted to drive a query by session date - as you'd need a session location as well.