> For the complete documentation index, see [llms.txt](https://docs.terraref.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.terraref.org/revisions/technical-documentation/data-processing-pipeline.md).

# Data Processing Pipeline

![](https://4042473796-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-L9HQFTifPjun_Gj6_At%2F-LBSUUgv7FZloAHqshV_%2F-LBSUXP7mM6URjSRg4eW%2Fpipeline.jpg?generation=1525208197961568\&alt=media)

## Maricopa Agricultural Center, Arizona

## Automated controlled-environment phenotyping, Missouri

![](https://4042473796-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-L9HQFTifPjun_Gj6_At%2F-LBSUUgv7FZloAHqshV_%2F-LBSUXPXJHMtNVONQRaH%2Fterraref-danforth-pipline-v3.jpg?generation=1525208209398906\&alt=media)

At two points in the processing pipeline, metadata derived from collected data is inserted into BETYdb:

* At the start of the transfer process, metadata collected and derived during Danforth's initial processing will be pushed.
* After transfer to NCSA, extractors running in Clowder will derive further metadata that will be pushed. This is a subset of the metadata that will also be stored in Clowder's database. The complete metadata definitions are still being determined, but will likely include:
  * plant identifiers
  * experiment and experimenter
  * plant age, date, growth medium, and treatment
  * camera metadata

## Kansas State University

## HudsonAlpha - Genomics