Editing HCDS (Fall 2017)/Schedule

From CommunityData
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 1: Line 1:
<!--
<noinclude>
<noinclude>
<div style="font-family:Rockwell,'Courier Bold',Courier,Georgia,'Times New Roman',Times,serif; min-width:10em;">
<div style="font-family:Rockwell,'Courier Bold',Courier,Georgia,'Times New Roman',Times,serif; min-width:10em;">
Line 19: Line 18:
}}</div></div>
}}</div></div>
</noinclude>
</noinclude>
-->


=== Week 1: September 28 ===
=== Week 1: September 28 ===
Line 205: Line 203:
=== Week 6: November 2 ===
=== Week 6: November 2 ===
[[HCDS_(Fall_2017)/Day_6_plan|Day 6 plan]]
[[HCDS_(Fall_2017)/Day_6_plan|Day 6 plan]]
[[:File:HCDS Week 6 slides.pdf|Day 6 slides]]


;Mixed-methods research: ''Big data vs thick data; qualitative research in data science ''
;Mixed-methods research: ''Big data vs thick data; qualitative research in data science ''
Line 272: Line 268:
=== Week 8: November 16 ===
=== Week 8: November 16 ===
[[HCDS_(Fall_2017)/Day_8_plan|Day 8 plan]]
[[HCDS_(Fall_2017)/Day_8_plan|Day 8 plan]]
[[:File:HCDS Week 8 slides.pdf|Day 8 slides]]


;User experience and big data: ''user-centered design and evaluation of recommender systems; UI design for data science, collaborative visual analytics''
;User experience and big data: ''user-centered design and evaluation of recommender systems; UI design for data science, collaborative visual analytics''
Line 337: Line 331:
=== Week 10: November 30 ===
=== Week 10: November 30 ===
[[HCDS_(Fall_2017)/Day_10_plan|Day 10 plan]]
[[HCDS_(Fall_2017)/Day_10_plan|Day 10 plan]]
[[:File:HCDS Week 10 slides.pdf|Day 10 slides]]


;Communicating methods, results, and implications: translating for non-data scientists ''
;Communicating methods, results, and implications: translating for non-data scientists ''
Line 360: Line 352:


;Resources
;Resources
* Bart P. Knijnenburg, Martijn C. Willemsen, Zeno Gantner, Hakan Soncu, and Chris Newell. 2012. ''[https://pure.tue.nl/ws/files/3484177/724656348730405.pdf Explaining the user experience of recommender systems].'' User Modeling and User-Adapted Interaction 22, 4-5 (October 2012), 441-504. DOI=http://dx.doi.org/10.1007/s11257-011-9118-4
* Sean M. McNee, Nishikant Kapoor, and Joseph A. Konstan. 2006. ''[http://files.grouplens.org/papers/p171-mcnee.pdf Don't look stupid: avoiding pitfalls when recommending research papers].'' In Proceedings of the 2006 20th anniversary conference on Computer supported cooperative work (CSCW '06). ACM, New York, NY, USA, 171-180. DOI=http://dx.doi.org/10.1145/1180875.1180903
* Megan Risdal, ''[http://blog.kaggle.com/2016/08/10/communicating-data-science-why-and-some-of-the-how-to-visualize-information/ Communicating data science: Why and how to visualize information].'' Kaggle blog, 2016.
* Megan Risdal, ''[http://blog.kaggle.com/2016/08/10/communicating-data-science-why-and-some-of-the-how-to-visualize-information/ Communicating data science: Why and how to visualize information].'' Kaggle blog, 2016.
* Megan Risdal, ''[http://blog.kaggle.com/2016/06/13/communicating-data-science-an-interview-with-a-storytelling-expert-tyler-byers/ Communicating data science: an interview with a storytelling expert].'' Kaggle blog, 2016.
* Megan Risdal, ''[http://blog.kaggle.com/2016/06/13/communicating-data-science-an-interview-with-a-storytelling-expert-tyler-byers/ Communicating data science: an interview with a storytelling expert].'' Kaggle blog, 2016.
Please note that all contributions to CommunityData are considered to be released under the Attribution-Share Alike 3.0 Unported (see CommunityData:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following CAPTCHA:

Cancel Editing help (opens in new window)