Note: You are currently viewing documentation for Moodle 3.1. Up-to-date documentation for the latest stable version of Moodle is probably available here: Publishflow Block : Global Settings.

Publishflow Block : Global Settings

From MoodleDocs

Back to index

Moodle Node Type

Chooses the publishing node type that this Moodle will adopt.

Options:

  • Standard: This Moodle acts as a Standard Moodle and will not be recorgnised as part of the publishing subnetwork.
  • Moodle Factory
  • Catalog
  • Combined Type (factory + catalog)
  • Learning Area
 Scope: All
 Default: Standard

Enable retrofeed of courses

Enables or disables the possibility to retrofit a course to a Course Factory in a Traning Center. This is a global switch that will entirely disable this feature even if your role has the capability of performing the action.

 Scope: Training Center
 Default: Yes

Local Data Storage

Files won't be distributed by network transfers but through the local file system. This option only works for moodles sharing the same storage area.

 Scope: Both sides of a course transfer must use the same storage protocol.
 Default: No

Allow Public Sessions

This parameter sets some accessibility option to the optional block Active Sessions that shows how many copies in activity exist in Training Nodes for a Catalog entry.

STATUS: This block is not yet published and needs some rework and optimisation.

Options:

  • Private sessions
  • Public sessions. User identity checked.
  • Public sessions. User unchecked.
 Scope: Training Center, effect in Course Catalog
 Default: Private sessions.

Receiving Course

Course for receiving course archive downloads. When tranfering a course archive, the publishing network needs to identify a physical location where to store the published archive. You may decide in which course file cabinet the archive will be stored.

On a Training Center platform, the deployed courses from a Catalog will be stored here. On a Course Catalog platform, published course archives will be stored there. On a Course Factory, retrofitted archives will be stored there.

Advice: You should not allow this course to be widely visible to users.

 Scope : Training Center, Course Catalog, Course Factory

Default Category for deployment

On a Training Center, deployed courses will not be yet given to use for users. The course needs to be opened after having being deployed. This prevents unpreprared settings to be accessible to users after deployment. You may designate a category in your target platform to which incoming courses are attached.

 Scope : Training Center

Active Category

Using the Publishflow built in Course Life Cycle control, you may open a course once properly setup. This setting allows you to define a catagory to move the course in when it is open.

 Scope : Training Center

Closing Category

Category for archived course sessions. When using the Publishflow built in Course Life Cycle controls and closing a course session, the course might be moved to a special archive category you can define here.

Main host prefix

Prefix of the Course Catalog platform. This is used by the Publishflow to recognize a Course Catalog within the Moodle network. This setting can be ignored if a network scan has been performed and a Course Catalog has been identified in the network.

 Scope: Course Factory
 Default: Empty

Factory prefix

Prefix pattern for finding course factory platforms in the Moodle network. This setting can be ignored.

 Scope: Training Center
 Default: Empty

Default role in incoming courses

This is the role that will be assigned to the user who initiates the course material transportation in the newly created course instance. This role is setup for incoming courses, that is, courses that are deployed in the current node. It will NOT affect the role you may be assigned to in remote platforms where you deploy from here.

 Scope: All nodes
 Default: No assignation