Ensure your content is on a filesystem accessible to Fedora 4
The file system federation connector supports mounting a single root path (and all that's present beneath it). Furthermore, unless you configure it to use an external properties store, it will add additional files to each visited directory with properties for the files (even if in read-only mode).
Make sure that:
- The path to your content and all files beneath it can be read by Fedora
- When using an external properties store, the external directory path exists and can be read by and written to by Fedora
- Otherwise the path to your content files must also be able to be written to by Fedora
On POSIX systems, when the original organization of content is not ideal for your Fedora federation, you may use symbolic links to include just the resources you wish in the structure that's most suitable for your needs. This may help you taylor your federation to include a subset of a larger archival storage or allow you to overcome performance or usability issues associated from an extremely flat hierarchy.