Zeroclickinfo-goodies: Conversions: Mistaking MB for Mb

Created on 8 Mar 2017  路  10Comments  路  Source: duckduckgo/zeroclickinfo-goodies

Description


Based on some user feedback, the Conversions IA is not disambiguating between MegaBytes (MB) and MegaBits (Mb). It is, therefore, nessesary to extend this IA to solve this issue

Correct 馃憤

screen shot 2017-03-08 at 1 49 40 pm

Not Correct 馃憥

screen shot 2017-03-08 at 1 49 26 pm

Get Started

Resources


Instant Answer Page: https://duck.co/ia/view/conversions

Highest Impact Tasks Conversions Triggering

Most helpful comment

@nalinbhardwaj I am already working on it, I'm waiting for https://github.com/duckduckgo/zeroclickinfo-goodies/pull/3988, then case sensitivity is the next step

All 10 comments

I think it's a better idea idea to make a separate issue to add case sensitivity to the IA. This and some other units can be sorted out with that. (cc @mintsoft, I think he's already working on this)

Thanks! Yeah, it's quite chaotic at the moment due to the backlog of solicited + unsolicited issues / prs. One thing that we're taking away from the Programming Mission is the success of consistent and descriptive task templates / Meta Issues. The highest priority tasks are coming from the SERP feedback box. The reason for this is that the feedback is internally vetted and search data is analyzed against the feedback. We'll continue #3544 here.

Edit:
It also seems there is a web of issues growing around certain IAs. If possible we should aim to consolidate them into small-project like tasks.

@mintsoft if you're not working on this issue I can take it up. Also I think this issue should be expanded to enable case sensitivity for all units.

@nalinbhardwaj I am already working on it, I'm waiting for https://github.com/duckduckgo/zeroclickinfo-goodies/pull/3988, then case sensitivity is the next step

@pjhampton Having just looked at it, this is definitely not low hanging fruit; it's going to be ... interesting getting this to behave as users expect

Sure, @mintsoft. Someone labeled it low hanging fruit in the internal pipeline - I didn't look into it enough to dispute this reasoning. Feel free to adjust the labeling as you feel fit.

@pjhampton I just noticed that both of the screenshot examples are wrong! The first query is actually kilobits to megabytes and the second is kilobits to megabits both mistreat Kb as kilobytes

@mintsoft Ah, nice catch! 馃槃
That's interesting though because that was the user's exact query from the feedback. I believe they were expecting a conversion from Kilobytes. Thanks for pointing this out! I will update the description later on for the sake of clarity 馃憤

Was this page helpful?
0 / 5 - 0 ratings

Related issues

moollaza picture moollaza  路  42Comments

rushsteve1 picture rushsteve1  路  13Comments

pjhampton picture pjhampton  路  11Comments

klntsky picture klntsky  路  13Comments

gautamkrishnar picture gautamkrishnar  路  16Comments