ELIS 1.9 Manual

ELIS Data Hub

Importing and Processing files

Importing/Processing Data Hub Files

The 'Import file location', specified in the Data Hub block settings, is where the files should be uploaded for processing by Data Hub. To complete the import process for the example above I will follow these steps:
  1. Name the CSV file, for this example it's named 'enroll.csv'. Make sure the file name shown on the Enrollment tab screen is the same, enroll.csv.
  2. Load the file to the 'Import file location' via SFTP. The files here are automatically processed every 10 minutes, the timing is configurable.
  3. To process the file immediately, select the Save and Process button from the bottom of the screen on the Enrollment tab.
A complete log of all actions is kept in the logs file, as well as (optionally) emailed to an address or addresses each time the DH script runs. The log file location is shown on the settings screen for the Data Hub block.

Log File Link

Once the file is processed there is a "log file" link. This opens a screen with a brief description explaining the action taken for each record in the file.

If you are receiving errors while trying to process files, it can be be for a number of different reasons. The error message should help explain where there is an issue.

The following is an example of an error message displayed in the log file link, "error with record 1: unable to find record".

This is an error message for an enrollment file. A user should have been enrolled as the instructor for a class, but the class record could not be found. The error was caused by a spelling mistake with the ELIS class name. Since the class name was spelled differently in ELIS than in the enroll file, the file being processed could not find the record of the class.

When assigning users to tracks in ELIS, the user is auto-enrolled in the curriculum the track is an instance of.

There is also use case to add users to tracks and auto-enroll them in the curriculum the track is an instance of with Data Hub Basic, the docs for that use case are here.