design_gene_fragment_order
Read-only
Write the sheet IDT's gene-fragment PLATE upload takes for one or more designed fragments: one worksheet per 96-well plate, wells in the template's own order, and the template's four columns (well, name, sequence, 5' phosphorylation).
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| names | No | a name per fragment, in the same order. Required with `sequences`: a well is ordered by name, so an unnamed fragment is refused rather than numbered. | |
| _files | No | The project: record references shaped like _subject. Their records become library documents a tool names in sequences/parts/document; a trace or alignment is found by file name. | |
| feature | No | order a named feature of the open record instead of the whole record: the insert rather than the vector it sits in. Advanced. | |
| product | No | which IDT fragment product to order the fragments as. It sets the length range a fragment must fall in, and eBlocks take a per-plate minimum. Values: idt-gblocks (gBlocks Gene Fragments (125–3,000 bp)), idt-eblocks (eBlocks Gene Fragments (300–1,500 bp)). | idt-gblocks |
| _subject | No | The record to act on: exactly one of sequence, accession (+source), sample (an id from list_samples) or file ({name, text} or {name, base64}); record_index picks one record of several. | |
| sequences | No | the fragments to order, 5'→3'. Leave unset to order the open record, or the current selection or named `feature` of it, under the record's name. | |
| plate_name | No | the plate's name, which becomes the worksheet's name. Several plates get ' (2)', ' (3)' appended. | Plate 1 |
| phosphorylate | No | ask for 5' phosphorylation on every fragment. IDT offers it for blunt cloning only. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| rows | Yes | every plate as header-first rows in the template's column shape, keyed by worksheet name: what the .xlsx holds | |
| sheets | Yes | one entry per PLATE: its worksheet name and every laid-out well, each with the published limits it sits outside | |
| columns | Yes | the template's header row | |
| profile | Yes | the vendor profile the length range came from, with its page and retrieval date | |
| reading | Yes | what the order is, generated from the laid-out plates | |
| refused | Yes | every fragment left OUT, with the reason | |
| plateCount | Yes | how many plates the fragments needed | |
| plateMinimum | Yes | set when the product takes a minimum per plate and a plate falls under it; empty otherwise |