Aggregate - Revision history

Peterb at 03:38, 5 April 2016

2016-04-05T03:38:39Z

Jguerra at 18:43, 4 April 2016

2016-04-04T18:43:20Z

Jguerra at 18:37, 4 April 2016

2016-04-04T18:37:14Z

Jguerra at 18:35, 4 April 2016

2016-04-04T18:35:02Z

Jguerra at 18:17, 4 April 2016

2016-04-04T18:17:00Z

Jguerra at 18:15, 4 April 2016

2016-04-04T18:15:22Z

Jguerra at 18:07, 4 April 2016

2016-04-04T18:07:59Z

Jguerra at 18:06, 4 April 2016

2016-04-04T18:06:51Z

Jguerra at 18:03, 4 April 2016

2016-04-04T18:03:08Z

Jguerra at 17:54, 4 April 2016

2016-04-04T17:54:14Z

@@ Line 8: / Line 8: @@
 * The figure shows several different Content apps (QuizJet, QuizPet, Webex, etc.). Each of these applications are integrated in 2 ways:
-** The content application needs to log information of the learner activity within the content to the User Model (letter c in the diagram). Currently, the content applications are using our ADAPT2 [[CUMULATE protocol|cbum protocols]].
+** The content application needs to log information of the learner activity within the content to the User Model (letter c in the diagram). Currently, the content applications are using our ADAPT2 [[CUMULATE protocol]].
 ** The content application provides a service to list all the available content. This service implement the [https://github.com/PAWSLabUniversityOfPittsburgh/mastery-grids/blob/master/documentation/Content_Brokering_API_2016_01_21.pdf content brokering specification], which defines a JSON-format protocol to allow external applications to discover content. Both Aggregate and the User Model use the content brokering to register new content.

@@ Line 13: / Line 13: @@
 Several content application and their respective content brokering are implemented in [http://acos.cs.hut.fi/ ACOS server].
 Associated resources
 * [https://github.com/PAWSLabUniversityOfPittsburgh/mastery-grids Mastery Grids repository] (contains aggregate, mastery grids interface, documentation and course authoring tool)
@@ Line 19: / Line 20: @@
 * [[CUMULATE|user modeling specification]]
-Content provider applications
+== Content application resources ==
 * [[Smart Content|Smart content]] : provides an explanation of content applications
 * [http://acos.cs.hut.fi ACOS server] : provides details of ACOS infrastructure, content and protocols

@@ Line 1: / Line 1: @@
 We developed an adaptive social learning architecture Aggregate to support [[Mastery Grids Interface]]. We design this architecture to integrate content from diverse sources. The explanation of the procedures and links to associated resources are given below.
@@ Line 18: / Line 20: @@
 Content provider applications
 * [https://github.com/PAWSLabUniversityOfPittsburgh/quizjet QuizJet repository]
 * [https://github.com/PAWSLabUniversityOfPittsburgh/quizpet QuizPet repository]
 * [https://github.com/PAWSLabUniversityOfPittsburgh/annotated-examples Annotated Examples (Webex) repository]
 * [https://github.com/PAWSLabUniversityOfPittsburgh/educational-videos Educational Videos repository]

@@ Line 6: / Line 6: @@
 * The figure shows several different Content apps (QuizJet, QuizPet, Webex, etc.). Each of these applications are integrated in 2 ways:
-** The content application needs to log information of the learner activity within the content to the User Model (letter c in the diagram). Currently we are usign our ADAPT2 [[CUMULATE protocol|cbum protocols]].
+** The content application needs to log information of the learner activity within the content to the User Model (letter c in the diagram). Currently, the content applications are using our ADAPT2 [[CUMULATE protocol|cbum protocols]].
-** The content application provides a service to list all the available content. This service implement the [https://github.com/PAWSLabUniversityOfPittsburgh/mastery-grids/blob/master/documentation/Content_Brokering_API_2016_01_21.pdf content brokering specification], which defines a JSON-format protocol to allow external applications to discover content.
+** The content application provides a service to list all the available content. This service implement the [https://github.com/PAWSLabUniversityOfPittsburgh/mastery-grids/blob/master/documentation/Content_Brokering_API_2016_01_21.pdf content brokering specification], which defines a JSON-format protocol to allow external applications to discover content. Both Aggregate and the User Model use the content brokering to register new content.
-This architecture supports several kinds of open student modeling, social comparison, and recommendation. The architecture fulfills a major objective, portability, which is the ability to be integrated to other systems with little set up and modification. The architecture is modular and includes different software components as follows:
+Associated resources
-*frontend user-system interaction interface, the [[Mastery Grids Interface]]
+* [https://github.com/PAWSLabUniversityOfPittsburgh/mastery-grids Mastery Grids repository] (contains aggregate, mastery grids interface, documentation and course authoring tool)
-*backend '''''Aggregate''''' services communicating between the main interface and user modeling services [https://github.com/PAWSLabUniversityOfPittsburgh/AggregateUMServices  ==> source code]
+Content provider applications
 An overall architecture of the system can be sen in the following figure.
 [[Image:arch_v2.png|Aggregate Architecture]]

@@ Line 6: / Line 6: @@
 * The figure shows several different Content apps (QuizJet, QuizPet, Webex, etc.). Each of these applications are integrated in 2 ways:
-** The content application needs to log information of the learner activity within the content to the User Model (letter c in the diagram). Currently we are usign our ADAPT2 protocol and our user model cbum for that. Specification of how
+** The content application needs to log information of the learner activity within the content to the User Model (letter c in the diagram). Currently we are usign our ADAPT2 [[CUMULATE protocol|cbum protocols]].
 ** The content application provides a service to list all the available content. This service implement the [https://github.com/PAWSLabUniversityOfPittsburgh/mastery-grids/blob/master/documentation/Content_Brokering_API_2016_01_21.pdf content brokering specification], which defines a JSON-format protocol to allow external applications to discover content.

← Older revision		Revision as of 18:06, 4 April 2016
Line 4:		Line 4:

	* To let Mastery Grids know the level of progress of the learners in the topics and the content, Aggregates call services from a User Model (UM in the figure). See point b) in the figure. These services are documented in [https://github.com/PAWSLabUniversityOfPittsburgh/mastery-grids/blob/master/documentation/User_State_protocol.pdf User State Protocol]		* To let Mastery Grids know the level of progress of the learners in the topics and the content, Aggregates call services from a User Model (UM in the figure). See point b) in the figure. These services are documented in [https://github.com/PAWSLabUniversityOfPittsburgh/mastery-grids/blob/master/documentation/User_State_protocol.pdf User State Protocol]
		+
		+	* The figure shows several different Content apps (QuizJet, QuizPet, Webex, etc.). Each of these applications are integrated in 2 ways:
		+	** The cntent application provides a service to list all the available content. This service implement the [https://github.com/PAWSLabUniversityOfPittsburgh/mastery-grids/blob/master/documentation/Content_Brokering_API_2016_01_21.pdf `content brokering].

	This architecture supports several kinds of open student modeling, social comparison, and recommendation. The architecture fulfills a major objective, portability, which is the ability to be integrated to other systems with little set up and modification. The architecture is modular and includes different software components as follows:		This architecture supports several kinds of open student modeling, social comparison, and recommendation. The architecture fulfills a major objective, portability, which is the ability to be integrated to other systems with little set up and modification. The architecture is modular and includes different software components as follows:

← Older revision		Revision as of 18:03, 4 April 2016
Line 1:		Line 1:
−	We developed an adaptive social learning architecture Aggregate to support [[Mastery Grids Interface]]. This architecture supports several kinds of open student modeling, social comparison, and recommendation. The architecture fulfills a major objective, portability, which is the ability to be integrated to other systems with little set up and modification. The architecture is modular and includes different software components as follows:	+	We developed an adaptive social learning architecture Aggregate to support [[Mastery Grids Interface]]. We design this architecture to integrate content from diverse sources. The explanation of the procedures and links to associated resources are given below.
		+
		+	* [[Mastery Grids Interface]] receives all the information to display (this is course structure, links to content and progress levels of the learner and the group of learners) from services hosted in Aggregate (a in the diagram). This information is passed in JSON format.
		+
		+	* To let Mastery Grids know the level of progress of the learners in the topics and the content, Aggregates call services from a User Model (UM in the figure). See point b) in the figure. These services are documented in [https://github.com/PAWSLabUniversityOfPittsburgh/mastery-grids/blob/master/documentation/User_State_protocol.pdf User State Protocol]
		+
		+	This architecture supports several kinds of open student modeling, social comparison, and recommendation. The architecture fulfills a major objective, portability, which is the ability to be integrated to other systems with little set up and modification. The architecture is modular and includes different software components as follows:

	*frontend user-system interaction interface, the [[Mastery Grids Interface]]		*frontend user-system interaction interface, the [[Mastery Grids Interface]]

← Older revision		Revision as of 17:54, 4 April 2016
Line 11:		Line 11:
	An overall architecture of the system can be sen in the following figure.		An overall architecture of the system can be sen in the following figure.

−	[[Image:~~architecture_v1~~.png~~\|1000x1500px~~\|Aggregate Architecture]]	+	[[Image:arch_v2.png\|Aggregate Architecture]]