Breadcrumbs

Course Learning Outcomes File

This file is optional and should only be utilized if you intend to provide Course Learning Outcomes (CLOs) via SFTP. It is recommended for institutions storing CLOs in their SIS or another third-party platform with easy export capabilities. If this does not apply, we advise manually entering CLOs for each Course/Activity or using the Bulk Export/Import Template within the platform.

As a best practice, refrain from sending the CLO File nightly as automated course revisions can impact some A&C Modules such as programs and data collections. It is ideal to provide the file only when necessary, such as just before each Semester/Academic year.

If you are in implementation, please discuss using this file with your implementation team, as most institutions choose an alternative method. If you are a current, in-service client, please reach out to the HelioCampus support team via our portal to make sure the functionality via the "EnableCLOImports" Feature Flag is enabled and prior to building your file to request that the import functionality be turned on for your platform instance. Our team will also provide you with an export of all existing CLOs for your review. Any row that does not have an exact code/XXXXXX match could potentially be duplicated and corrupt the data being collected. Please reach out to support@heliocampus.com if you have questions.

If you are sending this file, please reference the following article to understand how changes will be applied → CLO & PLO Files Validation

File Format:

Please note when creating the Data File in a text editor each column must be surrounded by double quotes and separated by a comma.

Example: "MatchType","SubjectCode", "CourseNumber", "CourseUniqueId", "CLODescription","ProcessDate"

Example File Name:

institution_clo.csv

Required Data

Data Field

Data Type

Required | Optional

Description

Impact

MatchType

String

Required

Matching type of the record

Needed for identifying which column to match (CLODescription will be used if blank):

  • MatchType = “code” (Institution must sent CLO Code for this logic)

  • MatchType = “description” (default matchtype)

SubjectCode

String

Required

Subject of the course; i.e. MATH, MEM etc.

Needed as part of the unique identifier

CourseNumber

String

Required

Course Number; i.e. 101, 700 etc.

Needed as part of the unique identifier

CourseUniqueId

String

Required

Unique identifier assigned to the Course

Used as unique identifier

CLODescription

String

Required

Course Learning Outcome Description

Example: Identify and summarize the connections amongst stocks and flows in the hydrosphere.

ProcessDate

datetime

Required

Date in which the data was extracted (exported) expected format: YYYY-MM-DD i.e. 2024-02-24

Needed to validate that consecutive data loads should update existing records

Optional Data

Data Field

Data Type

Required | Optional

Description

Impact

CLOCode

String

Optional

Course Learning Outcome Code

Example: 1-1, 2-5

If left blank in file, HelioCampus unique internal codes will be used

i.e “C1”, “C32”, “C450”, etc.

SortOrder

String

Optional

Order of the Course Learning Outcome

Course Learning Outcomes will be displayed in the UI based on this order. If providing Sort Order, please ensure that each CLO within a Course/Co-Curricular Activity has a unique value.

CourseLearningObjectiveType

String

Optional

Type of the Course Learning Outcome (Supported values are “Undergraduate”, “Graduate”, and “Undergraduate and Graduate”)

Used for display purposes. The value should match with the existing values in the platform

If a double quote needs to be used for the values, the escape character should be a double quote.

e.g., "This is a ""value"" with double quote."