Brightspace LeaP is an adaptive learning tool that builds personalized learning paths for learners. When you enable connections to Brightspace LeaP from Brightspace, users can access Brightspace LeaP over a secure (HTTPS) connection.
Brightspace LeaP creates learning paths based on course-specific, standard, or school-specific learning objectives. It uses content taken from the course to teach the objectives, and questions exported from the Question Bank to assess mastery of the objectives. It determines and recommends the most effective content per learning objective, guiding learners through content that adapts to their personal strengths and weaknesses as they interact with the tool.
You can use Brightspace LeaP in different ways:
- As a primary source of learning: You can create modules to be personalized learning paths with Brightspace LeaP. In this case, you do not enable pre-tests, and all learners are initially presented with a default learning path to review, like a typical content module. Personalization begins once learners take their first test.
- As review/test preparation: You can include Brightspace LeaP as the last item in a static content module so that learners can review and check their understanding of the material in the module.
- As remediation: You can direct learners to Brightspace LeaP when they are having problems. In this case, you may find it helpful to enable pre-tests and hiding the mastered content to ensure that Brightspace LeaP is delivering content only for the objectives the learner is having trouble with.
Requirements
Brightspace LeaP is not included with Brightspace Core. Clients must purchase the Performance+ package to access the LeaP tool.
Instructors require the following permissions to use LeaP:
Tool
|
Permission
|
Level
|
| Learning Objects Repository (LOR) |
Search the Learning Objects Repository |
org + course offering |
| |
Retrieve Objects in the Learning Objects Repository |
org + course offering |
| |
Create links to Objects in the Learning Objects Repository |
org + course offering |
| |
View Objects in the Learning Objects Repository |
org + course offering |
| Remote Plugins |
See Remote Plugins |
course template + course offering |
| External Tools |
Manage External Learning Tools Configuration |
course template + course offering |
| |
Launch External Learning Tool Links |
course template + course offering |
Visual tour of the LeaP tool
What types of content can I use in Brightspace LeaP?
If you want to use Flash or SCORM content, you may need to manually adjust or break down the content first.
|
Learning Management System (LMS)
|
Type of content added to the LMS
|
Notes
|
Relative links in HTML files work?
|
Linked URLs in the file also added to Brightspace LeaP as separate items of content?
|
|
|
Content file pointing to a non-text binary file (for example, JPG, PNG, Video)
|
The content is added as an item. Only the title text is used for mapping and indexing.
|
|
|
|
Brightspace
|
Content file pointing to the main HTML page of a website within the course files
|
This is the same as making a file type that points to the main index page of the website. Only the linked, main page is indexed and added to Brightspace LeaP. Other pages and associated files are skipped.
|
Yes
|
No
|
|
|
Content file pointing to a non-text binary file (for example, JPG, PNG, Video)
|
The content is added as an item. Only the title text is used for mapping and indexing.
|
|
|
| LTI |
Content file that is only available by using an LTI link |
Most often, LTI links provide access to content hosted by a publisher. |
Yes |
No |
|
Moodle
|
Content file pointing to the main HTML page of a website within the LMS course files
|
All files of a website are added and Brightspace LeaP decides which files to index.
|
Yes
|
No
|
|
|
Content file pointing to a non-text binary file (for example, JPG, PNG, Video)
|
The content is added as an item. Only the title text is used for mapping and indexing.
|
|
|
|
|
HTML file contained in a website but not explicitly added as the main file
|
The content is indexed and added. The < title > tag is used to fetch the content item title instead of the file name.
|
|
|
|
|
Non-HTML file (for example, PDF) contained in a website but not explicitly added as the main file
|
The content is indexed and added if it is on the accepted types list (.txt, .htm, .html, .doc, .pdf, .rtf, .xml, .docx). The Moodle link name is used as the content item title, not the file name.
|
|
|