Faculty180 Auto Upload Information

The content in this knowledge base is based upon the standard FACULTY180 environment. Your institution may have made changes to configure the FACULTY180 environment to meet your institution's needs; therefore, the screens in your FACULTY180 environment may differ slightly from the knowledge base. For more information, please contact your FACULTY180 administrator.

Time of Import

Imports will be executed at 3:30 AM EDT / EST daily  if no data is found, then the import will not occur.

Upload Configuration

If applicable (Courses Taught, Faculty, Courses, etc), the upload configuration will be based upon the current configuration in your system. If your system’s configuration is expected to change for manual uploads then pass along your desired configuration to Faculty 180 and we will lock all uploads to utilize the requested configuration for that upload type.

Note: Custom uploads (Grants, advising) will not be affected. They have their own configuration.

File Location

All files will be located in a directory created by Faculty 180. Each database will then have a subdirectory under the ​autoload ​directory. (For example, /autoload/databasename/ and /autoload/databasename_dev/)

The contents of each database directory should only contain text files. This means, there should not be any of the following formats: .doc, .docx, .pdf, .xls, .xlsx, subdirectories, etc. The file types accepted are .csv and .txt.

  • For sandbox and tests: /autoload/databasename_dev/
  • For production : /autoload/databasename/ 

Notification

Each directory under /autoload/ will have a file titled notification.txt. This file will hold, one per line, the email addresses of people who should be notified upon completion of auto upload processing. These emails will contain information on the upload, including counts of new, duplicate, and failed records as well as a list of lines that were duplicate or failed. Emails in this file could include FACULTY180 administration or the entity that creates files for automatic upload.

File Naming

  • Faculty180_<upload_type>_<yyyy>-<mm>-<dd>_<sequence>.csv
    •  Faculty180_CoursesTaught_2015-08-11_01.csv
      • This indicates a Courses Taught file to be uploaded and was the first upload file of this type received on 2015-08-11
      • If a second Courses Taught was to be sent on the same day, we cedatrcedarwould expect: Faculty180_coursestaught_2015-08-11_02.csv
    • Available upload types will include the following: 
Supported Import <upload_type> Example Filename
Faculty faculty faculty180_faculty_2019-08-11_01.csv
Faculty Classifications facultyclassifications faculty180_facultyclassifications_2019-08-11_01.csv
Current Positions current positions faculty180_currentpositions_2019-08-11_01.csv
Current Prefixes prefix faculty180_prefix_2019-08-11_01.csv
Courses courses faculty180_courses_2019-08-11_01.csv
Courses Taught courses taught faculty180_coursestaught_2019-08-11_01.csv

Additional Notes

  • Courses Taught  If providing terms in file
    • The first column should always be the term
    • The second column should always be the calendar year
  • Faculty Classifications  If providing terms in file
    • The first column should always be the starting term
    • The second column should always be the starting calendar year
    • The third column should always be the ending term
    • The fourth column should always be the ending calendar year

Base Data Load Options Documentation:

You can find information on base data loads here:

(C-2) Upload Base Data

What Happens?

When an upload occurs?

  • Supported Upload Types
    • Processed files are deleted and cataloged through our standard upload process
    • Bad files that are unable to be processed are cataloged and Faculty 180 personnel are notified of the issues
  • Custom Upload Types
    • Processed files are dealt with based upon the client's request
    • Bad files that are unable to be processed are dealt with based upon the client's request

 

  • If you have configured a given section for base data uploads and loaded data to the system in that section, you can still load another set of data to the same section, effectively modifying records to add additional fields (data points).
    • You can choose to modify an existing configuration by marking certain items that are currently being displayed in the configuration as not shown, or adding currently unshown items to the new configuration you are loading.
      • Note: It is important that all required fields remain. This allows us to identify the existing records the new data should be tied to.
    • You can also add new data points by updating the existing configuration. Based on the new configuration, the system will match required fields to existing records. It will load values to new data points that have been added and will update the data uploaded previously if those fields are still in the file.
      • Note: If a field is configured in an initial or earlier load, and that field is removed for a subsequent load, the system will not overwrite that field. It will maintain the previously loaded field even though not in the current file. If you want to delete a value in one field that was loaded previously,  you will need to make sure that field is in the configuration for the new upload, and will need to leave that field blank. 

When modifying records to add additional fields?

  • If you have configured a given section for base data uploads and loaded data to the system in that section, you can still load another set of data to the same section, effectively modifying records to add additional fields (data points).
    • You can choose to modify an existing configuration by marking certain items that are currently being displayed in the configuration as not shown, or adding currently unshown items to the new configuration you are loading.
      • Note: It is important that all required fields remain. This allows us to identify the existing records the new data should be tied to.
    • You can also add new data points by updating the existing configuration. Based on the new configuration, the system will match required fields to existing records. It will load values to new data points that have been added and will update the data uploaded previously if those fields are still in the file.
      • Note: If a field is configured in an initial or earlier load, and that field is removed for a subsequent load, the system will not overwrite that field. It will maintain the previously loaded field even though not in the current file. If you want to delete a value in one field that was loaded previously,  you will need to make sure that field is in the configuration for the new upload, and will need to leave that field blank.