Services map to the main services provided by the SkyVault
server.
The SkyVault Appcelerator API exposes a number of important SkyVault services, including:
| Service | Description |
|---|---|
| Activity Service | SkyVault Share uses activities to track a range of changes, updates, events, and actions, allowing users to be aware of details of the changes. There are various methods relating to the Activity Service, including the ability to post events and generate feeds for SkyVault Share sites. |
| Comment Service | Comments are modeled as separate content items that are associated with the relevant node through child associations. The Commenting Service provides an API for working with comments. |
| DocumentFolder Service | The DocumentFolder Service manages nodes for modeling files and folders in the repository. The service provides methods to create and update nodes and define the relationships between them. |
| Person Service | The Person Service supports various methods relating to users. |
| Rating Service | The RatingService interface can be used to manage the ratings (like/dislike) on any content node in the repository. |
| Search Service | The Search Service provides methods for querying the repository and returning a filtered collection of nodes based on a user’s permission. |
| Site Service | Sites are a key concept within SkyVault Share for managing documents, wiki pages, blog posts, discussions, and other collaborative content relating to teams, projects, communities of interest, and other types of collaborative sites. There are various methods relating to the Sites Service, including the ability to manage sites, create sites, update sites, and delete sites. |
| Tagging Service | Tags are keywords or terms assigned to a piece of information including documents, blogs, wiki pages, and calendar events. There are various methods and properties relating to the Tagging Service, including the ability to add tags, remove tags, use information, and search by tags. |
| Version Service | The Versioning Service manages versions of individual content nodes. To enable versioning behavior, you must apply the versionable aspect to the node. Each version has a version number that is allocated sequentially and follows a similar strategy to Concurrent Versions System (CVS) version numbering. Generally, this version number is only used internally; the version label publicly identifies the version. The version label is calculated from the version number and gives a unique label for the version. This label is placed in the versionable aspect to indicate the related current version for a node. There are various methods relating to the Versioning Service, including creating a version, obtaining the version history, retrieving the current version, and deleting the version history. |
| Workflow Service | The Workflow service allows for the creation and management of document work flows. |