The Brightspace Learning Repository Bulk Upload utility, also known as Bulk LOR Upload (BLU), enables you to upload many learning objects or assets into a Learning Object Repository (LOR) without using the LOR web interface. This is useful for publishing curriculum outlines, syllabuses, or defined assets from your document management system into a searchable repository for use within courses.
Note the following:
-
Learning Objects can be imported from a SCORM 1.2 compliant content package.
-
Assets can be created from any file type.
-
BLU can't be used to upload LMS Packages.
-
BLU doesn't allow publishing of URLs, Topics, Modules or QTI packages.
-
External metadata for an object or asset can be imported from an IMSMD 1.2.1 compliant XML file.
Enabling the Brightspace Learning Repository Bulk Upload utility
To enable:
-
Contact D2L Support to enable BLU in your learning environment. Share your desired schedule frequency for the BLU task (Once a day? Once a week?).
-
Two folders will be available under Organization Files > BLU after initial setup:
-
Inbox. Upload your files (PDFs, DOCs, Slides, etc.) into this location. Prepare a .txt file with a list of files to be processed. Sample snippet below:
-
Format: “Repository ID”, “Path and filename”, “Title”, “Description”, “Keyword”, “Role”, “FirstName”, “LastName”, “publish type”
-
LOR_Bulk_Upload.txt LoadType=CSVMetadata "1006","\\fs-cpledtest\cpledtest\WEB\Content\CPLED\BLU\Inbox\D2LBrightspace.png","ExampleTitle","ExampleDescription","ExampleKeyword","Instructor","NameFirst","NameLast",
-
Outbox. This where your files and log file will be located after BLU task runs. Check your logs to investigate the LOR import result.
Running the Brightspace Learning Repository Bulk Upload utility
The Bulk Upload utility normally runs as a scheduled task. It uses a configuration file that identifies the organization containing the repository that objects upload to, and the location of the directory containing the setup (input) files specifying the objects’ source. Each line in the setup file lists the path to a content package or asset file and the repository the file uploads to. Depending on the type of setup file, each line can also list the path to an external metadata file or provide a set of new metadata values to apply during import. The utility can also identify a specified image file and render it into a thumbnail that showcases the object in the LOR.
When the Bulk Upload utility finishes processing all the objects or assets in a setup file, it moves the setup file to the output directory specified in the configuration file and begins processing the next setup file. This process continues until all setup files are processed.
As the utility proceeds, it writes progress to a log file stored in the output directory. You can use the log file to verify that all objects are uploaded successfully.
To upload an asset or learning object to the repository:
-
Ensure that the asset file or content package containing the object is on the server and accessible via a file path (not a URL). If metadata for the asset or object is contained in a separate XML file, ensure that this file is also accessible via a file path.
-
Create a TXT setup file pointing to the asset file or content package and specify which repository to upload to (or add to an existing setup file).
-
Save the setup file in the input directory.
The asset or object uploads the next time the utility runs.
To change the timing of the scheduled task, contact D2L Support for assistance.
How the import interprets metadata at multiple levels in a manifest file
When using the Brightspace Learning Repository Bulk Upload utility, an object’s metadata can be located under multiple elements within a manifest file, depending on the type of object and whether the object is a sub-element in the file. If metadata for a single object is found under multiple elements, the following order of precedence is used: <manifest>, <organization>, <item>, <resource>.
For example, if you upload a content package consisting of a module with three topics, and there is metadata under the <manifest> element and under the highest <item> element, both are applicable to the module. The Bulk Upload utility takes the metadata from the <manifest> element and discards the metadata from the <item> element. If one of the topics in the package has metadata under its <item> element and also under the associated <resource> element, the metadata for the <item> element is used and the metadata for the <resource> element is discarded.