2.90:CMIS+ (Concept): Difference between revisions
Configadmin (talk | contribs) Created page with "All content platforms are exposed to Grooper under a single framework as if they were CMIS endpoints. CMIS+ provides standardized access to document content and metadata acro..." |
Configadmin (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
All content platforms are exposed to Grooper under a single framework as if they were CMIS endpoints. CMIS+ provides standardized access to document content and metadata across a variety of external storage platforms including: | All content platforms are exposed to Grooper under a single framework, called CMIS+, as if they were CMIS endpoints. CMIS+ provides standardized access to document content and metadata across a variety of external storage platforms including: | ||
* CMIS connections | * CMIS connections | ||
Revision as of 17:34, 26 December 2019
All content platforms are exposed to Grooper under a single framework, called CMIS+, as if they were CMIS endpoints. CMIS+ provides standardized access to document content and metadata across a variety of external storage platforms including:
- CMIS connections
- FTP directories
- Microsoft SharePoint sites
- Email servers
- NTFS file system.
The settings and programming used to connect Grooper to a storage platform is contained in a CMIS Binding. For example, the AppXtender Binding contains all the information Grooper uses to connect to the ApplicationXtender content management system.
Using this architecture, Grooper is able to create a more standardized import and export workflow. The CMIS Import and CMIS Export providers are configured the same, regardless of the storage platform used. They connect to a CMIS Repository imported from a previously created CMIS Connection and use that as Grooper's import or export path.
Only how you create a CMIS Connection differs from CMIS Binding to CMIS Binding.