Adding a branch table - Revision history

Joergw at 23:51, 24 December 2008

2008-12-24T23:51:26Z

← Older revision		Revision as of 23:51, 24 December 2008
Line 60:		Line 60:

	[[fr:Ajouter une table de branchement]]		[[fr:Ajouter une table de branchement]]
			[[de:Verzweigungsseite_einf%C3%BCgen]]

Rcollman: tip format

2008-10-06T18:09:23Z

tip format

← Older revision		Revision as of 18:09, 6 October 2008
Line 18:		Line 18:
	A branch table description appears to the student as a button. The button width fits the text and the height is fixed. The student selects the button which is associated with a jump. These buttons may be arranged vertically or horizontally. Vertical buttons are centered. Horizon buttons appear in a row, and a second row will appear if needed. The arrangement of buttons is the only thing a teacher can change and this is done in the Lesson settings.		A branch table description appears to the student as a button. The button width fits the text and the height is fixed. The student selects the button which is associated with a jump. These buttons may be arranged vertically or horizontally. Vertical buttons are centered. Horizon buttons appear in a row, and a second row will appear if needed. The arrangement of buttons is the only thing a teacher can change and this is done in the Lesson settings.

	*Tip: ~~the~~ "Description" box does not work like the "Answer" box in a question, no mater what it looks like. The "use editor" check box is there and the familiar HTML editor will appear. They do not work. For example, you will see the text in a description field in bold, but the student will not see it.		:''TIP:'' The "Description" box does not work like the "Answer" box in a question, no mater what it looks like. The "use editor" check box is there and the familiar HTML editor will appear. They do not work. For example, you will see the text in a description field in bold, but the student will not see it.

	*The "[[Adding/editing_a_lesson#The_Maximum_Number_of_Answers_.2F_Branches_in_a_Lesson\|Maximum number of answers/branches]]" in Lesson settings ("Update this Lesson" button) determines how many blank descriptions the teacher will see in edit mode.		*The "[[Adding/editing_a_lesson#The_Maximum_Number_of_Answers_.2F_Branches_in_a_Lesson\|Maximum number of answers/branches]]" in Lesson settings ("Update this Lesson" button) determines how many blank descriptions the teacher will see in edit mode.

Rcollman: /* Description */ add link

2008-08-06T18:35:12Z

Description: add link

← Older revision		Revision as of 18:35, 6 August 2008
Line 20:		Line 20:
	*Tip: the "Description" box does not work like the "Answer" box in a question, no mater what it looks like. The "use editor" check box is there and the familiar HTML editor will appear. They do not work. For example, you will see the text in a description field in bold, but the student will not see it.		*Tip: the "Description" box does not work like the "Answer" box in a question, no mater what it looks like. The "use editor" check box is there and the familiar HTML editor will appear. They do not work. For example, you will see the text in a description field in bold, but the student will not see it.

	*The "Maximum number of answers/branches" in Lesson settings ("Update this Lesson" button) determines how many blank descriptions the teacher will see in edit mode.		*The "[[Adding/editing_a_lesson#The_Maximum_Number_of_Answers_.2F_Branches_in_a_Lesson\|Maximum number of answers/branches]]" in Lesson settings ("Update this Lesson" button) determines how many blank descriptions the teacher will see in edit mode.

	== The Jump link ==		== The Jump link ==

Rcollman: /* Description */ add tip about where to change # of descriptions

2008-08-06T18:33:39Z

Description: add tip about where to change # of descriptions

← Older revision		Revision as of 18:33, 6 August 2008
Line 19:		Line 19:

	*Tip: the "Description" box does not work like the "Answer" box in a question, no mater what it looks like. The "use editor" check box is there and the familiar HTML editor will appear. They do not work. For example, you will see the text in a description field in bold, but the student will not see it.		*Tip: the "Description" box does not work like the "Answer" box in a question, no mater what it looks like. The "use editor" check box is there and the familiar HTML editor will appear. They do not work. For example, you will see the text in a description field in bold, but the student will not see it.

			*The "Maximum number of answers/branches" in Lesson settings ("Update this Lesson" button) determines how many blank descriptions the teacher will see in edit mode.

	== The Jump link ==		== The Jump link ==

Rcollman: /* Title */ also jump list

2008-07-11T00:29:21Z

Title: also jump list

← Older revision		Revision as of 00:29, 11 July 2008
Line 10:		Line 10:

	== Title ==		== Title ==
	The title in a branch table is similar to other pages but has some special uses. The title is the identifier in collapse edit mode. The title in a branch table is also used with the "display left menu" setting.		The title in a branch table is similar to other pages but has some special uses. The title is the identifier in collapse edit mode and appears on the pulldown jumpto list. The title in a branch table is also used with the "display left menu" setting.

	== Content==		== Content==

Rcollman: /* Branch Tables and branches in a nutshell */ add title and content

2008-07-11T00:28:32Z

Branch Tables and branches in a nutshell: add title and content

← Older revision		Revision as of 00:28, 11 July 2008
Line 8:		Line 8:
	# Branches can be nested within each other. For example, a lesson might usefully be structured so that specialist points are sub-branches within the main subject branches. Working on nested sub branches can get complicated without a plan.		# Branches can be nested within each other. For example, a lesson might usefully be structured so that specialist points are sub-branches within the main subject branches. Working on nested sub branches can get complicated without a plan.
	# Branch Tables can also be used to hold content in the lesson as a simple page. As such they are really non-graded content pages. With no description, their jump-link will automatically go to the next page if that is the default in the lesson setting.		# Branch Tables can also be used to hold content in the lesson as a simple page. As such they are really non-graded content pages. With no description, their jump-link will automatically go to the next page if that is the default in the lesson setting.

			== Title ==
			The title in a branch table is similar to other pages but has some special uses. The title is the identifier in collapse edit mode. The title in a branch table is also used with the "display left menu" setting.

			== Content==
			The content area in a branch table is typical of most informational areas used in Moodle. It has the standard Moodle [[HTML editor]].

	==Description==		==Description==

Rcollman: /* Branch Tables and branches in a nutshell */ add something about Description

2008-07-11T00:09:30Z

Branch Tables and branches in a nutshell: add something about Description

← Older revision		Revision as of 00:09, 11 July 2008
Line 8:		Line 8:
	# Branches can be nested within each other. For example, a lesson might usefully be structured so that specialist points are sub-branches within the main subject branches. Working on nested sub branches can get complicated without a plan.		# Branches can be nested within each other. For example, a lesson might usefully be structured so that specialist points are sub-branches within the main subject branches. Working on nested sub branches can get complicated without a plan.
	# Branch Tables can also be used to hold content in the lesson as a simple page. As such they are really non-graded content pages. With no description, their jump-link will automatically go to the next page if that is the default in the lesson setting.		# Branch Tables can also be used to hold content in the lesson as a simple page. As such they are really non-graded content pages. With no description, their jump-link will automatically go to the next page if that is the default in the lesson setting.

			==Description==
			A branch table description appears to the student as a button. The button width fits the text and the height is fixed. The student selects the button which is associated with a jump. These buttons may be arranged vertically or horizontally. Vertical buttons are centered. Horizon buttons appear in a row, and a second row will appear if needed. The arrangement of buttons is the only thing a teacher can change and this is done in the Lesson settings.

			*Tip: the "Description" box does not work like the "Answer" box in a question, no mater what it looks like. The "use editor" check box is there and the familiar HTML editor will appear. They do not work. For example, you will see the text in a description field in bold, but the student will not see it.

	== The Jump link ==		== The Jump link ==

Rcollman: /* Branch Tables and branches in a nutshell */ descriptions are seen by students

2008-06-25T21:21:55Z

Branch Tables and branches in a nutshell: descriptions are seen by students

← Older revision		Revision as of 21:21, 25 June 2008
Line 4:		Line 4:
	== Branch Tables and branches in a nutshell ==		== Branch Tables and branches in a nutshell ==
	# Branch Tables are simply pages which have a set of links to other pages in the lesson. Typically a lesson may start with a Branch Table which acts as a table of contents.		# Branch Tables are simply pages which have a set of links to other pages in the lesson. Typically a lesson may start with a Branch Table which acts as a table of contents.
	# Each link in a Branch Table has two components, a "~~description~~" and a "~~jump~~" that the student sees as a button.		# Each link in a Branch Table has two components, a "jump" and a "description" that the student sees as a button.
	# A Branch Table can effectively divide the lesson into a number of branches (or sections). Each branch can contain a number of pages (probably all related to the same topic). The end of a branch is usually marked by an End of Branch page. This is a special page which, by default, returns the student back to the preceding Branch Table. As with any page, the "return" jump in an End of Branch page can be changed, by editing the page. In some versions, using a "This page" jump in an End of Branch, will send the student to the first page in the lesson.		# A Branch Table can effectively divide the lesson into a number of branches (or sections). Each branch can contain a number of pages (probably all related to the same topic). The end of a branch is usually marked by an End of Branch page. This is a special page which, by default, returns the student back to the preceding Branch Table. As with any page, the "return" jump in an End of Branch page can be changed, by editing the page. In some versions, using a "This page" jump in an End of Branch, will send the student to the first page in the lesson.
	# Branches can be nested within each other. For example, a lesson might usefully be structured so that specialist points are sub-branches within the main subject branches. Working on nested sub branches can get complicated without a plan.		# Branches can be nested within each other. For example, a lesson might usefully be structured so that specialist points are sub-branches within the main subject branches. Working on nested sub branches can get complicated without a plan.

Rcollman: /* Branch Tables and branches in a nutshell */ Missed a cap

2007-12-19T13:36:05Z

Branch Tables and branches in a nutshell: Missed a cap

← Older revision		Revision as of 13:36, 19 December 2007
Line 4:		Line 4:
	== Branch Tables and branches in a nutshell ==		== Branch Tables and branches in a nutshell ==
	# Branch Tables are simply pages which have a set of links to other pages in the lesson. Typically a lesson may start with a Branch Table which acts as a table of contents.		# Branch Tables are simply pages which have a set of links to other pages in the lesson. Typically a lesson may start with a Branch Table which acts as a table of contents.
	# Each link in a ~~branch table~~ has two components, a description and a jump that the student sees as a button.		# Each link in a Branch Table has two components, a "description" and a "jump" that the student sees as a button.
	# A Branch Table can effectively divide the lesson into a number of branches (or sections). Each branch can contain a number of pages (probably all related to the same topic). The end of a branch is usually marked by an End of Branch page. This is a special page which, by default, returns the student back to the preceding Branch Table. As with any page, the "return" jump in an End of Branch page can be changed~~, if required~~, by editing the page. In some versions, using a "~~this~~ page" jump in an End of Branch, will send the student to the first page in the lesson.		# A Branch Table can effectively divide the lesson into a number of branches (or sections). Each branch can contain a number of pages (probably all related to the same topic). The end of a branch is usually marked by an End of Branch page. This is a special page which, by default, returns the student back to the preceding Branch Table. As with any page, the "return" jump in an End of Branch page can be changed, by editing the page. In some versions, using a "This page" jump in an End of Branch, will send the student to the first page in the lesson.
	# Branches can be nested within each other. For example, a lesson might usefully be structured so that specialist points are sub-branches within the main subject branches. Working on nested sub branches can get complicated without a plan.		# Branches can be nested within each other. For example, a lesson might usefully be structured so that specialist points are sub-branches within the main subject branches. Working on nested sub branches can get complicated without a plan.
	# Branch Tables can also be used to hold content in the lesson as a simple page. As such they are really non-graded content pages. With no description, their jump-link will automatically go to the next page if that is the default in the lesson setting.		# Branch Tables can also be used to hold content in the lesson as a simple page. As such they are really non-graded content pages. With no description, their jump-link will automatically go to the next page if that is the default in the lesson setting.

Rcollman: Capitalized page types, removed Question jump description,

2007-12-19T13:33:09Z

Capitalized page types, removed Question jump description,

← Older revision		Revision as of 13:33, 19 December 2007
Line 1:		Line 1:
	{{Lessons}}		{{Lessons}}
			A Branch Table is one of two content page types in a Lesson. Sometimes they are referred to as a Branch page. A branch is a series of pages.

	== ~~Branches~~ in a nutshell ==		== Branch Tables and branches in a nutshell ==
	# Branch ~~tables~~ are simply pages which have a set of links to other pages in the lesson. Typically a lesson may start with a ~~branch table~~ which acts as a ~~Table~~ of ~~Contents~~.		# Branch Tables are simply pages which have a set of links to other pages in the lesson. Typically a lesson may start with a Branch Table which acts as a table of contents.
	# Each link in a branch table has two components, a description and the ~~title of the page to jump to~~.		# Each link in a branch table has two components, a description and a jump that the student sees as a button.
	# A ~~branch table~~ can effectively divide the lesson into a number of branches (or sections). Each branch can contain a number of pages (probably all related to the same topic). The end of a branch is usually marked by an End of Branch page. This is a special page which, by default, returns the student back to the preceding ~~branch table~~. As any page, "return" jump in an End of Branch page can be changed, if required, by editing the page. In some versions, using a "this page" jump in an End of Branch, will send the student to the first page in the lesson.		# A Branch Table can effectively divide the lesson into a number of branches (or sections). Each branch can contain a number of pages (probably all related to the same topic). The end of a branch is usually marked by an End of Branch page. This is a special page which, by default, returns the student back to the preceding Branch Table. As with any page, the "return" jump in an End of Branch page can be changed, if required, by editing the page. In some versions, using a "this page" jump in an End of Branch, will send the student to the first page in the lesson.
	# Branches can be nested within each other. For example, a lesson might usefully be structured so that specialist points are sub-branches within the main subject branches. Working on nested sub branches can get complicated without a plan.		# Branches can be nested within each other. For example, a lesson might usefully be structured so that specialist points are sub-branches within the main subject branches. Working on nested sub branches can get complicated without a plan.
	# Branch ~~tables~~ can also be used to hold content in the lesson as a simple page. As such they are really non-graded content pages. With no description, their jump-link will automatically go to the next page if that is the default in the lesson setting.		# Branch Tables can also be used to hold content in the lesson as a simple page. As such they are really non-graded content pages. With no description, their jump-link will automatically go to the next page if that is the default in the lesson setting.

	== The Jump~~-to Link~~ ==		== The Jump link ==

	Each ~~Answer (for questions) or~~ Description ~~(for~~ Branch ~~pages)~~ has a Jump~~-to link~~. When ~~this answer~~ is chosen, the ~~answer's response~~ is ~~shown~~ to ~~the student. After that the student sees~~ the page ~~given~~ in the Jump~~-to link~~. ~~This link~~ can ~~be either~~ relative or absolute. Relative links are This page and Next page. This page means that the student sees the current page again. Next page shows the page which follows in the logical order of pages. An absolute page link is specified by choosing a page's title.		Each Description in a Branch Table has a Jump associated with it. When a Description button is chosen, the student is sent to the page defined in the Jump associated with the button. The jump can direct a student to a relative or absolute page. In edit mode the teacher can see all the possible jumps by a pull down menu. The most common Relative links are "This page" and "Next page". "This page" means that the student sees the current page again. "Next page" shows the page which follows in the logical order of pages. An absolute page link is specified by choosing a page's title.

	Note that a (~~relative)~~ Next page Jump~~-to~~ link ~~may~~ show a different page ~~after pages have been moved~~. Whereas Jump~~-to links which use~~ (~~absolute~~) ~~page titles~~ always show the same page after ~~pages have~~ been moved.		Note that when a page is moved, its relative (for example, "Next page") Jump link will show the student a different page than before. Whereas a Jump link that uses an absolute (For example, a page title) always show the same page after the page has been moved.

	===Special Jumps===		===Special Jumps===

	====Unseen Question within a ~~Branch~~====		====Unseen Question within a branch====

	This will link to a randomly chosen unseen (by the student in this attempt) question between this ~~branch table~~ and the End of the Lesson or the next End of Branch.		This will link to a randomly chosen unseen (by the student in this attempt) question between this Branch Table and the End of the Lesson or the next End of Branch.

	====Random Question within a ~~Branch~~====		====Random Question within a branch====

	This will link to a randomly chosen question between the current ~~branch table~~ and the End of Lesson or the next End of Branch. If the student has already seen the question and attempts are greater than 1, they will get another chance to earn the point(s) for that question. If attempts are set to 1, the question will be skipped and another random question shown.		This will link to a randomly chosen question between the current Branch Table and the End of Lesson or the next End of Branch. If the student has already seen the question and attempts are greater than 1, they will get another chance to earn the point(s) for that question. If attempts are set to 1, the question will be skipped and another random question shown.

	====Random Branch Table====		====Random Branch Table====
Line 31:		Line 32:
	It is best to create a branching structure in a lesson after you have created content pages in your lesson in some sort of logical order. Here is a simple example of creating branches that students can navigate to from a page at the start of a lesson.		It is best to create a branching structure in a lesson after you have created content pages in your lesson in some sort of logical order. Here is a simple example of creating branches that students can navigate to from a page at the start of a lesson.

	Go to All-Pages View or Expanded View of your lesson. Above each page of your lesson you will see a link: Add a Branch Table. Decide where you want to create a branch table and click on the Add Branch Table link. You will need to specify the name of your ~~branch table~~ (for example: Contents) and then write a few words introducing the topic/ topics covered in your branches.		Go to All-Pages View or Expanded View of your lesson. Above each page of your lesson you will see a link: Add a Branch Table. Decide where you want to create a branch table and click on the Add Branch Table link. You will need to specify the name of your Branch Table (for example: Contents) and then write a few words introducing the topic/ topics covered in your branches.

	Next, the name of each button link in the description and the page to which each button link will jump. This jump should be the start of each navigational branch section. ~~Be sure to~~ add a button for End of Lesson in at least this branch table.		Next, enter the name of each button link in the description and the page to which each button link will jump. This jump should be the start of each navigational branch section. As a best practice, add a button for End of Lesson in at least this branch table so the student can exit.

	Finally you will insert End of Branch pages where each navigational branch section ends. All the jumps ~~in this page~~ should be set to the Content page we created in this example.		Finally you will insert End of Branch pages where each navigational branch section ends. All the jumps your End of Branch pages should be set to the Content page we created in this example.

	== See Also ==		== See Also ==