File Store (Object): Difference between revisions
m Randallkinard moved page File Store to File Store (Object): new naming convention |
No edit summary |
||
| Line 1: | Line 1: | ||
{{stubs}} | {{stubs}} | ||
<blockquote> | <blockquote>{{#lst:Glossary|File Store}}</blockquote> | ||
</blockquote> | |||
If you select an object in the Node Tree, then go to the "Advanced" tab, then go to the "Files" tab underneath each file listed is stored in a '''File Store'''. | If you select an object in the Node Tree, then go to the "Advanced" tab, then go to the "Files" tab underneath each file listed is stored in a '''File Store'''. | ||
Revision as of 08:42, 29 April 2024
|
STUB |
This article is a stub. It contains minimal information on the topic and should be expanded. |
hard_drive File Store objects define a storage location within Grooper where file content associated with nodes are saved. They are crucial for managing the content that forms the basis of the Grooper's processing tasks, allowing for the storage and retrieval of documents, images, and other "files". Not every object in Grooper will have files connected to it, but if it does, those files are stored in the location defined by this object.
If you select an object in the Node Tree, then go to the "Advanced" tab, then go to the "Files" tab underneath each file listed is stored in a File Store.
File Stores can be any folder you have writable access to, but it is best practice to use a fully qualified UNC path.
Active File Store
New files, such as scanned or imported images of Batch Pages, are always written to the "Active File Store". This is a property set on the Grooper Root in the Node Tree. It will default to the File Store created when the Grooper Repository was initialized, unless otherwise specified.