The node will be organized like this:
With each artist indexed:
Here is a snippet of the ini:
Code: Select all
[Album Artists] icon=Artist sortLike=Artist hideIfEmpty=0 easyCriteria=AllTracks [A] icon=Artist sortLike=Artist hideIfEmpty=1 level=AlbumArtist level=Album trackCriteria="AlbumArtist LIKE 'A%'" parent="Album Artists" [B] icon=Artist sortLike=Artist hideIfEmpty=1 level=AlbumArtist level=Album trackCriteria="AlbumArtist LIKE 'B%'" parent="Album Artists" ...etc
I haven't perfected that aspect. Right now I have a node setup that is a catch-all for all non-letter nodes that has a track criteria such as this:
Code: Select all
trackCritera="(AlbumArtist NOT LIKE 'A%') AND (AlbumArtist NOT LIKE 'B%') AND ...."
As you can see that line would get a little unwieldly, but I know very little of SQL to see how else to do it. Perhaps there is a code I can use to generically pick up a letter, number, or other symbol (e.g. punctuation) as I have some items that lead with a ( or a " or something else (when indexing songs and albums).
I also wanted to note that in the parent node, "Album Artists", I actually have it picking up all tracks to mimic behavior I like to see. If you don't want to see all the tracks, you can eliminate that criteria. The trackCriteria under each letter/number index will refine the results to that particular letter as you set it up.
Last item is that the ini file will start to get very big if you have a lot of items indexed. I index artists, albums, titles, so it becomes useful to use comment lines to "graphically" separate nodes for your own sanity with the ini file. I hadn't even thought of it, but it might be useful to utilize secondary ini files to use global find and replaces for a batch of nodes and then copy them into the primary ini file.