2023:CMIS Import (Import Provider) - Revision history

Randallkinard at 14:27, 26 August 2024

2024-08-26T14:27:24Z

Randallkinard at 17:03, 3 May 2024

2024-05-03T17:03:44Z

Randallkinard at 15:41, 29 April 2024

2024-04-29T15:41:10Z

← Older revision		Revision as of 10:41, 29 April 2024
Line 1:		Line 1:
	{{AutoVersion}}		{{AutoVersion}}
	~~<section begin="glossary" />~~
	<blockquote>		<blockquote>{{#lst:Glossary\|CMIS Import}}</blockquote>
	~~'''''~~CMIS Import~~''''' is an '''''[[Import Provider]]''''' used to import content over a '''[[CMIS Connection]]''', allowing users to import from various on-premise and cloud based storage platforms.~~
	</blockquote>
	~~<section end="glossary" />~~
	Documents are imported from '''CMIS Connections''' using either the '''''Import Descendants''''' or '''''Import Query Results''''' providers. These can be used in two ways:		Documents are imported from '''CMIS Connections''' using either the '''''Import Descendants''''' or '''''Import Query Results''''' providers. These can be used in two ways:

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

2024-04-16T14:43:57Z

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

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

Dgreenwood at 18:12, 9 January 2024

2024-01-09T18:12:45Z

← Older revision		Revision as of 13:12, 9 January 2024
Line 1:		Line 1:
	{{AutoVersion}}		{{AutoVersion}}
	<section begin="~~cmis_import_glossary~~" />		<section begin="glossary" />
	<blockquote>		<blockquote>
	'''''CMIS Import''''' is an '''''[[Import Provider]]''''' used to import content over a '''[[CMIS Connection]]''', allowing users to import from various on-premise and cloud based storage platforms.		'''''CMIS Import''''' is an '''''[[Import Provider]]''''' used to import content over a '''[[CMIS Connection]]''', allowing users to import from various on-premise and cloud based storage platforms.
	</blockquote>		</blockquote>
	<section end="~~cmis_import_glossary~~" />		<section end="glossary" />
	Documents are imported from '''CMIS Connections''' using either the '''''Import Descendants''''' or '''''Import Query Results''''' providers. These can be used in two ways:		Documents are imported from '''CMIS Connections''' using either the '''''Import Descendants''''' or '''''Import Query Results''''' providers. These can be used in two ways:

Dgreenwood at 20:12, 4 January 2024

2024-01-04T20:12:20Z

← Older revision		Revision as of 15:12, 4 January 2024
Line 1:		Line 1:
	{{AutoVersion}}		{{AutoVersion}}
	<~~blockquote style~~="~~font-size:14pt~~">		<section begin="cmis_import_glossary" />
			<blockquote>
	'''''CMIS Import''''' is an '''''[[Import Provider]]''''' used to import content over a '''[[CMIS Connection]]''', allowing users to import from various on-premise and cloud based storage platforms.		'''''CMIS Import''''' is an '''''[[Import Provider]]''''' used to import content over a '''[[CMIS Connection]]''', allowing users to import from various on-premise and cloud based storage platforms.
	</blockquote>		</blockquote>
			<section end="cmis_import_glossary" />
	Documents are imported from '''CMIS Connections''' using either the '''''Import Descendants''''' or '''''Import Query Results''''' providers. These can be used in two ways:		Documents are imported from '''CMIS Connections''' using either the '''''Import Descendants''''' or '''''Import Query Results''''' providers. These can be used in two ways:

Dgreenwood: /* Import Query Results */

2024-01-03T22:24:08Z

Import Query Results

← Older revision		Revision as of 17:24, 3 January 2024
Line 194:		Line 194:
	* For another example, you can use CMISQL queries to easily filter email messages when importing from an inbox. If you only wanted to import messages from a certain sender, from an certain folder, with a certain subject line and only ones that have not been read, you could filter out any emails that didn't meet those query conditions by comparing metadata properties (like "Sender" and "Subject") to your criteria.		* For another example, you can use CMISQL queries to easily filter email messages when importing from an inbox. If you only wanted to import messages from a certain sender, from an certain folder, with a certain subject line and only ones that have not been read, you could filter out any emails that didn't meet those query conditions by comparing metadata properties (like "Sender" and "Subject") to your criteria.

	{class="attn-box"		{\|class="attn-box"
	\|		\|
	'''⚠'''		'''⚠'''

Dgreenwood at 22:23, 3 January 2024

2024-01-03T22:23:47Z

← Older revision		Revision as of 17:23, 3 January 2024
Line 23:		Line 23:

	# A '''CMIS Connection''' object must made and configured. This will connect Grooper to the document storage platform.		# A '''CMIS Connection''' object must made and configured. This will connect Grooper to the document storage platform.
	#* This may be a connection to a Windows folder, an email inbox, a true CMIS content management system, or other document storage platforms. What the '''CMIS Connection''' connects to is determined by the ''CMIS Binding'' selected when configuring the '''''Connection Type''''' property of the '''CMIS Connection''' object.		#* This may be a connection to a Windows folder, an email inbox, a true CMIS content management system, or other document storage platforms. What the '''CMIS Connection''' connects to is determined by the '''''CMIS Binding''''' selected when configuring the '''''Connection Type''''' property of the '''CMIS Connection''' object.
	# A '''CMIS Repository''' must be imported. This will create an object Grooper can use to import documents from the folders in the document storage platform.		# A '''CMIS Repository''' must be imported. This will create an object Grooper can use to import documents from the folders in the document storage platform.
	#* This acts as a "go-between" or a "hub" for Grooper to pull in documents from the content's source. Or, you may think of this as Grooper's representation of a folder location in the document storage platform.		#* This acts as a "go-between" or a "hub" for Grooper to pull in documents from the content's source. Or, you may think of this as Grooper's representation of a folder location in the document storage platform.
Line 194:		Line 194:
	* For another example, you can use CMISQL queries to easily filter email messages when importing from an inbox. If you only wanted to import messages from a certain sender, from an certain folder, with a certain subject line and only ones that have not been read, you could filter out any emails that didn't meet those query conditions by comparing metadata properties (like "Sender" and "Subject") to your criteria.		* For another example, you can use CMISQL queries to easily filter email messages when importing from an inbox. If you only wanted to import messages from a certain sender, from an certain folder, with a certain subject line and only ones that have not been read, you could filter out any emails that didn't meet those query conditions by comparing metadata properties (like "Sender" and "Subject") to your criteria.

	{~~\|cellpadding~~="~~10" cellspacing="5~~"		{class="attn-box"
	\|~~-style="background-color:#f89420; color:white"~~		\|
	~~\|style="font-size:22pt"\|~~'''⚠'''\|\|Only certain external storage platforms are currently queryable with the '''''CMIS Query''''' property. The following ''CMIS Binding'' sources '''''cannot''''' be queried currently. As such, they are '''''not''''' suitable for '''''Import Query Results'''''. You should instead use '''''Import Descendants''''' for the following '''''CMIS Bindings'''''.		'''⚠'''
			\|Only certain external storage platforms are currently queryable with the '''''CMIS Query''''' property. The following '''''CMIS Binding''''' sources '''''cannot''''' be queried currently. As such, they are '''''not''''' suitable for '''''Import Query Results'''''. You should instead use '''''Import Descendants''''' for the following '''''CMIS Bindings'''''.

	:• '''''FTP'''''		:• '''''FTP'''''
Line 224:		Line 225:
	Upon pressing the ellipsis button at the end of the '''''CMIS Query''''' property, the '''''CMIS Query Editor''''' window will appear.		Upon pressing the ellipsis button at the end of the '''''CMIS Query''''' property, the '''''CMIS Query Editor''''' window will appear.

	This interface allows you to configure the CMISQL query based on available metadata from the ''CMIS Binding''. For example, the ''Exchange'' binding has a selection of queryable metadata for email messages, such as the email's subject, sender and date the message was received.		This interface allows you to configure the CMISQL query based on available metadata from the '''''CMIS Binding'''''. For example, the '''''Exchange''''' binding has a selection of queryable metadata for email messages, such as the email's subject, sender and date the message was received.
	<br>		<br>
	<br>		<br>
Line 253:		Line 254:
	=== New Connection Types (2.72) ===		=== New Connection Types (2.72) ===

	By creating the [[CMIS+]] architecture, we have been able to create new connections between Grooper and content management systems. Grooper can now connect to Microsoft OneDrive, SharePoint, and Exchange via new ''CMIS Bindings''. Since these were created as ''CMIS Bindings'', they can be used by the '''''CMIS Import''''' and '''''CMIS Export''''' providers. Instead of having to create three new import providers and three new export providers for a total of six brand new components, we can use the already established CMIS import and export providers in the CMIS+ framework. A user can create a '''CMIS Connection''' using the ''OneDrive'', ''SharePoint'' or ''Exchange'' bindings, and use the same import and export providers for them as any of the other ''CMIS Bindings''.		By creating the [[CMIS+]] architecture, we have been able to create new connections between Grooper and content management systems. Grooper can now connect to Microsoft OneDrive, SharePoint, and Exchange via new '''''CMIS Bindings'''''. Since these were created as '''''CMIS Bindings''''', they can be used by the '''''CMIS Import''''' and '''''CMIS Export''''' providers. Instead of having to create three new import providers and three new export providers for a total of six brand new components, we can use the already established CMIS import and export providers in the CMIS+ framework. A user can create a '''CMIS Connection''' using the '''''OneDrive''''', '''''SharePoint''''' or '''''Exchange''''' bindings, and use the same import and export providers for them as any of the other '''''CMIS Bindings'''''.

	This will also allow Grooper to create ''CMIS Bindings'' to connect to currently unavailable content management systems in the future much quicker and easier.		This will also allow Grooper to create '''''CMIS Bindings''''' to connect to currently unavailable content management systems in the future much quicker and easier.

	=== Import Mode (2.72) ===		=== Import Mode (2.72) ===

Dsmith: /* Import Descendants */

2023-12-29T16:48:33Z

Import Descendants

← Older revision		Revision as of 11:48, 29 December 2023
Line 108:		Line 108:
	*For example, ''Copy'' mode allows items to be deleted immediately on import. Also, ''Full'' mode avoids the need for any follow-up content loading operations in the '''Batch Process'''.		*For example, ''Copy'' mode allows items to be deleted immediately on import. Also, ''Full'' mode avoids the need for any follow-up content loading operations in the '''Batch Process'''.

	**This mode was called ''Full'' in older versions of Grooper.		*This mode was called ''Full'' in older versions of Grooper.

	''Sparse''		''Sparse''

Dsmith: /* Import Descendants */

2023-12-29T16:48:12Z

Import Descendants

← Older revision		Revision as of 11:48, 29 December 2023
Line 102:		Line 102:
	\|}		\|}

	''~~Full~~''		''Copy''

	* Both properties and content will be loaded. This is a total duplication of the document from its source to your Grooper Repository's local file store. This is the slowest import mode, because the full content of each document is copied during a ''single-threaded'' import process. As such, this mode is not well-suited for high-volume imports, but provides some useful advantages in low-volume import scenarios.		* Both properties and content will be loaded. This is a total duplication of the document from its source to your Grooper Repository's local file store. This is the slowest import mode, because the full content of each document is copied during a ''single-threaded'' import process. As such, this mode is not well-suited for high-volume imports, but provides some useful advantages in low-volume import scenarios.

	*For example, ''~~Full~~'' mode allows items to be deleted immediately on import. Also, ''Full'' mode avoids the need for any follow-up content loading operations in the '''Batch Process'''.		*For example, ''Copy'' mode allows items to be deleted immediately on import. Also, ''Full'' mode avoids the need for any follow-up content loading operations in the '''Batch Process'''.

			**This mode was called ''Full'' in older versions of Grooper.

	''Sparse''		''Sparse''