version 1.47, 2014/04/30 17:17:25
|
version 1.51, 2015/05/30 16:14:38
|
Line 152 sub run() {
|
Line 152 sub run() {
|
The <credits> tag need only be used if the credits earned by the students will |
The <credits> tag need only be used if the credits earned by the students will |
be different from the default for the course. The course default is set when the |
be different from the default for the course. The course default is set when the |
course is created and can be modifed by a Domain Coordinator via "View or |
course is created and can be modifed by a Domain Coordinator via "View or |
modify a course or community" on the DC's Main Menu screen. |
modify a course or community" on the DC's Main Menu screen. |
|
|
A value for <inststatus> should be the institutional status used for students, |
A value for <inststatus> should be the institutional status used for students, |
and should be one of the types defined in inst_usertypes(). If no status |
and should be one of the types defined in the "Institutional user types" |
types are defined for the domain this tag can be omitted. If Autoupdate.pl |
section in the domain config screen for: |
is enabled in your domain, updates to the institutional status set here |
"Default authentication/language/timezone/portal/types" |
will be updated by Autoupdate.pl, should changes occur. |
|
|
If no status types are defined for the domain this tag can be omitted. |
|
If Autoupdate.pl is enabled in your domain, updates to the institutional |
|
status set here will be updated by Autoupdate.pl, should changes occur. |
|
|
If there were 10 students in fs03nop590001, 5 students in fs03nop59o601, |
If there were 10 students in fs03nop590001, 5 students in fs03nop59o601, |
8 students in fs03nop590602, and 2 students in fs03ost580002, |
8 students in fs03nop590602, and 2 students in fs03ost580002, |
Line 355 Other scenarios are possible, and the ro
|
Line 358 Other scenarios are possible, and the ro
|
to whatever rules a domain wishes to implement to run validations against |
to whatever rules a domain wishes to implement to run validations against |
given the data passed in to the routine. |
given the data passed in to the routine. |
|
|
validate_crsreq takes six arguments - |
validate_crsreq takes seven arguments - |
(a) the LON-CAPA domain that will contain the course. |
(a) the LON-CAPA domain that will contain the course. |
(b) the username:domain for the course owner. |
(b) the username:domain for the course owner. |
(c) the course type (official, unofficial or community) |
(c) the course type (official, unofficial or community) |
Line 469 sub crsreq_updates {
|
Line 472 sub crsreq_updates {
|
mt => '', |
mt => '', |
args => [], |
args => [], |
}]; |
}]; |
|
$outgoing->{'createdactions'} = { |
|
environment => {}, |
|
}; |
|
# environment can contain key=>value for |
|
# items to set in the course environment. |
|
# These would be items which are NOT included |
|
# in the items set via options in the course |
|
# request form. Currently self-enrollment |
|
# settings are the only ones allowed, i.e., |
|
# internal.selfenroll_types internal.selfenroll_registered |
|
# internal.selfenroll_section internal.selfenroll_start_access |
|
# internal.selfenroll_end_access internal.selfenroll_limit |
|
# internal.selfenroll_cap internal.selfenroll_approval |
|
# internal.selfenroll_notifylist |
} elsif ($action eq 'queued') { |
} elsif ($action eq 'queued') { |
$outgoing->{'queuedmsg'} = [{ |
$outgoing->{'queuedmsg'} = [{ |
mt => '', |
mt => '', |
Line 880 sub get_userinfo {
|
Line 897 sub get_userinfo {
|
|
|
=item inst_usertypes() |
=item inst_usertypes() |
|
|
|
Starting with LON-CAPA 2.11.0 use of this subroutine |
|
is deprecated. The domain configuration web GUI |
|
accessible to Domain Coordinators will be used to |
|
manage institutional types. If you have previously |
|
customized this routine, then values set there will |
|
be used when displaying the "Institutional user types" |
|
section in the domain config screen for: |
|
"Default authentication/language/timezone/portal/types". |
|
|
|
Once you have visited that screen and saved the settings, |
|
configuration thereafter will be via the web GUI of |
|
values stored in the domain's configuration.db file on |
|
the primary library server in the domain, and values in |
|
inst_usertypes() will no longer be consulted. |
|
|
Incoming data: three arguments |
Incoming data: three arguments |
(a) $dom - domain |
(a) $dom - domain |
(b) $usertypes - reference to hash which will contain |
(b) $usertypes - reference to hash which will contain |