CMIS+ (Concept) - Revision history

Dgreenwood at 19:37, 22 May 2025

2025-05-22T19:37:47Z

← Older revision		Revision as of 14:37, 22 May 2025
Line 25:		Line 25:

	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~~'''''~~ for any storage platform you can connect to with a '''CMIS Connection'''.		* You now use CMIS Import providers and CMIS Export for any storage platform you can connect to with a '''CMIS Connection'''.
	* This also speeds up development for adding new connection types for import/export operations.		* This also speeds up development for adding new connection types for import/export operations.

Dgreenwood: /* Current CMIS Bindings (AKA "connection types") */

2025-05-20T14:46:56Z

Current CMIS Bindings (AKA "connection types")

← Older revision		Revision as of 09:46, 20 May 2025
Line 83:		Line 83:
	* Or just "connection", as in an "Exchange connection".		* Or just "connection", as in an "Exchange connection".

	==== Current CMIS Bindings (~~AKA~~ "connection types") ====		==== Current CMIS Bindings (aka "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:

Dgreenwood: /* CMIS Bindings (AKA "connection types") */

2025-05-20T14:46:46Z

CMIS Bindings (AKA "connection types")

← Older revision		Revision as of 09:46, 20 May 2025
Line 61:		Line 61:
	#:** Upon importing the CMIS Repository, Grooper has full file access to that location in the storage platform.		#:** Upon importing the CMIS 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 based on what platform you're connecting to. Connection settings include folder paths, URL addresses or usernames or passwords.		How you configure a '''CMIS Connection''' only differs based on what platform you're connecting to. Connection settings include folder paths, URL addresses or usernames or passwords.

Dgreenwood: /* Anatomy of a CMIS Connection */

2025-05-13T19:34:42Z

Anatomy of a CMIS Connection

← Older revision		Revision as of 14:34, 13 May 2025
Line 32:		Line 32:
	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
	# The platform it's connecting to. This is defined by the "'''CMIS Binding'''" selected for the CMIS Connection's "Connection Settings".		# The platform it's connecting to. This is defined by the "'''CMIS Binding'''" (aka "connection type") selected for the CMIS Connection's "Connection Settings".
	# Its child '''CMIS Repositories'''		# Its child '''CMIS Repositories'''
	#*<li class ="fyi-bullet"> "Repository" is just a general term for a location where data lives. Different systems refer to "repositories" in different ways.		#*<li class ="fyi-bullet"> "Repository" is just a general term for a location where data lives. Different systems refer to "repositories" in different ways.
Line 54:		Line 54:
	# Create a CMIS Connection		# Create a CMIS Connection
	# Configure the "Connection Settings".		# Configure the "Connection Settings".
	#* Choose what platform you want to connect to (the "CMIS Binding").		#* Choose what platform you want to connect to (the CMIS Binding).
	#* Enter the connection settings required to connect to the platform (This will differ from platform to platform)		#* Enter the connection settings required to connect to the platform (This will differ from platform to platform)
	# Add child CMIS Repositories by importing the storage locations.		# Add child CMIS Repositories by importing the storage locations.

Dgreenwood: /* Anatomy of a CMIS Connection */

2025-05-13T19:32:03Z

Anatomy of a CMIS Connection

Dgreenwood at 13:42, 13 May 2025

2025-05-13T13:42:19Z

← Older revision		Revision as of 08:42, 13 May 2025
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 Settings" determine 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.		: Example: You want 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.		: Example: You want to import files from a Windows folder named "Grooper Imports". You would first create a '''CMIS Repository''' that represents that folder in Grooper. This imports a reference to the storage location Grooper can use. Then, you would point to that '''CMIS Repository''' when setting up [[CMIS Import]] to import the files 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.


	<section begin="cmisplus" />		<section begin="cmisplus" />
	== About CMIS+ ==		== About CMIS+ ==
Line 63:		Line 61:
	#:** Upon importing the repository, Grooper has full file access to that location in the storage platform.</li>		#:** Upon importing the repository, Grooper has full file access to that location in the storage platform.</li>

	=== CMIS Bindings (AKA ~~Connection Types~~) ===		=== CMIS Bindings (AKA "connection types") ===

	How you configure a '''CMIS Connection''' only differs based on what platform you're connecting to. Connection settings include folder paths, URL addresses or usernames or passwords.		How you configure a '''CMIS Connection''' only differs based on what platform you're connecting to. Connection settings include folder paths, URL addresses or usernames or passwords.
Line 85:		Line 83:
	* Or just "connection", as in an "Exchange connection".		* Or just "connection", as in an "Exchange connection".

	==== Current CMIS Bindings (~~aka Connection Types~~) ====		==== Current CMIS Bindings (AKA "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:

Dgreenwood: /* CMIS Bindings (AKA Connection Types) */

2025-05-13T13:25:38Z

CMIS Bindings (AKA Connection Types)

← Older revision		Revision as of 08:25, 13 May 2025
Line 82:		Line 82:

	The first step in configuring a '''CMIS Connection''' is choosing what platform you want to connect to. You do this by selecting a "CMIS Binding".		The first step in configuring a '''CMIS Connection''' is choosing what platform you want to connect to. You do this by selecting a "CMIS Binding".
	* You will ~~more~~ commonly hear "CMIS Binding" referred to as a "''CMIS ~~Connection Type''~~".		* You will commonly hear "CMIS Binding" referred to as a "CMIS connection type" or "connection type".
	* Or just ~~"connection type" or~~ "connection", as in an "Exchange connection".		* Or just "connection", as in an "Exchange connection".

	==== Current CMIS Bindings (aka Connection Types) ====		==== Current CMIS Bindings (aka Connection Types) ====

Dgreenwood: /* Current CMIS Connection Types */

2025-05-13T13:24:19Z

Current CMIS Connection Types

← Older revision		Revision as of 08:24, 13 May 2025
Line 85:		Line 85:
	* Or just "connection type" or "connection", as in an "Exchange connection".		* Or just "connection type" or "connection", as in an "Exchange connection".

	==== Current CMIS Connection Types ====		==== Current CMIS Bindings (aka 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:

	'''Most Commonly Used'''		'''Most Commonly Used'''

Dgreenwood: /* See Also */

2025-05-12T20:17:03Z

Dgreenwood: /* Basic creation steps */

2025-05-12T20:15:59Z

Basic creation steps

← Older revision		Revision as of 15:15, 12 May 2025
Line 53:		Line 53:

	==== Basic creation steps ====		==== Basic creation steps ====
	~~To reiterate, there~~ are three basic steps involved to connect Grooper to external storage platforms:		There are three basic steps involved to connect Grooper to external storage platforms:
	# Create a '''CMIS Connection'''		# Create a '''CMIS Connection'''
	# Configure the "Connection Settings".		# Configure the "Connection Settings".

← Older revision		Revision as of 15:17, 12 May 2025
Line 114:		Line 114:
	* '''[[CMIS Connection]]'''		* '''[[CMIS Connection]]'''
	* '''[[CMIS Import]]'''		* '''[[CMIS Import]]'''
			* '''[[CMIS Export]]'''
	* '''[[Export (Activity)]]'''		* '''[[Export (Activity)]]'''

← Older revision		Revision as of 14:32, 13 May 2025
Line 30:		Line 30:
	=== 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
	# The ~~type of connection~~ it's ~~using (~~defined by a "CMIS Binding")		# The platform it's connecting to. This is defined by the "'''CMIS Binding'''" selected for the CMIS Connection's "Connection Settings".
	# Its child '''CMIS Repositories'''		# Its child '''CMIS Repositories'''
	#*<li class ="fyi-bullet"> "Repository" is just a general term for a location where data lives. Different systems refer to "repositories" in different ways.		#*<li class ="fyi-bullet"> "Repository" is just a general term for a location where data lives. Different systems refer to "repositories" in different ways.
Line 39:		Line 39:


	For newer users, the difference between a ~~'''~~CMIS Connection~~'''~~ and a ~~'''~~CMIS Repository~~'''~~ can be confusing. The key distinction is as follows:		For newer users, the difference between a CMIS Connection and a CMIS Repository can be confusing. The key distinction is as follows:
	* '''CMIS Connections''' connect to storage platforms.		* '''CMIS Connections''' connect to storage platforms.
	** It's the phone number you dial.		** It's the phone number you dial.
Line 45:		Line 45:
	* '''CMIS Repositories''' represent a location ''within'' the connected platform.		* '''CMIS Repositories''' represent a location ''within'' the connected platform.
	** It's the person on the other end of that phone number you want to talk to.		** It's the person on the other end of that phone number you want to talk to.
	** ~~'''~~CMIS Repositories~~'''~~ represent storage locations (typically folders) in the storage platform. They are added as children to a parent ~~'''~~CMIS Connection~~'''~~.		** CMIS Repositories represent storage locations (typically folders) in the storage platform. They are added as children to a parent CMIS Connection.
	** The ~~'''~~CMIS Repository~~'''~~ nodes are what Grooper actually uses when configuring import/export operations.		** The CMIS Repository nodes are what Grooper actually uses when configuring import/export operations.
	*** You don't talk to a phone number. You talk to a person.		*** You don't talk to a phone number. You talk to a person.
	*** You don't reference the parent ~~'''~~CMIS Connection~~'''~~ when configuring [[CMIS Import]] or [[CMIS Export]]. Instead you reference a ~~'''~~CMIS Repository~~'''~~.		*** You don't reference the parent CMIS Connection when configuring [[CMIS Import]] or [[CMIS Export]]. Instead you reference a CMIS Repository.

	==== Basic creation steps ====		==== Basic creation steps ====
	There are three basic steps involved to connect Grooper to external storage platforms:		There are three basic steps involved to connect Grooper to external storage platforms:
	# Create a ~~'''~~CMIS Connection~~'''~~		# Create a CMIS Connection
	# Configure the "Connection Settings".		# Configure the "Connection Settings".
	#* Choose what platform you want to connect to (the "~~connection type~~").		#* Choose what platform you want to connect to (the "CMIS Binding").
	#* Enter the connection settings required to connect to the platform (This will differ ~~based on the connection type you're using~~)		#* Enter the connection settings required to connect to the platform (This will differ from platform to platform)
	# Add child ~~'''~~CMIS Repositories~~'''~~ by importing the storage locations.		# Add child CMIS Repositories by importing the storage locations.
	#:*<li class ="fyi-bullet">Importing a ~~'''~~CMIS Repository~~'''~~ is not the same as importing documents to a new ~~'''~~Batch~~'''~~.		#:*<li class ="fyi-bullet">Importing a CMIS Repository is not the same as importing documents to a new Batch.
	#:**"Importing" here is more like importing a reference (or bringing the repository into a framework Grooper can use).		#:**"Importing" here is more like importing a reference (or 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.~~</li>~~		#:** Upon importing the CMIS Repository, Grooper has full file access to that location in the storage platform.

	=== CMIS Bindings (AKA "connection types") ===		=== CMIS Bindings (AKA "connection types") ===