DS4UX (Spring 2016)/Day 5 coding challenge: Difference between revisions

Revision as of 03:20, 27 April 2016

Each of the challenges this week will ask you to modify and work with code in the Wikipedia API projects which you should have installed and begun working with in class.

It's not essential that you solve or get through all of these — I'm not grading your answers on these. That said, being able to work through at least many of them is a good sign that you have mastered the concepts for the week. It is always fine to collaborate or work together on these problem sets.

Challenges

Save the revision metadata printed in wikipedia1-2.py (i.e., the material already being printed out) to a file called "wikipedia_revisions.tsv".
Print out the revision ids and edit summaries (i.e., comment) of each revision for the article on Python.
Which article is in more categories? Python (programming language) or Python (genus)?
How many revisions to the article on "Python (programming language)" were made by user "Peterl"? How about "Hfastedge"?
How many revisions/edits has the user "Jtmorgan" has made to Wikipedia?

Bonus challenges

6. Can you build a list of all of the articles edited by "Jtmorgan"? What is the article with the longest title that user Jtmorgan has edited?

7. How many edits to the article "Python (programming language)" where made in 2015?

@@ Line 3: / Line 3: @@
 Each of the challenges this week will ask you to modify and work with code in the [[DS4UX (Spring 2016)/Wikipedia API|Wikipedia API projects]] which you should have installed and begun working with in class.
+It's not essential that you solve or get through all of these — I'm not grading your answers on these. That said, being ''able to'' work through at least many of them is a good sign that you have mastered the concepts for the week. It is always fine to collaborate or work together on these problem sets.
-This week, you will be required to attempt the first 4 challenges in this list, and upload your solution scripts via Canvas. You will NOT be graded on whether your solutions are correct, efficient, or even functional—just on whether you turn in an attempt at a solution that shows you tried. You WILL be marked down if you don't submit your solutions—so be sure to spend time attempting these challenges!
-You do NOT need to complete and turn in your answers to the bonus challenges (#6 and #7). You will not be graded on these. But if you do attempt them, I'd love to see your solutions!
-Being able to work through at least many of these challenges is a very good sign that you have mastered the important Python concepts we've covered so far. As always, it is fine to collaborate or work together on these problem sets, as long as you submit your solutions separately. And this week, please don't broadcast your responses via Canvas before Sunday night.
 == Challenges ==