the community site for and by developmental biologists

11 thoughts on “A primer or two in collegiality and mutual benefit”

  1. I can’t even remember how we kept track of primers in the lab. There may have been a database (we definitely had a database for constructs, and any primers used to create the constructs were listed in there.) I also definitely had a binder with all the info on the primers I designed/ordered/used, and for RT-PCR that contained test results including optimal temperatures etc.

    Also, I’ve played with the new polls feature before I went on vacation, but I forgot the details. It’s mostly straightforward how to create one from the sidebar menu, but to add it into the post you had to take note of a number and I forgot where that was so I’ll have to go through it again. It only does multiple choice (not yes/no) so if you can think of a question with multiple answers to chose from, that can be made into a poll. E-mail me question + answers and I can try to add a poll if you want.

    1. So, Eva, what would it take to convince you to enter/upload those validated, tested RT-PCR primers in something like RTPrimerDB?

      Because my point is, no matter how good an idea these sort of things seem to be, it’s rare that we want to consecrate more than a fleeting amount of time at any one sitting for the commonwealth, without some sort of incentive. I can’t imagine what the incentive would be for you to do that, unless somehow it was something like plasmids where a person who used them can at least say thank you in the publication, or use the words “generously provided by” etc.

  2. Thing is, I’m not sure that me testing them in *my* system would help someone else. They still have to test if it works for them.
    And no incentive indeed. That’s usually the problem with sharing anything… Although there have been some interesting discussions lately (including at Science Online London) about credit/incentive for uploading data, and primers would probably fit that same bill. The idea that’s being thrown around is that if you can actually say on something like a grant application that you shared primers/data, that it would eventually *matter*.

  3. Thanks for this post. I did my post-doc in a zebrafish lab, and it was pretty much every person for herself in terms of keeping track of primers for amplifying genes. We were more communally organized when it came to the primers used for amplify the SSLPs important for mapping mutants. More than a few years ago, many of the microsatelites in the zebrafish genome were characterized, and now nearly all of the SSLP primer sequences can be found at ZIRC (Zebrafish International Resource Center) or on the Ensemble genebuild.

    Our lab keeps a relatively up-to-date database of all the primers used for mapping, but the only info is the sequence and the genomic location. It would be a great idea to include a column for efficiency of amplification, etc.

    To keep track of my personal oligo collection (generally used for amplifying genes/partial genes from cDNA or from plasmids), I use a notebook dedicated to primers which lists the oligo sequence, its use, and sometimes the conditions for optimum amplification. I always think that I should transfer this to a database, but then I am deterred by the mind-numbing work of typing all those sequences. Maybe if I had started out keeping an excel spreadsheet, instead of a paper notebook…I would feel differently…

    1. I appreciate the pointers to the ZIRC, which I didn’t know about, and of course to, which I did.

      It’s not bad already to have the database the way you do, but wouldn’t it be better for labs to put that sort of thing on their websites at least, on their open lab notebook wikis even better?

      I only ever type sequences myself – I am too prone to copy errors if I write them out by hand, and I make ample use of cut-and-paste. So spreadsheets and text documents are mandatory.

  4. Therer are two intersting topics here. First, how some lab publishes results with some primers and then another lab tries to replicate those results without success? It is supossed that every result from a publication should be replicated independently by any scientist, and this implies that the publication should contain all the necessary information. In the case of PCR, the publication should include the sequence of the primers used, the protocol of the PCR (template concentration, primer concentration, etc) and the number of cycles used in every test. In human genetics, it is common to see that info. But in other disciplines, including developmental biology, it is not so common. Researcher should not assume that “every scientists knows how to make a PCR”, because that’s not the point. The point is what’s the whole idea of a publication.
    The second issue here is the behaviours of the research community. Some journals establishes in their author guidelines that the author agrees in sharing reagents, vectors, primers, etc, with other researchers if they request them. But, in reality, once the paper is published, some authors refuse to share those reagents. And also some authors do not publish detailed protocols, and when some fellow researcher writes an email to those authors, they don’t answer. That is annoying, and journals should have mechanisms to punish those authors that do not respect the guidelines. In the most extreme of the cases, the journal may even retract the paper, specially when authors refuse systematically to share detailed protocols and reagents, because such a behaviour indicates that somethin is wrong, or that results are not easily reproduced, going against the idea of a scientific report.

  5. As a developmental biologist by training but working in human genetics, I can tell you that it’s not instinctive for many of my colleagues to include even primer sequence information. Conditions are, like for immunohistochemistry, only really necessary if they are not standard, though a Tm can certainly save time. I don’t have a problem with these shortcuts.

    I do have a problem with malicious tampering – not-full disclosure. Easy enough to chalk things up to a typo but I have seen a great deal of “mistakes” and necessary omissions which makes me think that, on occasion, someone in the author list wants to control who does what with the information and oblige a scientist to write them and reveal their interest. Perhaps as a potential competitor?

    Anyhow, I firmly believe that when a “corresponding author” does not correspond, that the journal is under some reponsibility to intervene. I doubt this would ever go to the point of retraction but it would probably be effective for a representative of the journal to point out that continued behavior of the sort would preclude any other submissions to that journal, and that reputations get made and broken very easily.

  6. We always publish primer sets for any PCR-based assay we use in a paper. This is important for others to be able to repeat your work.

    In ancient times (1980’s-1990’s), for our first thousand oligos made, we used to scrupulously keep a log book of each oligonucleotide sequence, its extent of purity, and details on its use. Since automated synthesis has become much cheaper and we usually make many oligos at once, we now just keep the quality control page from the prep, which includes the sequence and basic information about the oligo. The quality control pages are kept in a lab resource binder. Each oligo is still given a lab number, in the binder, and stored in special boxes in our -80oC freezer. We have over 2500 oligos in the lab. So many are made and the cost has gone down, such that it is no longer economical to enter and check the sequence of each one in a database.

    1. Thanks for your thoughts, Ken. So, we do sort of the same – we keep of course such binders with all the sequences in it. However, I still think that is not the most efficient solution.

      a. what if the binder is destroyed somehow? (Well, perhaps you can pull the sequences out of the supplier again, to a certain extent, and out of your publications, for the ones that were published, and kudos for your policy!)

      b. Searching for information is not easy in such a binder – or your earlier log book – and at some point the primer sequences actually were text strings on a computer, to place the order. Why stay analog when it is possible to paste them into a digital file, and later search by keyword or sequence, as well as to store that precious resource in more than one location?

      (I’ve been through a lab fire before.)

      Now, for everything from the past, I totally understand why no one wants to go back and whip their primer data into standard shape. But prospectively? Or for re-orders?

      And, my point is, wouldn’t it be even MORE fantastic if there were a way to upload such files, perhaps standardized in format, to a central resource for the entire community? That is, no more work than the original entry to place the primer order itself, and then all one would have to do is check off a “validated” kind of box, and off it goes… and the resource could automatically calculate what the primers amplify, and one could add metadata if wanted.

      A girl can dream.

  7. Thanks for the post. I’ve worked on two non-model systems (with unsequenced genomes) where every gene has had to be degeneratively amplified. Usually, everyone in the lab has their own list of the primers that they’ve used. Then, if a particular gene amplified is published, the degenerate primers should be included in that publication. Realistically though, many additional genes (especially from non-model organisms) are amplified that are never published so it would be great to have some way of describing those. Some of the non-model organisms that people work on have such a small community that I doubt a primer database exists. What would be very useful (which might exist) is a database of all degenerate primers used, what organisms people have used them in, and perhaps also what degenerate primers were designed but did not produce a product.

Leave a Reply

Your email address will not be published. Required fields are marked *