Channels are shared spaces and their image fulfils the function of representing a learning area both in the list on the cover and in the header of the entity once it has been opened.
In channels, you can group sprints according to your needs and assign user groups directly to that channel. Sprints previously exceeded by the user of the assigned group will appear as exceeded, the rest will be available in your channel menu.
On the top bar we can sort and filter them, on the lower right we find a blue button with the '+' sign inside (New channel), here you can create your own channel.
When we create a new one we can edit 4 different configurations:
A. Name of the channel / pathway, it helps to order the channel alphabetically and will be part of what you are looking for in the magnifying glass icons.
B. Description, additional information to the channel name that is also used when searching for a channel.
C. Pathway activation switch, turns the channel into a pathway, if you need to know how a pathway behaves we explain it below.
D. Visible members, let students know (or not) the other users in their group who are in that same channel or pathway.
Once we press the NEXT button or hit the ENTER key it will send us to the SPRINTS window
E. Menu to add sprints to a channel / pathway, if we hit the blue button to add sprints we will go to the next screen.
H. Multiple choice column
I. Sprint Name Column
J. Compulsory column (only functional in Pathways)
K. Sprint start date column
L. Sprint end date column
(-REMEMBER- If a sprint has not started or is finished it will still be visible on the channel but cannot be completed by the student)
M. Sprint status column. PUBLISHED > Active to be carried out, UNPUBLISED > Momentarily not available for execution.
(-REMEMBER- Although the image shows Sprints without status (those in draft) from version 4.5.5 onwards these draft sprints will no longer be visible from here, only those published or those that have lost the publication status will be available to be added)
N. Filter by tags, here you can filter Sprints by selecting their tag.
O. Search by name or description
P. Button to add selected Sprints to the Channel/Pathway
Q. Browser between pages and selector of number of results shown.
F. Resources menu, second menu after entering the name and description Here, you can include your own links to external resources.
R. URL text box, it's where we add the address of the resource to use.
G. Members menu, last menu after the creation of the channel / pathway. Here we share the contents with the users depending on the groups they belong to
R. Groups column, shows us the names of the groups available to be added to our channel / pathway.
S. Subscription column, when activated we subscribe to the group within the channel /pathway.
T. Members column, shows the number of members in the group, if we double click on it, we see the user names of them.
U. Search by group name.
V. Button to save the changes.
What is a pathway?
A pathway is a grouping of sprints that gives an optional badge to the user who manages to meet the pathway's requirements.
What type of badge is awarded?
Pathway badges meet the same criteria as sprint or activity badges. In this case the system should be given extra verification, a badge that is being used on a Pathway in addition to a sprint or activity cannot be deleted.
How do you create a new pathway?
A pathway is always born from a channel (it is not a new entity, they are still channels). We will show a check to indicate that this channel is a pathway.
Once the pathway is created, a pathway can be optionally assigned a badge. In addition, the option to hide the members that belong to the pathway will be added, this option can be changed at any time.
Creating a pathway
The process of creating a pathway is done from the same screen as that of a channel, that is, from the channel listing screen on the "+" button located in the lower right area.
A pathway is always born from a channel (it is not a new entity, they are still channels). Instead of showing the switch to activate the order, we will show a check to indicate that this channel is a pathway.
Once the pathway is created, a completeness badge must be assigned. In addition we will add the option to hide the members that belong to the pathway, this option can be changed at any time.
We can also create a pathway from an already created channel by checking "Activate pathway" in the next screen.
Once this check has been chosen, the user will be shown a warning that it will not be possible to go back as the conversion between pathways and channels is one way. A channel can always be converted into a pathway, but a pathway can never be converted into a channel.
To go to the next point it will be necessary to select the masterbadge (optional) that we want to assign to the pathway completion according to the following screen.
Rules for obtaining the badge
Once the badge is assigned, the administrator will have to determine which of the sprints that make up the pathway are mandatory, these will be part of the rule for obtaining the pathway badge. That is, all sprints marked as mandatory must be performed.
Assigning Sprints to a Pathway
The administrator can add new sprints to a pathway through the same process as assigning sprints to a channel. The listing screen for pathways will be as follows:
For the assignment of sprints, we add sprints to a channel:
Once the sprints have been added to the pathway, we can select whether they are mandatory or not (only for this pathway) using the selector in the "Mandatory" column, according to the following screen:
By default the sprints will be added with the mandatory field to YES:
To perform this mandatory or not at pathway level, a new field should be generated in the Channel Entities(required) table that determines if it is or not necessary for the pathway completeness. In this way we can take advantage of all the existing logic already in the channel section and use that new field to solve the casuistry related to the ordering and completion.
Publishing a pathway
Once the pathway has been set up, the administrator selects the target groups and publishes the pathway. A pathway cannot be published where one of the sprints marked as mandatory is in the edit state, i.e. to publish a pathway all sprints marked as mandatory must be published or unpublished. Once a pathway has been published you cannot add, delete, change the order or assign mandatory status to the sprints that make up the pathway. For any change it will be necessary to unpublish the pathway.
Whether or not a sprint is necessary within a pathway will serve to determine the blocking of activities according to the following principles:
To complete a pathway the user must have completed (either inside the pathway or outside) all sprints that are marked as necessary.
The user decides whether or not to perform the sprints that are marked as not necessary.
The administrator can modify the need or not for a sprint on a pathway if he hides it beforehand.
The progress indicator is represented as:
% of mandatory sprints completed
completed sprints/N *100
In the event that a sprint included on a pathway has been completed at any time by the user, it will be taken as completed in the face of blockages on the pathway, according to the following:
If the sprint has been completed, is marked as required and is the next to be performed within the pathway, it will appear completed and the next required one unlocked
If the sprint has been completed, is marked as necessary and is not the next to go, it will be blocked. Once it is reached, it will appear as completed.
The progress calculation will take into account those that are completed regardless of whether they are blocked or not.
If the sprint has been completed and is not marked as necessary, it will appear as completed and if necessary it will enter into the progress calculation.
Sprint Sorting within Pathway
Sprint sorting within a pathway will be done directly on the listing screen by the process described in the following screens:
An administrator can reorder the sprints on a pathway by dragging and dropping on the Sprints list, provided that it has been previously hidden. The table filters will not be activated, since we will not have the option to sort within a pathway when the filters are activated.
Assigning users to a pathway
It follows the flow of user registration on a channel.
Delivery of Master Badge to user (Optional)
A user will earn a Master Badge when they complete 100% of the required sprints on a pathway or a % (see "Publishing a pathway" section) of the not required ones if none are required.
In the event of a dependency between pathways, the following will be done when the user enters the unlocked pathway (not in the background when winning the Master Badge that unlocks it):
If the user has all the sprints completed on the pathway, he will be assigned the corresponding masterbadge.
If the user has some of the pathway sprints completed, then the user will proceed as indicated in the "Modifying a pathway" section.
The user will be notified of the master badge by a background process that generates a notification for the topbar at the time the master badge is obtained to avoid problems with closing the channel screen without triggering the necessary events.
Modifying a pathway
Once published, the following actions will not be possible:
You cannot add new mandatory sprints or delete them
You can't change the order of the sprints
You cannot change the badge you award (if it exists, if it does not, it can be assigned as indicated below).
You can't change the type (mandatory/optional) of the sprints that make it up
If the administrator blocks the pathway, you will be able to perform the following actions:
That the pathway is "blocked" and members of the channel cannot access it
That the administrator can change the order of the sprints
That the administrator can add new sprints to the pathway.
That the administrator can change the mandatory nature of the sprints that make up the pathway.
The only change that can be made if the pathway is already published is to add a badge.
The user sees the pathway as any channel within the channel carousel. A special icon will be displayed for pathways.
Adding a progress indicator to the channel's home screen: When the user accesses the channel, he is visually placed on the first mandatory sprint not completed and all subsequent sprints are blocked.
Sprints that are not required for completion will appear as unlocked.
How is the user notified when a badge is obtained?
Badge notification can be done in the background and a notification section can be added to the topbar.
If we try to award the badge when progress is calculated (i.e. when the user leaves the sprint and returns to the channel screen having complied with the badge award rules) we risk that the user closes the browser without returning to the channel screen and the event is not triggered and the badge is therefore not awarded.
Messages to the user
Pathways with stages
As an administrator
The Pathways tool allows the creation of training itineraries by establishing blocks between Sprints to determine prerequisites between training content. From version 4.5.5 stages are established within Pathways.
Establishing stages allows to divide the training content and establish more flexible learning paths. Within each stage, at least one Sprint is required and there can be as many Sprints as we want. Stages establish blocks between each other. If you want to advance to the next stage you must have done (and completed) all Sprints marked as required in the previous stage.
In each stage there is no mandatory order for the completion of Sprints. Sprints can be performed in any order, only the order "recommended" by the administrator when establishing the list of Sprints will be part of a stage.
To change the order of the Sprints, simply drag & drop the Sprints to the desired position.
The Pathway may or may not have an associated badge that would be assigned after the Pathway is completed. If the requirements change during the process, i.e. if we increase the number of required Sprints or decrease the progress of the Pathway is calculated dynamically so that only students who have not completed the Pathway are affected.
As a student
A student when accessing their Pathway will see those Sprints belonging to the same stage unlocked and those belonging to a subsequent stage blocked.
As the students complete the Sprints, the next stages will be unlocked.
Students can view their progress and the Pathway badges any time.
One of the improvements introduced in this new release is that Sprints that belong to a pathway and are blocked, although they appear on the carousels, cannot be accessed.
Customer support service by UserEcho