Community hub - Revision history

Sarjona: This page will not be migrated to new devdocs

2025-02-10T08:01:20Z

This page will not be migrated to new devdocs

← Older revision		Revision as of 08:01, 10 February 2025
Line 1:		Line 1:
			{{Template:WillNotMigrate}}

	{{Moodle 2.0}}		{{Moodle 2.0}}

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

2021-07-14T13:22:08Z

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

← Older revision		Revision as of 13:22, 14 July 2021
Line 216:		Line 216:

	community block database structure:		community block database structure:
	{\| class="~~nicetable~~"		{\| class="wikitable"
	\|-		\|-
	! Name		! Name

Jmouneyrac: /* Harvest courses */

2010-09-02T01:25:06Z

Harvest courses

← Older revision		Revision as of 01:25, 2 September 2010
Line 281:		Line 281:

	== Harvest courses ==		== Harvest courses ==
	'''NOT IMPLEMENTED ~~- TO DO - TO BE DEFINED~~'''		'''NOT IMPLEMENTED'''
	''Note: site to hub communication is one way only''		''Note: site to hub communication is one way only, the following text may change.''

	Each hub will use cron to call every site that has registered a harvesting url on a periodic basis. This will be done at the same time as the link is checked to ensure the site is reachable, so the "time link was last checked" field in the site table also indicates when the site was last harvested.		Each hub will use cron to call every site that has registered a harvesting url on a periodic basis. This will be done at the same time as the link is checked to ensure the site is reachable, so the "time link was last checked" field in the site table also indicates when the site was last harvested.

Jmouneyrac: /* Harvest courses */

2010-09-01T04:04:17Z

Harvest courses

← Older revision		Revision as of 04:04, 1 September 2010
Line 282:		Line 282:
	== Harvest courses ==		== Harvest courses ==
	'''NOT IMPLEMENTED - TO DO - TO BE DEFINED'''		'''NOT IMPLEMENTED - TO DO - TO BE DEFINED'''
			''Note: site to hub communication is one way only''

	Each hub will use cron to call every site that has registered a harvesting url on a periodic basis. This will be done at the same time as the link is checked to ensure the site is reachable, so the "time link was last checked" field in the site table also indicates when the site was last harvested.		Each hub will use cron to call every site that has registered a harvesting url on a periodic basis. This will be done at the same time as the link is checked to ensure the site is reachable, so the "time link was last checked" field in the site table also indicates when the site was last harvested.

Jmouneyrac: /* Harvest courses */

2010-09-01T04:02:12Z

Harvest courses

← Older revision		Revision as of 04:02, 1 September 2010
Line 281:		Line 281:

	== Harvest courses ==		== Harvest courses ==
			'''NOT IMPLEMENTED - TO DO - TO BE DEFINED'''
	Each hub will use cron to call every site that has registered a harvesting url on a periodic basis. This will be done at the same time as the link is checked to ensure the site is reachable, so the "time link was last checked" field in the site table also indicates when the site was last harvested.		Each hub will use cron to call every site that has registered a harvesting url on a periodic basis. This will be done at the same time as the link is checked to ensure the site is reachable, so the "time link was last checked" field in the site table also indicates when the site was last harvested.

Jmouneyrac: /* Publish courses */

2010-09-01T04:01:16Z

Publish courses

Jmouneyrac: /* Site registration */

2010-09-01T03:55:43Z

Site registration

← Older revision		Revision as of 03:55, 1 September 2010
Line 195:		Line 195:

	# choose one or more Hubs to register with (hub.moodle.org and/or others in the Hub List, or directly to a particular Hub specified by URL)		# choose one or more Hubs to register with (hub.moodle.org and/or others in the Hub List, or directly to a particular Hub specified by URL)
	# choose to enable cron to re-send statistics to the hub on a periodic basis. (TODO)		# choose to enable cron to re-send statistics to the hub on a periodic basis. (TODO/TBD)
	# choose to enable the hub to harvest courses on a periodic basis (TODO: not shown on image)		# choose to enable the hub to harvest courses on a periodic basis (TODO: not shown on image/TBD)

	Each Moodle.org Hub will perform a check every week to verify that each site is accessible and optionally to harvest the courses from that site. Sites that fail two or three checks in a row will be disable in the Hub listing.

	== Community membership ==		== Community membership ==

Jmouneyrac: /* Site registration */

2010-09-01T03:53:41Z

Site registration

← Older revision		Revision as of 03:53, 1 September 2010
Line 195:		Line 195:

	# choose one or more Hubs to register with (hub.moodle.org and/or others in the Hub List, or directly to a particular Hub specified by URL)		# choose one or more Hubs to register with (hub.moodle.org and/or others in the Hub List, or directly to a particular Hub specified by URL)
	# choose to enable cron to re-send statistics to the hub on a periodic basis.		# choose to enable cron to re-send statistics to the hub on a periodic basis. (TODO)
	# choose to enable the hub to harvest courses on a periodic basis (TODO: not shown on image)		# choose to enable the hub to harvest courses on a periodic basis (TODO: not shown on image)

Jmouneyrac: /* Course global search functionality */

2010-09-01T03:48:01Z

Course global search functionality

← Older revision		Revision as of 03:48, 1 September 2010
Line 188:		Line 188:

	== Course global search functionality ==		== Course global search functionality ==
	In order to quickly search a course on all public hubs, Moodle.org will have a table equivalent to the course 'directory' table with dew additional field as "public hub id'', "site url", "site name"...		In order to quickly search a course on all public hubs, Moodle.org will have a table equivalent to the course 'directory' table with dew additional field as "public hub id", "site url", "site name"...

	== Site registration ==		== Site registration ==

Jmouneyrac: /* Course global search functionality */

2010-09-01T03:47:35Z

Course global search functionality

← Older revision		Revision as of 03:47, 1 September 2010
Line 188:		Line 188:

	== Course global search functionality ==		== Course global search functionality ==
	In order to quickly search a course on all public hubs, Moodle.org will have a table equivalent to the course 'directory' table with dew additional field as ~~'''~~public hub id'', "site url", "site name"...		In order to quickly search a course on all public hubs, Moodle.org will have a table equivalent to the course 'directory' table with dew additional field as "public hub id'', "site url", "site name"...

	== Site registration ==		== Site registration ==

← Older revision		Revision as of 04:01, 1 September 2010
Line 249:		Line 249:

	== Publish courses ==		== Publish courses ==
	'''Publish course''': to publish or update the description of the current course in one or more Hubs ~~(admins only)~~		'''Publish course''': to publish or update the description of the current course in one or more Hubs

	The '''Publish''' button only exists if the current user has the appropriate capabilities and if the current Moodle site has been registered with a Hub.		The '''Publish''' button only exists if the current user has the appropriate capabilities and if the current Moodle site has been registered with a Hub.
Line 256:		Line 256:

	Choosing "Publish" goes to a script where you can chose from the registered Hubs and whether you want to publish the course as:		Choosing "Publish" goes to a script where you can chose from the registered Hubs and whether you want to publish the course as:
	* enrollable, so that others can come here and use the course where it is, and/or		* enrollable/advertise, so that others can come here and use the course where it is, and/or
	* downloadable, so that a Hub can offer this course for download to others		* downloadable/share, so that a Hub can offer this course for download to others

	If the user wants to offer this course for download, then they are directed to the standard backup process to create and define the backup file (without users!). If the backup is successful the zip is stored in a standard place and then the user is returned to the publish script to continue. (If downloads are not required then this whole step is skipped).		If the user wants to offer this course for download, then they are directed to the standard backup process to create and define the backup file (without users!). If the backup is successful the zip is stored in a standard place and then the user is returned to the publish script to continue. (If downloads are not required then this whole step is skipped).
Line 265:		Line 265:
	Now the script presents a form with metadata that this course will be published with on the chosen Hub(s) (this is also available in the course settings page). Metadata includes information such as description, licensing, categories, screenshots etc (see the [[#Courses\|Courses]] section above for more info).		Now the script presents a form with metadata that this course will be published with on the chosen Hub(s) (this is also available in the course settings page). Metadata includes information such as description, licensing, categories, screenshots etc (see the [[#Courses\|Courses]] section above for more info).

	After checking/updating the metadata, the script will push the data to the selected Hub~~. The Hub will bounce back a confirmation which gets saved locally as the "Last publish date" for that course~~.		After checking/updating the metadata, the script will push the data to the selected Hub.

	If the checkbox to allow download was selected, then the URL to a course ~~download~~ script in the current Moodle is included with the metadata. This URL contains a token (eg an MD5 stored in the course table) that only the Hub knows.		If the checkbox to allow download was selected, then the URL to a course upload script in the current Moodle is included with the metadata. This URL contains a token (eg an MD5 stored in the course table) that only the Hub knows.

	The course ~~download~~ script (eg /~~course~~/~~download~~.php?id=55&~~secret~~=XXXXX) will ~~send~~ the cached .zip file for the given course.		The course upload script (eg /local/hub/webservice/upload.php?id=55&token=XXXXX) will expect the cached .zip file for the given course.