[BACK]Return to localenroll.pm CVS log [TXT] [DIR] Up to [LON-CAPA] / loncom / enrollment

Diff for /loncom/enrollment/localenroll.pm between versions 1.46 and 1.52

version 1.46, 2014/04/16 14:40:11 version 1.52, 2015/05/30 18:01:12
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 366  validate_crsreq takes six arguments - Line 369  validate_crsreq takes six arguments -
  (f) a comma-separated list of institutional sections included in   (f) a comma-separated list of institutional sections included in
      the course request (only applicable to official courses).       the course request (only applicable to official courses).
  (g) an optional reference to a hash of custom form data.   (g) an optional reference to a hash of custom form data.
      The custom form data will come from crsreq_updates().       The custom form data will come from crsreq_updates(), with one
        additional item: $custominfo->{'_LC_clonefrom'}, provided internally
        (the courseID of the LON-CAPA course being cloned).
   
 A valid courserequest is confirmed by returning 'process'.  A valid courserequest is confirmed by returning 'process'.
 The following can be returned: process, rejected, pending, approval or   The following can be returned: process, rejected, pending, approval or 
 error (with error condition - no :), followed by a : and then an optional message.   error (with error condition - no :), followed by a : and then an optional message. 
   
 (a) process  - the requestor is the recorded instructor - create the course  (a) process  - the requestor is the recorded instructor - create the course
   
 (b) rejected - the requestor should never be requesting this course, reject the  (b) rejected - the requestor should never be requesting this course, reject the
     request permanently      request permanently
   
 (c) pending - the requestor is not the recorded instructor, but could  (c) pending - the requestor is not the recorded instructor, but could
     become so after administrative action at the institution. Put the      become so after administrative action at the institution. Put the
     request in a queue and, if an official course, check       request in a queue and, if an official course, check 
     localenroll:validate_instcode() periodically until the status changes to       localenroll:validate_instcode() periodically until the status changes to 
     "valid".      "valid".
   
 (d) approval - the request will be held pending review by a Domain Coordinator.  (d) approval - the request will be held pending review by a Domain Coordinator.
   
 (e) error (followed by the error condition).  (e) error (followed by the error condition).
   
 =cut  =cut
Line 441  sub crsreq_checks { Line 450  sub crsreq_checks {
     return 'ok';      return 'ok';
 }  }
   
   =pod
   
   =item crsreq_updates()
   
   This is used to customize the LON-CAPA course request process.
   There are two hash references: $incoming, and $outgoing; $incoming can
   contain additional information collected from the requester, whereas $outgoing
   can contain custom items to send back to lonrequestcourse.pm, which creates the
   HTML displayed to the user during a course request.
   
   Different key-value pairs may be returned to lonrequestcourse.pm in the $outgoing
   hashref depending on the current action.  The available actions are:
   review, prevalidate, process, created and queued.
   
   One scenario would be to return HTML markup in: $outgoing->{'reviewweb'},
   i.e., where the action is 'review', to prompt the user to provide additional
   information as part of the course request, at the request review stage, 
   (i.e,, the page which contains the button used to submit a completed course request).
   
   The HTML could contain form elements (e.g., radio buttons etc.). The value(s)
   selected by the requester in those form elements will be available in the incoming
   hashref, for a subsequent action, if the corresponding keys have been included
   in $outgoing->{'formitems'}, i.e., $outgoing will be hash of a hash.  If a
   particular form item will the single valued, the value set for the key in the 
   inner hash in $outgoing should be 1, otherwise, if it will be multi-valued,
   the value should be multiple.
   
   The $outgoing hashref can contain a 'formitems' key for both the prevalidate
   and process actions, as calls to localenroll::crsreq_update() can originate
   in lonrequestcourse::process_request() for both of those actions.
   
   The retrieved form values are passed to localenroll::validate_crsreq() as the
   optional seventh arg (a hashref) -- $custominfo.
   
   =cut
   
 sub crsreq_updates {  sub crsreq_updates {
     my ($cdom,$cnum,$crstype,$action,$ownername,$ownerdomain,$fullname,$title,      my ($cdom,$cnum,$crstype,$action,$ownername,$ownerdomain,$fullname,$title,
         $code,$incoming,$outgoing) = @_;          $code,$accessstart,$accessend,$incoming,$outgoing) = @_;
     unless (ref($outgoing) eq 'HASH') {      unless (ref($outgoing) eq 'HASH') {
         return 'fail';          return 'fail';
     }      }
Line 469  sub crsreq_updates { Line 514  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 939  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 
Removed from v.1.46  
changed lines
  Added in v.1.52

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