| Table of Contents |
|---|
Ensure your content is on a filesystem accessible to Fedora 4
...
| Tip |
|---|
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. |
Determine where in your Fedora repository you wish to "mount" the federation
In the easiest configuration a federation may be mounted at the root level of your repository, but if you wish to have a more sophisticated organization, perhaps for the purpose of exposing cascading access controls, it is possible to mount such a federation at an arbitrary path.
| Info |
|---|
Configuring a path within a hierarchy is not currently a well-supported option. That said it can be accomplished as in the following example where we wish to mount a directory to the fedora path "/collection1/masters/files".
|
Update your repository configuration
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).