Fedora objects that are intended for public distribution or migration must be careful to assure portability so that they can be ingested by a foreign repository and expected to work. Currently, the primary concern is with links or other references to resources assumed to exist locally within the fedora server.
On this page:
| Table of Contents |
|---|
Motivation
Links to resources within the fedora web application typically take the form http://HOST:PORT/APP/PATH, where HOST is the host on which Fedora runs, PORT is the port on which the server runs, and APP is the name of the a web application, and PATH is the path, and PATH is the rest of the path.
...
- By default, Fedora will store objects internally in their portable form. It is only on runtime access that the URLs are translated to concrete values. Thus, changing the port or app server context of an already-installed Fedora instance with loaded objects should work fine
- Objects can be exported in portable form from an existing repository only when exported in the "Migrate" context. See Ingest and Export Object Reference for more details.