2023:CMIS+ (Concept) - Revision history

Randallkinard: // via Wikitext Extension for VSCode

2024-11-18T15:34:11Z

// via Wikitext Extension for VSCode

Randallkinard at 19:09, 23 April 2024

2024-04-23T19:09:01Z

← Older revision		Revision as of 14:09, 23 April 2024
Line 1:		Line 1:
	{{AutoVersion}}		{{AutoVersion}}
	~~<section begin="glossary" />~~
	<blockquote>		<blockquote>{{#lst:Glossary\|CMIS+}}</blockquote>
	~~Grooper's~~ CMIS+ ~~architecture provides standardized access to document content and metadata across a variety of external storage platforms.~~
	</blockquote>
	~~<section end="glossary" />~~
	All content platforms are exposed to Grooper under a single framework (called CMIS+) as if they were traditional CMIS endpoints by using a '''CMIS Connection''' in Grooper.		All content platforms are exposed to Grooper under a single framework (called CMIS+) as if they were traditional CMIS endpoints by using a '''CMIS Connection''' in Grooper.

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

2024-04-16T14:00:48Z

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

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

Dgreenwood at 18:12, 9 January 2024

2024-01-09T18:12:53Z

← Older revision		Revision as of 13:12, 9 January 2024
Line 1:		Line 1:
	{{AutoVersion}}		{{AutoVersion}}
	<section begin="~~cmis_plus_glossary~~" />		<section begin="glossary" />
	<blockquote>		<blockquote>
	Grooper's CMIS+ architecture provides standardized access to document content and metadata across a variety of external storage platforms.		Grooper's CMIS+ architecture provides standardized access to document content and metadata across a variety of external storage platforms.
	</blockquote>		</blockquote>
	<section end="~~cmis_plus_glossary~~" />		<section end="glossary" />
	All content platforms are exposed to Grooper under a single framework (called CMIS+) as if they were traditional CMIS endpoints by using a '''CMIS Connection''' in Grooper.		All content platforms are exposed to Grooper under a single framework (called CMIS+) as if they were traditional CMIS endpoints by using a '''CMIS Connection''' in Grooper.

Dgreenwood at 20:05, 4 January 2024

2024-01-04T20:05:39Z

← Older revision		Revision as of 15:05, 4 January 2024
Line 1:		Line 1:
	{{AutoVersion}}		{{AutoVersion}}
			<section begin="cmis_plus_glossary" />
	<blockquote>		<blockquote>
	Grooper's CMIS+ architecture provides standardized access to document content and metadata across a variety of external storage platforms.		Grooper's CMIS+ architecture provides standardized access to document content and metadata across a variety of external storage platforms.
	</blockquote>		</blockquote>
			<section end="cmis_plus_glossary" />
	All content platforms are exposed to Grooper under a single framework (called CMIS+) as if they were traditional CMIS endpoints by using a '''CMIS Connection''' in Grooper.		All content platforms are exposed to Grooper under a single framework (called CMIS+) as if they were traditional CMIS endpoints by using a '''CMIS Connection''' in Grooper.

Dgreenwood: Created page with "{{AutoVersion}}
Grooper's CMIS+ architecture 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 a '''CMIS Connection''' in Grooper. The '''CMIS Connection's''' '''''Connection Type''''' determines which storage platform you're connecting to. * F..."

2024-01-03T21:59:36Z

Created page with "{{AutoVersion}} <blockquote> Grooper's CMIS+ architecture provides standardized access to document content and metadata across a variety of external storage platforms. </blockquote> All content platforms are exposed to Grooper under a single framework (called CMIS+) as if they were traditional CMIS endpoints by using a '''CMIS Connection''' in Grooper. The '''CMIS Connection's''' '''''Connection Type''''' determines which storage platform you're connecting to. * F..."

New page

{{AutoVersion}}

<blockquote>
Grooper's CMIS+ architecture provides standardized access to document content and metadata across a variety of external storage platforms.
</blockquote>

All content platforms are exposed to Grooper under a single framework (called CMIS+) as if they were traditional CMIS endpoints by using a '''CMIS Connection''' in Grooper.

The '''CMIS Connection's''' '''''Connection Type''''' determines which storage platform you're connecting to.
* For example, if you wanted to connect to a Windows file system, you would create a '''CMIS Connection''' configured with an '''''NTFS''''' connection.

Once connected to a platform, Grooper can import from and export to that platform by importing a '''CMIS Repository''' that represents a location (usually a folder) in the storage platform.
* For example, if you wanted to import documents from a Windows folder named "Grooper Imports", you would first import that folder location as a '''CMIS Repository''' in Grooper. Then, you would point to that '''CMIS Repository''' when importing the documents into Grooper.

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.

<section begin="cmisplus" />
== About CMIS+ ==
"CMIS" stands for "Content Management Interoperability Services". It is an open standard that allows different content management systems to inter-operate over the Internet. Grooper expanded on this idea in version 2.72 to create our "CMIS+" architecture. CMIS+ unifies all content platforms under a single framework as if they were traditional CMIS endpoints.

Now, Grooper connects to any external storage platform by creating and configuring a '''CMIS Connection''' (not just CMIS 1.0 or CMIS 1.1 servers).
* Once a '''CMIS Connection''' is created, Grooper can "interoperate" with these platforms.
* "Interoperability " means Grooper has the same access to control the system as a human being does.
* Grooper has a "one-to-one" connection to the platform, allowing full and total control.

Using this architecture, Grooper is able to create a simpler and more efficient import and export workflow, using a variety of storage platforms.
* You now use '''''CMIS Import''''' providers and '''''CMIS Export''''', regardless of the storage platform.

=== Anatomy of a CMIS Connection ===

When connecting Grooper to external storage platforms, you'll start by creating a '''CMIS Connection'''. There are three important parts to understanding a '''CMIS Connection'''
* The '''CMIS Connection''' itself.
* It's '''''Connection Type''''' (and the "'''''CMIS Binding'''''" you select).
* It's child '''CMIS Repositories'''

{|class="fyi-box"
|
'''FYI'''
|
A "repository", in computer science, is a general term for a location where data lives. Different systems refer to "repositories" in different ways.
* An email inbox could be a repository. A folder in Windows could be a repository. A folder in a Box account could be a repository. A cabinet in ApplicationXtender could be a repository.
* We standardize the various terms used by various storage platforms to simply "repository".
* Put simply, it's a place to put stuff.
|}

For newer users, the difference between a '''CMIS Connection''' and a '''CMIS Repository''' can be confusing (and it doesn't help that some people use the terms interchangeably!). The key distinction is as follows:
* The '''CMIS Connection''' is the object in Grooper that Grooper uses to establish a connection to some external system.
** The '''''Connection Type''''' determines which ''specific'' platform you're connecting to, and any settings required to connect to it.
* '''CMIS Repositories''' represent a location ''within'' the connected platform.
** These are created ''after'' creating the '''CMIS Connection'''.
** Typically, these represent a folder location in the storage platform.

For example, imagine you want to use Grooper to connect to a Windows file system folder on some networked server.
* First, they would create a new '''CMIS Connection'''
* Then they would choose ''NTFS'' for its '''''Connection Type'''''
* Then they would import the folder location as a '''CMIS Repository'''
** It is then this '''CMIS Repository''' Grooper will point to when importing from or exporting to this folder location.
** The '''CMIS Connection''' is just the thing that allows Grooper to connect to Windows in this case. It is the '''CMIS Repository''' that acts as the Windows file system folder in Grooper.

To reiterate, there are three basic steps involved to connect Grooper to external storage platforms:
# Create a '''CMIS Connection'''
# Configure its '''''Connection Type''''' to select which platform you want to connect to (and enter any settings to connect to that platform).
# Import storage locations as one or more '''CMIS Repositories''', which are created as children of the '''CMIS Connection'''.

{|class="fyi-box"
|
'''FYI'''
|
Importing a '''CMIS Repository''' is not the same as importing documents to a new '''Batch'''.
* "Importing" here is more like bringing the repository into a framework Grooper can use.
* Upon importing the repository, Grooper has full file access to that location in the storage platform.
|}

=== CMIS Bindings (AKA Connection Types) ===

How you configure a '''CMIS Connection''' only differs from '''''CMIS Binding''''' to '''''CMIS Binding''''', as each binding has a different way of connecting to it.
* You don't connect to an Outlook inbox the same way you connect to a Windows file folder, for example.
* Thus, the property configuration for the '''''Exchange''''' binding is different from the '''''NTFS''''' binding.

A '''''CMIS Binding''''' provides connectivity to external storage platforms for content import and export. Each individual '''''CMIS Binding''''' contains the settings and logic required to exchange documents between Grooper and each distinct platform.
* The '''''Exchange Binding''''' contains all the information Grooper uses to connect to Microsoft Exchange email servers (i.e. Outlook inboxes).
* The '''''AppXtender Binding''''' contains all the information Grooper uses to connect to the ApplicationXtender content management system.
* The '''''NTFS Binding''''' contains all the information Grooper uses to connect to a Windows file system.
* And so on.

When creating a '''CMIS Connection''' the first step to configure the '''''Connection Type''''' property.
* When you select a '''''Connection Type''''' you're selecting which platform you want to connect to (using a '''''CMIS Binding''''').
** First, you select which platform you want to connect to (which '''''CMIS Binding''''' you want to use)
** Then, you enter connection settings unique to the platform (any values the ''''' CMIS Binding''''' needs to connect to the platform, like login information for many platforms)

==== Current CMIS Connection Types ====

Grooper can connect to the following storage platforms using below using '''''CMIS Bindings''''':

'''Most Commonly Used'''
* The Microsoft Windows [[NTFS (CMIS Binding)|NTFS]] file system.
* The following Microsoft content platforms
** The [[Exchange (CMIS Binding)|Microsoft Exchange]] mail server platform.
** The [[OneDrive (CMIS Binding)|Microsoft OneDrive]] cloud storage platform.
** [[SharePoint (CMIS Binding)|Microsoft SharePoint]] sites.

'''Somewhat Commonly Used'''
* The [[AppXtender (CMIS Binding)|ApplicationXtender]] document management platform.
* The [[Box (CMIS Binding)|Box]] cloud storage platform.

'''Less Commonly Used'''
* [[FTP (CMIS Binding)|FTP]] (File Transfer Protocol) and [[SFTP (CMIS Binding)|SFTP]] (SSH File Transfer Protocol) servers.
* [[IMAP (CMIS Binding)|IMAP]] mail servers

'''Least Used'''
* Content management systems using CMIS 1.0 or CMIS 1.1 servers.
* The FileBound document management platform.
* The IBM FileNet platform.
<section end="cmisplus" />

== See Also ==

* '''[[CMIS Connection]]'''
* '''[[CMIS Import]]'''
* '''[[Export (Activity)]]'''

← Older revision		Revision as of 10:34, 18 November 2024
Line 5:		Line 5:
	All content platforms are exposed to Grooper under a single framework (called CMIS+) as if they were traditional CMIS endpoints by using a '''CMIS Connection''' in Grooper.		All content platforms are exposed to Grooper under a single framework (called CMIS+) as if they were traditional CMIS endpoints by using a '''CMIS Connection''' in Grooper.

	The '''CMIS Connection's''' '''''Connection Type''''' determines which storage platform you're connecting to.		The '''CMIS Connection's''' '''''Connection Type''''' determines which storage platform you're connecting to.
	* For example, if you wanted to connect to a Windows file system, you would create a '''CMIS Connection''' configured with an '''''NTFS''''' connection.		* For example, if you wanted to connect to a Windows file system, you would create a '''CMIS Connection''' configured with an '''''NTFS''''' connection.

	Once connected to a platform, Grooper can import from and export to that platform by importing a '''CMIS Repository''' that represents a location (usually a folder) in the storage platform.		Once connected to a platform, Grooper can import from and export to that platform by importing a '''CMIS Repository''' that represents a location (usually a folder) in the storage platform.
	* For example, if you wanted to import documents from a Windows folder named "Grooper Imports", you would first import that folder location as a '''CMIS Repository''' in Grooper. Then, you would point to that '''CMIS Repository''' when importing the documents into Grooper.		* For example, if you wanted to import documents from a Windows folder named "Grooper Imports", you would first import that folder location as a '''CMIS Repository''' in Grooper. Then, you would point to that '''CMIS Repository''' when importing the documents into Grooper.

	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.
Line 15:		Line 15:
	<section begin="cmisplus" />		<section begin="cmisplus" />
	== About CMIS+ ==		== About CMIS+ ==
	"CMIS" stands for "Content Management Interoperability Services". It is an open standard that allows different content management systems to inter-operate over the Internet. Grooper expanded on this idea in version 2.72 to create our "CMIS+" architecture. CMIS+ unifies all content platforms under a single framework as if they were traditional CMIS endpoints.		"CMIS" stands for "Content Management Interoperability Services". It is an open standard that allows different content management systems to inter-operate over the Internet. Grooper expanded on this idea in version 2.72 to create our "CMIS+" architecture. CMIS+ unifies all content platforms under a single framework as if they were traditional CMIS endpoints.


	Now, Grooper connects to any external storage platform by creating and configuring a '''CMIS Connection''' (not just CMIS 1.0 or CMIS 1.1 servers).		Now, Grooper connects to any external storage platform by creating and configuring a '''CMIS Connection''' (not just CMIS 1.0 or CMIS 1.1 servers).
	* Once a '''CMIS Connection''' is created, Grooper can "interoperate" with these platforms.		* Once a '''CMIS Connection''' is created, Grooper can "interoperate" with these platforms.
	* "Interoperability " means Grooper has the same access to control the system as a human being does.		* "Interoperability " means Grooper has the same access to control the system as a human being does.
	* Grooper has a "one-to-one" connection to the platform, allowing full and total control.		* Grooper has a "one-to-one" connection to the platform, allowing full and total control.


	Using this architecture, Grooper is able to create a simpler and more efficient import and export workflow, using a variety of storage platforms.		Using this architecture, Grooper is able to create a simpler and more efficient import and export workflow, using a variety of storage platforms.
	* You now use '''''CMIS Import''''' providers and '''''CMIS Export''''', regardless of the storage platform.		* You now use '''''CMIS Import''''' providers and '''''CMIS Export''''', regardless of the storage platform.

	=== Anatomy of a CMIS Connection ===		=== Anatomy of a CMIS Connection ===
			When connecting Grooper to external storage platforms, you'll start by creating a '''CMIS Connection'''. There are three important parts to understanding a '''CMIS Connection'''
	When connecting Grooper to external storage platforms, you'll start by creating a '''CMIS Connection'''. There are three important parts to understanding a '''CMIS Connection'''
	* The '''CMIS Connection''' itself.		* The '''CMIS Connection''' itself.
	* It's '''''Connection Type''''' (and the "'''''CMIS Binding'''''" you select).		* It's '''''Connection Type''''' (and the "'''''CMIS Binding'''''" you select).
Line 38:		Line 37:
	'''FYI'''		'''FYI'''
	\|		\|
	A "repository", in computer science, is a general term for a location where data lives. Different systems refer to "repositories" in different ways.		A "repository", in computer science, is a general term for a location where data lives. Different systems refer to "repositories" in different ways.
	* An email inbox could be a repository. A folder in Windows could be a repository. A folder in a Box account could be a repository. A cabinet in ApplicationXtender could be a repository.		* An email inbox could be a repository. A folder in Windows could be a repository. A folder in a Box account could be a repository. A cabinet in ApplicationXtender could be a repository.
	* We standardize the various terms used by various storage platforms to simply "repository".		* We standardize the various terms used by various storage platforms to simply "repository".
	* Put simply, it's a place to put stuff.		* Put simply, it's a place to put stuff.
	\|}		\|}

Line 56:		Line 55:
	* Then they would import the folder location as a '''CMIS Repository'''		* Then they would import the folder location as a '''CMIS Repository'''
	** It is then this '''CMIS Repository''' Grooper will point to when importing from or exporting to this folder location.		** It is then this '''CMIS Repository''' Grooper will point to when importing from or exporting to this folder location.
	** The '''CMIS Connection''' is just the thing that allows Grooper to connect to Windows in this case. It is the '''CMIS Repository''' that acts as the Windows file system folder in Grooper.		** The '''CMIS Connection''' is just the thing that allows Grooper to connect to Windows in this case. It is the '''CMIS Repository''' that acts as the Windows file system folder in Grooper.


Line 69:		Line 68:
	\|		\|
	Importing a '''CMIS Repository''' is not the same as importing documents to a new '''Batch'''.		Importing a '''CMIS Repository''' is not the same as importing documents to a new '''Batch'''.
	* "Importing" here is more like bringing the repository into a framework Grooper can use.		* "Importing" here is more like bringing the repository into a framework Grooper can use.
	* Upon importing the repository, Grooper has full file access to that location in the storage platform.		* Upon importing the repository, Grooper has full file access to that location in the storage platform.
	\|}		\|}

	=== CMIS Bindings (AKA Connection Types) ===		=== CMIS Bindings (AKA Connection Types) ===
			How you configure a '''CMIS Connection''' only differs from '''''CMIS Binding''''' to '''''CMIS Binding''''', as each binding has a different way of connecting to it.
	How you configure a '''CMIS Connection''' only differs from '''''CMIS Binding''''' to '''''CMIS Binding''''', as each binding has a different way of connecting to it.
	* You don't connect to an Outlook inbox the same way you connect to a Windows file folder, for example.		* You don't connect to an Outlook inbox the same way you connect to a Windows file folder, for example.
	* Thus, the property configuration for the '''''Exchange''''' binding is different from the '''''NTFS''''' binding.		* Thus, the property configuration for the '''''Exchange''''' binding is different from the '''''NTFS''''' binding.


	A '''''CMIS Binding''''' provides connectivity to external storage platforms for content import and export. Each individual '''''CMIS Binding''''' contains the settings and logic required to exchange documents between Grooper and each distinct platform.		A '''''CMIS Binding''''' provides connectivity to external storage platforms for content import and export. Each individual '''''CMIS Binding''''' contains the settings and logic required to exchange documents between Grooper and each distinct platform.
	* The '''''Exchange Binding''''' contains all the information Grooper uses to connect to Microsoft Exchange email servers (i.e. Outlook inboxes).		* The '''''Exchange Binding''''' contains all the information Grooper uses to connect to Microsoft Exchange email servers (i.e. Outlook inboxes).
	* The '''''AppXtender Binding''''' contains all the information Grooper uses to connect to the ApplicationXtender content management system.		* The '''''AppXtender Binding''''' contains all the information Grooper uses to connect to the ApplicationXtender content management system.
Line 92:		Line 90:

	==== Current CMIS Connection Types ====		==== Current CMIS Connection Types ====

	Grooper can connect to the following storage platforms using below using '''''CMIS Bindings''''':		Grooper can connect to the following storage platforms using below using '''''CMIS Bindings''''':

Line 117:		Line 114:

	== See Also ==		== See Also ==

	* '''[[CMIS Connection]]'''		* '''[[CMIS Connection]]'''
	* '''[[CMIS Import]]'''		* '''[[CMIS Import]]'''
	* '''[[Export (Activity)]]'''		* '''[[Export (Activity)]]'''