Merge pull request #2297 from edx/ahodges-documentation-discussions

Ahodges documentation discussions

docs/en_us/course_authors/source/change_log.rst

@@ -8,19 +8,21 @@ Change Log
 ==============  ================================================================
      DATE       CHANGE
 ==============  ================================================================
-01/21/2014      Added information about accessibility in the topic :ref:`Add Textbooks`. 
-01/08/2014      Updated the topic :ref:`Set Important Dates for Your Course` to 
+24 Jan 2014     Added the :ref:`Discussions` and :ref:`Guidance for Discussion Moderators`
+                chapters.
+21 Jan 2014     Added information about accessibility in the topic :ref:`Add Textbooks`. 
+08 Jan 2014     Updated the topic :ref:`Set Important Dates for Your Course` to 
                 reflect change to default course start date to 2029.
-01/08/2014      Updated the topic :ref:`Add Files to a Course` to reflect addition of
+08 Jan 2014     Updated the topic :ref:`Add Files to a Course` to reflect addition of
                 sorting to the Files & Uploads page. 
-01/01/2014      Updated the chapters :ref:`Organizing Your Course Content` and 
+01 Jan 2014     Updated the chapters :ref:`Organizing Your Course Content` and 
                 :ref:`Testing Your Course` to reflect changes in the Course Outline design.
-01/01/2014      Updated the topic :ref:`Add Files to a Course` to reflect addition of
+01 Jan 2014     Updated the topic :ref:`Add Files to a Course` to reflect addition of
                 pagination to the Files & Uploads page.
-12/10/2013      Added the appendix :ref:`MathJax in Studio`.  
-12/11/2013      Added the chapter :ref:`Guidelines for Creating Accessible Content` 
-12/12/2013      Added the edX :ref:`Glossary`    
-12/05/2013      Complete revision of edX Studio documentation and integration 
+10 Dec 2013     Added the appendix :ref:`MathJax in Studio`.  
+11 Dec 2013     Added the chapter :ref:`Guidelines for Creating Accessible Content`. 
+12 Dec 2013     Added the edX :ref:`Glossary`.    
+05 Dec 2013     Complete revision of edX Studio documentation and integration 
                 of edX101 content.
 ==============  ================================================================
 

docs/en_us/course_authors/source/create_discussion.rst

@@ -14,7 +14,6 @@ See the following topics:
 
 * :ref:`Create a Discussion Component`
 * :ref:`A Student's View of the Discussion`
-* :ref:`Seed a Discussion Space in Your Course`
 
 
 Before you add a Discussion component, it is generally a good idea to add an HTML component that 
@@ -82,36 +81,3 @@ students can find the category and subcategory of the discussion in the left pan
  :alt: Image of the discussion page from a student's point of view
 
 
-.. _Seed a Discussion Space in Your Course:
-
-**************************************
-Seed a Discussion Space in Your Course 
-**************************************
-
-Many students may feel hesitant to be the first to
-post an answer to your question. You can get the discussion started by posting
-your own answer—preferably anonymously or as a student, so that students will be
-more comfortable replying if they disagree with your post.
-
-To post as a student, follow the steps below. If you later want to reply as
-yourself, log back into your usual account and omit steps 1 and 2.
-
-#. Set up a test account on with an e-mail address that is not associated with your Course Team.
-
-#. Go to your course URL and register for your course.
-
-  a. Locate the Unit that contains the Discussion component.
-
-  b. In the Unit, locate the discussion space.
-
-  c. Click **New post.**
-
-3. Type a title for your post in the Title field, and then enter text for your post.
-
-#. If you want to, select the **post anonymously** check box or the **follow this post** check box.
-
-#. When you are satisfied with your post, click **Add Post.**
-
-Your new post appears at the top of list in the unit. Posts are listed in
-reverse chronological order.
-

docs/en_us/course_authors/source/discussion_guidance_moderators.rst

+######################################
+Guidance for Discussion Moderators
+######################################
+
+Discussion forums are hugely important tools in running a successful MOOC; they allow for substantive community development, in addition to being excellent sources of feedback and ideas for future iterations of the course. 
+
+Moderators are the key to effectively managing these online communities. Moderators keep the discussions productive and relay important information (errata, student confusion or interest with particular topics, etc.) to the rest of the course staff. Discussions can be moderated by any of a number of members of the course team, but dedicating enough time to moderation is the best way to cultivate a successful discussion culture.
+
+Please feel free to use some or all of the information in this chapter to guide the contributions of your discussion moderators.
+
+**********************
+Responsibilities
+**********************
+
+* Answer basic questions posed by students, and direct students with questions to the right resources: syllabi, course documents, course updates, useful lecture segments, example problems, etc. 
+
+* Relay reports of errata, common misconceptions and questions, highly disruptive participants, bugs, and amusing or interesting posts to the most appropriate course staff. 
+
+* Enforce the Honor Code by editing or deleting problem answers, or requests for answers, promptly. 
+
+* Edit out offensive content from the discussion, and remind the originators of discussion etiquette and expectations. 
+
+* Communicate problems and successes to your fellow moderators. 
+
+* Identify students whose presence in the discussions has a strongly positive impact. These students can be promoted to community TA role and publicly acknowledged. 
+
+* Add helpful items to the FAQ or Course Info page. 
+
+***************************************
+Qualities of good discussion moderators
+***************************************
+
+* Good or great content knowledge: stellar students from previous years often make good moderators. 
+
+* Solid communication skills: the ability to organize positive, consistent, and effective communication with students, other moderators, and course staff. 
+
+* Time: keeping up-to-date with the discussions for a large MOOC requires at least 5 hours per week for reading posts, replying to or editing posts, and communicating with the other moderators and course staff. 
+
+* Enthusiasm: this is the best predictor of moderator excellence! 
+
+******************************************
+Best practices for discussion moderation
+******************************************
+
+* Always maintain a positive attitude. Keeping a positive attitude is crucial to encouraging participation in the discussion community. 
+
+* Encourage discussion between students. Actively thank students who answer the questions of others. 
+
+* Use the course’s FAQ and Course Info pages as resources. Provide links to these pages in your responses when appropriate. Suggest that information be added to these resources when necessary to respond to a common question or fix confusion. 
+
+* Always make it obvious that you have read the student’s question. When posting a response, make sure that you are on topic. Respond in the context of the thread.
+
+* Develop a discussion persona. Try to answer your questions in your own slightly unique way. 
+
+*******************************************
+Guidelines for specific types of posts
+*******************************************
+
+Certain types of posts require more attention from the moderators than others, or may need to be handled in a particular way.
+
+============================
+Time sensitive problems 
+============================
+
+* Try to be present on discussion threads when assignment due dates are approaching or new content is being released. The discussions tend to be extra busy at these times. 
+
+* Please alert the course staff about problems that need to be dealt with quickly, such as problems with a graded assignment. Setting up a course email address that is checked frequently is a good way to manage these alerts. 
+
+* Content Questions 
+
+ - Assist with content questions sensitively, but be careful not to post spoilers. Do not ask students to post their solutions!
+
+ - A good guiding question can be better than an answer.
+
+============================
+Redundant posts 
+============================
+
+* When possible, help discourage redundancy by responding to such posts with links to an earlier or higher quality thread that asks the same question. 
+
+* When responding to a post, search for similar posts and respond to the most pertinent thread. Redirect the other posts to the thread with your response and then close the redundant threads. 
+
+========================================================
+Off topic, inappropriate, or offensive posts 
+========================================================
+
+* Don’t simply delete them; instead, edit and explain why they were edited. Inappropriate posts include spoilers, solutions, and information on how to pirate educational materials. 
+
+* Check links that students post. If offensive sites and materials are found, they need to be edited quickly. 
+
+============================
+Bugs or errors 
+============================
+
+* Check if there is in fact an error. 
+
+ - If not, suggest to the students that they check their work. 
+
+ - If so, contact course staff, and notify the thread that the error has been reported.
+
+* Use language that does not assign blame or discourage users from the platform. 
+
+ You might say: “Thanks for letting us know about that issue. We are working with edX to get it fixed as quickly as possible.” 
+
+============================
+Feature requests 
+============================
+
+* Keep an organized collection of feature requests cultivated by the course team. That list can subsequently be shared with an edX product manager, who will log those requests internally. 
+
+* Reply to the post to let the person know that their request was heard, without promising that the feature will be implemented. 
+
+ You might say: “Thanks for your suggestion. I’ve logged it for review by edX staff, who will prioritize feature requests on the development roadmap.” 
+
+* Search the discussions for other similar requests, and respond to and close those as well.

docs/en_us/course_authors/source/index.rst

@@ -32,11 +32,12 @@ Contents
    accessibility
    checking_student_progress
    ora_students
+   discussions
+   discussion_guidance_moderators
    glossary
 
 
 
-
 Appendices
 ==========