The ProcessRun control file section enables you to keep track of all loading processes. A Process RUN can be considered as a batch job with an ID and description. The objects inserted during one run can later be deleted together using 'delete run' command. The Process RUNs in the table PROCESS_RUN can be of several types:

Process Type

Description

LOAD ORGANISM

Adding an organism being studied.

LOAD GDNA

Adding a physical map set with maps based on sequence.

LOAD MAPS

Adding a genetic map set and maps.

LOAD ANNOT

Adding annotations to a physical map set.

LOAD MARKER

Adding markers to a physical/genetic map set.

LOAD SYNTENY

Adding syntenic regions between two physical map sets.

LOAD ONTOLOGY

Adding ontology terms in OBO format.

LOAD QTL

Adding QTLs to a physical/genetic map set.

LOAD EXPRESSION

Adding expression data to a physical map set.

LOAD ALIGNMENT

Adding protein or DNA alignments to a physical map set.

LOAD VARIANT

Adding sequence variants to a physical map set.

 PersephoneShell will create a ProcessRun record with proper ProcessType depending on the command.

It is a good practice to record the source URL of the data being loaded in the Process Run description.

[ProcessRun]
; Run description: if specified, a custom description will be used. Will be ignored if a RunId is specified.
;                  otherwise, "Added annotations for {MapSet Accession No.} from {Sources}." will be used.
RunDescription="Load Gnomon annotations for SL3.2 from NCBI (ftp://ftp.ncbi.nlm.nih.gov/genomes/all/GCF/002/168/275/GCF_002168275.1_ASM216827v2/GCF_002168275.1_ASM216827v2_genomic.gff.gz)"