Our overall experience with eLab Journal has been exceptional. We are glad we chose to partner with them because they were definitely the right choice! They have helped us immensely and we would not have achieved a successful project outcome without them.

Working with the team at eLab Journal to implement our LIMS and make enhancements as our laboratory has grown has been a wonderful experience. Everyone we have worked with is responsive and collaborative. The software itself has amazing functionality and provides the features we need to act as an efficient, high throughput testing laboratory.

When we implemented the software in 2020, some of the menu items and navigation seemed disjointed and not exceptionally intuitive. eLab Journal has evolved since then and we have seen improvements. The team is also open to our feedback as system users.

Overall, I'm very pleased with eLab. It has greatly streamlined the tracking of sample receipt and downstream processing for thousands of samples, allowing me to set up standard procedures that even novice undergraduate students can follow without difficulty. Likewise, the pricing was very competitive and the team at eLab has been very responsive and pleasant to work with.

This product has greatly facilitated the standardization of sample intake and inventory. Likewise, I really appreciate the ability to set up lab protocols (with version tracking) and standardized experiment templates. These features, in particular, make it easy to bring on new lab helpers in an undergraduate setting. There is no need to manage and track shared files or folders, and when a student leaves, their records and activities are preserved. The interface has generally been quite intuitive and easy to maneuver, and customer support is responsive and helpful if a user runs into problems.

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.

When using eLabJournal we take advantage of: - We no longer use paper-based experiments. - Instead of having different repositories for experiment and sample results, everything is stored in a single digital repository, avoiding the exchange of mails with these results. - The Audit Trail of the samples is really good. - You can trace the Samples that are used in an experiment really easily. - Sample reception process using QR has simplified this process within Viralgen. - The ingestion of data from third party software using API is straightforward. - The implementation of eLAbJournal has allowed more communication between laboratories and departments. - The integration with other third-party applications is possible using the API. In our case with SAP.

- When being used to paper-based experiments, the investment of time you need to digitalize your experiments in eLabJournal is really high. - We miss some Project/Study/Experiment filtering tools.

Undecided if its an improvement or not. The jury is still out.

Not sure really havnt started using it properly yet, taken a lot of time to sort out the infrastructure, would be easier if the Elab team has better insight into the peripherals and things needed to start using the software effectively

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

quick integration and setting up the zebra printer only took seconds

I would use same name for experiement, project, and sometimes study.