234
A custom type describes a specialized sub-entity that extend a standard LOGS entity model by additional customized fields that are ordered in customizable sections.
Example:
Imagine a group that does NMR & EPR experiments, both methods use the LOGS core entity-type “Samples”. To emphasize the different type of samples used in the experiments for better discrimination, easier filtering and accurate meta-data tracking, an admin creates the following custom types:
-
NMR Sample,
-
EPR Sample.
The customized types extend the standard meta-data fields by the following custom fields & sections (for reference see Custom fields):
NMR Sample
Section: “Sample details”:
Custom fields:
-
NMR Solvent → Data-type: text, Fixed option: one of [“CDCl3”, “D2O”, “MeOD”, “H2O/D2O”, “DMSO”]
-
Weight [mg] → Data-type: number, Required
-
Is polymer → Data-type: boolean, default: false
Section: “Experiment details”:
Custom fields:
-
Temperature [°C] → Data-type: number, default: 24,
-
Experiment 1→ Data-type: text, Required
-
Experiment 2→ Data-type: text
-
Experiment 3→ Data-type: text
EPR Sample
Section: “Sample details”:
Custom fields:
-
EPR Solvent → Data-type: text, Fixed option: one of [“Pentane”, “Cyclopentane”, “Hexane”, “Cyclohexane”, “Benzene”, “Toluene”, “1,4- Dioxane”, “Chloroform”, “Diethyl Ether”]
-
Volume [μl] → Data-type: number, floating-precision
-
Is solid powder → Data-type: boolean, default: false
Section: “Experiment details”:
Custom fields:
-
Experiment 1→ Data-type: text, Required
-
Experiment 2→ Data-type: text
-
Experiment 3→ Data-type: text
