That’s correct.
ANYTHING that you enter into your “private” recipe (on the flavor line), goes into the database.
EVERYTHING that’s in the database, gets offered as an “option to select from” in the drop down menu, when it comes time (for you, or anyone else) to select the flavor to add to your recipe, as well as when you’re wanting to add a flavor to your stash.
So, in short, all the “trash” that gets added in a private recipe (speaking only about flavor names here) becomes another flavor option for other users to select from.
Great tip!
I would add to that, that you can also break things down to individual letter combinations, etc.
Examples:
Bak Tou LB - would return results looking for any results with those letters side by side, as well as, with the included capitalization.
bak to ch (lb - would return results for all letters which are side by side, without regard to capitalization [you would get both lower and uppercase entries in results], and would automatically omit any entries which do not include the use of the ‘open parenthesis’ bar.
By jove she’s got it!
After 3-4 years of trying to get this in order (and tens of thousands of entries fixed), the situation persists, because of one simple thing: users are allowed to enter their own custom flavor names.
Now, with that said, the more accurate statement would be that, the problem persists because there should have been two SEPARATE databases created (back in 2015): one for custom (user created) flavor names, and another database for mod-only-approved additions.
Then, the drop down menus (for adding to the stash/recipe sections) would only allow a user to select the correct flavors.
Anything manually typed into one of the flavor lines during recipe creation, would be added to the ‘custom entry’ database.
This would maintain the user’s ability to “create their own custom flavor” entries, without the side effect of polluting the drop down menu.
But until the system is refined (changed), it is what it is.
It does, but it doesn’t.
Bear in mind that ELR was pretty much the first MASSIVE undertaking of its kind.
One of the goals was obviously to allow the user to have maximum flexibility to create a recipe. This includes making your own flavors (either by mixing combinations of existing flavors, OR by creating a flavor from scratch).
Now, if you think about NET users, and even larger scale operations (places that start off as bedroom projects, turn into a mom and pop level business, etc) the original format (as designed) offers functionality that other calcs didn’t have.
By the same token, it also created the side effect of what we ALL have to deal with now.
So, while additional refinement would not be out of line, when you get to having to deal with a foundational aspect of how the site was designed, you can then hopefully understand that it’s a HUGE undertaking to have to try and address (on the backend).
Only one person gets paid by any of this: Lars
The rest of us are community volunteers who’s time and efforts are donated to the community as a whole.