2.72:OneDrive (CMIS Binding) - Revision history

Dgreenwood: Dgreenwood moved page 2.72:OneDrive (CMIS Connection Type) to 2.72:OneDrive (CMIS Binding)

2025-05-13T15:37:19Z

Dgreenwood moved page 2.72:OneDrive (CMIS Connection Type) to 2.72:OneDrive (CMIS Binding)

← Older revision	Revision as of 10:37, 13 May 2025
(No difference)

Randallkinard at 20:55, 19 April 2024

2024-04-19T20:55:39Z

← Older revision		Revision as of 15:55, 19 April 2024
Line 1:		Line 1:
	{{AutoVersion}}		{{AutoVersion}}

	[[image:onedrive.png\|frame]]		[[image:onedrive.png\|frame]]

	<blockquote ~~style="font-size~~:~~14pt">~~		<blockquote>{{#lst:Glossary\|OneDrive}}</blockquote>
	~~The '''OneDrive''' Connection Type is a CMIS Binding that connects Grooper to Microsoft~~ OneDrive ~~cloud services.~~
	</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 will expose themselves as hierarchical file system (HFS), where folders and files are represented by simple object types. As such, this binding is suitable for Unmapped rather than Mapped Export. You can still export metadata as a "buddy file" adjusting the Metadata Export property in the Unmapped Export Settings.		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 will expose themselves as hierarchical file system (HFS), where folders and files are represented by simple object types. As such, this binding is suitable for Unmapped rather than Mapped Export. You can still export metadata as a "buddy file" adjusting the Metadata Export property in the Unmapped Export Settings.
Line 14:		Line 13:

	== Version Differences ==		== Version Differences ==

	Connectivity to Microsoft OneDrive is brand new to version 2.72!		Connectivity to Microsoft OneDrive is brand new to version 2.72!

Randallkinard: Randallkinard moved page 2.72:OneDrive (CMIS Binding) to 2.72:OneDrive (CMIS Connection Type) without leaving a redirect: new naming convention

2024-04-17T20:53:12Z

Randallkinard moved page 2.72:OneDrive (CMIS Binding) to 2.72:OneDrive (CMIS Connection Type) without leaving a redirect: new naming convention

← Older revision	Revision as of 15:53, 17 April 2024
(No difference)

Dgreenwood: Dgreenwood moved page OneDrive (CMIS Binding) - 2.72 to 2.72:OneDrive (CMIS Binding) without leaving a redirect

2024-01-02T18:40:16Z

Dgreenwood moved page OneDrive (CMIS Binding) - 2.72 to 2.72:OneDrive (CMIS Binding) without leaving a redirect

← Older revision	Revision as of 13:40, 2 January 2024
(No difference)

Dgreenwood at 18:40, 2 January 2024

2024-01-02T18:40:05Z

← Older revision		Revision as of 13:40, 2 January 2024
Line 74:		Line 74:

	You cannot, however, export a metadata file using [[CMIS Export#Mapped Export]]\|Mapped Export]]. If you also want to export an XML document, for example, you would need to add a second Document Export step to your Batch process, use the [[CMIS Export#Unmapped Export\|Unmapped Export]] provider, and adjust the "Metadata Export" settings in Export Settings.		You cannot, however, export a metadata file using [[CMIS Export#Mapped Export]]\|Mapped Export]]. If you also want to export an XML document, for example, you would need to add a second Document Export step to your Batch process, use the [[CMIS Export#Unmapped Export\|Unmapped Export]] provider, and adjust the "Metadata Export" settings in Export Settings.

	~~[[Category:Articles]]~~
	~~[[Category:Version 2.72]]~~

Dgreenwood at 18:39, 2 January 2024

2024-01-02T18:39:31Z

← Older revision		Revision as of 13:39, 2 January 2024
Line 1:		Line 1:
			{{AutoVersion}}
	[[image:onedrive.png\|frame]]		[[image:onedrive.png\|frame]]

Dsmith: Removed redirect to OneDrive (CMIS Binding) - 2023

2023-12-14T15:45:48Z

Removed redirect to OneDrive (CMIS Binding) - 2023

← Older revision		Revision as of 10:45, 14 December 2023
Line 1:		Line 1:
	~~#REDIRECT [[OneDrive (CMIS Binding) - 2023]]~~

	[[image:onedrive.png\|frame]]		[[image:onedrive.png\|frame]]

Dsmith: Redirected page to OneDrive (CMIS Binding) - 2023

2023-12-14T15:45:21Z

Redirected page to OneDrive (CMIS Binding) - 2023

← Older revision		Revision as of 10:45, 14 December 2023
Line 1:		Line 1:
			#REDIRECT [[OneDrive (CMIS Binding) - 2023]]

	[[image:onedrive.png\|frame]]		[[image:onedrive.png\|frame]]

Dgreenwood at 18:09, 12 December 2022

2022-12-12T18:09:04Z

← Older revision		Revision as of 13:09, 12 December 2022
Line 75:		Line 75:

	[[Category:Articles]]		[[Category:Articles]]
	[[Category:2.72]]		[[Category:Version 2.72]]

Dgreenwood at 18:08, 12 December 2022

2022-12-12T18:08:49Z

← Older revision		Revision as of 13:08, 12 December 2022
Line 73:		Line 73:

	You cannot, however, export a metadata file using [[CMIS Export#Mapped Export]]\|Mapped Export]]. If you also want to export an XML document, for example, you would need to add a second Document Export step to your Batch process, use the [[CMIS Export#Unmapped Export\|Unmapped Export]] provider, and adjust the "Metadata Export" settings in Export Settings.		You cannot, however, export a metadata file using [[CMIS Export#Mapped Export]]\|Mapped Export]]. If you also want to export an XML document, for example, you would need to add a second Document Export step to your Batch process, use the [[CMIS Export#Unmapped Export\|Unmapped Export]] provider, and adjust the "Metadata Export" settings in Export Settings.

			[[Category:Articles]]
			[[Category:2.72]]