Benchling provides a structured and automated way to manage instrument files through the File object—a core object type that improves:
- data traceability
- metadata capture
- downstream usability
FIles ingested via Benchling Connect, are transformed into searchable, permissioned, and metadata-enriched resources across your scientific workflows.
- Automatically Created File Objects: Files detected via Benchling Connect are automatically created as File objects.
- Permissioned & Searchable: Files are associated with metadata, are @mentionable, and appear in global search.
- Structured for Downstream Use: Use File objects as inputs for runs and generate analysis-ready results.
- Accessible via API: Files can be created, retrieved, archived/unarchived using the Benchling API.
FAQs
Q: How is this different from previous file storage in Benchling?
A: Files are now clickable objects with metadata and permission control, unlike legacy blob attachments. However, this doesn’t mean that all attachments can become File objects. File objects are only created for data that comes in through a Connection, if you want to associate data with entity schemas, Inventory schemas, or Results schemas, you will still use attachments. If you need structured, permissioned, searchable data, consider incorporating Datasets into your data management plan.
Q: Are my older Connect files automatically updated?
A: Yes, with some exceptions:
- Archived files
- ASM-transformed files (.csv, .json)
- Intermediate blobs from Connect transform steps
Q: Can I mention File objects in notebooks?
A: Yes! Use @ to tag File objects in notebooks and worksheets.
Q: Can I access Files via the API?
A: Yes—Files support full lifecycle management through Benchling’s public API.