View source for Import Descendants (Import Provider)

This is a redirect page.

<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 ==

'''Import Descendants''' is an [[Import Provider]] used to import objects from a CMIS Repository that are "children" or "descendants" of a base CMIS Folder.  This is done using a SQL-style "filter" to select the items that will be imported.

* <code>AT_LEVEL</code> selects items at a specific level
* <code>MATCHES</code> allows RegEx against property values

=== Example ===

<tabs>
<tab name="Step 1">
===== Create a Batch =====
The easiest way to use Import Descendants is by creating a new batch.
* In Grooper Design Studio or Grooper Dashboard, create a new batch by pressing "Batch > CMIS Import > Import Descendants...".


[[image:1556571123332-495.png|center]]


</tab>
<tab name="Step 2">
===== Choose the Repository =====

If you have multiple CMIS repositories available, you'll need to choose the one from which you wish to import.
* Select the appropriate repository from the "Repository" property.


[[image:1556571692162-486.png|center|900px]]


[[image:1556632783258-847.png|center|900px]]


</tab>
<tab name="Step 3">
===== Analyze and Import =====

Now we can test it out.
* Pressing "Analyze" will run a search against your repository with your configured settings.
* Pressing "Import" will create a batch of documents that were imported using your configured settings.

Using the "Starting Step" property, you can choose from your published Batch Processes the step where your batch should be created. For example, in the screenshot below, the batch will be created at the "Image Review" step of a Batch Process.


[[image:1556632834217-872.png|center|900px]]


</tab>
</tabs>

=== Example Queries ===

These are samples of what you could type into the "Import Filter" to narrow which objects are imported.  They take the following general form.

<code>SELECT * FROM <ContentType> WHERE <Criteria></code>

Below are a few examples of this syntax in action.

{|
|-valign="top"
|style="width:50%"|'''Filter'''||'''Description'''
|-valign="top"
|<code>SELECT * FROM File</code>||Import all descendant files.  This will import all files in the repository without any foldering.
|-valign="top"
|<code>SELECT * FROM File WHERE AT_LEVEL(1)</code>||Import files which are immediate children.  This will only import files at that level, not from subsequent levels.
|-valign="top"
|<code>SELECT * FROM Folder</code>||Import folders which are immediate children.  This will import both files and their foldering.
|-valign="top"
|<code>SELECT * FROM File WHERE cmis:name MATCHES '^\d{4}-\d{2}-\d{2}'</code>||Import files with a specific naming pattern, using regular expressions.
|-valign="top"
|<code>SELECT * FROM File WHERE cmis:name LIKE 'ca%'</code>||Import files with a name starting with ca.
|-valign="top"
|<code>SELECT * FROM File WHERE cmis:contentStreamLength > 10000</code>||Import files larger than 10,000 bytes.