Comment 22 for bug 1152863

The approach we took to create this was from the prospective of a light weight plug-in that has no impact to the underlying systems in Evergreen. Our goal was to not change how the other searches work, but instead try to implement the functionality in a way that would not require a change to query parser. The reason for this was to not change how the current “power users” used Evergreen.

In short, we didn’t want to change how something works for everyone for the request coming from a subset of the community (MassLNC). If it turns out however that the majority of the community would want to use language “and/or/not” vs “&&/||/-“ then the change to query parser would make the most sense.

I would suggest I18n be implemented in the front end of any project. The underlying business logic should never depend on what language is being use. This is copying how .dtd is currently being used in other areas of Evergreen.

Let me know if there are any questions or suggestions about the above.