OneDrive (CMIS Binding) - Revision history

Dsmith: /* Configuring the Export Behavior */

2025-05-29T17:51:32Z

Configuring the Export Behavior

← Older revision		Revision as of 12:51, 29 May 2025
Line 76:		Line 76:
	# Select the CMIS Repository property and click <code> "☰" </code> to access the dropdown list.		# Select the CMIS Repository property and click <code> "☰" </code> to access the dropdown list.
	# Click down through the list and select the OneDrive Repository.		# Click down through the list and select the OneDrive Repository.
	#		# Configure the Target Folder if need be - otherwise, the Documents will be exported to the root level of the OneDrive
	#		# Choose the Object Type.
			# Click OK on the Export Definitions Editor window when finished.
			# Click OK on the Behaviors Editor window.
			# Save changes made.

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

Dsmith: /* Configuring the Export Behavior */

2025-05-29T17:48:22Z

Configuring the Export Behavior

← Older revision		Revision as of 12:48, 29 May 2025
Line 74:		Line 74:
	# Select the Export Definitions property and click <code> "..." </code> to open the Export Definitions Editor Window.		# Select the Export Definitions property and click <code> "..." </code> to open the Export Definitions Editor Window.
	# Click the Add button and select CMIS Export from the dropdown list.		# Click the Add button and select CMIS Export from the dropdown list.
	#		# Select the CMIS Repository property and click <code> "☰" </code> to access the dropdown list.
	#		# Click down through the list and select the OneDrive Repository.
	#		#
	#		#

Dsmith: /* Configuring the Export Behavior */

2025-05-29T17:44:48Z

Configuring the Export Behavior

@@ Line 68: / Line 68: @@
 === Exporting ===
 ==== Configuring the Export Behavior ====
 == See Also ==

Dgreenwood at 16:20, 13 May 2025

2025-05-13T16:20:54Z

← Older revision		Revision as of 11:20, 13 May 2025
Line 12:		Line 12:
	* The OneDrive binding can be used for import operations via [[CMIS Import]] using "Import Descendants" or "Import Query Results".		* The OneDrive binding can be used for import operations via [[CMIS Import]] using "Import Descendants" or "Import Query Results".
	* It can be used for export operations via [[CMIS Export]].		* It can be used for export operations via [[CMIS Export]].
	**<li class="attn-bullet"> OneDrive ~~drives are simple hierarchical file systems (HFS). HFS folders and files are represented by simple object types. It~~ only has one writable property: "Name". As such, this binding is unsuitable for "mapped exports". However, you can still export metadata as a "buddy file" by adding a metadata format in your [[CMIS Export]] definition.		**<li class="attn-bullet"> The OneDrive binding only has one writable property for exported documents: "Name". As such, this binding is unsuitable for "mapped exports". However, you can still export metadata as a "buddy file" by adding a metadata format in your [[CMIS Export]] definition.
	**<li class="attn-bullet"> If you are wanting to map data to field columns in SharePoint document libraries, you should use a [[SharePoint]] connection instead. The SharePoint binding ''is'' suitable for mapped exports.		**<li class="attn-bullet"> If you are wanting to map data to field columns in SharePoint document libraries, you should use a [[SharePoint]] connection instead. The SharePoint binding ''is'' suitable for mapped exports.
	<br clear=all>		<br clear=all>

Dgreenwood at 16:16, 13 May 2025

2025-05-13T16:16:04Z

← Older revision		Revision as of 11:16, 13 May 2025
Line 12:		Line 12:
	* The OneDrive binding can be used for import operations via [[CMIS Import]] using "Import Descendants" or "Import Query Results".		* The OneDrive binding can be used for import operations via [[CMIS Import]] using "Import Descendants" or "Import Query Results".
	* It can be used for export operations via [[CMIS Export]].		* It can be used for export operations via [[CMIS Export]].
	**<li class="attn-bullet"> OneDrive drives are simple hierarchical file systems (HFS). HFS folders and files are represented by simple object types. As such, this binding is unsuitable for "mapped ~~export~~". However, you can still export metadata as a "buddy file" by adding a metadata format in your [[CMIS Export]] definition.		**<li class="attn-bullet"> OneDrive drives are simple hierarchical file systems (HFS). HFS folders and files are represented by simple object types. It only has one writable property: "Name". As such, this binding is unsuitable for "mapped exports". However, you can still export metadata as a "buddy file" by adding a metadata format in your [[CMIS Export]] definition.
	**<li class="attn-bullet"> If you are wanting to map data to field columns in SharePoint document libraries, you should use a [[SharePoint]] connection instead. The SharePoint binding ''is'' suitable for mapped exports.		**<li class="attn-bullet"> If you are wanting to map data to field columns in SharePoint document libraries, you should use a [[SharePoint]] connection instead. The SharePoint binding ''is'' suitable for mapped exports.
	<br clear=all>		<br clear=all>

Dgreenwood at 16:11, 13 May 2025

2025-05-13T16:11:41Z

← Older revision		Revision as of 11:11, 13 May 2025
Line 5:		Line 5:
	<blockquote>{{#lst:Glossary\|OneDrive}}</blockquote>		<blockquote>{{#lst:Glossary\|OneDrive}}</blockquote>

	It provides access to OneDrive Personal or OneDrive for Business drives and SharePoint Online or SharePoint Server 2016 document libraries. More or less, all you have to do is sync Grooper and OneDrive by logging in using your OneDrive credentials and you can import from and export to your OneDrive folders.		The OneDrive binding provides access to OneDrive Personal or OneDrive for Business drives and SharePoint Online or SharePoint Server 2016 document libraries. More or less, all you have to do is sync Grooper and OneDrive by logging in using your OneDrive credentials and you can import from and export to your OneDrive folders.

	OneDrive drives and SharePoint document libraries are exposed as a '''CMIS Repository''', mimicking its file system hierarchy as well. Once connected, you can import, export, search, and browse documents from Grooper.

	The OneDrive binding can be used for import operations via CMIS Import using either "Import Descendants" or "Import Query Results". It can be used for export operations via the Document Export activity.

	SFTP directories use a a hierarchical file system (HFS), where folders and files are represented by simple object types. As such, this binding is suitable for the [[CMIS Export#Unmapped Export\|Unmapped Export]] provider rather than the [[CMIS Export#Mapped Export\|Mapped Export]] provider. You can still export metadata as a "buddy file" by adjusting the "Metadata Export" property in the Document Export activity's Export Settings.

	The SFTP Connection Type works largely the same as the [[FTP (CMIS Binding)\|FTP]] Connection Type. However, it uses SFTP protocol instead. How you set it up and use it within Grooper is functionally the same.


	The OneDrive binding can be selected as a connection option when configuring a '''CMIS Connection'''. After configuring the connection, OneDrive drives and SharePoint document libraries are exposed to Grooper as a '''CMIS Repository'''. CMIS Repository nodes are created as children of the CMIS Connection by importing a reference to their source location.		The OneDrive binding can be selected as a connection option when configuring a '''CMIS Connection'''. After configuring the connection, OneDrive drives and SharePoint document libraries are exposed to Grooper as a '''CMIS Repository'''. CMIS Repository nodes are created as children of the CMIS Connection by importing a reference to their source location.

Dgreenwood at 16:07, 13 May 2025

2025-05-13T16:07:54Z

← Older revision		Revision as of 11:07, 13 May 2025
Line 5:		Line 5:
	<blockquote>{{#lst:Glossary\|OneDrive}}</blockquote>		<blockquote>{{#lst:Glossary\|OneDrive}}</blockquote>

	It provides access to OneDrive Personal or OneDrive for Business drives and SharePoint Online or SharePoint Server 2016 document libraries. More or less, all you have to do is sync Grooper and OneDrive by logging in using your OneDrive credentials and you can import from and export to your OneDrive folders~~. OneDrive drives and SharePoint libraries can be individually imported as a '''CMIS Repository'''~~.		It provides access to OneDrive Personal or OneDrive for Business drives and SharePoint Online or SharePoint Server 2016 document libraries. More or less, all you have to do is sync Grooper and OneDrive by logging in using your OneDrive credentials and you can import from and export to your OneDrive folders.

	~~Each~~ OneDrive CMIS Repository ~~will expose themselves~~ as hierarchical file system (HFS). ~~Folders~~ and files are represented by simple object types. As such, this binding is unsuitable for "mapped export". ~~You~~ can still export metadata as a "buddy file" by adding a metadata format in your [[Export ~~Behavior~~]].		OneDrive drives and SharePoint document libraries are exposed as a '''CMIS Repository''', mimicking its file system hierarchy as well. Once connected, you can import, export, search, and browse documents from Grooper.

			The OneDrive binding can be used for import operations via CMIS Import using either "Import Descendants" or "Import Query Results". It can be used for export operations via the Document Export activity.

			SFTP directories use a a hierarchical file system (HFS), where folders and files are represented by simple object types. As such, this binding is suitable for the [[CMIS Export#Unmapped Export\|Unmapped Export]] provider rather than the [[CMIS Export#Mapped Export\|Mapped Export]] provider. You can still export metadata as a "buddy file" by adjusting the "Metadata Export" property in the Document Export activity's Export Settings.

			The SFTP Connection Type works largely the same as the [[FTP (CMIS Binding)\|FTP]] Connection Type. However, it uses SFTP protocol instead. How you set it up and use it within Grooper is functionally the same.


			The OneDrive binding can be selected as a connection option when configuring a '''CMIS Connection'''. After configuring the connection, OneDrive drives and SharePoint document libraries are exposed to Grooper as a '''CMIS Repository'''. CMIS Repository nodes are created as children of the CMIS Connection by importing a reference to their source location.

			The OneDrive CMIS Repository mimics the drive's file system hierarchy as well. Once a CMIS Repository is created, you can import, export, search, and browse documents from Grooper.
			* The OneDrive binding can be used for import operations via [[CMIS Import]] using "Import Descendants" or "Import Query Results".
			* It can be used for export operations via [[CMIS Export]].
			**<li class="attn-bullet"> OneDrive drives are simple hierarchical file systems (HFS). HFS folders and files are represented by simple object types. As such, this binding is unsuitable for "mapped export". However, you can still export metadata as a "buddy file" by adding a metadata format in your [[CMIS Export]] definition.
			**<li class="attn-bullet"> If you are wanting to map data to field columns in SharePoint document libraries, you should use a [[SharePoint]] connection instead. The SharePoint binding ''is'' suitable for mapped exports.
	<br clear=all>		<br clear=all>
	== Version Differences ==		== Version Differences ==

Dgreenwood: Removed redirect to OneDrive (CMIS Connection Type)

2025-05-13T15:40:11Z

Removed redirect to OneDrive (CMIS Connection Type)

← Older revision		Revision as of 10:40, 13 May 2025
Line 1:		Line 1:
	#~~REDIRECT~~ [[OneDrive (CMIS Connection Type)]]		{{AutoVersion}}
			[[Category:CMIS Connection Type]]
			[[image:onedrive.png\|frame]]

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

			It provides access to OneDrive Personal or OneDrive for Business drives and SharePoint Online or SharePoint Server 2016 document libraries. More or less, all you have to do is sync Grooper and OneDrive by logging in using your OneDrive credentials and you can import from and export to your OneDrive folders. OneDrive drives and SharePoint libraries can be individually imported as a '''CMIS Repository'''.

			Each OneDrive CMIS Repository will expose themselves as hierarchical file system (HFS). Folders and files are represented by simple object types. As such, this binding is unsuitable for "mapped export". You can still export metadata as a "buddy file" by adding a metadata format in your [[Export Behavior]].
			<br clear=all>
			== Version Differences ==
			When the '''''OneDrive''''' binding was added in version 2.72, it did not support full text querying. Full text searching is now possible as of Grooper version 2023.
			* Use the <code>CONTAINS()</code> predicate in a [[CMIS Query]] to search document content in a One Drive repository based on a search string.

			== How To: Create a New Microsoft OneDrive Connection ==

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


			#Expand the "Infrastructure" node.
			#Right click the "CMIS Connections" folder.
			#Mouse over "Add" and select "CMIS Connection...".
			#In the "Connection Properties" panel, select "OneDrive" from the "Connection Type" drop down list.
			#Expand the "Connection Settings" heading and the "Login" heading under that.
			#Select "Authentication" and press the ellipsis button at the end of the line.
			#Log in using credentials with a Microsoft account.
			#After you "Save", press the "List Repositories" button to show the folder paths you just added as repositories.


			== Importing and Exporting with a OneDrive CMIS Connection ==
			=== Importing ===
			==== Configuring the Import Behavior ====
			[https://app.supademo.com/demo/cma44n32401tp3b0i4to0a7os?step=1 Click here for an interactive walkthrough]

			# Select a Content Type Object; this can be a Content Model, Document Type, or Content Category, but a Content Model is the most common place to configure an Import Behavior.
			# Click <code> ... </code> at the end of the Behaviors property.
			# Click the Add button within the Behaviors List window and select Import Behavior.
			# Define the import by clicking <code> ... </code> at the end of the Import Definitions property after it appears on the right side of the Behaviors List window.
			# Click the Add button that appears within the Import Definitions window and select CMIS Import from the dropdown list.
			# Select the OneDrive CMIS Repository.
			# Choose the Content Type you'll be importing.
			# Configure Read Mappings and/or Write Mappings if necessary.
			# When finished, click OK.
			# Click OK to finalize the Import Behavior.
			# Save.

			==== Submitting an Import Job ====
			[https://app.supademo.com/demo/cma4fgqud016nyc0i4fhh7hym?step=1 Click here for an interactive walkthrough]

			# Click the Imports icon.
			#:* <li class="fyi-bullet"> IMPORTANT: You will need an Import Watcher service installed and running in order to submit an Import Job. </li>
			# On the Imports screen, click the Add New Jobs button.
			# Enter a Description for the Import Job.
			# Select the Import Provider.
			# Select the OneDrive Repository.
			# If you choose Import Descendants for your Provider, configure the Import Filter; for Import Query Results, configure the CMIS Query.
			#* Regardless of what Provider you have chosen, the purpose of the Import Filter/CMIS Query is to enable users to narrow down what file contents they want to import into Grooper.
			# If you plan to process the Batch upon import, then configure the Batch Creation property. If not, click Submit.
			# Once your Batch has been imported, you can view it by going to the Design page and clicking Batches --> Test --> Imported Batches
			#* This is for Batches that have not been processed upon import. To view a processed Batch, you will need to look in the Production folder.

			=== Exporting ===
			==== Configuring the Export Behavior ====

			== See Also ==

			For more information to use your '''CMIS Connection''' once its created, see the following articles:
			* [[CMIS Export]]
			* [[CMIS Import]]

Randallkinard: Randallkinard moved page OneDrive (CMIS Binding) to OneDrive (CMIS Connection Type): new naming convention

2024-04-17T20:53:42Z

Randallkinard moved page OneDrive (CMIS Binding) to OneDrive (CMIS Connection Type): new naming convention

New page

#REDIRECT [[OneDrive (CMIS Connection Type)]]