Notice for users of S. pombe clone sets and 26F09 clones


January 23, 2015

Notice for users of S. pombe clone sets and 26F09 clones

We, the RIKEN BioResource Research Center, regret to inform you that S. pombe raf2 gene clones SpEnt26F09, SpFFH26F09 and SpYFH26F09 contain defects and are needed to be deleted from the Entry, FFH-tag and YFH-tag clone sets, respectively.

These clone sets containing 4,812 clones each were deposited by a Japanese researcher in 2006. The depositor analyzed nucleotide sequences of all clones of the sets and published the results. We made copies in the culture conditions specified by the depositor and distributed these copies to our users. As the quality test, we analyzed terminal end sequences of several percent of clones randomly picked from the sets. For an individually requested clone, we have tested terminal end sequencing of every clone before shipment.

In 2007, we provided an individual 26F09 (raf2 gene) clone from the set after we confirmed the presence of the raf2 gene fragment in the 26F09 clone. But we did not perform detailed sequence analysis at that time.

Recently, there was a request for the 26F09 clone and we analyzed its sequence of vector-insert junction. We found that all SpEnt26F09, SpFFH26F09 and SpYFH26F09 clones lacked 81 bp just after att recombination site, including 7 bp of linker and 74 bp of the raf2 coding region.

We consulted with the depositor on this matter for a possibility that researchers might not be able to obtain expected results because of the 81 bp missing of 26F09 clones. The depositor told us that these clones should be deleted from the Entry, FFH-tag and YFH-tag clone sets.

It is often difficult for us to detect a small deletion such as these clones. We will keep doing our best to improve the quality of our resources to contribute to life science research. We ask you for your understanding and continuous support.

We have sent notes to all past users by January 13, 2015, expressing our sincere apology and explaining this matter.

If you have any question and concern on this matter, please feel free to contact us ( ).


Comments are closed.