Many research labs around the world have temporarily closed their doors in response to the COVID-19 pandemic, while others are experiencing unprecedented need for reagents to perform viral testing. This urgency has led many scientists to make new connections and build creative, collaborative solutions.
“In labs that are still open for testing or other purposes, there’s certainly heightened anxiety,” says Tony Vanden Bush, Client Support Specialist. “I feel that right now, I need to help them deal with that stress however possible.”
Last week, Tony was contacted by a lab at the University of Minnesota that was preparing to serve as a secondary COVID-19 testing facility for a nearby hospital lab. The two labs needed to process up to 6,000 samples per day, and the university lab was far short of that capacity.
Researchers having been sharing plasmids ever since there were plasmids to share. Back when I was in the lab, if you read a paper and saw an interesting construct you wished to use, you could either make it yourself or you could “clone by phone”. One of my professors was excellent at phone cloning with labs around the world and had specific strategies and tactics for getting the plasmids he wanted. Addgene makes this so much easier to share your constructs from lab to lab. Promega supports the Addgene mission statement: Accelerate research and discovery by improving access to useful research materials and information. Many of our technology platforms like HaloTag® Fusion Protein, codon-optimized Firefly luciferase genes (e.g., luc2), and NanoLuc® Luciferase are present in the repository. We encourage people to go to Addgene to get new innovative tools. Afterall, isn’t science better when we share?
I’d like to focus on some tools in the Addgene collection based on NanoLuc® Luciferase (NLuc). The creation of NanoLuc® Luciferase and the optimal substrate furimazine is a good story (1). From a deep sea shrimp to a compact powerhouse of bioluminescence, NLuc is 100-fold brighter than our more common luciferases like firefly (FLuc) and Renilla (RLuc) luciferase. This is important not so much for how bright you can make a reaction but for how sensitive you can make a reaction. NLuc requires 100-fold less protein to produce the same amount of light from a Fluc or RLuc reaction. NLuc lets you work at physiological concentrations. NLuc is bright enough to detect endogenous tagged genes generated through the CRISPR/Cas9 knock-in. NLuc is very inviting for endogenous tagging as it is only 19kDa. An example is the CRISPaint-NLuc construct (Plasmid #67178) for use in the system outlined in Schmid-Burgk, J.L. et al (2).
Imagine for a moment this conversation between a senior graduate student and his dissertation adviser:
“Everybody’s doing it. Physicists and computer scientists do it all the time. And even Carol Greider has done it, and she’s a Nobel laureate.”
“Yes,” his adviser from her work, “she is a Nobel laureate; she can take that risk. But, I don’t have tenure, and I am still working on my first NIH grant. You don’t have a degree yet. None of these things—your PhD, the grant renewal, my promotion—come without publications in a peer-reviewed journal, and most peer-reviewed journals in our field, at the least the ones that count for grant renewals and promotion, don’t allow publication of previously released data.”
“But why let the publishers decide what is good science—why not let the scientific community decide and crowd source the review?”
“I agree, but I also want a future. We write the paper and submit it. So do your homework, let’s go to a journal with a short turnaround time, open review, and a reputation for publishing good science.”
Open Data and the Biological Sciences
The debate over prepublication in biology is raging. Prepublication is the standard in physics, computer science, math, and economics to get results publicly available quickly for scientific commentary, and it doesn’t seem to interfere with career advancement and grant renewals. Is there a good reason that the same practice isn’t followed in the life/biological sciences? Continue reading “Prepublication: Everybody’s Doing It?”
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.