COMAND Integrations

Integrations will be introduced with COMAND 4.0.

Content types can be mapped to other storage systems, such as file systems or databases. For example, content types can be mapped to MIME types to simplify the import and export of content with a traditional file system.

A content type or content type interface can define MIME type integrations. An interface or content type MIME type integration will apply to all content types that implement or extend it, unless it is overridden.

MIME Type Integration

The MimeType content type maps a file mime type to a content type with a FileImport method.

COMAND Repository Integration

Another COMAND Repository can be queried to monitor, discover and import/sync content, or exported for the reverse process.

Database Integration

SQL, ODBC and other database drivers supported by PDO can be utilized to connect to an external database to be queried to monitor, discover and import/sync data, or export to for the reverse process.

SV File Integration

CSV, TAB and other character separated value text files can be imported and exported. The column and row separators can be customized, as well as the value encoding/escaping options. For example, a standard CSV uses optionally double-quote encoded values, commas for the column separator, and newline characters for the row separator.

ML File Integration

XML, HTML and other node/tree structured text files can be imported and exported.

Email Integration

IMAP and POP3 email accounts can be polled for new email. When new email is detected, the email, including all headers and attachments are available for processing. They can be pulled directly into the COMAND repository as an Email content record, or mapped to custom content types or processes.