Hi,
According to my colleague which takes care of our databases there is an issue in the ERD (v3.0.0) concerning the relation between setID in sets table with specimenSet, compartmentSet, mmSet, unitSet, aggregationSet, qualityIndSet, missingessSet in parts table. A foreign key must point at a primary key which contains always unique values. SetID can contain several identical values and thus cannot be a primary key neither a foreign key. A table linking sets and parts could solve this. This tables would contain a variable with all possible setID and could be used as a primary key toward the foreign key setID and toward foreign keys specimenSet, compartmentSet, mmSet, unitSet, aggregationSet, qualityIndSet, missingessSet. Or maybe set them as FK with partID in parts tables.