Perhaps you plugged in your MiSeq for the first time only a couple of weeks ago. You’ve completed the requisite validation runs and constructed some handsome libraries for your next set of experiments. Congratulations, you’re off to the races! For some, this exciting period is all about testing new experimental designs. For others, it’s about validating previous results. But I would wager that not enough users begin to think about implementing a long-term system for data management and backup.
You’ve no doubt heard that BaseSpace is a simple, and virtually free way to archive and share data. But there are a number of reasons that users might also want to work with local copies of their results – to run the data through their existing HiSeq pipelines, to visualize it in their favorite browser, etc. The truth of the matter is that there are often good reasons to keep a local copy of your data on hand in addition to using BaseSpace. We like to call this “dual mode,” and it means that there will be copies of MiSeq Reporter reports on your MiSeq and in BaseSpace when each run completes. If you are at all nervous about streaming data and adding another layer of complexity to your MiSeq repertoire, you can rest assured. What you’re really creating is a free layer of redundancy to your precious data.
Getting the data into BaseSpace is a nearly invisible process and, regardless of network conditions, won’t affect the progress of your local run and analysis. Here’s how it’s done. On MiSeq’s “Setup Options” screen, there is a checkbox that allows you to “replicate analysis locally on MiSeq.” And for many new users this will be the best way to begin using BaseSpace.
It’s important to remember that the diversity of analysis applications made available through BaseSpace will grow dramatically over the coming year, so keeping your data in a place that will allow for easy reanalysis is key. There is a similar opportunity for MiSeq runs that utilize a reference genome not currently found in BaseSpace. My next post will cover this topic in more detail.
So you can have it both ways – local and cloud-based storage, local and cloud based analysis. What’s stopping you?