If your LIMS runs in a web browser, do you really need to build an app in addition to that? Is a web-based LIMS all you need? The focus of this post is whether you need a LIMS website or app – or even both.
“Social Media” doesn’t mean only using FaceBook for your personal photos and contacts. Many people in our industry are doing LIMS social media using public tools such as LinkedIn or private tools such as the LabWare LIMS / ELN discussion group.
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.
As Yogi Berra said, “It’s deja vu, all over again. So, yes, you did see this same post just in recent weeks. However, I realize the first one just sounded too dry and robotic plus I did get some good feedback to that effect.
LIMS configuration versus customization remains an issue after many years of products and implementations. Here, we discuss the confusion behind these terms, as well as examining the decision-making process that goes on during implementations regarding these.
Today’s topic is actually not a written blog post but a podcast. This podcast’s topic is “Seven Initial Questions For Combining R&D and QC LIMS.”
Maybe. R&D and QC LIMS can be combined under some circumstances. However, there are a number of factors to consider.
Just yesterday, I ended up in a conversation about product safety. Today, I’m writing about how LIMS product safety tracking is part of that puzzle.
I recently wrote about the LabWare and the SampleManager systems but the last “big” system I started to learn was the Labvantage (LVS) system. Here are some thoughts to pass along to those of you thinking that that might be your next big adventure.
A recent post discussed modules within the LabWare LIMS and about not getting too crazy with downloading and installing things. Today’s post gives one example of how you can kill your system performance with one simple combination. This is an issue for just about any software, really, but here’s a specific example using the LabWare system.