Fig shows the dose ndash response relationships for

Parameter’s name and note (e.g. “Methane yield” and “NmL CH4/g OS”) PF-00562271 stored in the fields parameterName and parameterNote, respectively. The field valueType encodes the type of a parameter’s value (e.g. “textual”, “numeric”, “yes/no”), which also determines the associated server-side validator. The field category encodes parameter’s category (e.g. “substrate characteristics”). A unique value in the field parameterOrder determines the order in which a parameter appears in submission forms and auto-generated reports.
The outlined use of the two tables parameters and substrates for storing and bookkeeping reposited data assures maintainability of the repository and eases modifications of its structure. When a new parameter needs to be added, vaccination is enough to add an appropriate row in the table parameters together with creation of a new field in the table substrates. The newly added parameter becomes immediately operational and appears in forms and reports. Similarly, a parameter is renamed simply by changing an appropriate value of the entry parameterName, whereas there is no need to rename a field’s name in the table substrates, which would require modifications of the underlying PHP code as well.