What D2L's Open Content Catalog Actually Does
D2L OCC (Open Content Catalog) lets one Brightspace instance publish course content that other Brightspace institutions can import directly. It eliminates the traditional .SCOPE file shuffle. You sync once through institutional agreements and get a persistent connection between two learning management systems. I set up OCC cross-institutional sharing three years ago at a community college consortium. What looked clean in a demo environment got complicated once real student data and varying Brightspace versions entered the picture. Here is what I learned along the way.
Revolutionizing Education The Power Of D2l Occ
The Basic Setup Process
Start by confirming both institutions run compatible Brightspace versions. This matters more than anyone admits. A version mismatch between 11.1 and 11.2 breaks sync on modules with embedded H5P content. I spent six hours debugging what turned out to be a version incompatibility. Check your administration panel, note the exact build number on both sides, and confirm D2L has certified the versions to talk to each other. Next, navigate to Administration > Open Content Catalog in Brightspace. Enable the feature. You will see a section to define your content publishing rules. Set whether you want to share full courses, individual modules, or just course shell metadata. I recommend sharing only the modules you actually need. Publishing entire courses creates massive data transfer and confuses instructors who see unrelated material. After enabling publishing, generate your institution's unique catalog ID. Share that ID with the receiving institution's administrator. They enter it in their own OCC settings, establish a connection request, and approve it on your end. Once approved, the two systems are linked. This entire process takes approximately 45 minutes if both schools cooperate quickly. If IT departments drag their feet, it can stretch to two weeks.
Importing Content From the Catalog
The receiving institution goes to their course shell, selects Content Import, and chooses Open Content Catalog from the source dropdown. They search by course title, instructor name, or catalog ID. Results appear with basic metadata: course title, owner institution, last updated date, and module count. Select the modules you want and click Import. The system pulls the content, maps D2L activity types, and places everything into a staging area within your course shell. Do not skip the staging review. Imported content shows up with default due dates, sometimes inheriting release conditions from the original course that no longer make sense for your schedule. I had an instructor import a spring semester course into a fall offering and miss that three assignments had hard-coded due dates from the previous year. Took twenty minutes to fix, but nobody would have noticed until mid-semester.
Get the Full Details
Common Pitfalls That Nobody Warns You About
File paths in D2L do not always survive the sync cleanly. External links pointing to the originating institution's file storage become broken references on the destination side. Before publishing a course, audit all external URLs and replace institutional-specific paths with generic links or content that lives inside the LMS itself. Another issue: grade center mapping. When you import from OCC, the destination institution gets the column structure but not necessarily the grading weights or formulas intact. I discovered this the hard way when an imported course showed a perfectly organized grade book that assigned 40 percent weight to a participation column that had been recalibrated in the original course to 10 percent. The fix is simple: manually review grade center columns after every import, but you have to remember to do it. Version drift is real. If the sending institution updates Brightspace but the receiving school has not, the next sync will fail or produce corrupted module structures. Schedule sync windows during summer breaks or between academic terms whenever possible. Avoid syncing during active semesters unless you have tested the connection thoroughly on a sandbox course first.
When OCC Is Not the Right Tool
D2L OCC only works between Brightspace institutions. If your partner uses Canvas, Moodle, or Blackboard, this feature does nothing for you. The content migration path between different LMS platforms requires a completely different approach, typically involving QTI export imports or third-party migration tools. The catalog also depends on institutional willingness to share. Some schools publish almost nothing. Others treat their course content as proprietary and restrict sharing heavily. You cannot force a partner institution to publish useful material. Negotiate content availability as part of any partnership agreement before you invest time in the technical setup. There is also a bandwidth consideration. Large courses with embedded media files can take 15 to 30 minutes to import depending on your network. If you are importing several hundred modules across a consortium, plan for significant server load during the transfer window. I once watched a sync job stall for forty minutes because the source institution had an unoptimized video library running over 800 megabytes of course media.
A Practical Workflow That Actually Works
Create a master template course in your Brightspace instance with standardized module naming conventions, consistent release conditions, and placeholder content where receiving institutions should insert their own local material. Publish only this clean template through OCC. Instructors at partner schools import your template and customize it rather than importing messy live courses full of proprietary institutional content. Use a shared spreadsheet to track which partner institutions have active OCC connections, which courses are published, and when the last successful sync occurred. I maintain a simple internal document listing connection status, known version conflicts, and contact names at each partner school. When a sync fails, the spreadsheet tells me immediately whether it is a known issue or something new. Run a test import on a dummy course before asking any instructor to use OCC for a live class. Verify that all links resolve, grade center columns map correctly, and external media files display properly. The test takes about ten minutes and prevents approximately eighty percent of support tickets during the first month of use.
Technical Limits Worth Knowing
D2L OCC has a published limit on the number of modules a single course can expose through the catalog. The exact number varies by Brightspace version and institutional configuration, but I have seen it cap out around 250 modules per course in older releases. If your course library is larger than that, split the content across multiple catalog entries rather than trying to push everything through one course shell. Search indexing in the catalog is not real-time. Changes to published courses take between two and twelve hours to propagate through the catalog search. Plan your content updates accordingly. Do not assume that publishing a module means partner instructors can find and import it immediately. Sync logs are available but not particularly detailed. When an import fails, the error message usually points to a broad category like module mapping failure or media file unavailable. It rarely tells you which specific file or activity caused the problem. My workaround was to strip the course down to a single module and add modules back one at a time until the failing component surfaced. It was tedious but the only reliable method I found.
There is no built-in version control for imported content. If the source institution updates a module after you have already imported it, your copy does not automatically receive the changes. You must manually re-import or update the module yourself. This is by design but catches people off guard who expect a continuous content pipeline between institutions. The feature is functional and genuinely useful for consortia that already trust each other and want to reduce redundant course development work. It is not a magic solution for cross-platform content sharing or for institutions that have not standardized their Brightspace configurations. Use it where it fits and accept its boundaries rather than forcing it into situations where it was never going to work.
