Updating a Raw Read Submission Programmatically

The main difference between programmatically creating new experiment and runs and updating existing ones is that the MODIFY action should be used instead of the ADD action:


Please note that the new experiment or run XML must either contain the original alias or the assigned accession number for the correct object to be updated.

Detailed advice on how to programmatically update XMLs including instructions for retrieving previously submitted XMLs can be found in Programmatic Submission Options. Experiment and run XMLs can also be manually edited using the Webin submissions portal.

Reasons for Updating Experiment XML

Typical reasons for updating experiment XMLs include:

  • Change the library descriptor:
   <LIBRARY_CONSTRUCTION_PROTOCOL>Messenger RNA (mRNA) was isolated using the Dynabeads mRNA Purification Kit (Invitrogen, Carlsbad Ca. USA) and then sheared using divalent cations at 72*C. These cleaved RNA fragments were transcribed into first-strand cDNA using II Reverse Transcriptase (Invitrogen, Carlsbad Ca. USA) and N6 primer (IDT). The second-strand cDNA was subsequently synthesized using RNase H (Invitrogen, Carlsbad Ca. USA) and DNA polymerase I (Invitrogen, Shanghai China). The double-stranded cDNA then underwent end-repair, a single `A? base addition, adapter ligati on, and size selection on anagarose gel (250 * 20 bp). At last, the product was indexed and PCR amplified to finalize the library prepration for the paired-end cDNA.</LIBRARY_CONSTRUCTION_PROTOCOL>
  • Move the experiment to a different study by changing the STUDY_REF:
    <STUDY_REF accession="..."/>
  • Associate the experiment with a different sample by changing the SAMPLE_DESCRIPTOR:
    <SAMPLE_DESCRIPTOR accession=".."/>
  • Include more information in experiment attributes:
   <TAG>library preparation date</TAG>

Reasons for Updating Run XML

Most common reason for updating run XMLs is to change the file checksum:

<FILE filename="mantis_religiosa_R1.fastq.gz" filetype="fastq"
    checksum_method="MD5" checksum="9b8932f85caa54e687eba62fca3edce2"/>

You may need to change the checksum attribute for a file when a file has failed to be archived because of a mismatch between the provided and computed MD5 checksums.