2023:NTFS (CMIS Binding) - Revision history

Dgreenwood: Dgreenwood moved page 2023:NTFS (CMIS Connection Type) to 2023:NTFS (CMIS Binding)

2025-05-13T15:32:57Z

Dgreenwood moved page 2023:NTFS (CMIS Connection Type) to 2023:NTFS (CMIS Binding)

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

Randallkinard at 15:01, 22 November 2024

2024-11-22T15:01:19Z

← Older revision		Revision as of 10:01, 22 November 2024
Line 92:		Line 92:
	* [[CMIS Export]]		* [[CMIS Export]]
	* [[CMIS Import]]		* [[CMIS Import]]

	~~== Glossary ==~~
	~~<u><big>'''CMIS Connection Type'''</big></u>: {{#lst:Glossary\|CMIS Connection Type}}~~

	~~<u><big>'''CMIS Connection'''</big></u>: {{#lst:Glossary\|CMIS Connection}}~~

	~~<u><big>'''CMIS Export'''</big></u>: {{#lst:Glossary\|CMIS Export}}~~

	~~<u><big>'''CMIS Import'''</big></u>: {{#lst:Glossary\|CMIS Import}}~~

	~~<u><big>'''CMIS Repository'''</big></u>: {{#lst:Glossary\|CMIS Repository}}~~

	~~<u><big>'''CMIS'''</big></u>: {{#lst:Glossary\|CMIS}}~~

	~~<u><big>'''Export'''</big></u>: {{#lst:Glossary\|Export}}~~

	~~<u><big>'''Import Descendants'''</big></u>: {{#lst:Glossary\|Import Descendants}}~~

	~~<u><big>'''Import Query Results'''</big></u>: {{#lst:Glossary\|Import Query Results}}~~

	~~<u><big>'''NTFS'''</big></u>: {{#lst:Glossary\|NTFS}}~~

	~~<u><big>'''Repository'''</big></u>: {{#lst:Glossary\|Repository}}~~

	~~<u><big>'''Service'''</big></u>: {{#lst:Glossary\|Service}}~~

Randallkinard at 14:52, 27 August 2024

2024-08-27T14:52:07Z

@@ Line 17: / Line 17: @@
 Paths should be specified as UNC paths (ex: \\DomainName\Path\).  Grooper does give you the option to search for and use Windows system paths.  However, you probably should not.  These paths may not be accessible to other processors, users or machines.  For example, if you create a repository using a local path to your Documents folder and you export a batch using that NTFS binding to another user on another machine, the batch process is going to look for a repository on their local drive, not yours.
 |}
 == How To: Create a New NFTS Connection ==
@@ Line 117: / Line 92: @@
 * [[CMIS Export]]
 * [[CMIS Import]]

Randallkinard: /* NTFS CMISQL Query Limitations */

2024-07-02T18:24:08Z

NTFS CMISQL Query Limitations

← Older revision		Revision as of 13:24, 2 July 2024
Line 109:		Line 109:
	=== NTFS CMISQL Query Limitations ===		=== NTFS CMISQL Query Limitations ===
	<section begin="ntfs_query_limitations" />		<section begin="ntfs_query_limitations" />
	The '''''NTFS''''' connection binding will ''not'' support the <code>CONTAINS()</code> predicate (for full text searching) ''unless'' the Windows file system has been indexed by the Windows ~~Indexing~~ Service.		The '''''NTFS''''' connection binding will ''not'' support the <code>CONTAINS()</code> predicate (for full text searching) ''unless'' the Windows file system has been indexed by the Windows Search Service.
	<section end="ntfs_query_limitations" />		<section end="ntfs_query_limitations" />

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

Randallkinard at 16:09, 10 May 2024

2024-05-10T16:09:09Z

@@ Line 17: / Line 17: @@
 Paths should be specified as UNC paths (ex: \\DomainName\Path\).  Grooper does give you the option to search for and use Windows system paths.  However, you probably should not.  These paths may not be accessible to other processors, users or machines.  For example, if you create a repository using a local path to your Documents folder and you export a batch using that NTFS binding to another user on another machine, the batch process is going to look for a repository on their local drive, not yours.
 |}
 == How To: Create a New NFTS Connection ==

Randallkinard at 20:57, 19 April 2024

2024-04-19T20:57:10Z

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

	[[File:2023_NTFS_CMIS_Binding_00.png\|frame]]		[[File:2023_NTFS_CMIS_Binding_00.png\|frame]]
	~~<section begin="glossary" />~~
	<blockquote>		<blockquote>{{#lst:Glossary\|NTFS}}</blockquote>
	~~The '''~~NTFS~~''' Connection Type is a CMIS Binding that connects Grooper to files and folders in the Windows file system.~~
	</blockquote>
	~~<section end="glossary" />~~
	The connected NTFS folder or folders 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 connected NTFS folder or folders 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.

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

2024-04-17T19:55:35Z

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

← Older revision	Revision as of 14:55, 17 April 2024
(No difference)

Dgreenwood: /* See Also */

2024-04-10T19:46:48Z

Dgreenwood at 14:05, 12 January 2024

2024-01-12T14:05:51Z

← Older revision		Revision as of 09:05, 12 January 2024
Line 12:		Line 12:
	NTFS folders 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.		NTFS folders 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.

	{\|~~cellpadding~~="~~10" cellspacing="5~~"		{\|class="attn-box"
	\|~~-style="background-color:~~#~~f89420~~; ~~color:white"~~		\|
	\|~~style="font-size:14pt\|'''!'''\|\|~~Paths should be specified as UNC paths (ex: \\DomainName\Path\). Grooper does give you the option to search for and use Windows system paths. However, you probably should not. These paths may not be accessible to other processors, users or machines. For example, if you create a repository using a local path to your Documents folder and you export a batch using that NTFS binding to another user on another machine, the batch process is going to look for a repository on their local drive, not yours.		⚠
			\|
			Paths should be specified as UNC paths (ex: \\DomainName\Path\). Grooper does give you the option to search for and use Windows system paths. However, you probably should not. These paths may not be accessible to other processors, users or machines. For example, if you create a repository using a local path to your Documents folder and you export a batch using that NTFS binding to another user on another machine, the batch process is going to look for a repository on their local drive, not yours.
	\|}		\|}

Dgreenwood at 20:59, 8 January 2024

2024-01-08T20:59:18Z

← Older revision		Revision as of 15:59, 8 January 2024
Line 1:		Line 1:
	{{AutoVersion}}		{{AutoVersion}}
	[[File:2023_NTFS_CMIS_Binding_00.png\|frame]]		[[File:2023_NTFS_CMIS_Binding_00.png\|frame]]
			<section begin="glossary" />
	<~~blockquote style~~="~~font-size:14pt~~">The '''NTFS''' Connection Type is a CMIS Binding that connects Grooper to files and folders in the Windows file system.		<blockquote>
			The '''NTFS''' Connection Type is a CMIS Binding that connects Grooper to files and folders in the Windows file system.
	</blockquote>		</blockquote>
			<section end="glossary" />
	The connected NTFS folder or folders 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 connected NTFS folder or folders 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.

← Older revision		Revision as of 10:01, 22 November 2024
Line 92:		Line 92:
	* [[CMIS Export]]		* [[CMIS Export]]
	* [[CMIS Import]]		* [[CMIS Import]]

	~~== Glossary ==~~
	~~<u><big>'''CMIS Connection Type'''</big></u>: {{#lst:Glossary\|CMIS Connection Type}}~~

	~~<u><big>'''CMIS Connection'''</big></u>: {{#lst:Glossary\|CMIS Connection}}~~

	~~<u><big>'''CMIS Export'''</big></u>: {{#lst:Glossary\|CMIS Export}}~~

	~~<u><big>'''CMIS Import'''</big></u>: {{#lst:Glossary\|CMIS Import}}~~

	~~<u><big>'''CMIS Repository'''</big></u>: {{#lst:Glossary\|CMIS Repository}}~~

	~~<u><big>'''CMIS'''</big></u>: {{#lst:Glossary\|CMIS}}~~

	~~<u><big>'''Export'''</big></u>: {{#lst:Glossary\|Export}}~~

	~~<u><big>'''Import Descendants'''</big></u>: {{#lst:Glossary\|Import Descendants}}~~

	~~<u><big>'''Import Query Results'''</big></u>: {{#lst:Glossary\|Import Query Results}}~~

	~~<u><big>'''NTFS'''</big></u>: {{#lst:Glossary\|NTFS}}~~

	~~<u><big>'''Repository'''</big></u>: {{#lst:Glossary\|Repository}}~~

	~~<u><big>'''Service'''</big></u>: {{#lst:Glossary\|Service}}~~

← Older revision		Revision as of 14:46, 10 April 2024
Line 81:		Line 81:
	</tabs>		</tabs>

			== Known Issues & Limitations ==

			=== NTFS CMISQL Query Limitations ===
			<section begin="ntfs_query_limitations" />
			The '''''NTFS''''' connection binding will ''not'' support the <code>CONTAINS()</code> predicate (for full text searching) ''unless'' the Windows file system has been indexed by the Windows Indexing Service.
			<section end="ntfs_query_limitations" />
	== See Also ==		== See Also ==