Import Descendants (Import Provider) - Revision history

Dgreenwood at 20:56, 28 May 2025

2025-05-28T20:56:16Z

← Older revision		Revision as of 15:56, 28 May 2025
Line 1:		Line 1:
	~~This is a redirect page.~~		{{AutoVersion}}

	<blockquote>{{#lst:Glossary\|Import Descendants}}</blockquote>		<blockquote>{{#lst:Glossary\|Import Descendants}}</blockquote>

Dgreenwood at 20:55, 28 May 2025

2025-05-28T20:55:53Z

← Older revision		Revision as of 15:55, 28 May 2025
Line 2:		Line 2:

	<blockquote>{{#lst:Glossary\|Import Descendants}}</blockquote>		<blockquote>{{#lst:Glossary\|Import Descendants}}</blockquote>

	~~For information on '''''Import Descendants''''' visit the following resources:~~
	* [[CMIS Import]] - This is an article covering imports using '''CMIS Connections''' in general.
	* [[CMIS Import#About CMIS Import]] - This portion of the "CMIS Import" article briefly covers the differences between '''''Import Descendants''''' and '''''Import Query Results'''''.
	* [[CMIS Import#Import Descendants]] - This portion of the "CMIS Import" article explains '''''Import Descendants'''''.

	== About ==		== About ==

Dgreenwood: /* Example Import Descendants configuration */

2025-05-28T20:12:25Z

Example Import Descendants configuration

@@ Line 50: / Line 50: @@
 Regardless of the platform you're accessing with a CMIS Repository, you configure Import Descendants largely the same. Just pick a CMIS Repository and configure the rest of Import Descendants as needed.
 <big>Example: Submitting Import Descendants from the Imports Page</big>
@@ Line 71: / Line 75: @@
 # Press the "Submit" button when finished.
 # Your Import Watcher service will pick up and execute the Import Job.

Dgreenwood: /* Example Import Descendants configuration */

2025-05-27T21:58:20Z

Example Import Descendants configuration

← Older revision		Revision as of 16:58, 27 May 2025
Line 25:		Line 25:
	{{#lst:CMIS Import\|import_query_results_and_descendants_similarities}}		{{#lst:CMIS Import\|import_query_results_and_descendants_similarities}}

	== ~~Example Import Descendants configuration~~ ==		== Prereqs: CMIS Repository ==

			A CMIS Repository allows Grooper access to files and folders within a storage platform.

	Because Import Descendants imports from a CMIS Repository, you can import from numerous storage platforms determined by the "CMIS Binding" used. These CMIS Bindings include:		Because Import Descendants imports from a CMIS Repository, you can import from numerous storage platforms determined by the "CMIS Binding" used. These CMIS Bindings include:
Line 37:		Line 39:
	* [[AppXtender]] to connect to AppEnhancer applications		* [[AppXtender]] to connect to AppEnhancer applications

	Regardless of the platform, you configure Import Descendants largely the same. Just pick a CMIS Repository and ~~a base folder in that repository~~.		Before you can import files from these platforms using Import Descendants or Import Query Results, there's some setup required in the Grooper Design page. You must:
			# Create and configure a CMIS Connection.
			# Import a folder location as a CMIS Repository.

			This will allow you to import files from folders accessed by the CMIS Repository. For information on CMIS Connections and CMIS Repositories, including how to create them in Grooper, visit the [[CMIS Connection]] page.

			[https://app.supademo.com/demo/cm8ddjcr91rb92ugqp7k9phqo Click here for an interactive walkthrough.]

			== Example Import Descendants configuration ==

			Regardless of the platform you're accessing with a CMIS Repository, you configure Import Descendants largely the same. Just pick a CMIS Repository and configure the rest of Import Descendants as needed.

	<big>Example: Submitting Import Descendants from the Imports Page</big>		<big>Example: Submitting Import Descendants from the Imports Page</big>
Line 52:		Line 64:
	# Open the "Repository" node selector (Press the "☰" button).		# Open the "Repository" node selector (Press the "☰" button).
	# Select the CMIS Repository you wish to import from.		# Select the CMIS Repository you wish to import from.
	# Configure the Import Mode property as needed.		# Select a Base Folder, as needed.
			# Configure the Import Mode property, as needed.
	# Configure the Batch Creation settings, as needed.		# Configure the Batch Creation settings, as needed.
	# Configure the file disposition options (Delete Item, Move To Folder, or Update Properties), as needed.		# Configure the file disposition options (Delete Item, Move To Folder, or Update Properties), as needed.

Dgreenwood: /* Example Import Descendants configuration */

2025-05-27T21:35:14Z

Example Import Descendants configuration

@@ Line 39: / Line 39: @@
 Regardless of the platform, you configure Import Descendants largely the same. Just pick a CMIS Repository and a base folder in that repository.
-'''''WORK IN PROGRESS! CHECK BACK LATER''''''
+<big>Example: Submitting Import Descendants from the Imports Page</big>
 {{#lst:CMIS Import|shared_cmis_import_settings}}

Dgreenwood at 19:17, 27 May 2025

2025-05-27T19:17:03Z

← Older revision		Revision as of 14:17, 27 May 2025
Line 15:		Line 15:

	Just like any other Import Provider, Import Descendants is used to submit "'''Import Jobs'''". Import Jobs are how Grooper brings in files from a storage location for processing. For example, it's how PDFs from a Windows folder get into Grooper or messages from an email inbox get into Grooper. When an Import Job runs, Grooper first creates a Batch and then creates a Batch Folder for each imported file. A copy of the file is attached to the Batch Folder. This becomes the Batch Folder's "attachment" and is used when applying activities like "Split Pages".		Just like any other Import Provider, Import Descendants is used to submit "'''Import Jobs'''". Import Jobs are how Grooper brings in files from a storage location for processing. For example, it's how PDFs from a Windows folder get into Grooper or messages from an email inbox get into Grooper. When an Import Job runs, Grooper first creates a Batch and then creates a Batch Folder for each imported file. A copy of the file is attached to the Batch Folder. This becomes the Batch Folder's "attachment" and is used when applying activities like "Split Pages".
	:*<li class="fyi-bullet"> When files are imported into Grooper, a link to that file is stored on the Batch Folder. This link maintains a connection between the file's source location and the document in Grooper. This link also makes "Sparse" imports possible. [[#~~About~~ "Sparse" imports\|See below for more.]]		:*<li class="fyi-bullet"> When files are imported into Grooper, a link to that file is stored on the Batch Folder. This link maintains a connection between the file's source location and the document in Grooper. This link also makes "Sparse" imports possible. [[#Import Mode (and "Sparse" imports)\|See below for more.]]

Dgreenwood: /* About */

2025-05-27T18:10:02Z

About

@@ Line 23: / Line 23: @@
 In both cases, an "Import Descendants" can be selected and configured using using the "Provider" property.
-=== Similarities and differences between Import Query Results and Import Descendants ===
+{{#lst:CMIS Import|import_query_results_and_descendants_similarities}}
 == Example Import Descendants configuration ==

Dgreenwood at 16:21, 27 May 2025

2025-05-27T16:21:12Z

@@ Line 64: / Line 64: @@
 '''''WORK IN PROGRESS! CHECK BACK LATER''''''
-== About "Sparse" imports ==
+{{#lst:CMIS Import|shared_cmis_import_settings}}
 <!---

Dgreenwood: /* About "Sparse" imports */

2025-05-27T13:30:44Z

About "Sparse" imports

← Older revision		Revision as of 08:30, 27 May 2025
Line 85:		Line 85:
	* When you're importing hundreds or thousands of documents by copying them from a source location to the Grooper File Store, it takes a long time for the Import Job to complete.		* When you're importing hundreds or thousands of documents by copying them from a source location to the Grooper File Store, it takes a long time for the Import Job to complete.
	* By only importing a link to the file content, Sparse mode ''dramatically'' speeds up the time it takes to get a usable document into Grooper.		* By only importing a link to the file content, Sparse mode ''dramatically'' speeds up the time it takes to get a usable document into Grooper.
	* Then, the first step in your Batch Process should be "Execute" using the "CMIS Document Link > Load" command. This will allow you to load the files into the Grooper File Store using multiple threads.		* Then, the first step in your Batch Process should be "'''Execute'''" using the "'''CMIS Document Link > Load'''" command. This will allow you to load the files into the Grooper File Store using multiple threads.
			**<li class="attn-bullet"> Be Aware: The "Load" command has three modes (1) Content (2) Properties and (3) Full. For "Properties" and "Full" to work appropriately, the Batch Folders must be classified on import and use an Import Behavior to map the properties.
	* The end result is the overall import operation will be as if you had used the "Copy" mode. But it will be done in a way that runs multi-threaded.		* The end result is the overall import operation will be as if you had used the "Copy" mode. But it will be done in a way that runs multi-threaded.

Dgreenwood: /* Example Import Descendants configuration */

2025-05-27T13:25:51Z

Example Import Descendants configuration

← Older revision		Revision as of 08:25, 27 May 2025
Line 61:		Line 61:

	Regardless of the platform, you configure Import Descendants largely the same. Just pick a CMIS Repository and a base folder in that repository.		Regardless of the platform, you configure Import Descendants largely the same. Just pick a CMIS Repository and a base folder in that repository.

			'''''WORK IN PROGRESS! CHECK BACK LATER''''''

	== About "Sparse" imports ==		== About "Sparse" imports ==