Social Web Apps Design
Online Community Development

When You Hit the Wall in #RiteTag

by Saul Fleischman on July 18, 2012

Why does RiteTag give me a “no relevant tags” notice – when I know there are tags for a term or word-string?

You could search Klout, or surface, or any word or group of words or well-known tag in RiteTag and sometimes get your tags related to your search in the networks you intend to tag and share content on – but why do you get nothing from us sometimes?  Is RiteTag broken, buggy, or perhaps bogged down with users?  Actually, no, it is a problem that comes from the type of API calls RiteTag does; every network puts us on a temporary “cool-down” after a few searches.

Here is what it looks like: here is what I just got from my Twitter search of “Disrupt“:

How can there be "no relevant tags" for "disrupt?"

What to do, when you “hit the wall” on one or more networks in RiteTag

  • search the same words/word-strings or other words/strings – on other networks.
  • as a policy, only select networks to search on where you really plan to share or really want to have tags for
  • search on that network where you got “no relevant tags” – in about 10 minutes; chances are, the brief “cool-down” will be over (for 2-3 searches)
  • sometimes, there actually are no tags related to your searched tag, word or word-string

I did other searches, on other networks, did a little non-RiteTag work, and in ten minutes, got this:

Results for "Disrupt," 10 minutes later ("Load more" clicked once, at the bottom, for another 5 related tags)

RiteTag Hints:

  • You never need to include a ‘#’ character before a word to search; RiteTag will look for tags on the networks you select at the top.  In fact, in many networks, a tag (or their equivalent) does not have a ‘#’ before it.  Just give us words or word groups and RiteTag will dig for the tags and give you, when you select a tag from the center area, stats and recent content that has the tag used with it.
  • You will get different results for “microsoft surface,” “microsoftsurface” and “surface” – and because there is no way for RiteTag to know where you would like there to be a division between words, and people tag freely, this situation will continue.   Please try a couple variations, thus, if you do not immediately get tags that are well-used and clearly sufficient to be included with your content to be shared.
  • We made RiteTag as a tool to find tags, learn (from the stats tabs) what they are about and the when/who/what content they are used with – and then take them and use them.  Tick boxes in the center “Select the right tags” area and click “Save” at the bottom to clipboard those tags and paste them into the content you will be sharing.  In fact, in time, we intend to make this process even easier.

The stance of the RiteTag creators on search “cool-down” problem

  1. Ease-of-search, search results relevancy and search speed are of paramount importance, we believe.  Rather than integrate the additional 15+ networks that we have already researched and plan to provide searchability for, we are now spending our time refining our main search algorithm and the way we interact with each social network.  In our plans, have many networks to integrate and tons of features we think you will like; we would rather focus on quality rather than quantity, initially.
  2. We would like you to know that there is no work-around that will keep you from hitting the search wall in RiteTag; to get more access to dig into the social networks’ data costs, and it costs a lot.  Until we are profitable, this situation will persist, and so we wish to share with you the facts and the above suggestions for what you can do, when you “hit the wall” on one or more network.
  3. To deal with the frequent “no related tags” problem, we have several user experience improvements planned and scheduled for integration, and while we do not expect to be able to give our RiteTaggers unfettered access to social networks’ databases (since we do not get that ourselves), we have already greatly reduced the problem, speeded up searches, and are always listening to the suggestions, complaints, and basically everything our first RiteTaggers – the first class of beta-testers – are giving us every day.  For example, we are trying to make the following user experience improvements:
  • When you have temporarily hit the wall for a social network to search tags on, we want to keep it greyed out until it is again going to give you real results, rather than a “no related tags” report (which leaves you guessing whether there actually are no related tags, or RiteTag is simply getting rebuffed by that network – for about ten minutes.
  • When there are no tags for a network, we will display “no tags” in here (many thanks to one of our first RiteTaggers, and a great friend to RiteTag, Andrew Rowland) , so you do not even need to even click on it (two ways of expressing this are below):

My somewhat wordy, attitude-ridden proposed solution:

Would you like to see this next to a network when we find no relevant tags or hit the wall?

RiteTaggers Andrew Rowland and Martin Shirley favored this:

We'll probably use this: "no tags" right inside the network area, so you need not click it

Finally, our frontend guy, Michal tried a few solutions and ended up simply greying-out networks for which we can recommend no tags from your query.  Is this the way to go, would you say?  Is it clear?

Saves us some clicks: networks with no tags related to "hangoutsonair" query show as grey when network results appear in RiteTag

What would you like to see integrated into RiteTag?

Besides networks to search/get tags for, what else would serve your tagging needs, if RiteTag could do it?

About Saul Fleischman

Founder of emerging social media tool sites. Bootstrapping innovation with lean startup development teams. I do project management, user experience, PR, marketing and community development. size it!

Related OsakaBentures Must-Reads

  • Sandor Benko

    What’s wrong with “API limit reached” ?

    • Saul Fleischman

      Thanks, @sandorbenko:disqus  Social networks limit any service or person (we all count as “accounts,” actually – equally) that queries their databases.  We are working on unobtrusive work-arounds for collecting tag data we need. 

Previous post:

Next post:

All rights reserved, OsakaBentures 2012