[BACK]Return to ForceIDChange.tex CVS log [TXT] [DIR] Up to [LON-CAPA] / loncom / html / adm / help / tex
File:  [LON-CAPA] / loncom / html / adm / help / tex / ForceIDChange.tex
Revision 1.2: download - view: text, annotated - select for diffs
Wed Feb 19 18:05:36 2014 UTC (10 years, 5 months ago) by bisitz
Branches: MAIN
CVS tags: version_2_12_X, version_2_11_X, version_2_11_5_msu, version_2_11_5, version_2_11_4_uiuc, version_2_11_4_msu, version_2_11_4, version_2_11_3_uiuc, version_2_11_3_msu, version_2_11_3, version_2_11_2_uiuc, version_2_11_2_msu, version_2_11_2_educog, version_2_11_2, version_2_11_1, version_2_11_0_RC3, version_2_11_0, HEAD
- Content:
    - Fix typo
    - Split longish sentence into two
- Source file:
    - Remove double and trailing blanks
    - Line wrapping

    1: \label{ForceIDChange}
    2: Although the username is the principal unique identifier for a user in LON-CAPA, the student/employee ID
    3: is a secondary identifier, which needs to be defined (and unique) for certain applications.
    4: 
    5: The default is not to allow the student/employee ID for an existing user to be changed when
    6: modifying a user's information in course, author or domain context.
    7: 
    8: This default can be overridden by checking the ``Force change of existing ID'' checkbox. If that is
    9: done the old ID will be replaced with the new ID. (Note: the new ID can not be blank; i.e., once an ID
   10: has been set for a user, it can be changed to a different ID, but not set to be null).
   11: 
   12: A side effect of updating a student/employee ID is that the database file used for the quick
   13: look-up of username for a specified student/employee ID will be updated. This can potentially impact 
   14: bubblesheet grading, if there is a possibility that student/employee IDs are not unique.
   15: 
   16: However, there is no requirement to set a student/employee ID for a user, and you will not encounter
   17: issues doing that unless you attempt bubblesheet grading or uploading scores from a csv file 
   18: containing IDs and points as column data. If either of those actions are likely to occur in courses
   19: in your domain you should attempt to ensure that student/employee IDs are unique.
   20: 
   21: Your domain may have been configured to automatically update student/employee IDs from an institutional
   22: data source. Similarly, IDs may be retrieved (and set) automatically when creating a new user, if the
   23: username is for an institutional user, and your domain has been configured to support that.
   24: 
   25: Individual courses contain their own database files of class rosters, which include a copy of each
   26: student's ID. If a student/employee ID is changed by a Domain Coordinator, there is an option to
   27: propagate that change to the individual classlist database files for courses in which the student has
   28: a role that is currently active, or one that will become active in the future.
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>