Learning Analytics Specification - Revision history

Mudrd8mz: Text replacement - "class="nicetable"" to "class="wikitable""

2021-07-14T13:22:40Z

Text replacement - "class="nicetable"" to "class="wikitable""

← Older revision		Revision as of 13:22, 14 July 2021
Line 109:		Line 109:
	A source sub-plugin includes a number of common files in a standard structure. Some files need explanation for this plugin type.		A source sub-plugin includes a number of common files in a standard structure. Some files need explanation for this plugin type.

	{\| class="~~nicetable~~"		{\| class="wikitable"
	! File(s)		! File(s)
	! Explanation		! Explanation
Line 142:		Line 142:
	These functions are located within the ''lib.php'' file.		These functions are located within the ''lib.php'' file.

	{\| class="~~nicetable~~"		{\| class="wikitable"
	\|-		\|-
	! Method		! Method
Line 202:		Line 202:
	These functions are located within the ''lib/la/learning_analytics.php'' file.		These functions are located within the ''lib/la/learning_analytics.php'' file.

	{\| class="~~nicetable~~"		{\| class="wikitable"
	\|-		\|-
	! Method		! Method
Line 304:		Line 304:

	The following table lists available placeholders that can be used in a notification.		The following table lists available placeholders that can be used in a notification.
	{\| class="~~nicetable~~"		{\| class="wikitable"
	! Placeholder		! Placeholder
	! What it does		! What it does

Stronk7: /* See also */

2020-04-06T11:17:49Z

Dmonllao at 09:16, 28 July 2017

2017-07-28T09:16:23Z

← Older revision		Revision as of 09:16, 28 July 2017
Line 6:		Line 6:
	\|assignee = XXX		\|assignee = XXX
	}}		}}
	{{~~Work~~ in ~~progress~~}}		{{Note\|This specification is obsolete, it was discarded in favour of the current Moodle [[Analytics API]].}}

	This is a specification for a Learning Analytics system including an API for collection and combination of learning analytics data and a number of interfaces for presenting this information.		This is a specification for a Learning Analytics system including an API for collection and combination of learning analytics data and a number of interfaces for presenting this information.

Dmonllao at 13:14, 15 June 2017

2017-06-15T13:14:40Z

← Older revision		Revision as of 13:14, 15 June 2017
Line 2:		Line 2:
	\|name = Learning Analytics		\|name = Learning Analytics
	\|state = Planning		\|state = Planning
	\|tracker = ~~MDL-57791~~		\|tracker = XXX
	\|discussion = XXX		\|discussion = XXX
	\|assignee = XXX		\|assignee = XXX

Emdalton1: Undo revision 51818 by Emdalton1 (talk)

2017-02-01T07:41:24Z

Undo revision 51818 by Emdalton1 (talk)

← Older revision		Revision as of 07:41, 1 February 2017
Line 1:		Line 1:
	{{Infobox Project		{{Infobox Project
	\|name = Learning Analytics		\|name = Learning Analytics
	\|state = ~~In Development~~		\|state = Planning
	\|tracker = MDL-57791		\|tracker = MDL-57791
	\|discussion = ~~https://moodle.org/mod/forum/view.php?id=8044~~		\|discussion = XXX
	\|assignee = ~~moodle.com RESEARCH team~~		\|assignee = XXX
	}}		}}
	{{Work in progress}}		{{Work in progress}}

	~~==Welcome to Project Inspire!==~~

	This is a specification for a Learning Analytics system including an API for collection and combination of learning analytics data and a number of interfaces for presenting this information.		This is a specification for a Learning Analytics system including an API for collection and combination of learning analytics data and a number of interfaces for presenting this information.

Emdalton1 at 07:28, 1 February 2017

2017-02-01T07:28:37Z

← Older revision		Revision as of 07:28, 1 February 2017
Line 1:		Line 1:
	{{Infobox Project		{{Infobox Project
	\|name = Learning Analytics		\|name = Learning Analytics
	\|state = ~~Planning~~		\|state = In Development
	\|tracker = MDL-57791		\|tracker = MDL-57791
	\|discussion = ~~XXX~~		\|discussion = https://moodle.org/mod/forum/view.php?id=8044
	\|assignee = ~~XXX~~		\|assignee = moodle.com RESEARCH team
	}}		}}
	{{Work in progress}}		{{Work in progress}}

			==Welcome to Project Inspire!==

	This is a specification for a Learning Analytics system including an API for collection and combination of learning analytics data and a number of interfaces for presenting this information.		This is a specification for a Learning Analytics system including an API for collection and combination of learning analytics data and a number of interfaces for presenting this information.

Emdalton1: Updated tracker to Epic

2017-02-01T07:06:07Z

Updated tracker to Epic

← Older revision		Revision as of 07:06, 1 February 2017
Line 2:		Line 2:
	\|name = Learning Analytics		\|name = Learning Analytics
	\|state = Planning		\|state = Planning
	\|tracker = ~~XXX~~		\|tracker = MDL-57791
	\|discussion = XXX		\|discussion = XXX
	\|assignee = XXX		\|assignee = XXX

Deraadt: Adding to Project category

2016-02-01T04:38:20Z

Adding to Project category

← Older revision		Revision as of 04:38, 1 February 2016
Line 407:		Line 407:
	* [[Event Monitor specification]]		* [[Event Monitor specification]]
	* [[:en:Learning_analytics\|Learning analytics]]		* [[:en:Learning_analytics\|Learning analytics]]

			[[Category:Project]]

Deraadt: Adding idea for visual representations from sources

2016-01-19T00:51:46Z

Adding idea for visual representations from sources

← Older revision		Revision as of 00:51, 19 January 2016
Line 284:		Line 284:
	* The number of notifications sent from the system can be seen and there is an explicit link to allow individual notifications to be sent to the user.		* The number of notifications sent from the system can be seen and there is an explicit link to allow individual notifications to be sent to the user.
	* '''??? Should there be a history of notifications? How should it be presented? ???'''		* '''??? Should there be a history of notifications? How should it be presented? ???'''
	* Components of the status, from each source, are given and there could potentially be additional information provided by the relevant source (such as the last access date).		* Components of the status, from each source, are given and there could potentially be additional textual information provided by the relevant source (such as the last access date) or it could provide a graphical representation of information from the source (such as histogram of access counts over the last weeks).
	* A user (manager, teacher) will be able to see the status of an individual student across all that they have the appropriate capabilities to view.		* A user (manager, teacher) will be able to see the status of an individual student across all that they have the appropriate capabilities to view.
	* By default, the user (student) referred to in details should not be able to see this page. A capability controlling this should be created so exceptions can be made. (Studies have shown that showing at-risk students detailed evidence of their progress leads to poorer outcomes.) Such users would be able to see the status information for all courses where they have the required capability.		* By default, the user (student) referred to in details should not be able to see this page. A capability controlling this should be created so exceptions can be made. (Studies have shown that showing at-risk students detailed evidence of their progress leads to poorer outcomes.) Such users would be able to see the status information for all courses where they have the required capability.

Deraadt: Consolidation and revision

2015-12-23T01:41:35Z

Consolidation and revision

Show changes

← Older revision		Revision as of 11:17, 6 April 2020
Line 404:		Line 404:
	== See also ==		== See also ==

	* [[~~Event 2~~]]		* [[Events API]]
	* [[Event Monitor specification]]		* [[Event Monitor specification]]
	* [[:en:Learning_analytics\|Learning analytics]]		* [[:en:Learning_analytics\|Learning analytics]]

	[[Category:Project]]		[[Category:Project]]