The systems we work with are complex with complex processes. Many of the brands still require programming. Whether you use what you think is a “real” programming language or you think it’s a “scripting” language, code review is probably required. Many of you are doing LIMS code reviews, already,. Regardless, anyone working with these systems needs to understand more about how to properly do a LIMS code review or code review with their ELN, LES or LIS, as well.
When we talk about programming the LabWare LIMS, we have to be careful what we mean. The LabWare LIMS Smalltalk is NOT what we’re going to be using. Instead, think LabWare LIMS Basic.
Today’s blog post was inspired by a search phrase that brought readers to this blog, which is “labware user manual save off line”. Today, we will discuss storing the LabWare LIMS User Manual, locally.
Today’s blog post was inspired by a search phrase that brought readers to this blog, which is “labware lims modules”.
I had made some previous posts that talk about the fact that you need to be careful what you do when managing your LabWare LIMS / ELN or even other brands of these systems. The last such post was poorly titled as “How to Create Huge Problems With Your LabWare and Other Systems” because it was more of a warning than a “how to” guide. Today, I will talk specifically about the LabWare system and the terrible things people do to it to make it unusable. However, these tips often can be used with other brands, as well.
Lately, I’ve been blogging about proper system administration and maintenance. Today, I want to talk about the LabWare LIMS / ELN and the use of its Wait() command, which has basically become the felon of the programming world.
Some of you will be starting new projects, this year. Some of these will be LabWare LIMS / ELN projects. The number one thing to do is to set yourself up for success. First of all, don’t lose your LabWare LIMS static data. This is easy to do when you’re first starting. This is especially true when you’re doing the project by training your internal staff and not using experienced resources for implementation. Even with experienced people, there are times when they don’t necessarily communicate these issues in a memorable manner.
We have lots of discussion in the industry regarding who should be programming and which what tools. In my last post, I was comparing Thermo Scientific SampleManager’s VGL versus C#. Today, let’s discuss LIMSBasic.
I normally don’t give out product-specific tips. That’s what the LabWare Help Desk is for. However, there is one issue that I think many junior LabWare LIMS people don’t know about and there are even more senior LabWare LIMS specialists that don’t realize this. It’s something that pops-up so often and such a big issue that I want to draw attention to it.
In the last couple posts, I referred to the LabWare system as a LIMS and ELN, and the SampleManager system as a LIMS and LES. Are they really both a LIMS and something else?