CDD Blog

cdd-vault-update-say-hello-to-the-new-api

Written by Jasmyne Bunin | Nov 20, 2012 8:00:00 AM
For those of you that have been eagerly awaiting a way to connect your CDD data repository to other applications— the beta version of the API is here for your testing and coding pleasure! In addition to the Application Programming Interface, we've also updated the search results display and the handling of units of measurement.

Details by Default

When searching, the results will now display all batch and replicate readouts on separate table rows by default.

You still have the option to switch to the "batch/run" or "summary" display mode by using the "Customize your report" link above the result table.

Units of Measurement

We have introduced a concept of "data type", and streamlined the units of measurement handling when defining readouts in a protocol.

The "data type" is required when defining a new readout, while the "unit" field is now free-form and optional. No more scrolling through a long list!

Data types include:
  • Number can store any numeric value, as well as permitted numeric modifiers (=, +/-, >, >=, <, <=). This is the preferred data type for most experimental measurements. You can specify the units of measurement when choosing this data type, and this unit label will be displayed together with the readout definition name throughout CDD. For example: "IC50 (μM)".
  • Integer is the same as Number, except any decimal fraction will be rounded off when you import data.
  • Text can contain any alphanumeric value, and will be searched as text strings. If you plan to search your data by numeric ranges (e.g. >1 or <10), you should use the "Number" data type instead.
  • Reference is a special data type that allows you to cite PubMed and other references stored in your CDD reference module.

CDD API

The CDD API is currently in beta, but is available for you, the eager crowds of testers! This release allows you to programmatically access a saved search. Here are the basic requirements:
  1. An administrator of the vault must enable API access (under the “Manage Vault” tab)
  2. You create an API key (under “Account”)
  3. You use this key to connect to the API via HTTPS, programmatically accessing the results of saved searches

Head over to the Support Portal to see the full API documentation. This beta release of the API is available to all users; please contact sales if you are interested in using it long-term.