CTI is a very generic tool. To correctly define the general usage of CTI is a daunting task. The following chapter presents the most frequent user-based procedures without having to create new internal plugins.
The current chapter presents basic usage in the CTI command-line and CTS graphical interface. Generally, it is possible to perform the same tasks with either solution and, since users have different habits or preferences, the chapter reflects the two versions.
The first section of the chapter provides information about user account creation. Though for certain operations, a user account is not necessary, it is needed for the web services. It is considered a good practice to create the user account as a first step.
Repositories are the base of any file or data management system. A repository is somewhere to store, retrieve, and update data in its general terms. For code versionning systems, the data is source code. In CTI's case, the data is more general, it can be code, experimental results, etc. Section 2 presents the different available repositories and how to manipulate the data they contain and the repositories themselves.
File Management is the second logical step for using CTI. The user has finished a run and wants to store in an orderly manner the file into CTI. The section presents how to add a file, view a file, download, and update a file. If the file is a Comma Separated Value (CSV) file, the section presents also how CTI performs a simple viewer for the contained data.
Codelet Management is one of CTI main features. The user wants to store applications and splits them into codelets. The section presents the codelet manager's architecture, how to add an application, run Codelet Finder and automatically create the codelets.
This section shows how to integrate both directly into a single plugin. Such a technique allows a user to integrate directly a query search in a plugin, which sometimes provides a more powerful way to handle CTI entries.