Annotation of loncom/html/adm/help/tex/Domain_Configuration_Auto_Enrollment.tex, revision 1.5
1.1 raeburn 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:
1.4 raeburn 12: There are three configuration options:
1.1 raeburn 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.
1.4 raeburn 21: \item Automatically assign co-ownership
22: If this is set to yes, then whenever a Course Coordinator role is assigned
23: in a course with an institutional code, a check is made to see if the user
24: to whom the role is being assigned is officially listed as instructional
25: personnel. If so, and the user is not the course owner, then the user will
26: be identified as a co-owner. Co-owners are listed in the course catalog, and
27: also in the pop-up window displayed when picking a course (e.g., for cloning,
1.5 ! raeburn 28: ). For the validation to work the validate\_instcode() routine in localenroll.pm
1.4 raeburn 29: must have been customized to include the username supplied as the third argument
30: in the query made to the institutional data source which ties instructors to
31: institutional codes.
1.1 raeburn 32: \end{itemize}
1.4 raeburn 33:
1.1 raeburn 34: Auto-enrollment settings for each course consist of items set by a
35: Domain Coordinator within the \char`\"{}Modify Course\char`\"{} area,
1.2 raeburn 36: and those items set in a course context from the
37: \char`\"{}\underbar{Automated Enrollment Manager}\char`\"{}
38: link in the \char`\"{}Manage Users\char`\"{}
1.1 raeburn 39: menu. This link is only displayed if auto-enrollment has been set
40: to be active in the domain.
41:
42: The items which must be set by a Domain Coordinator include:
43:
44: \begin{itemize}
45: \item institutional code (used in mapping institutional rosters to LON-CAPA
46: courses)
47: \item default authentication
48: \item course owner
49: \end{itemize}
50: Your institution may have policies in place to control who may have
51: access to student information contained within course rosters. In
52: such cases, assignment of an appropriate course owner in LON-CAPA
53: may facilitate access to institutional rosters. When a course is first
54: created the initial Course Coordinator chosen will be identified as
55: the course owner. If, instead a course is created using an uploaded
56: XML course description file, the XML file will include tags to define
57: the username and domain of the course owner.
58:
59: Settings which control auto-enrollment which are modifiable by a Course
1.2 raeburn 60: Coordinator are described in the \ref{Course_Automated_Enrollment} help page.
1.1 raeburn 61:
62: The auto-enrollment process will update user information (name, e-mail
63: address, studentID etc.) for any student who is being added to the
64: course, but will not change it in other case (i.e., drops, section
65: switches) should there be a difference between the values in the institutional
66: roster and the values in the LON-CAPA classlist. To change user information
67: for students already in the course, the Auto-update process must be run
68: (see below).
69:
70: Warnings will be written to the Auto-enrollment log file found in
71: /home/httpd/perl/logs if a possible username change is detected. Although
72: the username is the unique identifier in LON-CAPA, the studentID operates
73: as an additional, mostly unique identifier. The same studentID may
74: not be assigned to more than one user - if an existing studentID is
75: assigned to adifferent user, the change will not occur, unless forced
76: (there's a checkbox for that). A blank studentID can be assigned,
77: and in this case multiple users can share the same studentID. StudentIDs
1.3 raeburn 78: are used for LON-CAPA grading of bubblesheets, and are also used
1.1 raeburn 79: to detect changes in username by the auto-enrollment and auto-update
80: processes.
81:
82: At present LON-CAPA does not support username changes, although this
83: functionality will be supported in the future. In the meantime, what
84: you must do for users who switch username mid-semester (assuming institutional
85: authentication will no longer authenticate the user's old username)
86: is to convert the authentication type in LON-CAPA for the user to
87: \char`\"{}internal\char`\"{}, set an initial password, make sure that
88: permanent e-mail is set for the user, then e-mail the user the initial
89: password, and ask them to use the \char`\"{}\underbar{Forgot password?}\char`\"{}
90: link on the log-in page to change the password to something secure.
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>