doc/gutshtml/SessionTw1.html - view

File: [LON-CAPA] / doc / gutshtml / SessionTw1.html
Revision 1.2: download - view: text, annotated - select for diffs
Tue Jul 22 14:47:00 2003 UTC (21 years, 5 months ago) by bowersj2
Branches: MAIN
CVS tags: version_2_9_X, version_2_9_99_0, version_2_9_1, version_2_9_0, version_2_8_X, version_2_8_99_1, version_2_8_99_0, version_2_8_2, version_2_8_1, version_2_8_0, version_2_7_X, version_2_7_99_1, version_2_7_99_0, version_2_7_1, version_2_7_0, version_2_6_X, version_2_6_99_1, version_2_6_99_0, version_2_6_3, version_2_6_2, version_2_6_1, version_2_6_0, version_2_5_X, version_2_5_99_1, version_2_5_99_0, version_2_5_2, version_2_5_1, version_2_5_0, version_2_4_X, version_2_4_99_0, version_2_4_2, version_2_4_1, version_2_4_0, version_2_3_X, version_2_3_99_0, version_2_3_2, version_2_3_1, version_2_3_0, version_2_2_X, version_2_2_99_1, version_2_2_99_0, version_2_2_2, version_2_2_1, version_2_2_0, version_2_1_X, version_2_1_99_3, version_2_1_99_2, version_2_1_99_1, version_2_1_99_0, version_2_1_3, version_2_1_2, version_2_1_1, version_2_1_0, 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_RC2, version_2_11_0_RC1, version_2_11_0, version_2_10_X, version_2_10_1, version_2_10_0_RC2, version_2_10_0_RC1, version_2_10_0, version_2_0_X, version_2_0_99_1, version_2_0_2, version_2_0_1, version_2_0_0, version_1_99_3, version_1_99_2, version_1_99_1_tmcc, version_1_99_1, version_1_99_0_tmcc, version_1_99_0, version_1_3_X, version_1_3_3, version_1_3_2, version_1_3_1, version_1_3_0, version_1_2_X, version_1_2_99_1, version_1_2_99_0, version_1_2_1, version_1_2_0, version_1_1_X, version_1_1_99_5, version_1_1_99_4, version_1_1_99_3, version_1_1_99_2, version_1_1_99_1, version_1_1_99_0, version_1_1_3, version_1_1_2, version_1_1_1, version_1_1_0, version_1_0_99_3, version_1_0_99_2, version_1_0_99_1, version_1_0_99, version_1_0_3, version_1_0_2, version_1_0_1, version_1_0_0, version_0_99_5, version_0_99_4, loncapaMITrelate_1, language_hyphenation_merge, language_hyphenation, bz6209-base, bz6209, HEAD, GCI_3, GCI_2, GCI_1, BZ4492-merge, BZ4492-feature_horizontal_radioresponse, BZ4492-feature_Support_horizontal_radioresponse, BZ4492-Support_horizontal_radioresponse

Convert GUTs HTML to PROPER line endings.

<html> <head> <meta name=Title content="Session Two: Spreadsheet and Messaging (Matthew)"> <meta http-equiv=Content-Type content="text/html; charset=macintosh"> <link rel=Edit-Time-Data href="Session%20Tw1_files/editdata.mso"> <title>Session Two: Spreadsheet and Messaging (Matthew)</title> <style> </style> </head> <body bgcolor=#FFFFFF link=blue vlink=purple class="Normal" lang=EN-US> <div class=Section1> <h2>Session Two: Spreadsheet and Messaging (Matthew)</h2> <h3><a name="_Toc421867092">Spreadsheets</a></h3> The spreadsheet presents data on student performance on homework problems. Spreadsheets are handled by loncom/interface/lonspreadsheet.pm and are completely web based. A person who has selected a student role will access the spreadsheets using the [GRDS] button. A course coordinator is given access via the [SPRS] button. Students are not able to see data on anyone's performance but their own. Students are also not allowed to save spreadsheets. <h3><a name="_Toc421867093">Spreadsheet Structure and Hierarchy</a></h3> The spreadsheets are laid out in the typical fashion, with some limitations. There can only be 52 columns, addressed [A-Za-z]. There may be any number of rows, but currently there do not exist facilities to add rows other than those automatically generated. There are three levels of spreadsheets, as illustrated in Fig. 2.2.1. <img width=432 height=278 src="Session%20Tw1_files/image003.png" v:shapes="_x0000_i1025"> Fig. 2.1.1 � Spreadsheet Hierarchy The rightmost spreadsheets are the assessment spreadsheets. The middle spreadsheets are the student spreadsheets. The left spreadsheet is the course spreadsheet. <h3><a name="_Toc421867094">Export Rows</a></h3> The hierarchy of spreadsheets described above allows data from the lower level spreadsheets (assessment and student) to be exported up to the higher level spreadsheets (student and course, respectively). Row 0 is the export row. Only the cells A0-Z0 are exported. Cells a0-z0 are not exported and can be used as 'scratch' space for the results exported in A0-Z0. The export rows in the image are shown shaded in figure 2.2.1. Where the exported rows appear in the student and course spreadsheets is indicated by arrows. <h3><a name="_Toc421867095">Assessment Spreadsheet</a></h3> The assessment spreadsheet gives data on the students performance on a specific resource in LON-CAPA (typically a *.problem resource). Parameters such as the due date, the number of tries possible, the number of attempts made, the correctness of the student solution, and any <parameter> tags inserted in the resource will be shown. Fig. 2.2.2 shows an example of an assessment spreadsheet. <img width=432 height=290 src="Session%20Tw1_files/image005.jpg" v:shapes="_x0000_i1026"> Fig. 2.2.2 � Example Spreadsheet on Assessment Level <h3><a name="_Toc421867096">Student Spreadsheet</a></h3> Each assessment spreadsheet exports a row into the student spreadsheet. Fig 2.2.3 shows an example student spreadsheet. The student spreadsheet exports a row to the course spreadsheet. Fig. 2.2.3 shows the next level up spreadsheet with the exported data from this sheet. <img width=431 height=240 src="Session%20Tw1_files/image007.jpg" v:shapes="_x0000_i1027"> Fig. 2.2.3 � Default Spreadsheet on Student Level <h3><a name="_Toc421867097">Course Spreadsheet</a></h3> The course spreadsheet gives a summary of each students performance in the course as a whole. Fig 2.2.4 shows the default course spreadsheet. <img width=432 height=143 src="Session%20Tw1_files/image009.jpg" v:shapes="_x0000_i1028"> Fig. 2.2.4 � Default Spreadsheet on Course Level <h3><a name="_Toc421867098">Spreadsheet definition</a></h3> The default spreadsheets are defined via xml. Fig. 2.2.5 shows a sample definition of a spreadsheet. However, it is possible to work with spreadsheets and never edit the xml for the spreadsheet itself. By modifying the contents of cells via the web interface and saving the results, instructors can create as complicated a spreadsheet as they like. It is now possible for users to upload spreadsheets to the library server, publish them, and set them as the default sheets for their course. <div style='border:solid windowtext .5pt;padding:1.0pt 4.0pt 1.0pt 4.0pt'> [www@zaphod www]$ cat /home/httpd/html/res/adm/includes/default.assesscalc <field col=A row=0>[stores_0_solved]</field> <field col=B row=0>'Tries:'</field> <field col=C row=0>[stores_0_tries]</field> <field col=D row=0>'Timestamp:'</field> <field col=E row=0>[timestamp]</field> <field col=F row=0>'Duedate:'</field> <field col=G row=0>[parameter_0_duedate]</field> <field col=W row=0>'Available Points:'</field> <field col=X row=0>[parameter_0_weight]</field> <field col=Y row=0>'Awarded Points:'</field> <field col=Z row=0>[parameter_0_weight]*[stores_0_awarded]</field> </div> Fig. 2.2.5 � Default Spreadsheet on Assessment Level <h3><a name="_Toc421867099">Template Row</a></h3> The template row of a spreadsheets will make the contents of a given column identical for each row. The contents of the template row are shown verbatim, and not evaluated. Fig 2.2.6 shows the template row in use. <img width=432 height=215 src="Session%20Tw1_files/image011.jpg" v:shapes="_x0000_i1029"> Fig. 2.2.7 � Customized Spreadsheet on Student Level Shows a course-customized student-level spreadsheet with many of these functions, templates and wildcards in action. In the dialog window, &SUM(�d*�) is entered as the expression for cell H0, which will add up all cells in column d. The template row is used to define expressions for columns a, b, c, and d, where for b and d both the �#� wildcard and access to the EXT function is used in order to multiply the respective X and Z cells in each row with 1 or 0 depending on whether the value in G (the duedate) is smaller or larger than the system time (�?� is the standard Perl choice operator). <h3><a name="_Toc421867100">What goes in a cell</a></h3> A cell contains either parameter data (which cannot be changed) or perl code. Additionally, cells can contain references to other cells and these references can be passed as parameters to perl functions. Parameters can be accessed via the cell they are stored in or by the parameter name. <h3><a name="_Toc421867101">Parameter Access</a></h3> Parameters can be accessed by enclosing the parameter name in square brackets. A new feature allows the accessing of parameters by enclosing only enough information to lead to a unique parameter. "[part_0_duedate]" will give the same value as "[duedate]" if there are no other parameters which contain the string "duedate". <h3><a name="_Toc421867102">Addressing other cells</a></h3> Cells are specified by the letter-number combination of their position in the table, for example "A5". There are also wildcards '*' and '#' which are used in ranges and templates, respectively, and symbolic names. Valid ranges are for example "A5..C7" which is the square between cells A5 to C7, as in A5, A6, A7, B5, etc. Also, wildcards can be used, as in "A*" for column A, or "*5" for row 5. For example, &SUM("d*") will add up all cells in column d. The table below gives a brief summary of the range options. *          all rows, all columns B*       all rows in column B *5        all columns in row 5 C5..F25           all cells in the rectangle between C5 and F25 The template row allows the use of "A#", which will result in "A5" in row 5, "A6" in row 6, etc. Spreadsheet Functions Many perl functions are available in the spreadsheet (see "The Safe Environment" below). Additionally, some spreadsheet specific functions have been defined as well. A complete list is available by executing 'perldoc loncapa/loncom/interface/lonspreadsheet.pm' on the command line. An abbreviated table appears in Fig. 2.2.7. <div style='border:solid windowtext .5pt;padding:1.0pt 4.0pt 1.0pt 4.0pt'> &NUM(range) � number of non-empty cells in range &BIN(low, high, range) � number of non-empty cells in range with values between low and high &SUM(range) � sum of the non-empty cells in range &MEAN(range) � mean value of non-empty cells in range &STDDEV(range) � standard deviation of non-empty cells in range &PROD(range) � product of non-empty cells in range &MAX(range) � maximum value of non-empty cell in range &MIN(range) � minimum value of non-empty cells in range &SUMMAX(n ,range) � sum of the maximum n non-empty cells in range &SUMMIN(n, range) � sum of the minimum n non-empty cells in range &EXT(expression) � access to EXT function in lonnet </div> Fig. 2.2.7 � Available Functions in Spreadsheet <h3><a name="_Toc421867103">The Safe Environment</a></h3> The spreadsheet cells are evaluated in a "Safe" environment. The module Safe.pm is included in the standard systemperl RPM put out by the LON-CAPA developers, but is written by Tim Bunce and Malcolm Beattie. If you execute 'perldoc Safe' you can read the documentation for the module. The Safe.pm module allows users to "compile and execute code in restricted compartments". We use this to allow users to implement in their spreadsheets a restricted set of perl functions, variables, and operators. No one using the spreadsheet should ever need access to the basic IO functions of Perl, for example, so these are not made available to the users. Each cell is evaluated within the same safe space, so cells can actually contain function and declarations. There is information the user may need which is not contained in the cells of the spreadsheet. So we poke a hole in the safe space using the Safe::Hole module. This lets us allow access to external information. Obviously this needs to be done with some degree of caution. At the beginning of lonspreadsheet.pm we have the following code: use Safe; use Safe::Hole; The function &initsheet, which is called when a spreadsheet is created or modified, defines the safe space for the execution of spreadsheet code: sub initsheet {     my $safeeval = new Safe(shift);     my $safehole = new Safe::Hole;     $safeeval->permit("entereval");     $safeeval->permit(":base_math");     $safeeval->permit("sort");     $safeeval->deny(":base_io");     $safehole->wrap(\&Apache::lonnet::EXT,$safeeval,'&EXT');     my $code=<<'ENDDEFS'; . functions and variables needed in the safe space are defined here . ENDDEFS     $safeeval->reval($code);     return $safeeval; } <h3><a name="_Toc421867104">Change is coming</a></h3> Currently the spreadsheet is scheduled to undergo major revisions by the end of the summer. The goal of these revisions is to increase the speed and add some requested functionality. We hope to add: *          Improved exporting of the spreadsheet date to client side spreadsheets *          Exporting of spreadsheet xml - allowing users to save spreadsheets from their classes for reuse. *          Additional spreadsheet functions. <h3>  </h3> <h3><a name="_Toc421867105">Discussion</a></h3> loncapa/loncom/interface/lonfeedback.pm handles feedback on resources. Feedback can be for course discussion of a resource or to communicate with the author of the resource. In the latter case, a screenshot of the resource and (if applicable) the students previous attempts to solve the problem. Course discussion messages appear at the bottom of the resource being discussed. There are two types of attribution in course discussion messages. Users may choose to have their LON-CAPA id shown to everyone or they may have it shown only to instructors. Complete anonymity is not an option. If the users choose to hide their LON-CAPA id (an 'anonymous' message), they can set the name given in the [PREF] page. Figures 2.2.8 through 2.2.10 show a course discussion feedback cycle. <img width=256 height=63 src="Session%20Tw1_files/image013.jpg" v:shapes="_x0000_i1030"> Fig 2.2.8 - A Simple Resource <img width=301 height=240 src="Session%20Tw1_files/image015.jpg" v:shapes="_x0000_i1031"> Fig. 2.2.9 Composing Discussion Feedback  <img width=292 height=170 src="Session%20Tw1_files/image017.jpg" v:shapes="_x0000_i1032"> Fig 2.2.10 The Resource with Anonymous and Non-anonymous Discussion <h3><a name="_Toc421867106">Messaging</a></h3> </div> <h1> </h1> loncapa/loncom/interface/lonmsg.pm provides functions for sending users messages. All messaging is currently done via lonmsg.pm. The following subroutines handle the sending of various types of messages: author_res_msg Send a message to the author of a resource. user_crit_msg Send a critical message to a user. Critical messages require the user to acknowledge receipt before any other action in LON-CAPA can be taken. user_crit_received Notify the sender of a critical message that the message has been received. user_normal_msg Send a non-critical message to a user. statuschange Change the status of a message (read, replied, forwarded, etc) The lonmsg::handler takes care of the display and sending of messages. If you have the time, communicate with yourself! Note: Critical messages are displayed on login to LON-CAPA. Some message types are only available for course coordinators. <h3> </h3> <h3><a name="_Toc421867107">Resource Feedback</a></h3> <img border=0 width=432 height=304 id="_x0000_i1028" src="handout_files/image004.jpg"> Fig. 2.2.11 � Example of a Feedback <div class=Section2> </div> </body> </html>