by Mizery_Made » Sat Dec 05, 2009 1:54 pm
I think it would be a bit much to have a drop-down/auto-complete for a field like Title, as the list would be a great deal larger than the list of Artists no doubt. Same could be said about the Custom fields, as there could be any number of strings in a given field across the library. Another factor is, Artist, Composer, Conductor and other such fields support multiple values and thus cuts down on the amount of indexed values (as "Artist 1", "Artist 1; Artist 2", "Artist 2", "Artist 1; Artist 2; Artist 3" and "Artist 3; Artist 1" would only require three indexed values as opposed to five for each variation.)
It may not be exactly what you're looking for, but the
eCustom script might be of some help. It provides a right click entry for various fields (Custom # and Grouping spring to mind as supported ones) and a pre-defined set of values you can apply to it.
Another option may be to store some data in an unused Classification field if you have any. If you don't use Quality for instance, you could migrate your Grouping data there, and that would give you a drop-down as well as Mutli-Value support (a tree node for the information as well). You would just have to remember you've populated the field with information other than what it was intended for.
This does stir up a thought I've had for some time though. Perhaps another custom field or two could be useful, but the additional one(s) would come with Multi-Value support (and thus have a drop-down as well as a tree node). Seems like something that would be found useful. Alwell.
Anyway, hope the script is of some use to you, or the other suggestion. If not, perhaps someone else has a better alternative for you, or perhaps the Devs will see this and take your request into consideration.
I think it would be a bit much to have a drop-down/auto-complete for a field like Title, as the list would be a great deal larger than the list of Artists no doubt. Same could be said about the Custom fields, as there could be any number of strings in a given field across the library. Another factor is, Artist, Composer, Conductor and other such fields support multiple values and thus cuts down on the amount of indexed values (as "Artist 1", "Artist 1; Artist 2", "Artist 2", "Artist 1; Artist 2; Artist 3" and "Artist 3; Artist 1" would only require three indexed values as opposed to five for each variation.)
It may not be exactly what you're looking for, but the [url=http://www.mediamonkey.com/forum/viewtopic.php?f=2&t=33691]eCustom[/url] script might be of some help. It provides a right click entry for various fields (Custom # and Grouping spring to mind as supported ones) and a pre-defined set of values you can apply to it.
Another option may be to store some data in an unused Classification field if you have any. If you don't use Quality for instance, you could migrate your Grouping data there, and that would give you a drop-down as well as Mutli-Value support (a tree node for the information as well). You would just have to remember you've populated the field with information other than what it was intended for.
This does stir up a thought I've had for some time though. Perhaps another custom field or two could be useful, but the additional one(s) would come with Multi-Value support (and thus have a drop-down as well as a tree node). Seems like something that would be found useful. Alwell.
Anyway, hope the script is of some use to you, or the other suggestion. If not, perhaps someone else has a better alternative for you, or perhaps the Devs will see this and take your request into consideration.