search

danithaca / balalab-public

Automatically exported from code.google.com/p/balalab-public
0 stars 0 forks source link

Thinking through topic granularity #117

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
This is brought up from design meetings. Below is some email correspondence:

--------
Hi Daniel,

Greg and I came up with a solution for the granularity issue today. We think 
the workaround solution that was mentioned yesterday will address the problems 
we discussed while avoiding any major changes to the backend. We came up with a 
subscription system that would take place during the on boarding process; 
however, users could have the option to complete it at a later time (resulting 
in all their views to be set to neutral).

After signing up, users would be directed to a page that displays 12 or so main 
categories (e.g. gun control, abortion...) in clickable boxes. When a user 
clicks on a box, a light box appears that allows them to set their views on the 
broad category (e.g. gun control) as well as related issues (e.g. assault 
weapons ban). Users would use sliders to set their views along a spectrum 
(strongly disagree, disagree, neutral etc.). Users will also have the option to 
provide more data about their views by clicking a plus icon next to each issue 
within the light box (to capture respect for the opposing side etc.). If a user 
skips this optional process, they will be prompted to complete it later.

We have solutions in mind on how to display the tags as well. We can fill you 
in on the specifics in person. Also, there is a rough mockup bellow on what 
this might look like.

Best,
Cody

-----------------

Thanks guys. At some point after soft launch, the whole team should sit down 
and discuss the differences among categories/topics/sub-topics. This is 
something that deserves more thoughts.

-----------------

One problem I have now is about assigning an article to multiple sub-topics. 
Suppose an article is in 2 sub-topics, then after a user read the article and 
answer the quiz, we don't know whether the user changes opinions under which 
one of the 2 topics. Or we could give the user 2 separate quiz on both topics, 
but that adds complexity. It also adds complexity to sharing. Suppose a user 
agrees with one sub-topic and disagrees with another sub-topic of the article, 
then should we show "change their views" or "challenge my views" or both? 

To avoid these complications, I'd like to have an article assigned only to one 
topic. Do you think there'll be some serious problems about it? 

-----------------

I agree that assigning one subtopic per article is the best approach. I think 
most articles will cleanly fall within a single subtopic, and I feel the one 
subtopic to one article organization will make the most sense to users. Simple 
is better in this case.

Original issue reported on code.google.com by danith...@gmail.com on 3 Mar 2014 at 10:36

GoogleCodeExporter commented 9 years ago 
Right now we are using a 2-level structure: Categories and Issues.

People can't pick a side on the categories. An issue has to be clearly 
debatable as Pro/Con.

Some questions to think about:
1. Do we allow items to be assigned to multiple Issues?
2. Do we allow Issues to be associated with multiple Categories?
3. What's the conceptual difference between "Gun Control" category and "Current 
Events" category? Do we allow the latter category?
4. Do we allow more than 2 levels of categories/issues/sub-issues?

Original comment by danith...@gmail.com on 3 Mar 2014 at 10:41

GoogleCodeExporter commented 9 years ago

Original comment by danith...@gmail.com on 16 Jul 2014 at 3:47