Data files need to be uploaded to the appropriate folder on our SFTP server.

• Grant files should be uploaded to: /incoming/<faculty180 instance>/grants
• Scholarly files should be uploaded to: /incoming/<faculty180 instance>/scholarly

• Activity Data Models are available for autoloading
• Profile Data Models are available, but not yet for autoload

• Autoload files are required to be in .CSV format.
• UTF-8 encoded file formats are supported. If particular uploaded .CSV file(s) are not encoded in UTF-8, re-save the files as UTF-8 in order for the data to be read correctly by the data base.
• Best practice is to provide a delta file, instead of a file containing the full data set. A delta file will include new records and records that have changed since the last load. This will help to reduce processing time and improve the accuracy of the updates.

Accordion BodyGrant files should use the following naming convention:

• Proposal file: Faculty180_proposal_yyyy-mm-dd_sequence#.csv
  • Example: Faculty180_proposal_2022-11-21_01.csv
• Award file: Faculty180_award_yyyy-mm-dd_sequence#.csv
  • Example: Faculty180_award_2022-11-21_01.csv
• Optional collaborator file for proposals: Faculty180_proposal_collaborator_yyyy-mm-dd.csv
• Optional collaborator file for awards: Faculty180_award_collaborator_yyyy-mm-dd.csv
• Scholarly activity files should use the following naming convention:
  • Scholarly activity file: Faculty180_section-name_yyyy-mm-dd_sequence#.csv
  • Optional collaborator file for scholarly activity: Faculty180_section-name_collaborator_yyyy-mm-dd.csv 
• Multiple files for the same section can be uploaded at the same time to be autoloaded. Use the sequence number within the file name to allow for multiples.
  • Faculty180_proposal_2022-05-10_01.csv
  • Faculty180_proposal_2022-05-10_02.cs

• Data files can be uploaded to the SFTP server at any point. The autoload can be scheduled for any time.
• If a file is not available at the scheduled time, the process will simply skip the process. The autoload will try again at the next scheduled time.
• Files can be scheduled for autoload as often as weekly. Files can also be scheduled for a given day on a monthly or quarterly basis. 

When an autoload process completes, an email notification can be sent to any email address requested. The email will include the name of the files processed, the name of the section loaded, the total number of new records, updated records, records not changed and errors. The notifications will come from the email address: noreply@f180-prod.localdomain

Sample email:

The autoload process generates two log files for each section load. These logs will post to the SFTP server under the location/outgoing/logs.

• Success Log: One log file contains those records that were successfully processed and did not error. The file includes a column indicating whether each record was inserted as new, updated, or not changed. 
• Error Log: One log file contains those records that failed to load. The log includes a column indicating the reason for the error and a column containing further details if applicable.

Autoloads are set up by the Interfolio Technical Services Team. To autoload data files, create a ticket to request that autoload be set up. To expedite setup, provide the following information in the ticket request:

• The name of the section to be autoloaded
• A sample of the data file(s)
• The email addresses that need to receive the autoload notification
• The autoload frequency required and the day/time for the process to run
  • For example, every Friday at 5 am EST

• Grants
• Scholarships