Imagine you’re taking a refreshing night swim in the warm blue waters of Vieques in Puerto Rico. You splash into the surf and head out to some of the deeper waters of the bay, when what to your wondering eyes should appear, but blue streaks of light in water that once was clear. Do you need to get your eyes checked? Are you hallucinating? No! You’ve just happened upon a cluster of dinoflagellates, harmless bioluminescent microorganisms called plankton, that emit their glow when disturbed by movement. These dinoflagellates are known to inhabit waters throughout the world but are generally not present in large enough numbers to be noticed. There are only five ecosystems in the world where these special bioluminescent bays can be seen, and three of them are in Puerto Rico.
But you don’t have to travel to Puerto Rico or swim with plankton to see bioluminescence. There are bioluminescent organisms all over the world in many unexpected places. There are bioluminescent mushrooms, bioluminescent sea creatures—both large and small (squid, jellyfish, and shrimp, in addition to the dinoflagellates)—and bioluminescent insects, to name a few. Bioluminescence is simply the ability of living things to produce light.
Developing a vaccine that is safe, effective, easily manufactured and distributed is a daunting task. Yet, that is exactly what is needed in response to the COVID-19 pandemic.
Vaccine development, safety and efficacy testing take time. The mumps vaccine is thought to be the quickest infectious disease vaccine ever produced, and its development required four years from sample collection to licensing (2). However, there are many reasons to anticipate quicker development for a COVID-19 vaccine: Researchers are collaborating in unprecedented ways, and most COVID-19 scientific publications are free for all to access and often available as preprints. As of August 11, 2020, researchers around the globe have more than 165 vaccine candidates in development, 30 of which are in some phase of human clinical trials (1). The range of vaccine formulations available to scientists has expanded to include RNA and DNA vaccines, replication-defective adenovirus vaccines, inactivated or killed vaccines and subunit protein vaccines. Equally important is that vaccine developers and researchers have greater access to powerful molecular biology tools like bioluminescent reporters that enable quicker testing and development.
Coronavirus (CoV) researchers are working quickly to understand the entry of SARS-CoV-2 into cells. The Spike or S proteins on the surface of a CoV is trimer. The monomer is composed of an S1 and S2 domain. The division of S1 and S2 happens in the virus producing cell through a furin cleavage site between the two domains. The trimer binds to cell surface proteins. In the case of the SARS-CoV, the receptor is angiotensin converting enzyme 2. (ACE2). The MERS-CoV utilizes the cell-surface dipeptidyl peptidase IV protein. SARS-CoV-2 uses ACE2 as well. Internalized S protein goes though a second cleavage by a host cell protease, near the S1/S2 cleavage site called S2′, which leads to a drastic change in conformation thought to facilitate membrane fusion and entry of the virus into the cell (1).
Rather than work directly with the virus, researchers have chosen to make pseudotyped viral particles. Pseudotyped viral particles contain the envelope proteins of a well-known parent virus (e.g., vesicular stomatitis virus) with the native host cell binding protein (e.g., glycoprotein G) exchanged for the host cell binding protein (S protein) of the virus under investigation. The pseudotyped viral particle typically carries a reporter plasmid, most commonly firefly luciferase (FLuc), with the necessary genetic elements to be packaged in the particle.
To create the pseudotyped viral particle, plasmids or RNA alone are transfected into cells and the pseudotyped viruses work their way through the endoplasmic reticulum and golgi to bud from the cells into the culture medium. The pseudoviruses are used to study the process of viral entry via the exchanged protein from the virus of interest. Entry is monitored through assay of the reporter. The reporter could be a luciferase or a fluorescent protein.
By clicking “Accept All”, you consent to the use of ALL the cookies. However you may visit Cookie Settings to provide a controlled consent.
If you are located in the EEA, the United Kingdom, or Switzerland, you can change your settings at any time by clicking Manage Cookie Consent in the footer of our website.
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Advertisement".
This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
6 months 2 days
This cookie is set by the provider Media.net. This cookie is used to check the status whether the user has accepted the cookie consent box. It also helps in not showing the cookie consent box upon re-entry to the website.
This cookie is used to store the language preferences of a user to serve up content in that stored language the next time user visit the website.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
This cookie is associated with Sitecore content and personalization. This cookie is used to identify the repeat visit from a single user. Sitecore will send a persistent session cookie to the web client.
This domain of this cookie is owned by Vimeo. This cookie is used by vimeo to collect tracking information. It sets a unique ID to embed videos to the website.
1 month 18 hours 24 minutes
This cookie is used to calculate unique devices accessing the website.
This cookie is installed by Google Analytics. The cookie is used to calculate visitor, session, campaign data and keep track of site usage for the site's analytics report. The cookies store information anonymously and assign a randomly generated number to identify unique visitors.
This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected including the number visitors, the source where they have come from, and the pages visted in an anonymous form.
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
1 year 24 days
Used by Google DoubleClick and stores information about how the user uses the website and any other advertisement before visiting the website. This is used to present users with ads that are relevant to them according to the user profile.
This cookie is set by doubleclick.net. The purpose of the cookie is to determine if the user's browser supports cookies.
5 months 27 days
This cookie is set by Youtube. Used to track the information of the embedded YouTube videos on a website.
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
This cookies is set by Youtube and is used to track the views of embedded videos.
This is a pattern type cookie set by Google Analytics, where the pattern element on the name contains the unique identity number of the account or website it relates to. It appears to be a variation of the _gat cookie which is used to limit the amount of data recorded by Google on high traffic volume websites.