All files will be located in a directory created by Faculty Activity Reporting (FAR). Each database will then have a subdirectory under the autoload directory. (For example, /autoload/databasename/).

• For base data: /autoload/databasename/
• For all other data types (scholarly, grants, custom sections):  /incoming/databasename/

To set up autoloads review file processing settings:

1. Navigate to File Configuration to configure the Upload Form.
2. Navigate to File Settings to conduct Bulk Data Uploads.

For Base Data, each directory under /autoload/ will have a file titled 'notification.txt.' This file will hold, the email addresses (one per line) of people who should be notified upon completion of autoload 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 FAR administration or the entity that creates files for automatic upload.

• Records to Delete: faculty180_[name_of_section]_DELETE_yyyy-mm-dd.csv

• Records to Keep: faculty180_[name of section]_RETAIN_yyyy-mm-dd.csv

1. Grants section: 

2. Scholary & Custom sections:

Place the ‘Delete’ or ‘Retain’ CSV in the same SFTP location as the corresponding bulk data file (for example, /incoming/grants). 

1. The ‘Delete’ file will be processed before the primary file, when both are present. 
   

   By default, both files (the primary and deletion files) will need to be present in order for the Delete file to process. For example, if you wish to delete data from a custom section, the data file must be present alongside the Delete file in order for the latter job to execute. This can be customized on a case-by-case basis.

    
2. The ‘Retain’ file will be processed before the primary file, when both are present.
   

   By default, both files (the primary and renention files) will need to be present in order for the Retain file to process. For example, if you wish to delete data from a custom section, the data file must be present alongside the Retain file in order for the latter job to execute. This can be customized on a case-by-case basis.

    
3. If more than one ‘Delete’ file is present, IDM will process only the most recent, based on the date in the file name.
4. If more than one ‘Retain’ file is present, IDM will process only the most recent, based on the date in the file name.
5. Our system will check for the file at the same time as your regular cadence for the data type in question. 

Once the file is processed, logs will be available under /outgoing/logs. Interfolio can configure any recipient to receive a notification email upon completion.

For Supported Base Data Autoload Types that Meet Requirements

• After processing, files are moved from the autoload folder to the processed folder.
• Unprocessed files (those that do not meet requirements) remain in the autoload folder. The system will continue to try to process the bad file.
• Please review the notifications that are sent. These failed files will be noted and the file should be deleted from the directory folder.

For Supported Non-Base-Data Autoload Types that Meet Requirements

• After processing, files are moved to a folder within the same directory called /old_files.
• Unprocessed files (those that do not meet requirements) remain in the /incoming folder.
• Please review the notifications that are sent and the outgoing logs for more details. These failed files will be noted and the file(s) should be removed from the directory folder or modified to meet requirements.

For Supported Base Data Autoload Types

• It is possible to start with a file that only has the required data field and then add additional fields as needed.
• This will require a change to the setup. Please submit a support request before making changes to the current file.

For Supported Non-Base Data Autoload Types

• Contact the Technical Services team via Interfolio-support@elsevier.com

By default, our system will not process the records of a “delete” or “retain” file if the number of impacted records exceeds 20% of the total data previously loaded in bulk to the section in question.

Your institution is responsible for sending accurate information to Interfolio regarding what records to keep and which to delete. In the event that records are impacted inadvertently, please contact Support immediately. The data can be restored via a bulk load provided by your institution (when applicable), or via a full-database restore to the latest available backup. Please note that the latter is a complete database restore, so all data in your database will be restored to an earlier state. Manual edits to records bulk imported to FAR will be lost.