Hi Bill,

Almost every module should have tables with a container column. There are a few cases where there is data that is shared across all the folders on a server, like the proteins loaded from FASTA files, but the vast majority is segmented into folders to make it easier to organize.

If a table contains data that is tied to data in another table, we'll usually just store the container on the parent table. For example, MS2 peptide identifications are always loaded in the context of an MS2 run, so we store the container on the run table, not the peptides table.

Thanks,
Josh