How to add document folders to an index
Open the index properties and go to the Document Folders tab to add folders that contain the files that you want to index.
You can also set up Windows share paths (UNC-based) and Macintosh volume mappings to enable network clients to access the high-resolution files, for instance to open them in third-party applications from FotoStation.
Note: Recent versions of FotoStation and FotoWeb can retrieve the file using the FotoWare Protocol, UNC paths are only used as a fallback mechanism or in network configurations that exclude the possibility to use FWP(S) on port 7000/7001.
Fill in the path to the document folder at the top of the screen in the Document folder area using the regular file path (e.g. C:\Archive\Pictures) or use the Browse button (...) to locate it. Then fill in the Windows Share path and the Macintosh Volume name if access to the high-resolution files is required.
Note: The document folder does not have to be on a local drive - it can also point to a network share.
To add a new document folder, click on the Add new folder link at the bottom of the window.
The Unique name column lets you type in a description of the folder you are adding to make it easier to tell the different folders apart. Once set, it should not be changed, since the permalinks in FotoWeb are based on the index' unique name. (See paragraph on FotoWeb permalinks below.)
What's the Offline folder?
When adding document folders to an index, there's always an Offline folder listed by default, and its location is inside the index folder itself.
This folder is used when a FotoStation client adds an offline resource to an index. FotoStation then copies thumbnails, previews and metadata to the Offline folder, so that these files show up in the index and can be searched for.
How many document folders are supported?
Up to 32 document folders can be added per index. Each of these document folders can contain any number of subfolders, so long as the hierarchy does not produce a path length that exceeds 225 characters, including folder path, file name and extension. In some languages a character is composed of several bytes and this will affect the number of characters a full path can have. If the path becomes too long, Index Manager will not index these files but rather record an error in the log: "Path too long" with a reference to the files that could not be indexed to allow you to correct the issue.
Document folder options
Each time you add or edit a document folder, a number of options become available just below the area where you type in the path information. The options you can choose from are:
Include subfolders: If the document folder contains subfolders with files that you also want to add to the index, you must choose to include subfolders. Index Manager will then scan through and monitor all subfolders within the top level document folder.
Enable background scanning: When you enable background scanning Index Manager will check all file folders for changes at regular intervals. If it finds that the modification date of a folder has changed it will scan the files in that folder and update the changes in the index.
Background scanning increases the network traffic if the document folders are on another server than Index Manager, and is generally intended for non-NTFS file systems and SMB connections that do not support the hotfolder system which automatically notifies Index Manager of file changes.
Scan unchanged folders: This option is related to the background scanning option above. It will force Index Manager to scan the contents of the document folders at regular intervals even if the folder's modification date is not changed. This is typically required when indexing files on certain Unix disk systems where modification of a file in a folder does not change the folder's modification date. Enabling this function will increase the amount of scanning performed and may reduce system performance.
When setting up a FotoWeb system, the asset paths that Index Manager serves to FotoWeb are used to create permalinks to the objects. If a document folder's Unique name changes, so do the permalinks to all objects in that document folder.
In short, changing the unique name of a document folder has the following consequences:
Permalinks to archives, folders and files become invalid
Assets disappear from albums and pins
Exported assets may be lost and cannot be exported again after they expire or are revoked
Comments disappear from assets
Changes that do NOT affect permalinks:
- Changing the physical path or folder name of a document folder (so long as the Unique name is not changed)
- Changing the name of an archive (However, when accessing an existing permalink, the user is redirected to the new archive - a 301 redirect.)
At this point you have created a working index with document folders that will be scanned once you save the configuration and start the service. Click on the Save button in the lower right corner to do so. Each index also has a number of more advanced options associated with it - you can read more about those possibilities in the guide's table of contents.