Skip to content

Search and import parts

The Registry search lets you find a known part by number or explore parts by their title, role, or description. Search results remain external until you choose to import a part.

Biological sequence import interface in Molecular Studio
Review Registry metadata and sequence content before importing a biological part into FlaskTrack.

Search for parts

  1. Open Molecular Studio → iGEM Registry.
  2. In Registry search, enter either:
  3. a complete part number, such as BBa_B0034; or
  4. descriptive text, such as ribosome binding site or fluorescent protein.
  5. Select Search Registry.
  6. Review the returned cards and select Review and import for the relevant part.

Exact part-number searches

A complete Registry identifier uses exact lookup. This is the best choice when you already know the part you need.

Part identifiers are not case-sensitive in FlaskTrack. Both BBa_B0034 and bba-b0034 resolve to the same Registry record.

Descriptive searches

Descriptive search results are ranked by the Registry. A result may match text inside a description rather than the primary part title, so review the part number, role, sequence length, and description before selecting it.

You can move through result pages with Previous and Next.

Review a Registry record

The part page may include:

Field Meaning
Part number The Registry identifier, linked to the source record.
Title and description The community-provided name and functional description.
Role The Sequence Ontology or Registry role assigned to the part.
Authors Contributors listed by the Registry.
Date entered When the part was entered into the Registry.
Source Source or citation text supplied with the record.
Sequence The published Registry DNA sequence, when available.
Length and GC content Basic metrics calculated from the published sequence.
Sequence features Available annotated regions and coordinates.
Registry usage The number of other Registry parts reported as using the part.

Use Open in Registry, Design page, and Experience page to inspect additional source information when available.

Note

Registry records vary in completeness. A missing source, feature list, or composition does not necessarily mean the part is unusable; it means that the field was not available from the Registry record when FlaskTrack loaded it.

Import a biological part

  1. Review the Registry record and confirm that the part number and sequence are the ones your team intends to reference.
  2. In Import biological part, enter a local display name. FlaskTrack suggests the Registry title, but you may use terminology familiar to your organization.
  3. Select Import into FlaskTrack.

After the import, FlaskTrack opens Registry parts and verification and shows an Import complete summary. The summary identifies the local biological-part record, Registry number, role, imported sequence length, description, and source provenance. The new part also appears under Imported Registry parts, where it remains available after you leave the success page.

The optional comparison form is prepared with the imported part and Registry number. You can record the reference-sequence comparison immediately or return to it later.

FlaskTrack stores the part as an organization-scoped biological-part record. It preserves:

  • the Registry UUID, part number, slug, and source URL;
  • title, description, role, topology, and source;
  • the Registry sequence and its SHA-256 digest;
  • authorship and entry dates;
  • available chassis, feature, composition, and usage metadata; and
  • the complete external metadata snapshot used during import.

Importing the same part again

Registry UUIDs are unique within your organization. Importing the same Registry part again refreshes its external metadata instead of creating a duplicate. Your local display name remains under your team's control.

What import does not do

Importing a Registry record does not:

  • create a physical plasmid inventory record;
  • mark a strain or sample as containing the part;
  • release a Molecular Studio design to the plasmid catalog;
  • verify that locally held material matches the Registry sequence; or
  • validate the claimed biological function, efficacy, or safety.

To compare an existing FlaskTrack sequence with the Registry, continue to Verify plasmids and genetic constructs.