Most tables start with a column for a unique identifier. This makes assignment and standardization easier.

Rules for Database item IDs

  • Uniqueness→ no ID should refer to two different items
  • Persistency → IDs should remain constant for the foreseeable future
  • Stability → IDs should never be re-used even if the original does not exist anymore

So please 

(warning) Do not duplicate any ID

(warning) Do not delete any ID

(warning) Do not reuse any ID

Naming conventions

It is recommended to use a three-letter code, which can be registered in separate database list (e.g. see picture below).

Add a consecutive number

(Optional: Add a title) Examples:  PRM00125 | 'T7 Promoter'

The version control of elabFTW automatically documents changes between versions. For some items (e.g. methods, SOPs) it is advised to specifically track the changes by indicating a version number in the item name. This allows to still be able to link back to previous versions (i.e. in previous experiments).

Example: A method was changed (e.g. a different instrument, chemical, amount of buffer, etc. was used). This method change is approved (i.e. it is not just an adaption for a single experiment), established and will be followed from now on as MTH00007_v2 | Transformation of E.coli using Heat-shock method.   

  • No labels
Write a comment...