Conejo, you were not being dense, you were being a very good beta tester.  Non-obvious features are bugs.  Searching for tags and tag completion are now in the bug database.

Thanks for the great feedback!

conejo23 wrote on Jan 2^nd, 2010 at 4:36pm:
The search field on the right side of the Content tab only searches by name and URL.  (That's why, when you delete all text from it, it fills in the placeholder "name, URL".)  So, if that is the search field you're using, that would explain these inexplicable results.

conejo23 wrote on Jan 2^nd, 2010 at 4:36pm:
Do you see the Tag Cloud at the top of the Content tab?  If not, pull down the dimple.  Your tags are all in alphanumeric order.  Select one or more, then set the Filter below the Tag Cloud to "Any" or "All" as you want.  Now, only bookmarks which meet your tag criteria will appear in the content.

Here are some screenshots and more explanation:
http://sheepsystems.com/bookmacster/HelpBook/SSYMH.01.01.html#tagCloud

For a finer-grained search, you can use the Find report:
http://sheepsystems.com/bookmacster/HelpBook/SSYMH.01.03.html#reportFind

Here's a ridiculous example:

That will find any bookmark containing "Appl", "iPhone" or "Mac" in its tags (for example a bookmark with a tag "Macintosh" would qualify), that was added since Sept 2, was visited less than 5 times, and is not on the apple.com site.

conejo23 wrote on Jan 2^nd, 2010 at 4:36pm:
Oh, it will be very happy when this beta test is over.  Thanks!

Maybe some of this stuff should be made more obvious?  Or did I miss the question?  If so, give me an example of a specific tag search that failed.

I know we should add more menu options to the magnifying glass in the search field, so you could search for other things besides name *and* URL.

thank you, sir. Just updated, will test shortly and report back anything interesting.

Jerry, my pleasure, sir. Always great to use an app with a developer behind it like you.

Question: when do you expect to have this revised functionality in place? just want to know when to get back in and test this stuff. Let me know and I'll be happy to report back, as well. I used to do software design and test in a previous life, always happy to help.

Jerry, I was thinking the same thing re OW keywords. You guess is the same as mine, “we might need it later”. I don’t even see how you can search for them within OW.

And sorry if I'm being dense, but just so I'm clear, when you get this functionality in place, I'll be able to import my bookmarks from OW, assign tags to them in BM, save and re-export out, quit BM and when I come back, the tag state will be the same as when I left it.

Do I have that right?

To me, then, the main value in tags will be tagging things that are related that don’t really belong in the same hard folder so that when I'm looking for something relatively obtuse, I can find it. Will also allow me to see a grouping of similar themed sites.

Thanks for your help.

conejo23 wrote on Dec 27^th, 2009 at 1:27am:
No, on the contrary, if you delete tags in a tag-supporting app like Firefox and then re-import from Firefox, the tags you deleted in Firefox will not be deleted in the Bookmarkshelf.  The only way to get rid of just a tag would be to delete in the Bookmarkshelf and then Export.  Now, if you want to "re-master" by importing from Firefox, you can use the Clean Slate option.  This will clean bookmarks as well as tags out of BookMacster and make it look like Firefox.  I hope this is the workaround by which the 20%, 1%, or whatever will "learn to like it".

conejo23 wrote on Dec 27^th, 2009 at 1:27am:
Keywords in OmniWeb map to Shortcuts in BookMacster, not tags.   The important difference, and the reason why we mapped it this way, is because you can only have one Keyword/Shortcut per bookmark.  Therefore, they are not tags which, by definition, allow a plurality.  So, the answer is that you can't manage tags in OmniWeb in any case, because OmniWeb doesn't support anything that looks like tags.

conejo23 wrote on Dec 27^th, 2009 at 1:27am:
Yes, and delete them.

And thanks for the feedback – we're thinking this through now!

conejo23 wrote on Dec 26^th, 2009 at 4:42pm:

Good – we're seeing the same thing.  The problem is the "Merge Tags" checkbox.  By default it is off, which means that tags in the Bookmarkshelf which are not also on a matching Client bookmark are deleted, as you are seeing.  But – duh – if the Client (OmniWeb) does not support tags, then – duh – all tags are deleted.  Further compounding the problem is that the checkbox is disabled if the Client does not support tags because, well, you shouldn't need to consider things that don't exist.

After considering the various solutions to this paradox, I believe this is a case where we want to apply the "Steve Jobs Rule" – if more than 80% of the users want vanilla and 20% want chocolate, set it to vanilla and the other 20% will learn to like it.  In this case, I believe we're probably looking at 99% and 1%.  Here is the new behavior:

## Behavior of Tags during Import and Export

During an Import, when a bookmark existing in the Bookmarkshelf is matched and merged with one from a Client, any new tags on the bookmark in the Client are added to the bookmark in the Bookmarkshelf.

During an Export, when a bookmark existing in the Client is matched and merged with one from the Bookmarkshelf, the tags on the bookmark in the Client are completely replaced by the tags on the bookmark in the Bookmarkshelf.  Any tags on the Client bookmark not on the Bookmarkshelf bookmark are deleted.


As to the latter (export) behavior, that's the way it's been since the first beta version, and no one has complained.  We'll leave the attribute in the data model just in case this turns out to be a bad decision, but unless someone replies real soon and presents a valid objection to the above, the "Merge Tags" checkbox is going to be gone and the above text will go into the Help Book.

conejo23 wrote on Dec 26^th, 2009 at 4:42pm:
Yes, I know, but it works fine for me.  It's on the to-do list, but pretty far down.  If it is a bug, I'm hoping that the YaBB folks already know it and have it fixed for YaBB version 3. 

It's wiping out the tags when re-importing from OmniWeb.  That's why I see them for a second.  Don't save the Bookmarkshelf in that condition or you will lose your tags.  Wiping out the tags is a bug.  I'll get back to you later today with a fix.  Meanwhile, if you hold down the 'option' key while opening the document, this will override Mirror-Open from OmniWeb and the tags will not be wiped out.  But, for now, they will also be wiped out if you import from OmniWeb.

Thanks for the report.