# GBDI4.1

### Sonargd Directory Structure

The following directory structure will be created under the base directory (see Base Directory) upon first run of sonargd (if it does not exist already):

#### incoming

The incoming directory is where new data files are written, and is persistently monitored for incoming files. Newly discovered files are processed by sonargd. Sonargd can differentiate new files from those that have already been processed; a copy operation is only triggered when new files or file sets are added to the directory.

When processing is complete, files will be moved to the archive directory. Files that generated any errors during processing will be moved to the audit directory.

#### inprogress

The inprogress directory is where files currently being processed are stored. The compressed files from the incoming directory are extracted and moved into this folder; files in this folder are the source files for sonargdm import.

The inprogress directory is cleaned up at the end of the processing cycle.

#### audit

File(s) that generate an error will be copied, regardless of whether they are corrupted compressed files or files that generated errors while being processed by sonargdm to the audit folder.

#### archive

Successfully processed files will be moved into the archive folder. Only files from the incoming folder will be moved to the archive folder; none of the intermediary files used during the process will be moved to the archive folder. By default, files are only kept in the archive for 24 hours. This can be changed by passing a different value to --keep command line argument. Zero will disable removal of files from the archive.

There are additional files stored in the base directory. For example, the session_cache.sqlite is an important file stored in the base directory; this file allows sonargdm to synchronize session data between files.