File:  [LON-CAPA] / loncom / html / adm / help / tex / Domain_Configuration_Auto_Enrollment.tex
Revision 1.2: download - view: text, annotated - select for diffs
Tue Jul 29 18:33:15 2008 UTC (15 years, 11 months ago) by raeburn
Branches: MAIN
CVS tags: version_2_9_X, version_2_9_99_0, version_2_9_1, version_2_9_0, version_2_8_X, version_2_8_99_1, version_2_8_99_0, version_2_8_2, version_2_8_1, version_2_8_0, version_2_7_X, version_2_7_99_1, version_2_7_99_0, version_2_7_1, version_2_7_0, version_2_6_99_1, bz6209-base, bz6209, bz5969, bz2851, HEAD, GCI_3, GCI_2, GCI_1, BZ5971-printing-apage, BZ5434-fox
- Fix xome links.

    1: \label{Domain_Configuration_Auto_Enrollment}
    2: If your institution can provide access to roster information for courses
    3: using LON-CAPA then your domain can offer automated enrollment once
    4: localenroll.pm has been customized on each of the library servers
    5: in your domain which serves as a home server for one or more courses.
    6: The required customization is the creation of connections to rosters
    7: for institutional course sections providing enrollment to each LON-CAPA
    8: course. These connections can involve queries of database tables,
    9: in real time, or can involve retrieval from a data source which is
   10: only updated periodically.
   11: 
   12: There are two configuration options: 
   13: 
   14: \begin{itemize}
   15: \item Set auto-enrollment as active or inactive in the domain. 
   16: \item Set the username:domain used in the notification messages sent when
   17: changes in enrollment occur as a result of auto-enrollment updates.
   18: By setting these to a specific user (you might create one for this
   19: purpose), you can view all auto-enrollment change messages for the
   20: entire domain by viewing the contents of the sent messages folder for that user.
   21: \end{itemize}
   22: Auto-enrollment settings for each course consist of items set by a
   23: Domain Coordinator within the \char`\"{}Modify Course\char`\"{} area,
   24: and those items set in a course context from the 
   25: \char`\"{}\underbar{Automated Enrollment Manager}\char`\"{} 
   26: link in the \char`\"{}Manage Users\char`\"{}
   27: menu. This link is only displayed if auto-enrollment has been set
   28: to be active in the domain.
   29: 
   30: The items which must be set by a Domain Coordinator include: 
   31: 
   32: \begin{itemize}
   33: \item institutional code (used in mapping institutional rosters to LON-CAPA
   34: courses)
   35: \item default authentication
   36: \item course owner
   37: \end{itemize}
   38: Your institution may have policies in place to control who may have
   39: access to student information contained within course rosters. In
   40: such cases, assignment of an appropriate course owner in LON-CAPA
   41: may facilitate access to institutional rosters. When a course is first
   42: created the initial Course Coordinator chosen will be identified as
   43: the course owner. If, instead a course is created using an uploaded
   44: XML course description file, the XML file will include tags to define
   45: the username and domain of the course owner.
   46: 
   47: Settings which control auto-enrollment which are modifiable by a Course
   48: Coordinator are described in the \ref{Course_Automated_Enrollment} help page.
   49: 
   50: The auto-enrollment process will update user information (name, e-mail
   51: address, studentID etc.) for any student who is being added to the
   52: course, but will not change it in other case (i.e., drops, section
   53: switches) should there be a difference between the values in the institutional
   54: roster and the values in the LON-CAPA classlist. To change user information
   55: for students already in the course, the Auto-update process must be run
   56: (see below).
   57: 
   58: Warnings will be written to the Auto-enrollment log file found in
   59: /home/httpd/perl/logs if a possible username change is detected. Although
   60: the username is the unique identifier in LON-CAPA, the studentID operates
   61: as an additional, mostly unique identifier. The same studentID may
   62: not be assigned to more than one user - if an existing studentID is
   63: assigned to adifferent user, the change will not occur, unless forced
   64: (there's a checkbox for that). A blank studentID can be assigned,
   65: and in this case multiple users can share the same studentID. StudentIDs
   66: are used for LON-CAPA grading of scantron sheets, and are also used
   67: to detect changes in username by the auto-enrollment and auto-update
   68: processes.
   69: 
   70: At present LON-CAPA does not support username changes, although this
   71: functionality will be supported in the future. In the meantime, what
   72: you must do for users who switch username mid-semester (assuming institutional
   73: authentication will no longer authenticate the user's old username)
   74: is to convert the authentication type in LON-CAPA for the user to
   75: \char`\"{}internal\char`\"{}, set an initial password, make sure that
   76: permanent e-mail is set for the user, then e-mail the user the initial
   77: password, and ask them to use the \char`\"{}\underbar{Forgot password?}\char`\"{}
   78: link on the log-in page to change the password to something secure.

FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>