| ... | ... | @@ -320,19 +320,3 @@ Please beware that, for simplicity, here I have omitted processes that are relev |
|
|
|
* Filling up the table of targets to show.
|
|
|
|
|
|
|
|
### New data mapping |
|
|
|
|
|
|
|
## Data access scripts
|
|
|
|
|
|
|
|
The CC resource provides a very simple API to query the data within the resource. In brief, the API facilitates the following:
|
|
|
|
|
|
|
|
* Given one or more `inchikeys`:
|
|
|
|
* It lists the corresponding `datasets`.
|
|
|
|
* It returns the InChI structure(s).
|
|
|
|
* If a `dataset` is specified, it returns the signatures (`sign*`) or vectorial data (`neig*`, `clus*`, etc.) of choice.
|
|
|
|
* Given one or more `datasets`:
|
|
|
|
* It lists the corresponding `inchikeys`.
|
|
|
|
* It returns the signatures (`sign*`) or vectorial data (`neig*`, `clus*`, etc.) of choice.
|
|
|
|
* It deletes the dataset from the resource (might be convenient when we are testing datasets).
|
|
|
|
* Given one or more `levels` or `coordinates`:
|
|
|
|
* It lists the corresponding `datasets`.
|
|
|
|
* It indicates the exemplar `dataset(s)`. |
