I know we can create custom list values for tags, and we can set MP3Tag to prefer those values, but is there a way to delimit the terms that can be used strictly, so that only the terms on the list could be used? I find that sometimes there are typing errors, but if the field was limited as such, this would preclude this problem.
As you can input anything into any field, I do not think that you can limit the contents of a field to such a set of terms..
That was my suspicion. Is this a limitation or rather a feature of this program or tagging fields in general? While the fields might be able to be populated with anything perhaps the program could limit what you could input in certain fields in order to avoid spelling errors resulting in failed matches? I understand it is not something MP3 tag can do right now, but would it be possible perhaps as a feature request?
Could you elaborate a little on how you would like to see the interaction?
Where and how do you save that list?
What should happen during input of data?
How fuzzy should the algorithm be to allow input?
What should happen if a new input is valid but resembles one of the limiting entries a lot?
In which fields would you need this feature?
Could you elaborate a little on how you would like to see the interaction?
It would be the same pull down menu with pre-fixed values that would sort as you type in the field. So if you wanted to input Latin Jazz, as you typed Latin J the list would scroll down and the first matching term would be highlighted. Once you found the term you wanted to use, you can hit enter or tab and it will be populated. Similarly, and as is the case now in the program, if you typed part of the entry and hit tab or enter, Mp3Tag would just populate the first value that matches. If one types something that does not match any value the field would remain blank, or if you tried to hit tab or enter, you will get an error sound.
Where and how do you save that list?
The same way and location as the those we use now for user defined lists. There would just be an option that would state "Only Use values from the pre-defined list" as another option to "Prefer the predefined values."
What should happen during input of data?
See above
How fuzzy should the algorithm be to allow input?
I don't know enough to answer this
What should happen if a new input is valid but resembles one of the limiting entries a lot?
The term would have to be an exact match, and, as I state above, if there are two matching options and you don't type the whole value, the first matching value would be populated into the field.
In which fields would you need this feature?
There are many custom fields I use that I would like to do this, for example my language, genre, mood, country, main instrument and others.
I am not the one to implement any of this.
But it looks to me as though except for the error sound and the additional option "allow only values" it can all be done right now.
In a way it boils down to the disciplin to maintain the list of pre-defined values and use it.
I see problems for the usablity in fields that have yet unforeseen entries. There it would lead to a multiplication of work as I first enter the data, then get the refusal, have to edit the list, enter the data again.
Not really because I can type something very similar with perhaps the last letter misspelled and the field will take it. I want the field to reject the value if it is not included in the predefined list. I will put in a feature request. Who know if it will gain traction.