2.90:CMIS+ (Concept) - Revision history

Dgreenwood at 15:55, 5 August 2025

2025-08-05T15:55:03Z

← Older revision		Revision as of 10:55, 5 August 2025
Line 1:		Line 1:
			__NOINDEX__
	{{AutoVersion}}		{{AutoVersion}}

Randallkinard at 19:08, 23 April 2024

2024-04-23T19:08:13Z

← Older revision		Revision as of 14:08, 23 April 2024
Line 1:		Line 1:
	{{AutoVersion}}		{{AutoVersion}}
	<blockquote ~~style="font-size~~:~~14pt">~~
	CMIS+ provides standardized access to document content and metadata across a variety of external storage platforms. All content platforms are exposed to Grooper under a single framework, called CMIS+, as if they were traditional CMIS endpoints by using ''[[CMIS Binding]]s''.		<blockquote>{{#lst:Glossary\|CMIS+}}</blockquote>
	</blockquote>

	This provides Grooper the necessary infrastructure to import, access, and publish documents and their metadata to both CMIS and non-CMIS storage platforms, including on-premise and cloud based platforms.		This provides Grooper the necessary infrastructure to import, access, and publish documents and their metadata to both CMIS and non-CMIS storage platforms, including on-premise and cloud based platforms.

Randallkinard: Randallkinard moved page 2.90:CMIS+ to 2.90:CMIS+ (Concept) without leaving a redirect: new naming convention

2024-04-16T14:00:07Z

Randallkinard moved page 2.90:CMIS+ to 2.90:CMIS+ (Concept) without leaving a redirect: new naming convention

← Older revision	Revision as of 09:00, 16 April 2024
(No difference)

Dgreenwood at 17:17, 22 December 2023

2023-12-22T17:17:57Z

← Older revision		Revision as of 12:17, 22 December 2023
Line 1:		Line 1:
	~~<onlyinclude>~~		{{AutoVersion}}
	<blockquote style="font-size:14pt">		<blockquote style="font-size:14pt">
	CMIS+ provides standardized access to document content and metadata across a variety of external storage platforms. All content platforms are exposed to Grooper under a single framework, called CMIS+, as if they were traditional CMIS endpoints by using ''[[CMIS Binding]]s''.		CMIS+ provides standardized access to document content and metadata across a variety of external storage platforms. All content platforms are exposed to Grooper under a single framework, called CMIS+, as if they were traditional CMIS endpoints by using ''[[CMIS Binding]]s''.
Line 46:		Line 46:
	* [[IMAP (CMIS Binding)\|IMAP]] mail servers		* [[IMAP (CMIS Binding)\|IMAP]] mail servers
	* The Microsoft Windows [[NTFS (CMIS Binding)\|NTFS]] file system.		* The Microsoft Windows [[NTFS (CMIS Binding)\|NTFS]] file system.

	~~[[Category:Articles]]~~
	~~[[Category:Version 2.90]]~~

Dgreenwood: Dgreenwood moved page CMIS+ - 2.90 to 2.90:CMIS+ without leaving a redirect

2023-12-22T17:08:12Z

Dgreenwood moved page CMIS+ - 2.90 to 2.90:CMIS+ without leaving a redirect

← Older revision	Revision as of 12:08, 22 December 2023
(No difference)

Dgreenwood at 16:21, 9 December 2022

2022-12-09T16:21:09Z

← Older revision		Revision as of 11:21, 9 December 2022
Line 46:		Line 46:
	* [[IMAP (CMIS Binding)\|IMAP]] mail servers		* [[IMAP (CMIS Binding)\|IMAP]] mail servers
	* The Microsoft Windows [[NTFS (CMIS Binding)\|NTFS]] file system.		* The Microsoft Windows [[NTFS (CMIS Binding)\|NTFS]] file system.

			[[Category:Articles]]
			[[Category:Version 2.90]]

Dgreenwood: Dgreenwood moved page CMIS+ to CMIS+ - 2.90

2021-09-24T15:44:35Z

Dgreenwood moved page CMIS+ to CMIS+ - 2.90

← Older revision	Revision as of 10:44, 24 September 2021
(No difference)

Dgreenwood at 15:44, 24 September 2021

2021-09-24T15:44:06Z

← Older revision		Revision as of 10:44, 24 September 2021
Line 1:		Line 1:
	<onlyinclude>		<onlyinclude>
	<blockquote style="font-size:14pt">		<blockquote style="font-size:14pt">
	CMIS+ provides standardized access to document content and metadata across a variety of external storage platforms All content platforms are exposed to Grooper under a single framework, called CMIS+, as if they were traditional CMIS endpoints by using ''[[CMIS Binding]]s''.		CMIS+ provides standardized access to document content and metadata across a variety of external storage platforms. All content platforms are exposed to Grooper under a single framework, called CMIS+, as if they were traditional CMIS endpoints by using ''[[CMIS Binding]]s''.
	</blockquote>		</blockquote>

Dgreenwood: /* CMIS Bindings */

2020-11-20T22:12:30Z

CMIS Bindings

← Older revision		Revision as of 17:12, 20 November 2020
Line 27:		Line 27:
	=== CMIS Bindings ===		=== CMIS Bindings ===

	A ''CMIS Binding'' provides connectivity to external storage platforms ~~for content~~ import and export. Grooper's CMIS+ architecture expands connectivity from traditional CMIS servers to a variety of on-premise and cloud-based storage platforms by exposing connections to these platforms as ''CMIS Bindings''. Each individual ''CMIS Binding'' contains the settings and logic required to exchange documents between Grooper and each distinct platform. For example, the ''AppXtender Binding'' contains all the information Grooper uses to connect to the ApplicationXtender content management system.		A ''CMIS Binding'' provides connectivity logic for external storage platforms, allowing '''CMIS Connection''' objects to import and export content. Grooper's CMIS+ architecture expands connectivity from traditional CMIS servers to a variety of on-premise and cloud-based storage platforms by exposing connections to these platforms as ''CMIS Bindings''. Each individual ''CMIS Binding'' contains the settings and logic required to exchange documents between Grooper and each distinct platform. For example, the ''AppXtender Binding'' contains all the information Grooper uses to connect to the ApplicationXtender content management system.

	''CMIS Bindings'' are used when creating a '''CMIS Connection''' object. The first step to creating a '''CMIS Connection''' is to configure the '''''Connection Type''''' property. Which binding you use (and therefore which platform you connect to) is set here. First, the user selects which ''CMIS Binding'' they want to use, selecting which storage platform they want to connect to. The second step is to enter the connection settings for that binding, such as login information for many bindings.		''CMIS Bindings'' are used when creating a '''CMIS Connection''' object. The first step to creating a '''CMIS Connection''' is to configure the '''''Connection Type''''' property. Which binding you use (and therefore which platform you connect to) is set here. First, the user selects which ''CMIS Binding'' they want to use, selecting which storage platform they want to connect to. The second step is to enter the connection settings for that binding, such as login information for many bindings.

Dgreenwood at 22:06, 20 November 2020

2020-11-20T22:06:18Z

← Older revision		Revision as of 17:06, 20 November 2020
Line 1:		Line 1:
			<onlyinclude>
	<blockquote style="font-size:14pt">		<blockquote style="font-size:14pt">
	CMIS+ provides standardized access to document content and metadata across a variety of external storage platforms All content platforms are exposed to Grooper under a single framework, called CMIS+, as if they were traditional CMIS endpoints by using ''[[CMIS Binding]]s''.		CMIS+ provides standardized access to document content and metadata across a variety of external storage platforms All content platforms are exposed to Grooper under a single framework, called CMIS+, as if they were traditional CMIS endpoints by using ''[[CMIS Binding]]s''.
Line 4:		Line 5:

	This provides Grooper the necessary infrastructure to import, access, and publish documents and their metadata to both CMIS and non-CMIS storage platforms, including on-premise and cloud based platforms.		This provides Grooper the necessary infrastructure to import, access, and publish documents and their metadata to both CMIS and non-CMIS storage platforms, including on-premise and cloud based platforms.
			</onlyinclude>

	== About CMIS ==		== About CMIS ==