LogoDocumentation

Automated data ingestion from scientific instruments

How research teams, laboratories and core facilities can move data from large scientific instruments into managed storage automatically, with metadata attached.

Modern instruments produce data faster than people can copy it. Microscopes, spectrometers, sequencers, tomographs and simulation workflows generate gigabytes to terabytes per session. In many labs, those data still travel by USB drive, sit on the instrument PC until its disk fills up, or end up in personal folders without a record of who measured what, on which instrument, with which settings.

This documentation shows how to replace that manual handling with an automated ingestion workflow. In such a workflow, data leave the instrument as soon as a measurement ends, land in managed institutional storage, and carry the metadata needed to find, share, process and eventually publish them.

CEITEC dataset workflow: data and metadata from the instrument and console PC to central storage, with sharing and processing, then transfer to repositories and publication with a DOI

Click the image to open it in full size.

What automation gives your team

  • No more manual copying. Data move from the instrument PC to managed storage automatically. Nobody carries drives between rooms or waits for overnight copies.
  • Context is captured at the source. Every dataset is linked to the instrument, the operator, the project and the experiment. Technical metadata from the instrument and descriptive metadata from the user travel with the files.
  • Instrument PCs stay clean and safe. Data no longer pile up on ageing, often unpatched acquisition computers. Some solutions also keep those computers isolated from the network.
  • Faster access for the whole team. Collaborators open the data from their office, a cluster or a cloud notebook as soon as the measurement ends.
  • Ready for FAIR data and publication. Structured metadata, persistent identifiers and repository integration make it far easier to publish data that support a paper.
  • Institutional control. Data are stored as an institutional asset with access control, retention and backup, not as files owned by whoever happened to be at the instrument.

How it works in a nutshell

  1. Before measuring, the operator selects or creates a project and dataset in a web application, or the instrument is already pre-configured for it.
  2. During measurement, the instrument software writes data to a local folder as usual.
  3. Ingestion runs automatically. A client on the instrument PC, or a central service that pulls from it, transfers the files to managed storage and verifies the transfer.
  4. Metadata are recorded alongside the data: who, when, which instrument, which project, plus user-filled forms based on templates.
  5. Data are available for browsing, sharing, processing and later publication.

Read more in How automated ingestion works.

Available solutions

Three solutions are documented here. They solve the same problem with different trade-offs, so pick the one that fits your instruments, network and storage. If unsure, start with Choosing a solution.

Who this is for

  • Research teams and principal investigators who want reliable access to their measured data, with context, without chasing files.
  • Core facility and laboratory managers responsible for shared instruments used by many groups.
  • Instrument operators who run measurements and want the data to “just arrive” in the right place.
  • Data stewards who care about metadata quality, retention and publication.
  • IT and infrastructure administrators who deploy and operate the systems. Each solution has a dedicated For administrators section.

Where to start

Funding

This activity is supported by the EOSC CZ initiative, funded by the European Union and the Ministry of Education, Youth and Sports of the Czech Republic.

Funded by the European Union, Ministry of Education, Youth and Sports and EOSC CZ

publicity banner

On this page

einfra banner