Every measurement with context and metadata Raw data locked, edits traceable Sharing in line with the data management plan

Custom app for managing measurement data in research projects

Appfront builds apps for research groups, knowledge institutions and R&D departments that take a lot of measurements in projects: every measurement recorded with instrument, setting, sample, date and who took it, the raw data stored immutably, every processing step traceable, and datasets shared with partners in line with the data management plan. So a result can still be reproduced two years later and nobody has to dig through folders full of files named final_v3_new.

What is a measurement data management app for research projects?

A measurement without context is just a number. To understand or reproduce a result later, you need to know which instrument, which setting, which sample, under what conditions and by whom it was taken, and what happened to the data afterwards. A measurement data management app records that at the moment of measuring, not afterwards in a lab notebook.

Without such an app, raw files sit on the laptop connected to the instrument, processed versions in a shared folder, and the metadata in a notebook or a spreadsheet that isn't linked to the files. A PhD student who leaves takes the knowledge of which file is which with them. A partner in the consortium asks for a dataset and gets a zip file with an explanation in an email. And a funder who asks for a data management plan gets a plan that isn't followed in practice.

We build custom because the app has to fit your research: which instruments you use and which files they produce, which metadata are standard in your field, how you work with partners, and which storage and repository your institution requires. A general document system stores files; it doesn't know the measurement behind them.

Measurement with metadata

With every import, the metadata according to the project's schema: instrument, setting, sample, conditions, date and researcher. A measurement without the mandatory fields isn't saved.

Raw data locked, edits traceable

Raw data is stored immutably. Every processing step, such as calibration, filtering or averaging, gets a version with the method and the source attached.

Sharing datasets

Datasets compiled per analysis or publication, shared with partners according to the permissions in the project, and exported in open formats with the metadata included.

How we build your measurement data management app for research projects

We start with the project: which instruments, which data streams, which partners, and what is in the data management plan that isn't happening yet.

1
Mapping data and agreements

The instruments and their files, the metadata that are standard in your field, the partners and their permissions, and the requirements from the data management plan.

2
Import and metadata schema

The import from instruments and data loggers, the metadata schema per type of measurement, and the immutable storage of raw data.

3
Processing and datasets

Versions and processing steps with method and source, compiling datasets, and permissions per partner and per dataset.

4
Export and maintenance

Export in open formats, the integration with your institution's repository, reporting for the data management plan, and ongoing maintenance after that.

What a measurement data management app for research projects actually does

The components below appear in almost every research project. Which ones you need depends on your instruments and on who you work with.

Instrument import

Files from instruments and data loggers are imported automatically or by drag and drop, with recognition of the format and the instrument.

Metadata schema

For each type of measurement, the mandatory and optional fields, with dropdown lists from your field, so metadata is comparable across measurements and researchers.

Raw data and versions

Raw data stored immutably with a checksum, and every processing step saved as a new version, with the method, the code or script, and the source.

Search and filtering

Search measurements by instrument, sample, period, conditions or researcher, across the whole project, without browsing through folders.

Datasets and permissions

Datasets per analysis or publication, with permissions per partner, and a persistent identifier so a publication points to the right version.

Export and archive

Export in open formats with the metadata included, to your institution's repository or an archive, ready for reuse in line with the FAIR principles.

Who we build a measurement data management app for in research projects

The app is intended for research where a lot is measured and where data is currently scattered across laptops, folders and emails.

University research groups

PhD candidates who come and go, and funders who ask for a data management plan. The metadata schema and the immutable storage are the core.

Professorships and applied research

Measurements in the field or at companies, often with students. Import from data loggers and sharing with partners matter most.

Company R&D departments

Test series for product development and confidential data. Permissions and the traceability of processing steps are what's needed.

Multi-partner consortia

Data from several institutions in one project. Permissions per partner and shared datasets are the core.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Technology and integrations

This page is about measurement data in research projects. For samples and analyses in a laboratory, see our page on laboratory software, for instrument calibration our page on calibration software, and for reports based on measurements our page on a research report app. You can read about our approach at custom software development.

If you work with questionnaires full of routing, randomisation and experimental conditions, there is our software for questionnaire routing and research design.

Import from instruments and data loggers Metadata schema per type of measurement Immutable storage with checksum Versions and traceable processing Integration with scripts and notebooks Permissions per partner and dataset Persistent references to datasets Export in open formats Integration with the institution's repository Reporting for the data management plan

Why Appfront for your measurement data management app for research projects?

A result is only as good as the data beneath it. That's what we build on: every measurement with its context, raw data that doesn't change, and processing steps that someone else can repeat.

Reproducible

From result back to the raw measurement, with every processing step in between. Anyone who wants to redo it in two years can.

Knowledge stays in the project

Metadata is attached to the measurement, not stored in the researcher's head. A departing PhD candidate leaves behind a dataset that someone else can understand.

The plan is followed

What's in the data management plan happens in the app: storage, metadata, permissions and archive. Accountability to the funder comes out of everyday practice.

Security and privacy in a measurement data management app for research projects

The app contains research data, sometimes confidential or containing personal data. Access is set up per project, per partner and per dataset, and every view, download and change is logged with name and time. Participant data can be stored pseudonymised, separately from the key.

The app runs in a European data centre or on your institution's own infrastructure, with encrypted storage and daily backups. Raw data is stored with a checksum, so you can demonstrate that it has not been altered.

Frequently asked questions about a measurement data management app for research projects

Questions researchers ask before getting started.

It reads measurements from instruments and data loggers, records the metadata for each measurement according to a fixed schema, stores raw data immutably, tracks every processing step as a traceable version, assembles datasets for each analysis or publication, and shares them with partners in line with the data management plan.

Yes. Funders often require a data management plan, and the app makes that plan executable: where data is stored, which metadata is recorded, who has access, and where it is archived. The reporting shows how the plan is followed in practice.

Data must be findable, accessible, interoperable and reusable. The app provides metadata according to a schema, persistent references to datasets, explicitly recorded access rights, and export in open formats, so a dataset can also be used outside your group.

In the first step, we look at which instruments you use and which files they produce. For common formats, importing is straightforward; for a manufacturer's proprietary formats, we write a reader, or we store the file with its metadata alongside.

Participant data can be stored pseudonymised, with the key kept separately and with restricted access. Access and use follow the terms of the consent given and the review by your institution.

No. The app is the working environment during the project; the repository is the archive afterwards. The app exports datasets with their metadata to the repository your institution prescribes.

Check that first. An electronic lab notebook records what was done, and that is enough if the data itself is small. Custom development makes sense if large volumes of measurements come from instruments, if metadata must be fixed per type of measurement, or if partners in a consortium need to share datasets with their own access rights.

Measurement data that still means something in two years?

Tell us which instruments you use, which partners you work with and what your data management plan says. We'll show you what the import, the metadata schema and the datasets look like.

Edit content