...
The file system federation connector supports mounting a single root path (and all thatwhat'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).
...
- 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 Fedorais Fedora-readable and Fedora-writeable
- Otherwise, Otherwise the path to your content files must also be able to be written to by Fedora
| Tip |
|---|
On POSIX systems, when if the original organization of content is not ideal for your Fedora federation, you may use symbolic links to include just the resources you wish to be included in the structure that's most suitable for (as defined by your needs). This may help you tailor your federation to include a subset of a larger archival storage or allow you to overcome performance or usability issues associated from with an extremely flat hierarchy. |
Determine where in your Fedora repository you wish to "mount" the federation
In It is the easiest, configuration-wise, to mount a federation may be mounted at the root level of your repository, but if you wish to have . But if you need a more sophisticated organization, perhaps for the purpose of exposing to expose cascading access controls, it is possible to mount such mounting a federation at an arbitrary path is possible.
| Info |
|---|
Configuring a path within a hierarchy is not currently a well-supported option. That said, it can be accomplished, as it's demonstrated in the following example where we . We wish to mount a directory to the fedora Fedora path "/collection1/masters/files".:
|
...
Changes to your repository configuration (repository.json) require a restart to take effect. Configuration options are detailed here, but in general you'll need to add an element for your new file system federation that points to the directory path that contains your federated files (and possibly a path for your external properties).