When a file says “thermo” and your pipeline is looking for Thermo Fisher Scientific, the result never reaches the ELN. Nothing errors, and nobody finds out for weeks. This showcase covers how to fix that where it starts.
Labels are how you find data and how a pipeline decides what to do with a file. They only work if everyone writes them the same way. In this showcase, TetraScience's head of product Justin Pront demos two new Scientific Data Foundry capabilities coming in the December platform release. Scientific Solutions Partner Benedikt Brink then shows a concept we’d like your feedback on.
What you’ll see
- Controlled lists. Connect a label to an approved list of values. You see what’s already off the list without changing any files, and near-misses get flagged as people type them.
- Metadata Health. Check every file against the labels your policy requires and group the failures by source. You can trace a bad value back to the agent that has been setting it on every file.
- Instrument registry (concept). Keep each instrument’s vendor, model, type and site in one place, so its files arrive already labeled.
You’ll also see how your own vocabularies come in with the next release in early 2027, from a spreadsheet or an ontology tool such as CENtree.
Speakers: Justin Pront, VP, Product · Benedikt Brink, Scientific Solutions Partner · Nicole Rose, Product Manager/host