Kora Transition Overview for users with Classic CSV import experience.

Version: Kora Courses, July 2023 or later
Permissions required: Administrators


Digication administrators have the ability to batch-create and update users, courses, and registration using a CSV import file. These CSV files can be imported manually using the administration UI or through automated uploads. Digication Kora features an improved CSV import with some new functionality. 

The CSV imports for Kora must be used when a school moves to Kora. The deadline for moving to Kora is September 1, 2024. However, schools can opt to move to Kora immediately. 

Documentation for Kora CSV Imports

What's New?

  • The three import files - User, Course, and Registration - must now be imported separately.
  • There is no longer a required order for the columns in the import files.
  • The column headers must be included in the import file for upload.
  • When you upload your CSV using the admin interface, you can preview a few rows and adjust mapping as needed.
  • Additional metadata fields are now supported in the same import files (noted below).

What’s New - User Import

  • You can choose to automatically notify users when their accounts are created via the User import using an email notification template. Only newly created accounts will be notified.
  • Fewer required columns make it easier to do common user management tasks.
       Creating new users only requires:
        • First name 
        • Last name 
        • Username
        • Sync ID is no longer required, but is recommended

        Updating or deleting existing users only requires:

        • Sync ID or field mapped as a unique identifier (such as username or email)

The following outlines the differences between fields used in the Classic CSV import file in comparison to the Kora import file.

Classic Import Field Kora Import Field Notes
Field Name Required Field Name Required  
A. SyncID Yes Sync ID

No (for create)


Yes (for update) 

Sync ID is no longer a required field in Kora. However, it is recommended if you intend to have SSO, LTI, or other integration.
B. First Name  Yes First Name

Yes (for create)


No (for update)

First Name is no longer required when updating an existing user.
C. Last Name  Yes Last Name

Yes (for create)


No (for update)

Last Name is no longer required when updating an existing user.
D. Password Yes Password

No

(Not recommended)

Password is no longer a required field in Kora. We do not recommend using the password field.
E. Username  Yes Username

Yes (for create)

No (for update)

Username is no longer required when updating an existing user.
F. Email  Yes Email No In Kora, you can choose to map the Email field as the sync ID.
G. Show Image  No Show Image No  
H. Major  No Major No  
I. Graduation - Date of graduation (yyyy-mm-dd). No Graduation No Graduation in Kora must be formatted as YYYY-MM-DD
J. Faculty  No

This field has been deprecated. 

See the ROLE  fields

   
K. Website  No Website No  

L. Active 
Yes Active No In Kora, the default value for the active field is 1 (active).
M. Birthdate No This field has been deprecated.    
N. COPPA  Yes COPPA - This field now has two options: Age under 13 with parental consent or Age 13 or older. This field is optional.  No In Kora, if this field is left empty, the user will be asked to verify that they are Age 13 or older when they accept the terms and conditions upon first login.
O. Update  Yes This field has been deprecated. See ACTION column    
P. Delete  Yes This field has been deprecated. See ACTION column    
NEW COLUMN   Action:
  • Add only (Default)
  • Add or update 
  • Add or update (Ignore if exist)
  • Add or update (Skip if blank)

  • Update only 
  • Update only (Ignore if exist)
No The Action column in Kora replaces the Update and Delete columns in Classic.  This column will determine how Digication processes the data in the import file and provides additional options for updating user account information.These additional options give administrators more flexibility for updating user account information. The sync ID is the only required field when updating existing users.
New column   Role: Admin No In Kora, each user role option has its own column. To change Admin role for this user, enter “Add” or “Remove”
New column   Role: Faculty No In Kora, each user role option has its own column. To change Faculty role for this user, enter “Add” or “Remove”
New column   Role: Student No In Kora, each user role option has its own column. To change Student role for this user, enter “Add” or “Remove”
New column   Role: Alumni No In Kora, each user role option has its own column. To change Alumni role for this user, enter “Add” or “Remove”
New column   Enable Notification No

This is a new feature in CSV imports for Kora. This column enables you to send an email notification to new users upon account creation.


You can decide on a per user basis whether or not to send a welcome email.


Only newly created users will be notified. There is no way to email existing users through this CSV import


If you do not want to email the user, leave this column  blank.


1 (Enables Notification Email)


0 (Disables Notification Email)

New column   Custom Group No

In Kora, group management is handled via the user import. 


Enter “Group:Your Group Name” to create the group, and enter “Add” to add a user to the group and “Remove” to remove a user from an existing group.

New column   Custom Admin Group No

In Kora, admin group management is handled via the user import. 


Enter “Admin:Your Group Name” to create the group, and enter “Add” to add a user to the group and “Remove” to remove a user from an existing group.

New column   Custom Metadata No

In Kora, user metadata is now handled via the user import.

This column enables you to create a column for user metadata and add metadata for individual users.

The title of the column identifies the metadata category, and the value in each cell is the metadata being added for the user.


Title example Metadata: Credit Hours


Cell value example:
20
 


What’s New - Kora Course Import

  • You can import assignments by course ID.
  • You can import assignments by assignment ID.
  • You can enable self-enrollment for Kora courses
  • You can set a self-enrollment password for Kora courses.
Classic Import Field Kora Import Field Notes
Field Name Required Field Name Required  
SyncID 
Yes
SyncID

No (for create)


Yes (for update)

In Kora, syncID is only required when updating or deleting an existing course.
Course Type  Yes Course Type No In Kora, the default value for Course Type is COURSE.
Title  Yes Title

Yes (for create)

No (for update)

 
Course Number  Yes Course Number No  
Description  No Description No  
Active  Yes Active No In Kora, the default value for the active field is 1 (active).
Start Date  Yes Start Date

Yes (for create)

No (for update)

Start Date in Kora must be formatted as YYYY-MM-DD
End Date Yes End Date

Yes (for create)

No (for update)

End Date in Kora must be formatted as YYYY-MM-DD
Gradebook  Yes This field has been deprecated.    
Attendance  Yes This field has been deprecated.    
Update  Yes This field has been deprecated. See ACTION column  

Delete Yes This field has been deprecated. See ACTION column    
Discussion Yes This field has been deprecated.    
e-Portfolios  Yes This field has been deprecated.    
Assignments Yes This field has been deprecated.    
Standards Yes This field has been deprecated.    
Section Number  No Section Number No  
Department Code  No Department Code No  
New column  

ACTION - This column will determine how Digication processes the data in the import file. These additional options give administrators more flexibility for updating course information: 

  • Add only (Default)
  • Add or update 

If the course exists, the record will be updated with the data on the file.

  • Add or update (Ignore if exists)

If the course exists, the data will not be overwritten with the data on the file.

  • Add or update (Skip if blank)

If a field is empty, the import will skip that field. Existing fields will be updated with the data on the file.

  • Update only 
  • Update only (Ignore if exists)
No The Action column replaces the Update and Delete columns in Kora and provides additional options for updating course information. The course sync ID is the only required field when updating existing users. 
New column   Import Assignments Using Assignment ID No In Kora, you can import existing assignments into your course using the assignment ID.
New column   Import Assignments Using Course ID No In Kora, you can import assignments from another course in the system using that course’s sync ID.
New column   Custom Metadata No

In Kora, course metadata is managed via the course CSV import. 


This column enables you to create a column for course metadata and add metadata for individual courses.


Example: 


Title example Metadata: Major


Cell value example:
Biology


New column   Self Enrollment No In Kora, you can enable self-enrollment for courses via the course CSV import. 
New column   Self Enrollment Password No In Kora, you can set a password for a self-enrollment course via the course CSV import.


What’s New - Registration Import

  • If your import file consistently includes all current users, you can now enable “Overwrite Registration Data” and choose to drop users who are no longer in the import file.
Classic Import Field Kora Import Field Notes
Field Name Required Field Name Required  
Course SyncID  Yes Course Sync ID Yes  
User SyncID  Yes User Sync ID Yes  
Faculty  Yes Faculty Yes  
Delete  Yes This field has been deprecated. See ACTION column    
New Column   ACTION - This column will determine how Digication processes the data in the import file. 
  • Enroll
  • Unenroll
  • Unenroll (Ignore if manually added)
Yes In Kora, the action column replaces the delete column and also determines how Digication will process the registration data in the CSV import.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.