Would it be possible to amend one or both existing $TagContains functions to accept a partial/exact parameter? This would allow users to find exact-string matches instead of only partial-string matches.
As a simplified example of what I mean, the current behavior is for $TagContainsAnyString(<URL>,Genre,Pop|Rock) to return T for the exact matches of Pop and Rock in the Genre tag. It also returns T for partial matches like Synthpop, Hard Rock, etc.
What I am asking for would look more like $TagContainsAnyString(<URL>,Genre,Pop|Rock,1). By entering a "1" for the parameter identifies that I only want to return T if the Genre tag is exactly Pop or exactly Rock. Everything else, including partial matches would return F. Alternately, using a "0" (default value) for the parameter would result in the existing behavior.
Reverse-compatibility would probably require the assumption of the default value whenever the parameter is totally excluded. Effectively, $TagContainsAnyString(<URL>,Genre,Pop|Rock) and $TagContainsAnyString(<URL>,Genre,Pop|Rock,0) would both work in exactly the same way that the existing function currently works.
Lastly, I recognize that there are multiple workarounds that would probably achieve the same result. The problem is that those workarounds all become pretty cumbersome if you want exact matches for more than just a few strings. The requested update would scale up much more easily.
