Return to Domain_Configuration_Auto_Enrollment.tex CVS log

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

- Help files for Domain configuration (new file names better for online manual).

    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 \char`\"{}\underbar{Automated
   25: Enrollment Manager}\char`\"{} link in the \char`\"{}Manage Users\char`\"{}
   26: menu. This link is only displayed if auto-enrollment has been set
   27: to be active in the domain.
   28: 
   29: The items which must be set by a Domain Coordinator include: 
   30: 
   31: \begin{itemize}
   32: \item institutional code (used in mapping institutional rosters to LON-CAPA
   33: courses)
   34: \item default authentication
   35: \item course owner
   36: \end{itemize}
   37: Your institution may have policies in place to control who may have
   38: access to student information contained within course rosters. In
   39: such cases, assignment of an appropriate course owner in LON-CAPA
   40: may facilitate access to institutional rosters. When a course is first
   41: created the initial Course Coordinator chosen will be identified as
   42: the course owner. If, instead a course is created using an uploaded
   43: XML course description file, the XML file will include tags to define
   44: the username and domain of the course owner.
   45: 
   46: Settings which control auto-enrollment which are modifiable by a Course
   47: Coordinator are described in the \underbar{Automated Enrollment help page}.
   48: 
   49: The auto-enrollment process will update user information (name, e-mail
   50: address, studentID etc.) for any student who is being added to the
   51: course, but will not change it in other case (i.e., drops, section
   52: switches) should there be a difference between the values in the institutional
   53: roster and the values in the LON-CAPA classlist. To change user information
   54: for students already in the course, the Auto-update process must be run
   55: (see below).
   56: 
   57: Warnings will be written to the Auto-enrollment log file found in
   58: /home/httpd/perl/logs if a possible username change is detected. Although
   59: the username is the unique identifier in LON-CAPA, the studentID operates
   60: as an additional, mostly unique identifier. The same studentID may
   61: not be assigned to more than one user - if an existing studentID is
   62: assigned to adifferent user, the change will not occur, unless forced
   63: (there's a checkbox for that). A blank studentID can be assigned,
   64: and in this case multiple users can share the same studentID. StudentIDs
   65: are used for LON-CAPA grading of scantron sheets, and are also used
   66: to detect changes in username by the auto-enrollment and auto-update
   67: processes.
   68: 
   69: At present LON-CAPA does not support username changes, although this
   70: functionality will be supported in the future. In the meantime, what
   71: you must do for users who switch username mid-semester (assuming institutional
   72: authentication will no longer authenticate the user's old username)
   73: is to convert the authentication type in LON-CAPA for the user to
   74: \char`\"{}internal\char`\"{}, set an initial password, make sure that
   75: permanent e-mail is set for the user, then e-mail the user the initial
   76: password, and ask them to use the \char`\"{}\underbar{Forgot password?}\char`\"{}
   77: link on the log-in page to change the password to something secure.