CDD Vault Update: Project-Based Collaboration
November 19, 2010
… and we’re back! We’ve spent the last three months building projects, the next generation of CDD Collaborate.
We built projects to help you do the following kinds of things:
- Collaborate on live data: Colleagues at another institution will be running followup studies on your hit list, and you’d like them to upload the data they generate directly into your CDD Vault.
- Share data selectively: You only want your collaborators to see a specific hit list, not any other data in your vault.
- Organize your data: Focus only on the data you’re currently working on, while still being able to search across all of your historical data when you need to.
- Keep data private until it’s ready to share with your colleagues: Create a private project to store new compounds you’re synthesizing, then share them with other projects when they are ready for testing.
Molecules, batches, plates and protocols can belong to multiple projects. Rather than a simple folder system, they are organized like a Venn diagram.
A molecule can belong only to project A, or only to project B, or to both project A and B. This means you can screen one compound library in three separate projects, without creating copies of the compounds.
Runs and messages only belong to one project. In this case projects work more like folders in a filing cabinet:
A run of a protocol can belong to only one project at a time: either to A or to B. This restriction makes the organization of your assay results clearer.
You will now see a project sidebar when exploring and searching data in CDD. Simply toggle the selected projects to filter what data is visible.
Anyone who can add data to a vault can create a project. To do this, click on the Manage Projects tab at the top and click “Create a new project”. After filling out the form with the name of the project, you’ll be returned to the list of projects to add other Vault members to your project. Note that if you’ve made a mistake, you can still delete the project at this stage. Once you’ve added any data, however, deleting a project is disabled.
Adding data to projects
Each time you create a new resource (protocol molecule, run, etc.) you are now asked to select an initial project to contain it.
When viewing an existing resource such as a protocol, you’ll see a link to Manage Access in the side panel. This allows you to share the resource with additional projects.
Manually sharing a protocol with some projects is reasonable, but how can you share a 50,000 compound library? Importing data is the best way to add large numbers of plates, molecules or batches to a project. For example, let’s say you just screened your existing library against a new target and want to add the compounds and assay results to a new, empty project. Simply choose that project when uploading the assay results, and the software will share all the molecules with the new project, so long as you have access to those molecules in another one of your projects.
If the person uploading the assay results is not a member of a project that contains the compounds, someone else would have to import the list of compound names or plate/well locations into that project to ensure that the molecules are available to the person performing the upload. For plates it is even easier: you only need to upload a file that mentions each plate once, and all molecules and batches on that plate will be added to the project.
Projects and beyond
This is the first major release of projects functionality, and we’re excited to see how you make use of it. We are planning to touch base with customers over the next several weeks to help you get started with this new collaborative tool, and to hear what’s working and what could be better. As always, if you have feedback outside of that process, please feel free to contact support.