Update the configuration of your D2L Standard CSV source system

Brightspace Learning Environment automatically defaults to your most common settings. However, these settings can be edited at any time with the appropriate permissions.

To update the configuration of your D2L Standard CSV source system:

  1. From the Admin Tools menu, select IPSIS Administration.
  2. Select the Configuration tab and update the configuration details as listed in the following sections.

SFTP Credentials

Each source system has its own unique SFTP credentials. These credentials can be found on the Configuration screen. D2L recommends generating a new password when you initially create your source system. SFTP credentials are used to upload files.

To generate a new password:

  1. On the Configuration tab click Generate Password.
  2. Record the Address, Username, and Password.
  3. Select Save Configuration.

Note: Once the page has been saved, the password is hidden and is not recoverable. Passwords can be regenerated. SFTP credentials must be updated when transferring zip to the SFTP.

Source System

  1. In the SIS Name field, enter the name of your SIS. It is recommended to keep this up to date.

Overwriting Brightspace

  1. Choose to allow, not allow, or sometimes allow the SIS to overwrite changes made in Brightspace Learning Environment.
  2. If you select sometimes allow, more granular configuration of what the SIS is allowed to overwrite is displayed.

People

SIS Role Mappings

This section contains freeform text fields to map SIS specific role names to Brightspace Learning Environment role names.

  1. To add additional SIS specific role names to map to Brightspace Learning Environment roles, click + Add Role.

Note: Instructor and Learner roles are included by default but they can be deleted.

Deletion

This section provides the three following options on how a DELETE command updates a user’s profile in Brightspace Learning Environment.

  • Do Nothing – the user mapping is deleted from IPSIS mappings, but the user remains unchanged in Brightspace Learning Environment.
  • Inactivate that user in Brightspace – the user mapping is deleted from IPSIS mappings and the user is marked inactive in Brightspace Learning Environment.
  • Delete the user from Brightspace – the user mapping is deleted from IPSIS mappings and the user is deleted from Brightspace Learning Environment. When a u is deleted in Brightspace Learning Environment that user's user progress is lost.

Map SIS entries to course and sections

This section provides the option to map SIS entries based on code to existing org units that were created outside of the SIS (manually, using bulk operations, or APIs). If mappings are turned off, duplicates may be created.

SIS Group Mappings: Freeform text fields to map SIS specific org unit names to Brightspace Org Unit Type names.

  1. Click + Add Org Unit Type to add additional SIS specific org unit type names.
  2. The following Org Unit Types are mandatory:
  • CourseOffering
  • CourseSection
  • CourseTemplate
  • Department
  • Semester

Note: Other Org Unit support requires manifest version 2.0.

Deletion

This section provides three options on how a DELETE command updates an org unit in Brightspace Learning Environment.

Do Nothing – the org unit mapping is deleted from IPSIS mappings, but the org unit remains unchanged in Brightspace Learning Environment.

Inactivate course offering – the org unit mapping is deleted from IPSIS mappings, the course offering is marked inactive in Brightspace. Requires all users to be unenrolled before the course can be marked inactive.

Delete the course or section – the org unit mapping is deleted from IPSIS mappings, the section, course offering, and enrollments are deleted from Brightspace Learning Environment.

Map SIS entries to course and sections

This section provides the option to map SIS entries based on code to existing org units that were created outside of the SIS (manually, bulk operations, API). If mappings are off, duplicates may be created.

Course Content

This section provides the ability to copy course content from a master course or a course template to the newly created course.

  1. Select Yes and choose one of the following:
  • Parent course template of the new course: Content is copied from the parent Course Template to the new child Course Offering
  • Sibling course where the Org Unit Code matches the parent template: Content is copied form a Master Course Offering to the sibling Course Offering when the Master Course Offering and Course Template share the same Org Unit Code

Departments, Semesters and Other Org Units

This section provides the option to map SIS entries based on code to existing org units that were created outside of the SIS (manually, using bulk operations, using APIs). If mappings are turned off, duplicates may be created.