+- MinimServer Forum (https://forum.minimserver.com)
+-- Forum: MinimServer (/forumdisplay.php?fid=1)
+--- Forum: Support (/forumdisplay.php?fid=4)
+--- Thread: Sort value conflict for Date filter (/showthread.php?tid=6900)
Sort value conflict for Date filter - paulM - 17-04-2023 17:56
I recently discovered the Date.yearOnly.index setting for the tag options - which is great. It's a shame I didn't know about it 10 years ago because date tags for all the files in my library are currently in YYYY format and it's quite a lot of work to retrospectively edit them all to YYYY-MM-DD format. But I had a little experiment with a small number of files and the result was perfect. I have used Album.sortTags for quite some time now and the only problem I had was with those pesky artists who released more than one album per year. And this function sorts out that last niggly problem.
I parked the exercise after that experiment a couple of weeks ago as I am quite busy at the moment. To the best of my knowledge it continues to perform correctly on the limited number of files that have been edited but I have just observed a significant number of "Sort value conflict for Date filter" reports in the log file. I don't know if this is causing problems but I thought I would ask what the issue is before editing any more files into YYYY-MM-DD format.
Are these reports anything to be concerned about?
RE: Sort value conflict for Date filter - simbun - 17-04-2023 20:19
If I understand you correctly, for artists that have released multiple albums in the same year you've modified the Date tag to now include the month and day e.g. YYYY-MM-DD.
When using a tag for an index MinimServer needs to know the value that you want displayed, and where to place that value in the index.
With the setting <Date.yearOnly.index> you're truncating all the Date values to just YYYY for use in the index (that's what the index part of Date.yearOnly.index means), but that produces a mapping of (using the first couple of rows from your log file):
Code:
Index Value Sort Order
1976 1976-06-01
1976 1976Given MinimServer no longer has a way to establish exactly where that index value should appear within the list, it issues the warnings. To fix this you need to modify your tagOptions so that the sort value is also truncated:
Code:
Date.yearOnly.index.sortHope that makes sense.
EDIT: Corrected from Date.yearmonth to Date.yearOnly
RE: Sort value conflict for Date filter - simoncn - 17-04-2023 21:24
This is the correct soiution but I presume you meant to say yearOnly, not yearMonth.
RE: Sort value conflict for Date filter - paulM - 17-04-2023 21:54
Thanks for the advice to both Simons. I have added .sort to Date.yearOnly.index and I will see how it goes.
yearmonth is not what I was looking for by the way, so simoncn, you are correct with your assumption!
RE: Sort value conflict for Date filter - simbun - 17-04-2023 22:03
Dammit!
I do a very similar thing, but use <OriginalDate.yearOnly> for sorting my albums and <Date.yearmonth> for indexing by the release date of the version I own. I meant to copy and paste then replace the operation, and obviously forgot.
I edited the original version to avoid any confusion.