Learning Object Repository Overview

Before instructors can use the LOR, administrators need to configure access and plan the rollout. These pages cover the privileges required for each role and a recommended adoption sequence.

• Required Privileges for the Learning Object Repository How to configure system privileges for managing the repository, uploading content, and inserting objects into courses. Start here if you're setting up access for custom roles.

• Learning Object Repository Adoption Plan How to plan and execute a phased rollout of the LOR at your institution, plus a sample email for communicating the repository's value to instructors.

Once access is configured, administrators create and maintain objects in the repository and manage how changes are distributed to courses. These pages cover the core management tasks.

• Add Objects to the Learning Object Repository How to create, upload, and copy objects in the repository.

• Manage Learning Object Repository Objects How to edit, move, delete, view associations, and edit order for objects in the repository.

• Sync Learning Object Repository Content How updates to repository objects are pushed to associated courses and organizations, including what syncs and how to manage sync behavior for students who need extended course access.

Instructors and course builders insert objects from the repository directly into their course content. Objects inserted from the repository are locked for editing, ensuring institutional content stays consistent across courses.

• Insert Learning Object Repository Objects Into Courses How instructors and course builders insert repository objects into courses and organizations, and what editing restrictions apply to the inserted objects.

If your institution uses Institutional Hierarchy, each node in your hierarchy has its own dedicated repository with its own access controls and content.

• Learning Object Repository and Institutional Hierarchy How the LOR works when Institutional Hierarchy is enabled, including how nodes map to repositories, how to delegate repository management to node administrators, and how courses access node-level content.

• Object: An object is a piece of content stored in the LOR. At this time, supported object types are learning modules, Documents, folders, and files. Objects are created, uploaded, or copied into the LOR by administrators and are inserted into courses and organization by instructors and course builders.

• Association: An association is made when an object in the LOR is inserted into a course or organization. The inserted object maintains a relationship with the original object in the LOR. Anytime the original object is updated, the changes are pushed to all associated objects. Associated objects receive the changes unless they're in a course that has ended or has been marked complete. New associations are also created when an object that originated from the LOR is copied. Users can perform a full course copy or granular copy and know that their copied objects also have a relationship with the original in the LOR.