SciSure

Our internal servers are not connected to the ELN.

As with any new system, in the beginning it takes some time to get used to the navigation in eLabjournal. Logically also the structure is different than in a "diary-like" hard-copy lab book.

The slow adoption of the protocols function within the eLab protocol may be attributed to some of the clunky nature of generating a protocol from scratch in eLab, which can be challenging from a format perspective. However, generating the outline in a 3rd party platform such as Microsoft Word and then utilizing the import function has been great for generating rapid protocol skeletons that can then be populated/fine-tuned based on the user. Also the lack of a spell-check function makes 3rd party platforms more effecitive for generating error-free templates.

Very slow to get up and running-this is mainly due to limited home resource and nothing to do with the product. However Eppendorff could start to sell printers and labels etc so they cover everything you need to start embedding the software effectively

There are still a few glitchy (largely aesthetic) areas. For example, the "Lineage" button appears to multiply as one clicks on or manipulates successive sample records. This can be resolved by refreshing the page, but it is not guaranteed that you will remain on the same sample record when you refresh. This doesn't seem to impact the integrity of sample records, but can be annoying when working with a lot of sample records. There is not yet a function to create copies of plates of samples (e.g., whole-plate aliquots, series, or downstream product). One can work around this with batch importation, but I do look forward to this feature eventually being incorporated.