Plasmid Maps That Survive a Tool Change: Interchange Versus Lock-in
Open versus proprietary plasmid file formats are two archive classes, not two brand loyalties. An open file is an interchange record another tool can parse. A proprietary file is a vendor project. If only one vendor can open it, the map is not archived. Migrating plasmid files is the procedure for moving copies. Cutover is the Monday the default changes. This page only names the classes those later walks still have to carry.
If Only One Vendor Can Open It, the Map Is Not Archived
The search is open vs proprietary plasmid file formats. Keep the test. NCBI’s GenBank sample record is a public sequence layout: locus, features, and bases that any compliant parser can read. INSDC is the collaboration that keeps that layout shared. Neither page is a cloning-CAD manual. They are the reason a .gb or .gbk companion is an interchange object. A vendor project file can store layout, enzyme preferences, and history that another tool will not read. That extra comfort is not an archive. It is a dependency.
Prefer a pair: the working project file if you need it, plus an interchange copy that names features. Reject a core policy that stores only the vendor binary because “everyone here has the license.” Licenses lapse. People leave. The next tool will not owe you that binary.
What Survives a Tool Change
| Dimension | Interchange record (GenBank / FASTA plus features) | Vendor-locked project file |
|---|---|---|
| Who can open it later | Any tool that reads the public layout | Usually that vendor, sometimes a paid converter |
| What typically survives | Sequence, many feature names and coordinates | Layout, local history, vendor-only annotations |
| What often disappears | Pretty canvas settings | The map itself, if the license or converter is gone |
| What it can prove | That this sequence and these features existed | That you once had that vendor |
| Archive status | Eligible once features are named | Not an archive on its own |
FASTA alone is interchange for the bases and a weak archive for a plasmid, because it drops features. GenBank-class files are the usual feature-bearing interchange. Neither is a promise that every vendor annotation will round-trip. The test is whether a second tool can reconstruct the molecule well enough to find marker and origin. If it cannot, you stored a picture of a dependency.
What Each Class Can Prove Later
When a construct is challenged next year, the interchange file answers “what sequence did we claim.” The vendor file answers “which program we liked.” Those are different proofs. A core that can only open last year’s maps inside one installer has a collection of projects, not a library. The migrate page will tell you how to copy. It will not tell you that the copy is an archive. Provenance documentation still owns source, passage, and license. A locked file can carry those fields and still fail the openability test.
Hybrid storage is allowed. Keep the vendor file for daily work. Keep the interchange file for the identity that must survive a tool change. Do not invert that pair. Do not treat a cloud workspace as an archive if the only export it offers is its own binary. That is lock-in with a login.
Require an Interchange Path Before You Trust a Workspace
Name the interchange path before anyone debates a destination brand. ZettaGene is a workspace that must accept that path after the classes are distinct. Official product language describes sequence visualization and standard molecular-biology jobs. Official simulation coverage is restriction, Gibson, and homologous alignment. Golden Gate is not a Zetta feature on those pages. If the workspace cannot write or read an interchange file that another tool can open, you do not have an archive destination. You have another project folder. Cutover still waits until old IDs resolve. Formats come first.
A practical archive pair is boring on purpose. Keep the daily vendor file if the canvas is faster. Write a dated interchange copy the same day the map is declared complete, and store that copy where a second person can find it without the original installer. If the only backup is a screenshot of the circular map, you archived a picture. If the only backup is a cloud workspace that cannot emit GenBank-class text, you archived a login. Re-open the interchange file in a second tool before you trust it. The second open is the proof. The first save is only a hope.
Frequently Asked Questions
Is a vendor project file an archive of the plasmid map?
Not by itself. If only that vendor can open it, you have a project file, not an archive.
Is migrating files the same as choosing an interchange format?
No. Migration is the move. This page names which file class can survive the move.
Related Articles