====== Usage ======
This page shows a usage example of the toolset, as a means to provide a better understanding of how the [[learningknowledgecycle|learning knowledge cycle]] is supported and to show the implemented user interface. It is assumed that the framework learner has access to the wiki and has already sign in with her credentials, which gives permission to view the documentation and use the [[components|components]].
===== Start your learning path =====
As depicted in Figure 1, the learner has access to a small menu on the top left side of the wiki. This menu allows her to signal she’s about to start her learning, so the system can begin capturing her navigation steps.
{{ :driver_ss_start_stop.png?500 |}}
Figure 1 - DRIVER menu when going from not capturing to capturing state.
After entering the capturing state, the system provides the following new actions to
the learner while she is browsing the wiki:
* **Stop your Learning Path**. Used to signal the system that she no longer wants her browsing steps to be captured. The system moves to the //not capturing// state and the menu resumes its previous set of actions.
* **Mark as Landmark**. This action enables the learner to mark a page as //of noticeable importance// to her learning experience. If she reaches a partial conclusion (not yet the final answer), or realises something important to her knowledge needs (that she wants to point out and share), this feature allows her to do so.
* **Ignore Page**. This action marks the current page as //non-capturable//, i.e., every time the user returns or browses through this page, it is not added to the existing browsing steps. This is useful if the learner is recurrently going through a certain page, probably because it is a central page with many links or an index page.
==== Learning trail ====
Besides these new actions, the learner is presented, in the top of the page and at all times, with a //trail// of the last steps she took (and that were captured) while browsing the wiki. These steps can have associated markings or icons, as explained in Figure 2.
{{ :driver_ss_trail.png?800 |}}
Figure 2 - Depictions of the DRIVER’s learning path trail of the last steps, explaining its constituent parts and icons.
Each cell or step is composed of an icon (optional) and the captured wiki page title. Both these elements are clickable anchors to their respective pages, so that the user can directly navigate to them. In the case of sections, the section title appears first, followed by an abbreviation of the page the section belongs to (subscript and bracketed). The tooltip shows the full name of the page.
==== Adding a section to the trail ====
Capturing a page being browsed is easy because the //dokuwiki// allows for the capturing of the navigation between wiki pages. The same is not true for sections. In the case of sections, the user has to manually mark the section as read. For this, each section has a //**like**// action link at the end of its contents. Consequently, the user can add that particular section to the captured learning path. Usually this enables parts of a documentation artifact to be emphasised, instead of the whole document. Later on, the learner can re-arrange the final learning path to indicate only these sections and not the whole document. This **//like//** action link only appears when the system is in //capturing// state (**Figure 3**).
{{ :driver_ss_section_like.png?500 | Adding a section to the trail.}}
Figure 3 - Adding sections to the learning path by hitting the like action link at the end of the section.
===== Filtering and storing =====
At any time during the //capturing// state, the learner can filter and store her learning path. For that purpose, she uses the **Prune/Graft** component, accessible by clicking on a tab on the right side of the wiki. This tab is visible at all times, despite the state the system. If the system is at a //not capturing// state, the available learning steps remain from the last capturing session.
The **Prune/Graft** component opens up on a different layer from the wiki itself, providing a set of features without conflicting with the current work session. The user interface can be seen in **Figure 4**.
{{ :driver_ss_prune_graft.png?800 |}}
Figure 4 - Prune/Graft component user interface, showing the main functionalities
As such, the following functionalities are allowed:
* **Drag and drop learning steps**. The user is presented with all the learning steps she took during the learning session((All steps so far (if still in //capturing// state) or all steps from last session (if in //not capturing// state).)). These can be dragged into a different area where she can compose the effective learning path she wishes to store and share. The steps can be re-arranged at will.
* **Preview learning step**. The learning steps can be previewed in an auxiliary pane so that the user can confirm, if her memory fails, the contents of that step. The user just have to open the preview pane (//Show Previewer// button on top of the page), click on the name of the step, which, at this point, loads that page into the pane. This functionality can be seen in **Figure 5**.
{{ :driver_ss_preview_lp_step.png?500 |}}
Figure 5 - Prune/Graft component user interface, showing the preview pane where the user can preview any step from his capturing session. The preview pane visibility can be toggled using the Show/Hide button on the top.
* **View similar existing learning paths**. While the user is dragging steps into the effective learning path area, the system automatically searches((Search results are sorted by similarity first, and rating, second.)) for similar learning paths that already exist in the knowledge-base. This allows the user to check for relevant discrepancies between the learning path she is building and existing others. If the system encounters an exact match of the learning path the user is constructing, it does not duplicate when saving. Instead, it will merge the tags the user assigns to her learning path with the existing ones. This functionality can be seen in **Figure 6**.
{{ :driver_ss_similar_lps.png?800 |}}
Figure 6 - Prune/Graft component user interface, showing similar learning paths when found. The user can toggle the showing of this list. The shown elements are the same as if doing a search (Search component, see below), except for the rating ability.
* **Tagging**. At the bottom of the page, the user can tag the effective learning path using, again, a drag and drop behaviour. She has a list of tags that were present in the captured wiki pages and from where she can drag the tags she wants to assign the learning path. There is also the possibility of adding new tags through a text box.
* **Save**. The user can save the effective learning path she has composed, tagged accordingly.
* **Save unprunned**. The user can save the learning path //as is//, i.e., exactly as it was captured, having only to tag it accordingly.
===== Searching and rating =====
The quickest way to access the knowledge-base of learning paths is to use the **Search** component. For that, the learner just have to open the respective tab (visible at all times) on the right side of the wiki, or clicking on the search option on the menu on the left sidebar.
The interface is quite simple and straightforward (see **Figure 7**), if you are used to the popular web search engines (Google((http://www.google.com)), Yahoo((http://www.yahoo.com)) or Bing((http://www.bing.com))). The user just have to enter((The text box where the tags are entered has an //auto-complete// feature that shows existing tags on the knowledge-base so that the user can maximise the hit ratio.)) the tags by which she wants to query the knowledge-base and the matched learning paths will be listed.
The search heuristics finds all learning paths that have those tags, where the learning paths with the most matched tags appear first, sorted descendent by rating.
{{ :driver_ss_search.png?800 |}}
Figure 7 - Search component user interface, showing results for a query with the tag start. There is also a depiction of all the elements present in a result item. The Show Previewer button works similarly to the preview functionality in the Prune/Graft component, showing a preview pane directly below the respective result item.
Each result item has 5 constituent elements:
* **Steps**. This shows the learning path steps, conveying to the standardised form of showing learning paths as depicted in **Figure 2**.
* **Tags**. On the top left corner of each result item, the tags associated with that learning path are listed, where the matched tags are shown in bold.
* **Overall rating**. On the top right corner of each result item, the overall rating of that learning path is shown. The rating value varies between 0 and 5 and follows a //star-like// graphical representation, complemented by its numerical value in brackets.
* **User rating**. On the lower right corner of each result item, the user can view and change her personal rating of that learning path. The //Rate// button commits the user’s rating, entered by using a similar star-like interface.
* **Previewer**. On the lower left corner of each result item, there is a //Show Previewer// button that allows the user to preview the steps of the learning path, similarly to the same operation on the Prune/Graft component. The only difference is that the preview pane appears below the respective learning path.
As such, the Search component not only allows finding a suitable learning path, but enables the community to give their feedback on the usefulness of the learning paths, improving the effectiveness of the learning knowledge.
===== Recommending =====
While in the //capturing// state, the system can provide the learner with directions on possible next steps in her learning path. This is done using the **Hint** component in **Figure 8**. The user has access to a tab at the top of the page that slides open to show a list of recommended next steps, based on the existing learning paths in the knowledge-base.
The list item is composed of clickable links to the page or section to where the user can directly navigate. Prefixed to each item is the number of learning paths (in brackets) that have the current page as the previous step.
{{ :driver_ss_hint.png?800 |}}
Figure 8 - Hint component user interface, showing recommended next steps, based on the current location of the user. The picture shows the hint tab located at the top of the page on a closed state and then on an opened state.
This enables the learner to rely on the knowledge captured from the community to assist on her learning process. Generally, this only happens when the learner is at a loss, and seems to be //disoriented// in her quest for knowledge that might help her. The common behaviour is to fall back to the last //known// point, i.e. documentation artifact that appears to lead somewhere, and try to proceed from there. The Hint component can, then, provide an //educated// guidance to possible solution directions. Of course, if the learner is hacking her way into //virgin land//, i.e. paving new learning directions, the Hint component won’t be of much use.
[[start |< back to start page]]