ELIS 2013 Manual

ELIS Data Hub 2

Batch Import/Update of Track Information

On the Course fields tab you can set the track properties for your import. Because the course.csv file can create five different ELIS items - courses, classes, programs, tracks, and user sets, the file mapping contains more information. Go to the Administration block > Site Administration > Plugins > Local plugins > Data Hub plugins > Version 1 ELIS import > Field mapping > Course fields tab.

Course fields tab

Course field mapping table image 2

If you make changes to any property values, be sure to select the Save changes button.

The following table has the standard course fields that can be included in the track import files. ELIS custom fields can also be included.

action: The action field is always required. Enter create, update, or delete.
context: The context is always a required field. Enter track.
idnumber: The track idnumber is a required field. This value must be unique.
name:
This is a required field for track creation. Enter the name of the track.
description:
The description of the track if it has one.
startdate:
The startdate of the track. The new format is MMM/DD/YYYY, e.g., Jan/01/2014. Formats from previous versions of Data Hub will work as well, MM/DD/YYYY
enddate:
The date the track ends.
autocreate: Auto-create the classes of the track - a class for each course in the program the track is an instance of. Enter 1 to auto-create classes and 0 or leave blank if classes won't be auto-created.
assignment:
The idnumber of the program/curriculum the track is assigned to.

The required fields for track creation are:
  1. action
  2. context
  3. idnumber
  4. name
  5. assignment

The required fields for updating or deleting tracks are:

  1. action
  2. context
  3. idnumber
Note: For auto-created classes of a track to be automatically set to auto-enroll, the course descriptions the classes are instances of must be set to required in the program. So when a program has course descriptions set to required, track instances of that program will have auto-created classes automatically set to auto-enroll. Class instances auto-created for course descriptions that are not required will have auto-enroll set to No.

ELIS Data Hub tells ELIS what needs to be done with imported data via the Actions column. The sample csv file below illustrates this function. The following example is a course file with all 5 course contexts being added. Row 5 is adding a track with the auto-create field set to no.

Image of course csv file

Select this link to download the file in the previous image.

Note: The two Moodle template courses identified in the course "link" field have to be added to the site before the file will run successfully. To run the file without adding Moodle template courses delete the four values in the "link" column.

Importing/Processing Data Hub Files


ELIS Data Hub import files can be scheduled to automatically process or can be manually processed. Import files should be scheduled to process in most instances, docs for scheduling imports are at this link. Manual processing should be used for testing small files only. Manual processing is currently limited to 28 seconds of processing time in our standard Data Hub installs. Scheduled processing will continue imports on subsequent cron runs when processing takes to long, manual processing does not do this.

The sample file being used here is simple enough to process manually. To manually process files go to the Administration block > Site Administration > Plugins > Local plugins > Data Hub plugins > Manage Plugins. Under the Import Plugins section go to the Version 1 ELIS import row and select the "Go" link in the Run manually column.

Manually run job link

Select the "Choose a file" button. Select a file to process and then select the Run Now button.

Manually run job

Once the file is processed there will be a brief log message stating whether or not the file import was successful.

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 Data Hub script runs. Logs can be accessed from the Administration block > Site Administration > Reports > Data Hub logs link.

For information about scheduling imports to automatically process go to this page Importing/Processing files.