Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Check that the data type matches the control type #11

Open
getodk-bot opened this issue Feb 1, 2017 · 4 comments
Open

Check that the data type matches the control type #11

getodk-bot opened this issue Feb 1, 2017 · 4 comments
Assignees
Labels

Comments

@getodk-bot
Copy link
Member

Issue by mitchellsundt
Thursday Jul 09, 2015 at 19:14 GMT
Originally opened as getodk/getodk#767 (4 comment(s))


Originally reported on Google Code with ID 766

In the last bar in the attached example, Nyati, Pongo, Digidigi are all clumped together
as one item. Ideally, there should be an option for bar graph for each answer. 

I suppose the fundamental problem is that it's hard to analyze data in selects without
them being broken into separate columns. One good work around might be document a way
to do this in Excel

Reported by [email protected] on 2013-02-14 19:08:16


- _Attachment: bar-graph.png
![bar-graph.png](https://storage.googleapis.com/google-code-attachments/opendatakit/issue-766/comment-0/bar-graph.png)_
@getodk-bot
Copy link
Member Author

Comment by mitchellsundt
Thursday Jul 09, 2015 at 19:14 GMT


This looks like a bug in the visualization code. Should the first bar be split also:

- Muhanga
- Kima_kic...

??

Reported by mitchellsundt on 2013-02-14 19:38:15

@getodk-bot
Copy link
Member Author

Comment by mitchellsundt
Thursday Jul 09, 2015 at 19:14 GMT


Or perhaps this is displaying all the combinations that are present in the data?

Reported by mitchellsundt on 2013-02-14 19:38:45

@getodk-bot
Copy link
Member Author

Comment by mitchellsundt
Thursday Jul 09, 2015 at 19:14 GMT


Ugh. This is a mistake on my part. Although the data type is select1, the control widget
was still select. I suppose that's the real bug. Anyway to catch that in Validate?

Reported by [email protected] on 2013-02-14 22:23:54

  • Labels removed: Aggregate

@getodk-bot
Copy link
Member Author

Comment by mitchellsundt
Thursday Jul 09, 2015 at 19:14 GMT


Yikes. That's a mistake.

Changing this to a Validate issue.  

Not sure what we can do there, but it would definitely be worth fixing.

Reported by mitchellsundt on 2013-02-14 23:58:31

  • Labels added: Validate

@yanokwa yanokwa changed the title Better visualization of multi-selects Check that the data type matches the control type Feb 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants