About the Brightspace Learning Repository Bulk Upload utility

The Brightspace Learning Repository Bulk Upload utility enables you to import multiple learning objects or assets into a Learning Object Repository (LOR) without having to upload each one individually.

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 files 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.

Note the following:

  • Learning Objects can be imported from a SCORM 1.2 compliant content package.

  • Assets can be created from any file type.

  • External metadata for an object or asset can be imported from an IMSMD 1.2.1 compliant XML file.