Posted 11 December 2012 - 03:51 AM
Here's something that I noticed just now; not sure whether it's in earlier 4.6 versions:
I have several joined notebooks, and there's evidently some overlap in tags. So for example, when I have "All Notebooks" selected, I have three tags named "wiki" in my tag tree (one of them is from one of my own notebooks; the other two are from joined notebooks). They have different associated note counts: one has no note count, one has 45 notes, the other (defined in my note database) has 1. That's confusing. Moreover, and more confusing, clicking on them in the tag tree causes different results in the note list. If I click on the tags from the joined notebooks; no note filtering is done at all -- the full set of notes in all notebooks is returned, and saved search properties in that case yields an empty search string. If I click on the 'wiki' tag from my own account, I get the old (and expected result): all notes containing the tag 'wiki' from all notebooks are returned, and the saved search properties reflects this.
It's not clear to me that having different tags with the same name in the same tree gives any user benefit. Bug, or design choice? In my opinion, tags are their own data (i.e., it's just a string), no matter where they came from, and they should just be collapsed into one single tag in the list. OK, I can maybe see a case for disambiguating identically named tags from different sources, but I think that this should be more explicitly indicated, maybe something like C++ namespaces: <notebook>:<tag>. And of course, if you're going to have different semantic tags for identical tag names, then that needs to be reflected in the search grammar as well.
Also, the same issues with joined-vs-owned-vs-all notebooks I noted in earlier betas are still there. I'd add that there's probably a case for being able to treat all the notebooks shared from a single user as a single unit for searching in addition, so that gives. Gonna have to think about that to get more concrete than that, though.
Ultimately, I think that the search grammar has a lot of stuff that needs to be added, what with these types of issues and the impending due date supoort. Since the Evernote Business support happened across all major clients more or less at the same time, maybe this will all happen in the search infrastructure in a similar fashion.