marklogic-samplestack
marklogic-samplestack copied to clipboard
marklogic-community
Tag % display
Selecting a tag displays the % of total questions where that tag is present. That is not the intended behavior - should be absolute number of questions in the current set with that tag. @yawitz can confirm.
Stu proposed this change, since the count (for the selected tags) will be the same as the count shown at the top of the results list, and thus is arguably redundant. This adds some additional information about the proportion of that tag in the results list (at no additional performance cost, if I understand correctly).
I'm inclined to agree with this enhancement. Kasey, since it doesn't really conflict with any of the explicit requirements, do you have any objections?
I know I was in the dev meeting where we talked about this change. My $0.02 upon seeing it in action...
BEFORE: Up top: "Browsing 1740 questions" Select "java (168)" from tags menu
AFTER: Up top: "Browsing 168 questions" Tags menu: "java (9.7% of 1740)"
At this point, I'm not initially sure what 1740 is referring to in the tags area. Yes, it was at the top originally, but I was focusing on the tags selection. I feel like some redundancy can be useful for the user in that it confirms what they expect, rather than possibly introducing confusion (in an effort to add expanded info/context).
I see that upon further selection, clicking "swing (13)", for instance, I get another "n% of 1740" for the next selected tag. I guess it's not clear to me (without careful investigation) that "1740" is a special number, in this case representing the total documents available.
My concern is also in wondering what 1740 is. Percent itself is not a bad thing, can actually be fairly illustrative, but continuity to see when i click java (168) and then see 168 questions is nice.
OK, all good comments. So how about, for now, we restore the spec'd behavior (just show the count, even though it's redundant), and revisit these ideas as an enhancement (with some additional UX sketching to be done). I assume these kinds of adjustments are very low priority, given the volume of issues still to be addressed.
Kasey, can you make the call?
Yes for now, revert to spec'd behavior. We can iterate on new UX. All lower priority - an EA3 task.
continuity to see when i click java (168) and then see 168 questions is nice.
So to confirm, you want all of the numbers above the line to to match what shows up in the "Browsing NNN Questions" title, and you want the numbers below the line to match what will showup in the "Browing NNN Quetsions" title if the tag is selected?
For now, yes.
(Though I didn't really think of it in that particular way; I thought of it simply as "the count reflects the current result set," which takes search and all filters into account. Stu's framing is a logical consequence of that behavior.)
Agreed that there is an opportunity to do something more interesting here, but OK to revisit in a subsequent release, when we have more time to consider and try a variety of approaches.
As per Stu's process, removing this as a milestone (since we will not change this from the design documented in the wireframes).
The original issue has been resolved, Mitch, can you confirm the wireframes address this? If so, this should be closed.
Please discuss with Stu. His proposal is of some interest, but not for current release, so I think he wanted to leave this open w/no milestone.