(11-09-2014 12:12)DavidHB Wrote: Sorry not to come back sooner; I've not had much keyboard time available recently.
(10-09-2014 13:50)jake.t Wrote: from the root, selecting a month or a day doesn't make much sense because they are arbitrary without a year so I want to nest the month index within the Year index, and day within the Month.
does that make sense?
Yes it does, as a concept. I didn't quite get your reference to %file_create_date%, though it would make sense if it was a reference to something you are doing in MP3Tag.
Let us assume that you have a create_date tag in your files, derived from the original file creation date and therefore equivalent to the accession date of your file in your library. If you were to put, say, "-create_date" (index by accession date in descending order) in your indexTags property, this would order file creation dates with the most recent entries at the top. Likewise, in your TagOptions property, you could use the create_date tag in the Album.sortTag entry. This would pretty readily enable you to identify the most recent items in the current selection.
In the normal intelligent browsing fashion, if the items in the current selection (for example of a particular artist) have different accession dates - as they would have - there will be a create_date option in the browse tree at that point, with the most recent items at the top of the date list when you select it.
If you wish to go further than this, things start to get complicated. It is theoretically possible to have separate create_year, create_month and create_day tags, and add them (descending) to indexTags. This would, at least conceptually, allow you to use the browse tree to select, say, the year and then the month. It seems to me to be a lot of work for not much gain, but you might think differently. Personally, if I were implementing date-based indexing, I'd be inclined to stick with a single date for the accession field, and use the browse tree to filter entries before selecting a date-based list.
[Edit] Of course, all this assumes that you structure your date tags in such a way that they will sort correctly, as in "2004-10-21" or whatever.
I hope these thoughts help.
David
Thanks David, that works for me!
the mp3tag reference is correct, %file_create_date% is an informational tag I can pull. Although it its raw form it is listed with Month first I can reformat the output to the new created tag as I wish to manipulate things a little to come out how I want.
thanks for you help!