A 5-minute read
Scientific work grows through conversations, shared observations, and decisions made along the way. A question raised during an analysis, a parameter explained in a comment, or a discussion with a supervisor can shape what happens next. That context is part of the research, and it needs a place alongside the work itself.
With our latest product release, Every project, one space, we are bringing four improvements together to make D.LAB a more connected workspace for research teams.
A logbook your whole team can write together
Research knowledge develops continuously. Observations become discussions, discussions lead to decisions, and those decisions shape the next experiment or analysis.
The project logbook now supports real-time collaborative editing, so multiple team members can contribute to the same document simultaneously. Researchers can capture observations, add explanations, and develop project notes as the work unfolds. The logbook becomes a shared record that everyone can help maintain.
Over time, this helps preserve the knowledge behind a project. When a new PhD researcher joins or a colleague moves on, their successors have more than results to work with: they have a record of how the team got there.
In-context Collaboration
Advisors and collaborators cannot always be at your desk when an issue arises. Yet meaningful feedback often depends on seeing the work in context: what the researcher is trying to achieve, what has already been attempted, and where the analysis stalled.
This release brings more of that collaboration into D.LAB. On the details page of any running virtual desktop, researchers can leave comments and tag colleagues with an @-mention, alerting them immediately and bringing them straight to the session overview. When written feedback is not enough, researchers can grant access to the running desktop itself so an advisor or colleague can step in and investigate the issue firsthand, without needing to recreate the environment or transfer data.
These updates make getting timely support faster and far less disruptive, leaving researchers fully in charge of when they share access. Troubleshooting becomes a natural part of the research workflow, with all the necessary context already in place.
Analysis that still makes sense months later
An analysis may be clear on the day it runs. Months later, the reasoning behind it can be harder to recover. What was the job intended to test? Why was a particular parameter used? What went wrong, and what should someone try next?
Job comments and keywords help keep that context attached to the job. Comments give researchers space to explain their intent, record decisions, and document failures. Keywords add useful labels that help identify what a job relates to.
For researchers returning to earlier work or reviewing a colleague’s analysis, these details make it easier to understand what happened and why. Less knowledge depends on someone remembering the explanation months later.
A clearer view of your lab
A shared research environment also needs a clear starting point. The redesigned lab space introduces a simpler view, with usage across all licenses visible from the home page. This gives teams a more accessible overview of lab usage and makes it easier to see that information in one place.
Keeping the work and its knowledge together
These four updates support a common goal: keeping research, conversations, and project knowledge together. D.LAB helps your team carry more understanding forward with every project.
