[BACK]Return to BT_documentation.doc CVS log [TXT] [DIR] Up to [LON-CAPA] / doc / help

Annotation of doc/help/BT_documentation.doc, revision 1.1

1.1     ! rezaferr    1: ࡱ;	&&&&%&	
        !             2: 
 !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~Root Entry&	
        !             3: &
        !             4: 	FMicrosoft Word-Dokument
        !             5: MSWordDocWord.Document.89q&DyKRef_Chapter%208wDyK
        !             6: Ref_Slots&&՜.+,088g
        !             7: &[bbDefault$a$1$&*$&A$/B*OJQJCJmH	sH	PJ^JaJ_H&tH&nHx&&x	Heading 16&@&
        !             8: &F&
        !             9: &F&&^&]P`P<$&OJQJCJ 5&KH&^JaJ \&z&z	Heading 26@&&
        !            10: &&F&
        !            11: &&F&@^@]`<$& OJQJCJ6&5&^JaJ]&\&t&t	Heading 36@&
        !            12: &F&
        !            13: &F&^]0`0<$&OJQJCJ5&^JaJ\&h&h	Heading 46@&
        !            14: &F&
        !            15: &F&`^`]`<$&CJ5&aJ\&l&l	Heading 53@&
        !            16: &F&
        !            17: &F&^]`<CJ6&5&aJ]&\&f&f	Heading 63@&
        !            18: &F&
        !            19: &F&^]`<CJ5&aJ\&X&X	Heading 73@&
        !            20: &F&
        !            21: &F&^]`<^&^	Heading 83@&
        !            22: &F&
        !            23: &F&^]```<6&]&l	&l	Heading 93	@&
        !            24: &F&
        !            25: &F&0^0]`<OJQJCJ^JaJBA@BAbsatz-Standardschriftart**	WW8Num2z0OJ&QJ&.&&.	WW8Num2z1OJQJ^J*&*	WW8Num2z2OJQJ.!&.	WW8Num3z0OJ&QJ&CJ.1&.	WW8Num4z0OJ&QJ&CJ.A&.	WW8Num4z1OJQJCJ.Q&.	WW8Num4z2OJQJCJ.a&.	WW8Num6z0OJ&QJ&CJ.q&.	WW8Num6z1OJQJCJ.&.	WW8Num6z2OJQJCJ.&.	WW8Num7z0OJ&QJ&CJ.&.	WW8Num7z1OJQJCJ.&.	WW8Num7z2OJQJCJ2&2	WW8Num8z0OJQJPJ^J.&.	WW8Num8z1OJQJ^J*&*	WW8Num8z2OJQJ.&.	WW8Num9z0OJ&QJ&CJ.&.	WW8Num9z1OJQJCJ..	WW8Num9z2OJQJCJ0!0
        !            26: WW8Num10z0OJ&QJ&CJ010
        !            27: WW8Num10z1OJQJCJ0A0
        !            28: WW8Num10z2OJQJCJ0Q0
        !            29: WW8Num11z0OJ&QJ&CJ0a0
        !            30: WW8Num13z0OJ&QJ&CJ0q0
        !            31: WW8Num13z1OJQJCJ00
        !            32: WW8Num13z2OJQJCJ00
        !            33: WW8Num14z0OJ&QJ&CJ00
        !            34: WW8Num14z1OJQJCJ00
        !            35: WW8Num14z2OJQJCJ00
        !            36: WW8Num15z0OJ&QJ&CJ00
        !            37: WW8Num15z1OJQJCJ00
        !            38: WW8Num15z2OJQJCJ<<Default Paragraph FontB&BAbsatz-StandardschriftartHHWW-Absatz-Standardschriftart.!.	WW8Num1z0OJ&QJ&CJ.1.	WW8Num1z1OJQJCJ.A.	WW8Num1z2OJQJCJ.Q.	WW8Num3z1OJQJCJ.a.	WW8Num3z2OJQJCJ.q.	WW8Num5z0OJ&QJ&CJ..	WW8Num5z1OJQJCJ..	WW8Num5z2OJQJCJ**	WW8Num8z3OJ&QJ&00
        !            39: WW8Num11z1OJQJCJ00
        !            40: WW8Num11z2OJQJCJ,,
        !            41: WW8Num12z0OJ&QJ&BBWW-Default Paragraph Font6U6
Internet LinkB*ph>*&&X&&Emphasis6&]&``Heading 2 Char4OJQJCJmH	sH	6&5&PJ^JaJ_H&tH&]&\&:!:Footnote CharactersH*&:1:Comment ReferenceCJaJ(A(tagsOJQJCJ^J8Q8Footnote ReferenceH*&2a2Numbering Symbols8q8Endnote CharactersH*&::WW-Endnote Characters66BulletsOJQJCJPJ^JaJ66Endnote ReferenceH*&2&2Footnote anchorH*&0*0Endnote anchorH*&66Placeholder:&B*
        !            42: ph>*F&FHeading
Nx$&OJQJCJPJ^JaJ.B&.	Text body
        !            43: Ox / ListP^J@&@Caption
Qxx$&CJ6&^JaJ]&&&"&IndexR$&^J8&28Normal (Web)
        !            44: S&&PJ,&B,FootnoteTCJaJ@&R@Balloon TextUOJQJCJ^JaJ4&b4Comment TextVCJaJ8ab8Comment SubjectW5&\&D&Dbulleted!X
        !            45: &F^]`&TagsY^^Contents HeadingZ^]`$&CJ 5&aJ \&H!H
        !            46: Contents 1"[
&!
        !            47: ^]`H!H
        !            48: Contents 2"\
&!
        !            49: &^&]`H!H
        !            50: Contents 3"]
&!
        !            51: 6^6]`H!H
        !            52: Contents 4"^
&!
        !            53: Q^Q]`&HTML Preformatted:_
2(
        !            54: Px4 #\'*.25@9*$OJQJCJPJnH^JaJ\&\CodeExample`$a$
h&8pOJQJCJ^JaJH!H
        !            55: Contents 5"a
&&
        !            56: l^l]`H!"H
        !            57: Contents 6"b
&&
        !            58: ^]`H!2H
        !            59: Contents 7"c
&&
        !            60: ^]`H!BH
        !            61: Contents 8"d
&&
        !            62: ^]`H!RH
        !            63: Contents 9"e
&&
        !            64: ^]`J!bJContents 10"f
&&
        !            65: 	^	]`3E}bp&/&i&&>.C[dstuvwxyz$
        !            66: .=0JLvWF`dejfjl|D"{|}~E4&{I6`6b6bp
8&&@&&@&(&	&&
        !            67: 
        !            68: 
        !            69: H&&&&&&&&$&&&?C"
        !            70: 
        !            71: H&&&&&&&&$&&&?C"<
        !            72: &C&&&&&&h00cp4:t4t	Ref_SlotsRef_Chapter%208Djbp&Djbp&&&&&&P&&  &@&@ .& &0& .&. &`&`	 .&.. &
        !            73: & .&... &
        !            74: &
 .&.... &
        !            75: & .&..... &
        !            76: `& .&...... &
        !            77: 0&0 .&....... &8&8OJ&QJ&CJ&&&&.&&OJQJCJ&l&8&8OJ	QJ	CJ&&&OJQJCJ&%&&OJQJCJ&l&p&pOJ	QJ	CJ&&	&	OJQJCJ&%&@&@OJQJCJ&l&&OJ	QJ	CJ&&&OJQJCJ&%&&&.&&8&8&.&&&.&&&.&&p&p.&&	&	.&&@&@.&&&.&&&.&&&.&&8&8&.&&&.&&&.&&p&p.&&	&	.&&@&@.&&&.&&&.&&OJ
        !            78: QJ
        !            79: CJ^JaJ&l&8&8OJQJCJ^JaJ&&&OJQJCJ^JaJ&%&&OJ
        !            80: QJ
        !            81: CJ^JaJ&l&p&pOJQJCJ^JaJ&&	&	OJQJCJ^JaJ&%&@&@OJ
        !            82: QJ
        !            83: CJ^JaJ&l&&OJQJCJ^JaJ&&&OJQJCJ^JaJ&%&&OJ
        !            84: QJ
        !            85: CJ^JaJ&l&8&8OJQJCJ^JaJ&&&OJQJCJ^JaJ&%&&OJ
        !            86: QJ
        !            87: CJ^JaJ&l&p&pOJQJCJ^JaJ&&	&	OJQJCJ^JaJ&%&@&@OJ
        !            88: QJ
        !            89: CJ^JaJ&l&&OJQJCJ^JaJ&&&OJQJCJ^JaJ&%&WW8Num11WW8Num12WW8Num15WW8Num16WW8Num17@bpbpPG&Times New Roman5&Symbol3&&ArialI&SimSunMS Mincho5&&Tahoma?4&Courier NewG4&
        !            90: MS Mincho-3 fg;&Wingdings_&StarSymbolArial Unicode MS?&Wingdings 2;&Wingdings?&Wingdings 2B&h&JF|Q
&&&&&&&'0&&Oh+'0`&`h	
        !            91: 
&
All about BTReza FerrydiansyahNormal.dotReza Ferrydiansyah16@@ʟ>@,3&@@d>g&G(|&~~~tttttt~~~iiittt~~~iiitttttt~~~~~~~~~iii~~~iii~~~~~~tttttt~~~~~~iiitttiii~~~~~~iii~~~iii~~~iiittt~~~iiiiii~~~iii~~~~~~tttttt~~~NNNiiiiii~~~ttt~~~~~~~~~~~~iii~~~~~~~~~NNN~~~iiitttiiittt~~~~~~iii~~~~~~iiitttiiitttttt~~~ttttttttt~~~ttt~~~tttiii~~~~~~tttttt~~~~~~tttttt~~~iiiiiittt~~~tttiii~~~~~~tttiiittttttNNNttt~~~Ჲнннٽώٌ駧駧&&𽽽ٽٽᚚЧٲٲhhh鲲ǧhhhЧнв|||в𲲲|||ǧMMMٽв|||ώDzٽጌnjٽώጌώጌٽጌጌ᧧ǽnjǽώᲲǽвٲвǧǧM 	0Caolan80	&bps{lDD|D+::AU+.X+@&a}*!+f+Bridge Task Documentation
By: Reza Ferrydiansyah

Table of Contents TOC \f \o "1-9" \t "Heading 9;9;Heading 8;8;Heading 7;7;Heading 6;6;Heading 5;5;Heading 4;4;Heading 3;3;Heading 2;2;Heading 1;1;Heading 1;1;Heading 2;2;Heading 3;3;Heading 4;4;Heading 5;5;Heading 6;6;Heading 7;7;Heading 8;8;Heading 9;9"  1  Introduction	3
 2  Main features of a BT	3
 3  CSE 101 method of creating BT	4
 3.1  XML File	5
 3.1.1  Questions	5
 3.1.2  Criteria	5
 3.1.3  Variability in Bridge Tasks	7
 3.2  Transforming the file	8
 4  LON CAPA .task format	9
 4.1  Header Information	9
 4.2  Variables and Parameters	9
 4.3  Questions and Criteria	10
 4.4  Finishing up	12
 5  Creating Conditional Sequences	12
 6  Slots	13
 6.1  Adding Slot Using the Interface	14
 6.1.1  Required Slot Attributes	14
 6.1.2  Optional Slot Attributes	14
 6.1.3  Selecting Resource Available Within Slots	14
 6.1.4  Specifying Proctors	14
 6.1.5  Specifying Users	15
 6.2  Uploading Slot Files	15
 6.2.1  Specifying Types of Input Fields	15
 6.3  Editing and Deleting Slots	16
 7  Uploading Files Using Portfolio	16
 8  XML File Specification 	17
 8.1  XML Elements	17
 8.2  task	17
 8.3  question	17
 8.4  sub question	18
 8.5  gradingcriteria	18
 8.6  criteria	18
 8.7  gradernote	18
 8.8  entity	19
 8.9  instance	19
 8.10  spec	19
 8.11  variable	19
 9  XML	20
 9.1  Elements	20
 9.2  Attributes	20
 9.3  Headers and Root Element	20Introduction
BTs or Bridge Tasks are open-ended, performance-based assessments.  BTs are based on a mastery-model of assessment and evaluated on a pass-fail basis.  You may use BTs in a variety of ways, from supporting the scoring of a final project, to individual lab assignments.  

Bridge tasks consist of as one or more individual tasks that describe what the student is to do, usually in the form of a problem to solve.  LON-CAPA supports the creation of multiple versions of each task, so that each student may receive a mix of randomly assigned tasks to perform. Students use LON-CAPA to view the bridge task.  LON-CAPA supports the scheduling of BTs to restrict access by IP address range and to allow students to schedule slots of time to take a BT.  

When students complete a BT, they upload files they have created for grading. Files are uploaded using LON-CAPA s portfolio system. 

LON-CAPA supports the creation of scoring rubrics associated with each individual task to guide graders and ensure inter-rater reliability among multiple graders in a course. Instructors specify criteria to assign an overall score to a BT based on the scores of the individual rubrics.  

BTs are used in Michigan State University s CSE 101 course. The course is designed to teach computer competencies by having students solve problems using a variety of computer software  (MS-Word, MS-Excel, World Wide Web, and MS Access).  In CSE 101, BTs are used for summative assessment, the majority of students  grades are based upon the BTs.  Here, students must successfully pass a BT before attempting the next BT.  A student s final course grade is based on the highest level BT passed.  The CSE 101 class is quite large, approximately 2000 students per semester.  Students may take up to one BT per week; typically there are over 14,000 BTs administered per semester. Thus there is a need to quickly and accurately access students.  LON-CAPA successfully supports the load requirements.  

 The main features of a BT are described in the next section, followed by a section describing creating BT problems. The next two sections describes the creation of a Bridge Task using the LON-CAPA native .task language method. The chapters after that discusses the administrative aspects of Bridge Tasks, this includes determining which Bridge Tasks to show to the students as well as determining when and where students may take Bridge Tasks. Following that is a section on handing in files using the portfolio. The final two sections is a reference section on XML.
Main features of a BT
There are many ways in which BTs differ from other assessments. 

Multiple Versions. There are multiple versions of a BT. A person taking a BT may receive a different version than the person taking the same BT sitting next to him or her. To create BTs that have different versions, the instructors who created the BT will create multiple sub-questions. The BT engine then chooses one of the sub questions and gives that sub question to the student, thus creating multiple versions.
Essay/task based. Bridge task questions open-ended. Users create files which they upload and submit to the system.
Rubric-Based Grading. Each question in a bridge task has scoring rubrics, criteria, associated with them. These criteria are used as the basis of grading. The grading page provides the criteria checklist on which the grader enters whether a student passes or fails each criterion. This ensures inter-rater reliability among multiple graders.
Mandatory and Optional Criteria. Some criteria can be made mandatory, that is a student will fail if the student does not pass that criteria. Some criteria are optional and the student must pass a certain number of these optional criteria. Criteria are associated with questions, which can also be made optional or mandatory. The LON-CAPA calculates whether a student has passed or fail based on the number of mandatory and optional questions the student has passed.
Automatic Bookkeeping. The system calculates whether the student has passed a BT or not and records it into the database. The system stores 
a complete record of the BT each student received
when each student s BT was administered 
the BT instance
the files the student turned in
the associated grading criteria
the grading results (and history of grading, including grader ID)
Sequential Bridge Tasks. The system can be set in such a way that a student can only take a certain bridge task after passing the previous bridge task on the list. This is done using conditionals in LON-CAPA. There are other ways to use conditionals and bridge tasks to customize the usage of bridge tasks in a course.
Slots. Slots can be created to relate students with time and location. This allows control of where and when a student can take a bridge task. 
Proctor Authentication. Slots also allow a particular proctor to be in a particular location for a bridge task. Each student who is scheduled to take the bridge task must be authenticated by the proctor. 
LON CAPA .task format
The LON CAPA .task format is an XML file used directly by LON CAPA. A primer on XML is given in section  REF Ref_Chapter%208 \n \h &8. An XML file contains elements in tags, and elements may contain attribute. The syntax, spelling (including capitalization) of the XML file must be exact, otherwise the XML file will not be understandable. 

The online editor for the .task format is discussed in the next section. This section describes creating the .task file by simply using a note editor such as Notepad. 
In this section the elements of this file is described. The .task format consists of three parts:
The header, which contains information about the file itself. The header can be copied from this documentation as is.
Parameter information. This part consists of the possible values for various parameters in the Bridge Task.
Questions section. This part consists of the actual text the user sees as well as all criteria and questions.

Header Information
The root node of the .task format is the task element, which is an XML element written as follows:
<Task OptionalRequired="0">
Variables and Parameters
To create differences in Bridge Tasks between students, some part of the questions are given as variables. Each variable contains multiple instances of possible values and LON-CAPA randomly selects an instance to give to the student. 
All variables are placed inside a Setup element. Each setup element has an id attribute which contains the name of the variable. The possible instances or values of those variables are placed inside the setup element inside an Instance tag. Each Instance element has two attributes, the OptionalRequired attribute which should be set to 0, and the unique id of that instance.
The actual data of the instance is placed inside InstanceText tags. Currently the instance data is created with a loncapa/perl script. In this script, the parameters of the variable are set. The syntax to set the parameter of a variable is  $variableName {fieldname} =  fieldValue  . The variable name is taken from the attribute id from the Setup element, thefield name is the name of the parameter the author sets, and the fieldValue is simply the value of the field. The first parameter that must be set is the instance field, with the value being an identifier of the instance.
Example:
<Setup id= entitySubject >
<Instance OptionalRequired= 0  id= instanceHarry >
<InstanceText>
	<script type='loncapa/perl'>
	$entitySubject{instance} =  instanceHarry ;	
	$entitySubject{personname} =  Harry ;	
	$entitySubject{place} =  zoo ;	


	</script>
</InstanceText>
</Instance>

<Instance OptionalRequired= 0  id= instanceBetty >
<InstanceText>
	<script type='loncapa/perl'>
	$entitySubject{instance} =  instanceBetty ;	
	$entitySubject{personname} =  Betty ;	
	$entitySubject{place} =  park ;	

	</script>
</InstanceText>
</Instance>

</Setup>
The example above describes a variable question. It has two different possible values for the entity  subject , Harry-zoo or Betty-park. Variables can be placed inside the questions by using the variable name and field name. 
Example:
This is a test question. $entitySubject{personname}
 went to the $entitySubject{place}. .
 
Based on this code, two different questions are possible:
This is a test question. Harry went to the zoo
This is a test question. Betty went to the park

Questions and Criteria

The task description should be divided into questions. Questions can also be divided into sub questions. A question must have one or more criteria, a task may also have a criteria. These criteria are used by the graders to determine whether a student passes a particular bridge task. Both questions and criteria should be interspersed with the task description, placed where the user would see them when reviewing their graded bridge task.
Questions are created by using the Question tag. Each question must have a unique id attribute which identifies the question. Each question must also have the mandatory attribute which can be set to  Y  if the question is mandatory or  N  otherwise. Finally the question may also have a OptionalRequired attribute, which determines how many optional criteria must the student get in order to pass this question. 
The question element will have the actual text of the question. The questions are created inside the QuestionText element. The question descriptions are placed inside the file by simply typing the text. The text can be marked up to have various formatting. The mark up language used is simple HTML. 
Criteria are created using the Criteria tag. The attributes for the criteria tag are almost the same  as the attributes for the questions tag. Criteria tags have id attributes as well as Mandatory attributes. However criteria tags do not have OptionalRequired attributes. The criteria description are created inside the CriteriaText element and can be formatted the same way as the formatting of the questions (using HTML).
Sample Bridge task
<Question id= q.testquestion  Mandatory='Y' OptionalRequired= 1 >
	<QuestionText>
		Some test explanation
			<Criteria id= criteria.overall.handin  Mandatory= Y >
				<CriteriaText>
			Criteria text 1
			<GraderNote> 
				This part cannot be seen by students
					</GraderNote>
				</CriteriaText>
			</Criteria>

			<Question id= q.question1  OptionalRequired= 0 >
				<QuestionText>
					The actual test question
					<Criteria id= criteria.question1  Mandatory= Y >
						<CriteriaText>
							Criteria text 2
						</CriteriaText>
			</Criteria>
				</QuestionText>
			</Question>
		
Instruction on submitting
	</QuestionText>
</Question>

The example above shows a code for the creation of criteria. There are 2 criteria in the above question, The student will never see the criteria when the student is taking the test. The grader will see this on his/her screen:

Criteria text 1. Grader Note: This part cannot be seen by the student
o Pass 		o Fail
Comment:


Criteria text 2.
o Pass 		o Fail
Comment:



When the bridge task is graded the student will see both the questions and the criteria in his space as follows:
Some test explanation
Criteria text 1
Pass
The actual test question
Criteria text 2.
Pass 
Instruction on submitting

Finishing up
Once all questions are written, the file must be closed with the </Task> tag. The file must be saved with a .task extension then placed into a LON CAPA author's folder. To upload the file simply go to the construction space and simply upload the new file using the upload new document button. Once the file is uploaded to LON CAPA, the author can publish the file so that the domain coordinator will be able to use the file.
Setting Up the Bridge Task in a Course
The first step in making bridge tasks available to students is to include it in the document space. To do this, first enter the course coordinator space for the course, go to "Course Documents" and click on import. This page gives the list of files that you have created. Check on the bridge task and press import to insert the file to the list of documents.
There are two ways of making bridge tasks available to students. One method is by using slots (the default method), which restrict the bridge task document to open at certain time/place only. The other method allows students to take bridge task like any other Lon-CAPA assignments, that is at any time they want. 

If you want to use slots, first create the slots as described in chapter  REF Ref_Slots \n \h &6. Once the resource is imported (and slots are created) go back to the document list and click on the bridge task resource, this should take you to a page that shows the resource content. Click on PPRM (a button on the top menu) to modify parameters for this resource.
Set the opening date and the due date (if any) of the resource. To do this, click on the * in the in course for resource column. A pop up should appear. Enter the date for the date.

If you are using slots:
Change the "Use slot based access controls" parameter to "Yes".
Change the "Slots of availability" parameter" for the course in for resource column to the name of the slot that you created. You may need to change the input type (the combo box at the top of the popup) to 'String Value' instead of 'default'.

If you are not using slots: 
Change the "Use slot based access controls" parameter to "no" 
The bridge task should now be available to students.
Creating Conditional Sequences
It is possible to configure bridge tasks such that only when a student passes a Bridge Task does the next Bridge Task appear to the student. This feature is useful in such cases as  Bridge Tasks are related to one another, and the results of one Bridge Task is needed for the next Bridge Task.    

To create configure bridge tasks these way, a sequence page must be created. A resource author starts at his/her construction space (Main menu -> CSTR). Once in the construction space, the author create a new assembled sequence.

The author must create various conditionals to determine which resources to show. The easiest way to do this is by using advanced edit. The advanced edit visualizes the various conditions and resources. This interface needs popups, so make sure  popups are enabled in the browser.

In the main starting view of the advanced edit, there are two squares, marked start and end respectively. Start by creating a link between the start square and the end square. To do this click on the start square (on the row under the text start), select "Link Resource", then click on the end square. A link is now created between the start and the end boxes.

Once a link is created the author adds resources and conditions. Click on the link and then choose insert resource into link. This allows the placement of a resource such as a bridge task into the sequence. Once the resource is placed into the link, the author should create a mapalias. To do this, select the resource, then click on set parameters, and change the value of Custom Parameter to an alias. 

Under each square is an area of the same color as the square, these areas can be used to create conditionals to get to the next resource to the sequence. This document only discusses using conditionals to block access to the next resource (including Bridge Tasks).

Add conditionals by clicking on the area just under the squares. A popup window will appear with a condition box and some options. The condition box allows the author to enter a variety of different conditions. To block access to the next resource, select the second option "Blocking this link if false". 

The conditions used will be :
&EXT('user.resource.resource.0.awarded','<alias of resource>') eq '1'
<alias of resource> should be changed to the alias set for the previous resource that the student needs to pass before the next resource is unblocked. If the student has not passed a particular homework/problem/bridge task, the value of user.resource.resource.0.awarded is 0 otherwise the value is 1. This line checks whether the value of user.resource.resource.0.awarded for that resource is equals to 1, if not the link is blocked and the next resources are not shown to the user.

Slots
To restrict the when and where BT's can be taken, the slots feature of Lon-Capa is used. Slots allow the instructors to specify the room, the time, the students that can take the Bridge Tasks, and finally any proctors that will authenticate the students.

A course coordinator can add slots, by pressing Managing Parameters on the main menu and then clicking on the link Managing Slots. The link will take the user to a page showing all available slots. The user can control which slots to show based on opening date, as well as what slot information to show.
	
There are two ways of creating slot, using the web interface in LON CAPA and uploading a comma delimited file. Uploading a file allows the coordinator to use other applications in creating the comma delimited file and automate the entry of multiple slots. The following text is taken from the LON CAPA course manual.

Adding Slot Using the Interface
One way to add new slots is by using the LON-CAPA interface for adding slots. This is
simply done by pressing the Create a New Slot button.
Required Slot Attributes
In the first page, input an identifier (name) for this slot. The identifier must be unique, and it must be one word without any special characters. You must also specify the time the slot is open by setting the starting time and the ending time.

Finally, you must specify whether this slot is instructor assignable or student selectable. Instructor assignable means that the instructors select which students go to which slots, while student selectable means that students can choose from a number of slots that they schedule themselves in.
Optional Slot Attributes
Once the required attributes are selected, you press next to get to the next page. The next page shows the various optional attributes available. One attribute that you can set is whether a proctor is needed for authentication. If a proctor is needed for authentication, the proctor must put a username and password into the student s resource page in order for the student to see the resource.

If you had chosen student selectable, you can also set the time the students will be able to apply for the slots. The maximum capacity for each slot can also be set which restrict the number of students per slot. Finally, you can set that for a particular time period, a student may only apply for one slot. This is mainly used to limit the number of times a student may use this resource.

Finally it is possible to limit the computers that are allowed to open the resource by setting the ip address range allowed. By setting this, you can set that a slot can only be opened from a particular room.\

Selecting Resource Available Within Slots
You can also specify which resources/files can a student open during the slot time. To do this, you must set that the slot is restricted to a specific resource (on the optionalattributes page). When this option is selected, the next page allows you to choose which resource this slot is restricted to.

Specifying Proctors
If you set that a proctor is needed for authentication. You will get a screen that allows you to set a valid proctor for that slot. Select proctor by checking the checkbox next to their names. The select and unselect button checks or unchecks the checkbox depending on the person s group.

Specifying Users
The next screen allows the instructor to restrict the person who can use the resource. There are many ways to select persons who may use the resource. You can individually select each person, you can select the groups, the role, or by the sections that they are enrolled in.

Uploading Slot Files
Another way of entering slot is by uploading a comma delimited file. A comma delimited file is a text file that separates each field with a comma. An easy way to create comma delimited files is to use a spreadsheet application such as Microsoft Excel, and save the file as a comma separated value (CSV) file. 

To upload a file press the Upload Slot List button on top of the page. On the first page, select the file with the slot data to upload by pressing the Browse button. There is an option to ignore the first line. This is useful when the first line of your comma delimited file consists of headers for each field. You can also upload space and tab delimited file by changing the type combo box. Press Upload to upload the file 

Specifying Types of Input Fields
The system will read the file into the system. You will then be prompted to specify the input type of each field. A set of types is given for each field. There are three mandatory types, slot name, starting time, and ending time. A mandatory type means that a field must be specified having that meaning. The input choices are as follows:

Slot name. The name or identifier of the slot. The name of the slot must be unique, and it must have no spaces. This input is mandatory, you must specify a field for this input type.
Type of slot. This determines whether students are allowed to schedule him/herself for this slot or whether the instructors assign students to this slot. The valid inputs for this field is either  preassigned  or  student selectable . There must be no space before or after the comma. If this type is not specified, the slot type defaults to preassignedor instructors assignable.
"  Slot Description. A description of the slot. If this isn t provided the default description of a slot is  Slot name From Start Time to End Time .
Start Time of slot. This determines the time when a slot starts to open. This input type is mandatory. There are various accepted format for this field. Two of which are  YYYYMMDDHHMNSS  and  MM/DD/YYYY HH:MM:SS .
End Time of slot. This determines the time when a slot ends and a user cannot access the resource. This input is mandatory. The accepted format for this field is the same as for the start time of slot.
Reservation Start Time. This determines when a student can start reserving for the slot. The accepted format for this field is the same as for the start time of slot.
Date range of slot exclusion. Sometimes a student is limited to a number of slot use for a particular date period. This field allows a range of dates where a student may not have more than one slot reservation/use. The format is  StartingDate,EndingDate , where starting date and ending date are time, which is the same for start time of slots.
Maximum number of reservations. The number of students allowed to reserve this slot. This is useful when slots are opened in a classroom/lab, and there is a limited number of seats.
IP or DNS restriction. The set of computers that can be used to use this slot between the starting time and the ending time of slots. This a comma sepearated list of items that can be
Specific IP address, Ex. 192.168.1.1
Specific IP address range, Ex. 192.168.1.[24-120]
Wildcard IP address, Ex. 192.168.1.*, 192.168.*
Specific Hostname, Ex. computer1.lab1.msu.edu
Wildcard Hostname, Ex. *.lab1.msu.edu or *.msu.edu
List of proctor ids. The list of proctor id that must authenticate the student before the student can open the slot. The proctor ids are separated by a comma. 
Secret word proctor uses to validate. The password the proctors use when authenticating the students.
Resource Restriction. Restricts which page (only test/homework pages) can be opened using this slot. This must be a full symb reference ?? to a resource.
Sections slot is restricted to. When choosing preassigned slot type, you can choose a section that can access this slot. Only students in that section can open a particular slot. Separate multiple sections by commas.
Users slot is restricted to. When choosing preassigned slot type, you can choose a list of students that can open this slot. Student ids are separated by commas.
Editing and Deleting Slots
You can also delete slots when you no longer need them as well as edit the slot attributes.
This is simply done by clicking the link Edit or Delete next to the slot name.

Uploading Files Using Portfolio
After a student finishes creating the Bridge Task, the student must hand in the files. There are many ways to do this, students can email the files necessary, or students can email a link to the instructor that shows where his files are. LON-CAPA provides a way to upload file using the portfolio. The portfolio is a space given to each student which can contain files and is shareable. 

The process of handing in files consists of:
Upload files into portfolio
Select the files to be submitted
Submit the files

At the end of every bridge task there will be a box to submit files in the portfolio for grading. When the student click on the link  select portfolio files , a new window is opened showing the content of the student s portfolio. The student can create directories in the portfolio and upload files using the upload file buttons.

Once the files that are needed are uploaded, the student select (by checking the checkbox next to the filenames) of all files that he needs to submit to the instructor. Once all files needed are checked off, the student needs to press the  select checked files and close window  button. 

By pressing the close window button, the student s portfolio window should close, and the student should see his or her Bridge Task Page. The text field in the upload files into portfolio should contain the list of names. The student must then press  submit answer  to submit the answer to be graded. 

If the student needs to resubmit the file, the student must repeat the process and check&&&&&&&	&
        !            92: &&&
&&&&&&&&&&&&&&&&&&& &!&"&#&$&'&(& off all the files (not only new files) that needs to be submitted. Once a file is submitted, the student may not overwrite or delete the files.
XML
XML is an abbreviation of eXtended Markup Language. It is a language often used to store data and the data descriptor in a text format. XML is a generalized markup language, anyone can create a language (or perhaps more appropriately: a dialect) to use for his or her application. In this section a short introduction to XML is given.

Elements
The main structure of an XML file is its element. Each element has a name to differentiate it with other elements. An element in XML contains an opening tag, content,  and a closing tag. The opening tag is basically a text in the form of  < ElementName AttributeList> . The content can be text or other elements. Finally the closing tag is in the form of  </ElementName> . The element-names in tags are case sensitive.

Example:
<Name>Reza Ferrydiansyah</Name>

<Person>
	<Name>Reza Ferrydiansyah</Name>
</Person>

Attributes
Each element can have a list of attributes. Each attribute consists of a attribute name and the value for the attribute. The attributes are placed inside the opening tag of the element.  Attribute names are also case sensitive. The format for the attribute are AttributeName= AttributeValue . 

Example:
<Person type= 1  alive= true >
	<Name>Reza Ferrydiansyah</Name>
</Person>
Headers and Root Element
Every XML document has exactly one root element. Every document usually has text to describe it as an XML document. 

Example:
<?xml version="1.0" encoding="UTF-8"?>
<rootElement>
	& &  Content & .
</rootElement>

4bhjl24Z\
        !            93: @Bvx$	&	p	r					$
        !            94: &
        !            95: l
        !            96: n
        !            97: 
        !            98: 
        !            99: LN(*vx 
"
L
N
~







#B*CJmH	sH	PJ^JaJ_H&tH&U&#B*CJmH	sH	PJ^JaJ_H&tH&)B*CJ8mH	sH	5&PJ^JaJ8_H&tH&\&M,.RThj46<>z|~"####&&''V(j())n**.>.٭٭٭ٙٙٙ٭~ٙٙ4B*CJmH	sH	fHq
        !           100: PJ^JaJ_H&tH&&B*CJmH	sH	5&PJ^JaJ_H&tH&)B*CJmH	sH	6&PJ^JaJ_H&tH&]&-B*CJ mH	sH	5&KH&PJ^JaJ _H&tH&\&#B*CJmH	sH	PJ^JaJ_H&tH&U&#B*CJmH	sH	PJ^JaJ_H&tH&1>..///0D001613344@6l6<7>7t7v7x7z7|72;<<===>>>*?ADANAAABBBB>C^CCCC튊tttttt+B*CJmH	sH	PJ^JaJ_H&tH&OJQJ+B*CJmH	sH	PJ^JaJ_H&tH&OJQJ/B*CJmH	sH	6&5&PJ^JaJ_H&tH&]&\&j&U&U&-B*CJ mH	sH	5&KH&PJ^JaJ _H&tH&\&&B*CJmH	sH	5&PJ^JaJ_H&tH&#B*CJmH	sH	PJ^JaJ_H&tH&-CRDjDDD|HHH*IHIII0JrJtJvJJJJJ,KJKKK2LvLxLLLLLLNNNOO`OdOO:PPPPP<TTTTTzUUzVVvW@XXXYZZZVZfZ[[/B*CJmH	sH	6&5&PJ^JaJ_H&tH&]&\&PJnH&+B*CJmH	sH	PJ^JaJ_H&tH&OJQJ+B*CJmH	sH	PJ^JaJ_H&tH&OJQJ#B*CJmH	sH	PJ^JaJ_H&tH&@[D[V[[[N\f\]D]F]]]]]]^"^n^^^^^^J_T_X_p_______ `F`P`````aFara|aaaaaab2b6bJbLbddddddd+B*CJmH	sH	PJ^JaJ_H&tH&OJ&QJ&#B*CJmH	sH	PJ^JaJ_H&tH&+B*CJmH	sH	PJ^JaJ_H&tH&OJQJ+B*CJmH	sH	PJ^JaJ_H&tH&OJQJ#B*CJmH	sH	PJ^JaJ_H&tH&<ddddddddd
        !           101: eee*e,e.e0e2ef@f`fjfffffggppppppptuvv$wwxLxؔ-B*CJ mH	sH	5&KH&PJ^JaJ _H&tH&\&j&U&U&/B*CJmH	sH	6&5&PJ^JaJ_H&tH&]&\&+B*CJmH	sH	PJ^JaJ_H&tH&OJ&QJ&'B*CJmHsHPJnH^JaJ_H&tH&	jU&#B*CJmH	sH	PJ^JaJ_H&tH&/"^\6zĩ(ԹhhDRT TJ|
        !           102: 6vx>Xj#0JDB*mH	sH	PJnHaJ_H&tH&0JD0JDPJnHaJ6&#B*CJmH	sH	PJ^JaJ_H&tH&/B*CJmH	sH	6&5&PJ^JaJ_H&tH&]&\&)B*CJmH	sH	5&PJ^JaJ_H&tH&\&?&4bdf2Z@v$	p			$
        !           103: &]&\&[&[&\&\&\&\&[&\&]&]&]&\&[&[&[Z^]`x$&&$&a$&O$&a$&$
        !           104: l
        !           105: 
        !           106: L(v 
L
~



,Rh&\&\&\&[&\&\&\&\&\&\&\&\&\&\&\&[&[&\&]&\&]&]&]&]46<>z|"###&'n*.
        !           107: &F
&^]`&&&&&&&&&&&&&&
        !           108: &F&
&&&^&]P`P
        !           109: 
        !           110: &F
6!
        !           111: ..///0D00134@6l699n:2;<<=
        !           112: &F
&^]`&&&&&
        !           113: &F&
&&&^&]P`PX
        !           114: &F
&88^8]`
        !           115: &F
&^]`===>>*?AC|HHH*IHIII0J$a$$a$$a$$a$$a$$a$	
&@<	
&@<	
&@<	
&@<	
&@<	
&@<
        !           116: &&F&
&@@^@]`&0JrJtJvJJJJJ,KJKKK2LvLxLLLLL$a$$a$$a$$a$$a$$a$$a$$a$$a$$a$$a$$a$$a$$a$$a$$a$$a$$a$LLNNOdOhOO:PPPPP<TvW	
&@<	
&@<	
&@<
        !           117: &&F&
&@@^@]`
&^]`
        !           118: &F
&^]`&&$a$&_	
&@<	
&@<$a$vWY]D]]]^^^^^J_p____ `F`$a$
h&8p^]`$a$
h&8p^]``$a$$a$
h&8p$a$	
&@<	
&@<F```aFaraaaaab2bJbLbdd&$a$$a$$a$
h&8p^]`$a$
h&8p	@$a$
h&8p$a$
h&8p^]`ddddddde}cI^]`$d&&&%d&&&d&&&'d&&^]`$d&&&%d&&&d&&&'d&&^]`$d&&&%d&&&d&&&'d&&^]`$d&&&%d&&&d&&&'d&&^]`$d&&&%d&&&d&&&'d&&^]`$d&&&%d&&&d&&&'d&&^]`$d&&&%d&&&d&&&'d&&e*e.e0e2ef@f`fjf{aG^]`$d&&&%d&&&d&&&'d&&^]`$d&&&%d&&&d&&&'d&&^]`$d&&&%d&&&d&&&'d&&&^]`$d&&&%d&&&d&&&'d&&^]`$d&&&%d&&&d&&&'d&&^]`$d&&&%d&&&d&&&'d&&^]`$d&&&%d&&&d&&&'d&&jfffffggljj}hfK&
        !           119: &F&
&&&^&]P`P<$&&
        !           120: &&F&
&@@^@]`^]`$d&&&%d&&&d&&&'d&&^]`$d&&&%d&&&d&&&'d&&^]`$d&&&%d&&&d&&&'d&&^]`$d&&&%d&&&d&&&'d&&^]`$d&&&%d&&&d&&&'d&&jmoprNtPttuvv$wwxLxzzl|&&&&
        !           121: &F&
&&&^&]P`P&
        !           122: &F
&^]`&
        !           123: &F^]`
        !           124: &F
&^]`&&&&&&&l|n|~~tvX&&&&&&&
        !           125: &F&
&&&^&]P`P&&&&&&&&&&&&&&&ؔ"^Z\6xz&&&&&&&&&&&&&
        !           126: &F&
&^]0`0&&
        !           127: &&F&
&@@^@]`©ĩZ\(ԹhhD
        !           128: &F
&^]`&&
        !           129: &F&
&^]0`0&&&&
        !           130: &&F&
&@@^@]`&&DRT TJ8 "&&&
        !           131: &F&
&&&^&]P`P<$&&&&
        !           132: &&F&
&@@^@]`
        !           133: &F
&^]`
        !           134: &&F
&88^8]`"|NP"*
        !           135: &&F&
&@@^@]`<$&&&&
        !           136: &F&
&&&^&]P`P<$&&&&&&&&
^]`
        !           137: &&F
&88^8]`&"$6vxDFX&
        !           138: &&F&
&@@^@]`<$&&_
_^]@`@&_&&&
        !           139: &&F&
&@@^@]`<$&&&_&_&_&_&_&&&
        !           140: j&&_&_&_&_&&-0&/ =!"#$2P1h&3P(2080&/ =!"#$2P1h&3P(2(2	05/ =!"#$2P1h&3P(2(2	080&/ =!"#$2P1h&3P(2(2	0&&_EmailSubject
_AuthorEmail_AuthorEmailDisplayName_AdHocReviewCycleIDAll about BT documentationurban@msu.eduMark Urban-Lurain[GRoot Entry&	F&CompObjj&Ole
        !           141: 1Table1Data
        !           142: SummaryInformation(WordDocument&ObjectPool&DocumentSummaryInformation8<&
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>