Return to Domain_Configuration_Scantron_Format.tex CVS log

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

Annotation of loncom/html/adm/help/tex/Domain_Configuration_Scantron_Format.tex, revision 1.8

1.1       raeburn     1: \label{Domain_Configuration_Scantron_Format}
1.8     ! raeburn     2: 
        !             3: \textbf{Bubblesheet format file}
        !             4: 
1.4       raeburn     5: Where bubblesheet exams are used in a course, the format of data in the
                      6: file generated from the processing of bubbled-in bubblesheets may
1.1       raeburn     7: vary between institutions. The format definitions available when performing
1.4       raeburn     8: bubblesheet grading in LON-CAPA were originally listed in the scantronformat.tab
1.1       raeburn     9: file, stored in /home/httpd/lonTabs, which might have been modified
                     10: locally on each server. 
                     11: 
1.4       raeburn    12: Starting with LON-CAPA 2.7, bubblesheet format information is read from
1.1       raeburn    13: either a custom.tab file, or a default.tab file both of which belong
                     14: to the special domain configuration user (\$dom-domainconfig, where
                     15: \$dom is the name of the domain) and which are automatically published
                     16: into resource space. 
                     17: 
                     18: For LON-CAPA installations older than 2.7, when the primary library
                     19: server for the domain has been updated, a Domain Coordinator should
1.7       raeburn    20: display the ``Bubblesheet format file'' configuration
                     21: page via ``Domain Configuration''. The first time
1.1       raeburn    22: this page is displayed, a default.tab (a copy of the standard LON-CAPA
                     23: scantronformat.tab file), and a custom.tab (if the scantronform.tab
                     24: file currently on the server differs from the standard file) will
1.4       raeburn    25: be copied and published. Thereafter any changes to bubblesheet format
                     26: files to be used for grading bubblesheet exams in courses from the domain
1.1       raeburn    27: will be made via the Domain Configuration menu. Any scantronform.tab
                     28: files in /home/httpd/lonTab directories on servers in the domain will
                     29: no longer be used.
                     30: 
1.7       raeburn    31: The settings available via ``Bubblesheet format file'' 
1.1       raeburn    32: support upload of a new custom file, or deletion of an existing custom
                     33: file (in which case grading will default to use of the default.tab
1.4       raeburn    34: file). An uploaded bubblesheet format file contains one or more lines
1.1       raeburn    35: of colon-separated values for the parameters in the following order:
                     36: 
1.5       raeburn    37: \begin{quote}
                     38: {\scriptsize name:description:CODEtype:CODEstart:CODElength:IDstart:IDlength:Qstart:Qlength:Qoff:Qon:PaperID:PaperIDlength:}
                     39: {\scriptsize FirstName:FirstNamelength:LastName:LastNamelength} 
                     40: \end{quote}
1.1       raeburn    41: 
1.6       bisitz     42: \begin{enumerate}
                     43: \item \emph{name} is the internal identifier used within LON-CAPA
                     44: \item \emph{description} is the text displayed for each option in
1.3       raeburn    45: the {}``Format of data file'' dropdown in the Bubblesheet grading
1.4       raeburn    46: screen.  The user will choose the appropriate format for the bubblesheet 
                     47: file currently being used for bubblesheet grading.
1.6       bisitz     48: \item \emph{CODEtype} can be either 'none' 'letter' 'number' 
                     49: \item \emph{CODEstart}: (only matters if a CODE exists) column in the line where the CODE starts
                     50: \item \emph{CODElength}: length of the CODE
                     51: \item \emph{IDstart}: column where the student ID starts
                     52: \item \emph{IDlength}: length of the student ID
                     53: \item \emph{Qstart}: column where the information from the bubbled 'questions' start  
                     54: \item \emph{Qlength} is the number of characters in the raw data used to record the student's bubbled answer for each row on the bubblesheet.
                     55: 
                     56: If the raw data indicate bubble position by a letter or a number (e.g., A = first bubble or 1 = first bubble etc.) then the number of characters would be 1 (assuming 10 bubbles or less for the number case).  If however, bubble position is indicated by position of the Qon (bubbled) character, then each bubble row might have 10 characters (one for each of the 10 possible positions with Qon at the position bubbled and Qoff elsewhere, (e.g. if Qon = 1, Qoff = .  the portion of a student's record for a single bubble row might be:  ...1......  indicating position 4 was the one bubbled.
                     57: \item \emph{Qoff} is the character used to indicate an unfilled bubble, this is commonly a single blank space.
                     58: \item \emph{Qon} is the character used in the raw data generated by the bubblesheet scanner to indicate a filled-in bubble.
1.1       raeburn    59: 
1.6       bisitz     60: \emph{Qon} can be either:
1.1       raeburn    61: \begin{itemize}
                     62: \item the symbol that says a bubble has been selected, or
                     63: \item 'letter' (for when the selected letter appears), or 
                     64: \item 'number' for when a number indicating the selected letter appears 
                     65: \end{itemize}
1.6       bisitz     66: \item \emph{PaperID}: if the scanning process generates a unique number for each sheet scanned the column that this ID number starts in
                     67: \item \emph{PaperIDlength}: number of columns that comprise the unique ID number for the sheet of paper
                     68: \item \emph{FirstName}: column that the first name starts in
                     69: \item \emph{FirstNamelength}: number of columns that the first name spans
                     70: \item \emph{LastName}: column that the last name starts in
                     71: \item \emph{LastNamelength}: number of columns that the last name spans
                     72: \end{enumerate}
1.1       raeburn    73: As an example, below are four different format lines: the first two
                     74: were used at MSU prior to 2006; the last two have been used since
                     75: then.
                     76: 
                     77: \begin{itemize}
                     78: \item msunocode:MSU without any CODE:none:0:0:57:9:77:10: :1:5:5:51:1:41:10 
                     79: \item msucode:MSU with CODE in separate location:letter:69:6:57:9:77:10:
                     80: :1:5:5:51:1:41:10 
                     81: \item msucodelet:MSU with CODE in separate location (letter format):-1:69:6:57:9:77:1:
                     82: :letter:5:5:51:1:41:10 
                     83: \item msucodenum:MSU with CODE in separate location (number format):-1:69:6:57:9:77:1:
                     84: :number:5:5:51:1:41:10
                     85: \end{itemize}
1.8     ! raeburn    86: 
        !            87: \textbf{Bubblesheet data upload formats}
        !            88: 
        !            89: Starting with LON-CAPA 2.11.3, bubblesheet data generated from the processing of bubbled-in bubblesheets to be uploaded to a course may either be column data (i.e., in a .dat file) or comma separated value data (in a .csv file). Internally in LON-CAPA all bubblesheet data will be stored in .dat format, with start and end column numbers for different pieces of information defined by one of the entries in custom.tab (if in use) or default.tab.
        !            90: 
        !            91: If the checkbox for csv data is checked then a CSV Column Mapping table will be displayed, which will be used to designate the column location in the CSV data (with 1 being the leftmost column) for each of:
        !            92: 
        !            93: \begin{itemize}
        !            94: \item Paper ID
        !            95: \item Last Name
        !            96: \item First Name
        !            97: \item Student ID
        !            98: \item Section
        !            99: \item CODE
        !           100: \item First Question Response
        !           101: \end{itemize}
        !           102: 
        !           103: Responses to additional question(s) should occur in column(s) immediately to the right of the column for the first question.  Besides mapping columns to contents, there are also three Yes/No options: 
        !           104: 
        !           105: \begin{itemize}
        !           106: \item Remove first line in file?
        !           107: \item Prepend 0s to PaperID?
        !           108: \item Remove leading spaces?
        !           109: \end{itemize}
        !           110: 
        !           111: If the original CSV data includes an initial row with column titles, indicate removal of the first line.  If the data in each column, is padded with spaces, indicate removal of leading spaces. Note: this will not remove spaces from data in any columns which are designated to contain question responses.
        !           112: 
        !           113: Note: the expectation is that all bubblesheet data in CSV format used in a domain will have the same arrangement of columns, so that  a ``CODE'' column will be present at the same location in data for both CODEd (i.e., anonymous) exams, and ``named'' exams, with the only difference being that the tables cells will be empty for that column in the case of bubblesheet data from students in a ``named'' exam.      
        !           114: 
        !           115: If both .dat and .csv formats are specified for the domain, then when either a user assigned a Bubblesheet Scanning Operator role in the domain or a Course Coordinator uploads bubblesheet data to a course, the uploader will specify the data format: Plain Text or CSV.  If CSV is chosen, and there is more than one bubblesheet type in the domain's default.tab (or custom.tab), then the uploader will also need to specify the bubblesheet type. 
        !           116: