I'm having a heck of a time creating view schemes where a string field is to be limited.
The problem is with fields that are shared amongst different types of data, like the album field, for example.
The minute I create an Image View Scheme that has to select an album or two the drop down list displays every album in my database, including over 5,000 audio albums.
So when I create an Image rule to include my Spain and Italy (photo) albums I have to go through a HUGE list of all audio, data, video, podcast and image albums to find it. It is too unwieldly.
To fix this I've already started adding some custom album fields to deal with this issue, such as Cooking Albums, Woodworking Albums and I was about to create a Photo Albums field when it occurred to me that I'm creating even more problems by doing this.
I already have a rule to rename/move my files after import that uses [genre]\[album] directories.
Now I'm going to have to have [genre]\[cooking album], [genre]\[woodworking album], [genre]\[photo album] etc. One problem is being fixed only to create more complications on the other end.
Is there any way to have smartlist rules respect either the first rule in the smartlist (Media type = Image) such that selecting Album after that would only display the Image albums in the drop-down list? Or can the view scheme smartlist respect the parent scheme rules?