Category: Products & Services

30 Apr 2018

Quick Look: Integrating Data From Multiple Assays in LabKey Biologics

Generating analytical data can be a complex process. It can involve navigating internal and/or external approval processes, hours of experiment planning, and the set-up and use of complex equipment. But even with all of these complexities, the most difficult part of the process often ends up being the analysis of the data in a way that generates meaningful, actionable insights.

Experiment data can get siloed, making it difficult to access, and it often takes different shapes that don’t inherently integrate. Scientists need to be able to join and view data from multiple sources in order to understand how measurements from one analysis may correlate, or be impacted by, measurements from another analysis.

Connecting Assay Data in LabKey Biologics

LabKey Biologics provides powerful querying capabilities that allow teams to join data from multiple experiments and view this data as a single grid or report. This data can then be searched, filtered, and shared just like any other grid of data within LabKey Biologics.

This power is essential when observing the relationship between measures. For example, a team may want to investigate whether or not a correlation exists between characteristics like pH and temperature and observed cell growth in a bioreactor. These measures are collected by different instruments, but they need to be viewed side-by-side in order to conduct this analysis.

Building a Query

Using the powerful SQL Schema Browser within LabKey Server, teams can build and execute queries that combine data from different datasets. One common way to compare assay measures is to join datasets by common Sample IDs. This type of join allows the user to see the measurements from multiple assays side-by-side for each Sample ID. Teams can design and execute queries of varying complexity, comparing two assay measures or many assay measures.

Leveraging Sample Lineage

Users can also query the lineage of each sample and present the parent sample (Bioreactor Run) to which a sample is tied as well as what Expression System entity was used in its creation. Sample lineage provides context for the joined assay data, allowing scientists to easily ask questions and conduct comparisons with other sequences that are seen in different experiments.

Manipulating the Joined Data Within Biologics

Once queries have been created, they operate much like any other grid of data in LabKey Biologics. The results of queries are automatically updated every time new data is added into the system and lineage details like Sample IDs, Bioreactor Runs, and Expression Systems are automatically rendered as links, allowing for easier navigation to details about the entities. Query data grids can be manipulated with all of the standard operations available in LabKey Biologics allowing users to search, sort or filter integrated data. Query data can also be easily exported to allow for analysis in downstream systems.

Ready to see this functionality in action? Check out the quick look video above. For more information, request a demo or register for an upcoming “Intro to LabKey Biologics” webinar.

19 Mar 2018

3 Key Reasons Data Accessibility is Essential in Research

Modern research technologies have greatly increased the amount of scientific data being generated, but making full use of that data is still a major challenge. Data accessibility is a consideration at all stages of the research process; for bench scientists making data accessible to informaticians, for teams sharing data cross-departmentally, and for researchers making data accessible to the public.

The accessibility of data is essential for a number of reasons:

1. Minimizing Redundancy of Research Efforts

Research redundancy is a major problem within research organizations and across the research community. By making data accessible to their desired audience, researchers can reduce the number of redundant experiments conducted and instead iterate upon existing research to accelerate discovery.

2. Drawing More Reliable Conclusions from More Data

Broader data accessibility allows research teams to pool data and conduct analysis with greater confidence in their results. The more data a researcher has access to, the more statistical power they have to validate research conclusions and preempt questions of data quality.

3. Inspiring Novel Questions from Different Approaches

New research questions are inspired by different research approaches and through the study of new methodology. Attacking scientific investigations from varying perspectives also helps reduce bias in analytics, experimental design, and conclusion drawing.

Expanding Accessibility with LabKey Server

LabKey Server not only helps teams collect and curate their data, but also helps make it accessible to collaborators and downstream researchers.

Web-Based Access

LabKey Server allows researchers to make their data accessible to a broad or narrow audience through a web-based portal. Web-based access makes it easy to share data as desired and allows interested collaborators to evaluate and alternatively analyze “self-serve” research data. This method of data sharing is both more secure than email (see fine grained permissioning below) and much lower overhead than a standard institutional database as users can query, view, and export data without having to interface with a data scientist.

Fine-Grained Permissions

LabKey’s fine-grained permissions model makes secure, selective sharing of to data simple and reliable. With LabKey Server, teams can easily control who sees their data, restricting access to selected individuals or pre-defined groups, or making data accessible the general public. Researchers also have fine-grained control over what datasets are shared: either a single table of data or an entire research project.

Powerful Metadata

LabKey Server captures detailed metadata to help increase discoverability of research data and provide crucial context for other researchers who hope to explore, reanalyze, and/or expand upon it. Research teams can customize metadata captured for each of their data types and add organization specific metadata to support internal needs.

Interested in learning more about how LabKey Server can enhance the accessibility of your research data? Contact the LabKey team for more information or request a demo!

*To learn how configure accessibility features of LabKey Server, read documentation >

08 Mar 2018

Quick Look: Integrating Analytical Data and Understanding Its Context in LabKey Biologics

One of the core challenges laboratory teams encounter is centralizing their data so it can be easily viewed and analyzed in a single place. Without centralized data, teams must turn to time consuming and error prone manual integration methods to derive value from their analytical data.

LabKey Server’s robust mechanisms for defining assays and uploading assay data are helpful for bringing analytical data into a single system, but LabKey Biologics takes this one step further and provides valuable structure and connections that help biologics research teams understand how that analytical data fits into the larger context.

LabKey Assay Designs: Standardizing Analytical Data Structures

LabKey Biologics allows teams to define or customize assay designs (many editable assay design templates come pre-defined within the system) to capture analytical data in a specific structure. Some teams using LabKey Biologics may need to define only a few assay designs to support their research, while others working in a more complex environment may need to define 100+.

When building an assay design, laboratory teams can choose to add fields specific to batches, runs and results to provide additional context for their data. LabKey supports a wide variety of field types (including integer, float, boolean, and text) and users can configure aliases, validation rules, and a variety of other characteristics for each.

Integrating Data Into the System

Once an assay design has been built in LabKey Biologics, data can be added to the system using that design to provide its structure. There are a number of different ways to load your assay data into LabKey Biologics including:

  • Automatically uploading via the LabKey API
  • Manually uploading spreadsheets
  • Pasting spreadsheet-type data
  • Entering data into a form

The first strategy, automatically uploading, leverages the APIs of LabKey Biologics to allow other instruments or file systems to talk directly to the system. The other three strategies involved a manual process suitable for varying use cases. If you have a large spreadsheet to integrate, you might want to use the manual upload method or paste the tabular data directly into the application. If you just have a couple of values you want to enter, simply entering the data into a form in the LabKey Biologics UI might be the simplest strategy.

Leveraging Sample Lineage for Context

As you know, analytical data generated during experiments is tied to a specific sample. Because the lineage of samples is tracked in LabKey Biologics, the application will automatically query sample lineage when data is uploaded and present relevant biological entities side-by-side with analytical data. Showing the sequence or molecule information adjacent to the analytical data, allows scientists to easily ask questions of their data and conduct comparisons with other sequences that are seen in different experiments.

Ready to see this functionality in action? Watch the quick look video above. For more information, request a demo or check out our “Intro to LabKey Biologics” webinars.

31 Jan 2018

Two Key Things Your Spreadsheet-Based Research Data Management Strategy is Lacking

High-throughput analysis techniques are incredibly powerful and provide teams with more data than ever. While that depth of data often holds the key to scientific insights, organizing such large quantities of data in a consistent and discoverable way has become a major challenge for research teams.

Many teams rely on spreadsheet-based systems to organize and manage their data. This approach becomes less-effective as research scales because spreadsheet-based strategies lack two essential characteristics:

1. Consistency

Spreadsheet data management lacks consistencyManual file management relies on the individual contributor’s abilities to consistently create, name, and store data files. This opens the door to a wide range of human errors that will ultimately impact the discoverability and reliability of your data. Common consistency errors that result from manual data management include:

  • Poorly named files
  • Inconsistent locations
  • Duplicate files

2. Discoverability

Spreadsheet data management lacks discoverabilityCollecting data is a giant hurdle in research, but in reality, it is just the first of many. Researchers need to be able to locate datasets of interest in order to conduct analysis. In a file based environment, discoverability of files is dependent on the consistency with which they are maintained. Were they saved in the correct location? Have they been named according to an agreed upon convention? Is there a clear authoritative file or are there duplicates?

A hitch in any one of these areas can severely hinder the discoverability of your data and make it significantly more difficult to:

  • Track what research data has already been collected
  • Find the data you are looking for when it comes time to analyze

Biology-Aware Data Management with LabKey Server

Scientific data management systems like LabKey Server, help increase the consistency and discoverability of your research data. LabKey Server increases the consistency of data management by providing structured data grids for storing various type of research data. Each data grid type also captures relevant metadata, specific to that data type, in order to help make data more discoverable.

Research-Centric Data Structures

Unlike spreadsheets that treat all types of data the same, LabKey Server provides four primary data structures with unique features to better support common types of research data.*

LabKey Assays – Assay data grids capture data generated from individual experiment runs. Assay data is automatically structured in a batch-run-results hierarchy when data files are added. LabKey Server supports data a variety of common assay designs out of the box, but teams can also design their own assay data structure using LabKey’s General Purpose Assay Design.

LabKey Datasets – Datasets track patient/subject measurements over time. LabKey datasets are automatically aligned and joined together, making it easy to query the integrated data and to create visualizations from multiple datasets.

LabKey Specimens – Specimen repositories track the status of each specimen and vial in your inventory. Built-in reports provide a birds-eye view of specimen information, and advanced search capabilities allow for easy location of specimens.

LabKey Lists – LabKey lists provide general purpose, online, interactive grids for any tabular data. Data stored as a LabKey list can be sorted, filtered, and visualized using built-in tools.

Storing data in a consistent, structured manner is the key for teams that hope to achieve maximum efficiency in operations and maximum value from their data. Not only is it much simpler to find data when it is stored in an expected location, but the centralization and integration makes it possible to query data to more quickly locate information of interest.

Interested in learning more about how LabKey Server can increase consistency and discoverability of your research? Contact the LabKey team for more information or request a demo!

*To learn how to add data to LabKey Server, read documentation >

18 Jan 2018
LabKey Vision 2018

LabKey Vision 2018

2017 was a year of many milestones for the LabKey team. Our newest product, LabKey Biologics, launched in April and has been implemented at four leading pharma and biotech companies, we redesigned the LabKey Server user interface, and we took our compliance functionality to the next level with the introduction of compliant hosting and a suite of new features to support teams working within HIPAA, FISMA and CFR Part 11 compliant environments. LabKey is excited about what the next year has in-store and we want to share our vision for 2018 with the growing LabKey community.

LabKey Server Premium Functionality: R Studio, PHI/PII Handling, Clinical Ontologies

Reinvesting Premium Dollars into Premium Functionality

Each year, LabKey invests in a number of development projects that premium subscribers have shared as key priorities. In 2018, we plan to dedicate development time to a variety of key areas including:

  • Helping secure access to protected data with added support for PHI/PII handling
  • Opening the power of R to more users in a secure manner by introducing sandboxing of R code execution
  • Increasing the reliability and reproducibility of results via versioning of R engines and packages within RStudio configurations
  • Streamlining data integration and enabling rich querying by adding support for clinical ontologies and controlled vocabularies
  • Automating and expanding data acquisition options through pipeline file watchers and integration with cloud storage providers

Curious what new  functionality was introduced in 2017? Read our “What’s New” updates >

Biologics R&D Roadmap: Experiment Grouping of Samples, Assay Data, Lineage Delivering on the Biologics Roadmap

The LabKey Biologics team, in partnership with our product advisory council, has developed an aggressive roadmap for continued development of this flexible system for biologic discovery and development. In 2018, the team will be focusing much of their efforts on:

  • Simplifying access to all relevant experiment data by enabling the grouping of samples, assay data, and notes by experiment
  • Helping teams better understand their data by expanding reporting and visualization capabilities
  • Making it easier for users to standardize and track the creation of media batches through usability improvements to the application’s media registration tools

Interested in learning more about LabKey Biologics? Watch our “Quick Look” video series >

LabKey Software Infrustructure: Java 9, Javascript Shared ComponentsStrengthening our Core Technology Infrastructure

In order to support our ongoing commitment to providing reliable software solutions, each year we dedicate resources to evolving our technology infrastructure to ensure its on-going stability. This year, we are largely focused on enhancements that will improve efficiency for both internal and external developers working with LabKey Server. Our key priorities include the development of a method for sharing JavaScript components between modules, fully supporting Java 9, and maintaining full compatibility with new versions of third-party components.

LabKey Server UX Refinements: New User Experience, Hosted Data Management Solutions, Compliant HostingRefining the LabKey Server User Interface, According to User Feedback

We have heard from new users of LabKey Server that the current experience makes it difficult to get started using the platform. In order to make sure new users can be successful using LabKey Server from the get go, our UX team will be working with new users over the next few months to understand how we can improve our user interface and the tools we provide. In addition, we will be continuing to expand our our hosted solutions in 2018 to make it easier for organizations to adopt and support LabKey Server.

Want to learn more about the recent LabKey Server UI changes? Check out our “New LabKey Server UI” blog series >

In addition to strengthening our solutions this year, we want to continue to strengthen our relationships with you, the LabKey community. We hope that you will join us in this journey toward creating robust and powerful tools for accelerating research. A few ways that you can get involved this year include:

Providing Feedback on the New UI

As teams upgrade to LabKey Server version 17.3 and later, we encourage you to provide feedback about the new UI through the “Give Feedback” form that can be accessed in your LabKey Server account menu. This feedback is reviewed, prioritized, and used directly to help us make decisions about refinements to the LabKey Server UI.

Participating in a New User Walk-Through

Are you new to using LabKey Server? We want to hear about your experience and how we can improve! LabKey User Experience Manager, Jessi Murray, is looking for new users who would be willing to discuss their experience getting started with LabKey Server and how it could be improved.

Email Jessi Murray at jessim@labkey.com for more information!

Attending the LabKey User Conference

The LabKey User Conference is an opportunity for users to gather together and share about how they are using and extending the LabKey platform and solutions. Attendees also participate in round table discussions and work sessions with the LabKey developers where they can explore current challenges and shared feedback directly with the LabKey team.

Interested in speaking at the LabKey User Conference? Email conference manager, Kelsey Gibson at kelseyg@labkey.com for more information!

20 Dec 2017

LabKey Biologics: A Year in Review

As this year comes to a close, we wanted to take a few minutes to reflect on the year and thank you for joining us on the LabKey Biologics journey. It has been an amazing year and we couldn’t be more excited about what’s coming in 2018!

Launching LabKey Biologics

One of the key parts of developing this application has been the engagement from our LabKey Biologics Product Advisory Council. Since its inception, we’ve been meeting monthly with eight different biotech, pharma, and academic institutions to get feedback. They’ve let us know what we’re doing right (and wrong) and have been invaluable in guiding the product development.

After working with the Product Advisory Council and our initial collaborator, Just Biotherapeutics, for 18 months, we officially launched LabKey Biologics in March. This first version focused on:

Just Biotherapeutics has been rolling out LabKey Biologics and has registered hundreds of biological entities, used workflow management to request thousands of assays, and uploaded analytical data for tens of thousands of samples. Several other members of our advisory board have also become clients and are in the process of implementing LabKey Biologics at their organizations.

Following the release of LabKey Biologics, we had the chance to talk with hundreds of individuals about the new product at PEGS Boston and Bio-IT (we’ll be at both shows again in 2018). Gathering feedback from folks in different roles throughout the industry, active users, and advisory board members has helped us improve the product and plan for future enhancements.

Since we launched in March, we’ve worked on many different improvements to the product. Some of the larger efforts include:

  • Additional Methods to Upload Assay Data
  • Defining the Lineage of a Sample, from Bioreactor Run to Purified Antibody
  • Media Registration – More Options and Ease of Use
  • Updates to the User Interface

What’s Next

As we look to 2018, we are excited to continue expanding the functionality of LabKey Biologics. We’ve got big plans for the next 12 months, including:

  • Defining Experiments
  • Building Analyses and Reports
  • Mapping and Characterizing Post-Translational Modifications
  • Improvements to Bulk Import of Entity Registry, Assay, and Media Data
  • Integrating Custom Assay Definitions with LabKey Biologics

Product Feedback

We’re always interested in feedback! We’d love to connect with each of you in the new year, and have a conversation (or several) to hear about your needs and thoughts on the product’s direction. If you’d like to learn more about LabKey Biologics, we’re hosting a free Intro to Biologics webinar on January 9.

Don’t hesitate to get in touch with us – and best wishes to you in the New Year!

LabKey Biologics Team

Ryan Luce, Product Manager
Email: ryanl@labkey.com

Kevin Krouse, Lead Software Engineer
Email: kevink@labkey.com

21 Nov 2017

What’s New in LabKey Server v17.3

We are excited to announce the release of LabKey Server v17.3! This release marks the launch of our newly redesigned user interface and includes a wide variety of other key feature and security enhancements.

Feature Highlights of Version 17.3

User Interface Update

The 17.3 release includes big improvements to the LabKey Server user interface. Enhancements include:

  • Project Navigation – Project and folder navigation has been redesigned as a single-column scrollable list, which also works well on tablets and other small windows. (docs)
  • Frameless Web Parts – You now have the option to render cleaner looking pages using “frameless” web parts, which removes the web part title, the surrounding border, and the top banner. (docs)
  • Grid Interface – Improvements include: (1) new graphics and buttons, (2) filters and sorts are automatically included when saving a custom view, and (3) when saved views exceed 10 items, a text-based filtering box makes it easier to locate the relevant views. (docs)

Electronic Signatures
Electronically sign a data grid snapshot, and specify a reason for signing. Signed documents and associated metadata, such as the signatory, the date of signing, etc. are extensively logged for auditing purposes. (docs)

REDCap Improvements
REDCap integration has been updated and enhanced, including a new graphical user interface which replaces the XML-based configuration interface, making it easier to configure connections and data export from REDCap servers. (docs)

For details on all the new features, read the release notes on the LabKey Support Portal, or download the latest version of LabKey Server.

19 Sep 2017

Before & After: A Side-by-Side Look at the New LabKey Server UI

The upcoming redesign of the LabKey Server user interface includes a variety of updates; some of which are focused on look and feel, some on interface behavior, and some technical stability. All of these changes and enhancements were carefully selected because of the contribution they will make to the overall usability of the platform. Prior to the release of the new UI as part of LabKey Server v17.3, we wanted to give users a side-by-side look at some of the key updates and how they will differ from the current UI.

Landing Page

Many of the key changes to the LabKey Server UI can be seen upon your arrival on the LabKey Server landing pages. The new interface features an updated header style with a more compact navigation and reorganized menus, the addition of a new “frameless” webpart style, and updated logic that will hide the tab bar on home projects if there is only one tab present.

Page Administration

In order to reduce the visual noise and present a cleaner UI for administrators, we have introduced a “page admin mode.” Options like “add web part” and tab editing will no longer be presented at all times and will instead only be visible when the user turns on page admin mode. Page admin mode can be easily turned on when edits to a page are needed and turned off when edits are complete.

Data Grids

Several changes have been made to the LabKey data grids in order to declutter the grid navigation and increase readability. The most notable changes include the introduction of a more icon-driven button bar with tooltips for each action available on hover, a simplified “edit” link presentation, and the addition of row highlighting.

Grid Customization

The customizing grids of data has been simplified in the new LabKey Server UI. With this update, filters and sorts added to a grid are always carried with view and no longer require an opt-in. Additionally, filters can be quickly edited using one click to reopen the filter pane or removed with by clicking the newly added [x] icon next to each filter definition.

Menus

Updates to the LabKey Server menu are both visual and technical in nature. A major shift included as part of the redesign is the transition to menus written in Bootstrap instead of Ext, that take advantage of Bootstrap’s consistent styling and built-in behavior for multiple form factors. Sub-menu behavior has also been updated so that sub-menus now replace the menu content (with a back to menu option) instead of appearing next to the primary menu. This change makes the navigating to 2nd level sub menus a much cleaner experience, as users navigate within one menu frame instead of 3. Finally, type-to-filter functionality has been added to the menus with greater than 10 values. This can initially be seen in the “More Modules” list as well as the “Grid Views” list.

12 Sep 2017

Key Steps for a Successful UI Transition

Whether you’re implementing a brand new software solution or updating an existing solution, changes that affect the workflow of team members are often a major pain point for organizations. Taking steps to manage and communicate these changes and their benefits to your users can greatly reduce the friction faced during implementation and, in turn, increase adoption by users. As you prepare to transition to the new LabKey Server UI (being released as part of LabKey Server v17.3), we encourage you to take the following steps to help manage this change and help make the UI transition a success.

Test the Redesigned Interface

Test the new interface extensively in your staging and/or test environments. As part of the 17.2 release of LabKey Server, we included the “Core UI Migration” experimental feature that allows administrators to turn on the new UI. While the interface is still in active development and certain elements may shift slightly, the bulk of the navigation changes are represented, and we encourage administrators to explore the new UI and test for:

Changes to your primary user workflows (editors, readers, administrators, etc.)
Go through the workflows of your primary users; click through the available buttons and navigate through the interface as your user would, checking for changes to their standard workflows.

Broken customizations
Check to see that customizations you have made to the interface are still functioning as expected. As part of the UI redesign, we have refactored a good portion of our own CSS in order to make it easier to maintain the platform in the long run. As a result customizations made to your server’s CSS may need updating.

UI bugs that should be reported to LabKey
Reporting bugs that you encounter during testing is an important part of the redesign process. Your feedback helps us identify and prioritize fixes that need to be made to the interface.

Identifying updates that need to be made to your server customizations and changes to your user workflows early will give you the opportunity to make adjustments and prepare for any new-interface training that might need to be done with users.

Set a Go Live Date

Decide on a date that you will make the transition to the new UI. Make sure you account for adequate time to test the new version, communicate upcoming changes and your transition plan, and train users on the new UI.

Communicate Upcoming Changes and Transition Plan

Communicating upcoming changes and their implications for your users early and often is crucial to a smooth interface transition. When communicating details about the interface transition to users, make sure to include information about:

  • Transition timeline
  • Key benefits of the transition
  • Key changes/potential areas of frustration
  • How users can ask questions
  • How users can provide feedback

Provide User Training

Some of the changes being made to the LabKey Server interface during this redesign will affect how users perform certain tasks. If you discover through testing the interface in the context of your team’s key workflows that core tasks are affected by navigation changes, then providing training on how to accomplish this work in the new interface will help avoid frustration. For smaller changes, simply documenting the new process may be sufficient training, but in cases where a user’s workflow is significantly changed a training session may be more appropriate.

Answer Questions

Even with thorough testing, communication, and training, questions from your users are still inevitable. Develop and communicate how users can ask questions as they are are adjusting to the redesigned interface. Depending on the size of your team, that may mean communicating who the contact person is for questions, you may create a message board for questions and discussion, or you may host a handful of Q&A workshop sessions post-implementation. Whatever the method, making sure a user knows how they can have their questions answered will help prevent frustration when they encounter a change to their workflow.

Provide Feedback

Communicating feedback to the LabKey team is an essential part of the redesign process, and we are committed to making sure that you and your users have the best possible experience using LabKey Server. As you explore the redesigned interface in your test environment as an experimental feature, you can provide feedback using the “Give Feedback” button in the top right corner of the interface. You can also provide feedback directly to your LabKey account manager.

Related Resources

17 Aug 2017

Quick Look: Automated Generation of Molecular Species in LabKey Biologics

One of the most common ways LabKey Biologics is used is in researching protein based molecules, often times antibodies. To support this research, LabKey Biologics is equipped with specialized triggers that automatically register commonly seen molecular species when a new antibody is created.

Antibodies and Protein Sequences

When engineering antibodies, the heavy chain and light chain sequences often have signal peptides (or leader sequences) as part of their overall sequence. When these proteins are expressed within a transformed cell line, these signal peptides are cleaved as the proteins are brought out of the cell.

Within LabKey Biologics, when you register a new “molecule” (that is composed of solely of protein sequences), the application automatically examines these sequences to determine if there are signal peptides present. If there are, LabKey Biologics will also register “molecular species” that have the same sequences (and stoichiometry) as the original molecule, without the leader sequences. This is called the “mature” molecular species. Similarly, if the molecule’s heavy chain contains a C-terminal lysine, LabKey Biologics will register a “mature, desK” molecular species that has cleaved the leader sequence(s) as well as the C-terminal lysine(s).

The “mature” and “mature, desK” molecular species are automatically generated and registered by LabKey Biologics. In the laboratory, however, you might detect other molecular species that stem from over-clipping and under-clipping of the leader sequences. LabKey Biologics allows you to manually register these as well, allowing you to connect all of these observed and predicted entities.

New Protein Sequences and Molecule Sets

For molecular species that are automatically generated, their components are often times new protein sequences. These sequences are also automatically generated, along with information about where the sequence came from. LabKey Biologics helps you keep track of those relationships.

Finally, researchers needed a mechanism to refer to all molecules for which the only difference is the leader sequence(s) of the protein sequence(s). For this, LabKey Biologics also automatically assign each molecule to a molecule set. For each molecule in a molecule set, the “mature” molecular species has the exact same components.

For a quick look at this functionality in action, check out the video above. Want to see more? Request a demo or register for an upcoming “Intro to LabKey Biologics” webinar.

CONTACT US