Return to Create_Course.tex CVS log

Up to [LON-CAPA] / loncom / html / adm / help / tex

Annotation of loncom/html/adm/help/tex/Create_Course.tex, revision 1.3

1.1       www         1: \label{Create_Course}
1.2       raeburn     2: The ``Course and Community Creation'' menu provides access to a number of utilities
                      3: which Domain Coordinators can use to either manage the process of course creation.  An individual course or community can be created interactively by completing a web form which offers several choices for generating the new course or community: 
1.1       www         4: 
                      5: \begin{itemize}
1.2       raeburn     6: \item Username: set the username of the owner, who will also receive a coordinator role.
1.1       www         7: \item Course Title: This is the name under which the course will appear on the
1.3     ! bisitz      8: Roles screen.
        !             9: \item Course Home Server: This is the server where the course will be housed.
1.1       www        10: \item Course ID: This is an optional parameter to internally label the course. 
                     11: Stored in the course environment.
1.2       raeburn    12: \item Course Code: This is the institutional code used to identify the course according to the naming scheme adopted by your institution for ``official'' courses.
                     13: \item Map: This the top level sequence file in the course. If left blank, a 
                     14: standard course will be created containing the first resource item (see below).
1.1       www        15: \item NOT Standard Course: It this box is checked, the Map above becomes the
                     16: top-level map for the course, and
                     17: the main course sequence cannot be edited in DOCS. For standard courses, 
                     18: the top-level map is a course-specific ``uploaded'' document, and points to 
                     19: the above map.
                     20: \item First Resource: This is the first resource which comes up after somebody
                     21: selects a role in this course (standard courses only).
1.2       raeburn    22: \item Clone an existing course: An alternative to creation of a new course with
                     23:  a single item or a non-standard course with a sequence file as the top-level map is to copy the contents of an existing course into the new course.
1.3     ! bisitz     24: \item Open all assessments: Sets the course-level open date for all assignments 
1.1       www        25: to ``now''. Circumvents the ``not open to be viewed'' problem.
                     26: \item Set policy/content feedback: Sets the recipient address for these types
                     27: of feedback messages to the course coordinator.
                     28: \item Disable student resource discussion: Disables the ``bottom-of-the-page'' discussions.
                     29: \end{itemize}
1.2       raeburn    30: 
1.3     ! bisitz     31: Two types of course ``containers'' are currently available in LON-CAPA: 
1.2       raeburn    32: \begin{itemize}
                     33: \item Course 
                     34: \item Community 
                     35: \end{itemize}
                     36: The key difference between the two is that the Coordinator of a Course may import any published resource into the course as long as he/she has access rights for it, whereas import into a Community is restricted to just those resources for which the Coordinator is the author, or a co-author.  In addition, the names of standard roles in the two containers have different names: (Course Coordinator vs. Coordinator, Instructor vs. Leader, Teaching Assistant vs. Assistant Leader, Student vs. Member).
                     37: 
                     38: In addition to using a web form to create courses one-at-a-time, Domain Coordinators can upload an XML file containing descriptions of courses (see: \ref{Batch_Creation} Batch Creation) to create multiple courses.  If the ability to request courses has been enabled, and certain course types have been set to require Domain Coordinator approval, then the ``Approve or reject requests'' item can be used to display a list of requests requiring approval.  These may be approved or rejected.  If a conduit has been established to an institutional data source which provides information about instructors of record, then the ``View pending official course requests'' may contain a list of requests for official courses, held pending validation. Validation can be attempted; if it still fails it is possible to override this and force creation of the course.
                     39: 
                     40: Lastly, there is access to a utility which can be used to display course and community creation history.