Loading Profile...
Ranking threshold ignored as seen by Google Reader Firefox add-in
Hello All,
I have done the following, and I'm facing a bit of a conundrum and am hoping for a little insight.
I exported all my blogs from Google Reader. I then imported them into PostRank. Using the Web UI, I selected the rank I was interested in for each blog. I then exported the OPML file from PostRank. Next, I deleted all my subscriptions from Google Reader. I then imported the OPML file from PostRank. Finally, I installed both FireFox extensions, AideRSS Google Reader Integration 2.4 and PostRank 1.0.
As expected, all the subscriptions were routed through PostRank, which is fantastic. The add-ins are freaken killer (mostly)! However, there were two problems, one minor and one major:
1. The exported feeds didn't maintain the case/spaces in the tags. For example, I had a tag called ".NET Services". This got imported as the tag ".net.services". The spaces were converted to periods and the casing was made all lowercase. Not a big deal, but not idea.
2. I set the rank of a number of blogs to best and greatest. However, when I view them in Google Reader, the integrated add-in shows that many entries are still showing up that are below the specified rank as you can see in the screenshot below:
Any ideas?
--
Regards,
Travis Spencer
P.S. Great data entry form for posting to this forum!
I have done the following, and I'm facing a bit of a conundrum and am hoping for a little insight.
I exported all my blogs from Google Reader. I then imported them into PostRank. Using the Web UI, I selected the rank I was interested in for each blog. I then exported the OPML file from PostRank. Next, I deleted all my subscriptions from Google Reader. I then imported the OPML file from PostRank. Finally, I installed both FireFox extensions, AideRSS Google Reader Integration 2.4 and PostRank 1.0.
As expected, all the subscriptions were routed through PostRank, which is fantastic. The add-ins are freaken killer (mostly)! However, there were two problems, one minor and one major:
1. The exported feeds didn't maintain the case/spaces in the tags. For example, I had a tag called ".NET Services". This got imported as the tag ".net.services". The spaces were converted to periods and the casing was made all lowercase. Not a big deal, but not idea.
2. I set the rank of a number of blogs to best and greatest. However, when I view them in Google Reader, the integrated add-in shows that many entries are still showing up that are below the specified rank as you can see in the screenshot below:
Any ideas?
--
Regards,
Travis Spencer
P.S. Great data entry form for posting to this forum!
I’m confused
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company marked this problem solved.
The best solution from the company
-
Hi Travis -- One of our devs tells me that export bug is fixed now. (He seemed a bit embarrassed, too, so I think you stumbled on something we should have noticed -- good catch! We give out schwag for stuff like that, so if you're interested, let me know your size and mailing address -- melanie at aiderss dot com.)
The one caveat is that you will have to re-import the feeds into Google for the fix to appear. (And if you still notice anything quirky, please let us know.)
Re. the tags problem. Yeah, that's actually by design. We've set lower case as the standard, and we use dots as separators, since we've assigned spaces for other spacing duties. Basically it was a design decision re. trying to cover as many use cases as possible, including things like international characters, acronyms, and accented characters.
That said, if it becomes enough of an issue for enough users, we'll revisit it and look at changing the format.
The company says
this solves the problem
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?I found another discrpency. This time between what the FF plug-in shows and what the Web UI shows on the PostRank site. Check this out:
The same feed, same blog entries, with different ranked values. That doesn't make sense.
If anyone can clarify this for me, I would appreciate it. -
Inappropriate?Hi Travis -- Thanks for the detailed report. I've asked our developers to take a look at it, and will let you know if we have any additional questions or when we know more about the issue.
Regarding the second issue with the PostRank scores not matching, we're aware of that and it's not technically a bug. PostRank scores on the website are calculated slightly differently (feed-based) than PostRank scores in the extension are (thematically). There's a really long, technical explanation for this, but basically the reason for it is so that the Top Posts in the extension aren't just an unmoving list of 10s. The website will show you how all of a site's content is doing on engagement, including its best content, and the Top Posts widget in the extension will show you the best of the best, I guess you could say.
Top Posts are still the highest ranked posts for the site, and posts with the highest scores on the website will still make it into the Top Posts list, it's just that the scores look a bit different because they're calculated a bit differently.3 Comments Add a comment
This solves the problem
-
Hi Melanie,
Can you point me to the really long, technical explanation because I didn't quite follow the short, non-technical one? I understand that there are two different types of analysis going on and one overloaded, ranking number is being shown in multiple UIs. Given this, I'm sure you aren't surprised that your users are a bit confused.
If I may offer my opinion, I would suggest adding different ranking numbers for the different algorithms. If the FF add-in is showing me thematic ranking, indicate that some how (e.g., a different icon that the one shown on the PostRank.com Web UI or two different ranking numbers for the two different calculation procedures). In the PostRank Web UI, if the algorithm being used is feed-based, indicate this some how (e.g., using words like relative best rather than best and provide a link to a not-so-technical overview and an in-depth overview of what's going on). -
Travis those are great ideas on making the difference between Thematic and Feed-based PostRank be more explicit in the UI.. We'll brainstorm some ideas around that!
-
Travis those are great ideas on making the difference between Thematic and Feed-based PostRank be more explicit in the UI.. We'll brainstorm some ideas around that!
-
Inappropriate?Hi Travis -- One of our devs tells me that export bug is fixed now. (He seemed a bit embarrassed, too, so I think you stumbled on something we should have noticed -- good catch! We give out schwag for stuff like that, so if you're interested, let me know your size and mailing address -- melanie at aiderss dot com.)
The one caveat is that you will have to re-import the feeds into Google for the fix to appear. (And if you still notice anything quirky, please let us know.)
Re. the tags problem. Yeah, that's actually by design. We've set lower case as the standard, and we use dots as separators, since we've assigned spaces for other spacing duties. Basically it was a design decision re. trying to cover as many use cases as possible, including things like international characters, acronyms, and accented characters.
That said, if it becomes enough of an issue for enough users, we'll revisit it and look at changing the format.
The company says
this solves the problem
EMPLOYEE
