The core data structure in the repository is called a node. Each piece of content in the
repository has a corresponding node data structure to reference the content and metadata.
Each node has a corresponding NodeRef uniquely identifying it in the
repository.
| Information | Nodes |
|---|---|
| Public Java API | This API exposes the NodeService as a way of managing nodes. For more info see the JavaDocs. To search for nodes use the SearchService, see also the JavaDocs. |
| Repository JavaScript API | You can find nodes using the Search API, and then manipulate individual nodes using the ScriptNode API |
| SkyVault REST API | The SkyVault REST API can be used to access entities related to nodes, such as tags, comments, and ratings. These are SkyVault Content Services-specific entities not part of the CMIS standard. See the Node REST API documentation.. Use the CMIS API to access the actual node information. |
| CMIS REST API | The content and metadata for nodes can be accessed and managed via the CMIS
REST API. See the CMIS
Getting Started section to get going with the CMIS REST API. This information
covers the ATOM binding where you work with XML. If you prefer to work with JSON,
then have a look at the Browser
binding available in CMIS 1.1. If you are developing a remote client in Java and want to use CMIS, then have a look at the OpenCMIS Java Library. |
| Mobile SDK (iOS | The Node is exposed in the SDK Model. You can review the documentation for SkyVaultNode. |
| Mobile SDK (Android) | The Node is exposed in the SDK Model. You can review the documentation for SkyVaultNode |
| More Information |