...
Table of Contents
| Table of Contents |
|---|
...
Fedora digital objects can be encoded in several XML formats for ingest and export. Those formats are FOXML 1.1, FOXML 1.0, METS 1.1, METS 1.0, ATOM 1.1, and ATOM ZIP 1.1.
For encoding ingest files in FOXML 1.1, please refer to the FOXML 1.1 XML schema and the Introduction to FOXML guide in the Fedora System Documentation. Also look at the FOXML ingest example file for a model of a typical ingest file using FOXML.
FOXML 1.0 is included for backwards compatibility. This facilitates ingesting any existing objects you may have in FOXML 1.0 format or exporting objects in FOXML 1.0 for ingest into a legacy repository. It is recommended that if you are creating new objects using FOXML, that you use the FOXML 1.1.
For encoding ingest files in METS 1.1, please refer to the METS XML schema (Fedora extension) and also rules for encoding Fedora objects in METS.
For encoding ingest files in ATOM 1.1 or ATOM ZIP 1.1, please refer to Fedora Atom documentation.
...
formats that can be ingested and exported in a variety of ways. This document gives an overview of the formats and methods by which Fedora objects can be ingested and exported.
On this page:
| Table of Contents |
|---|
Fedora Object Formats
Ingest and Export Methods
Via the Fedora Web Administrator
...
The Fedora Web Administrator provides options to ingest and export single objects from the repository using a web-based user interface. The Fedora Web Administrator uses the Fedora REST API to perform all of its functions. Please refer to the Fedora Web Administrator documentation for more information.
...
Via the Fedora Swing Administrator
The Fedora Swing Administrator also provides options to ingest and export objects. It allows multiple objects to be ingested or exported at a time.
Via Command Line
The Fedora installation also includes command line utilities for ingesting and exporting Fedora objects, fedora-ingest and fedora-export, respectively. More information about those can be found in the Client Command-line Utilities
Via Fedora's Web APIs
You can also ingest and export Fedora objects using the SOAP or REST APIs.
...
The Fedora Administrator client provides a graphical user interface for ingesting and exporting from the repository. Behind the scenes, the Administrator uses Fedora API-M, and the appropriate SOAP calls are made to the repository to accomplish the ingest. Objects are ingested as XML files. The Fedora Administrator allows for ingesting single files and file sets, both from the local file system and from other repositories. Please refer to the Fedora Administrator documentation for more information.
Ingest an Object via Command Line
The Fedora Administrator client provides a command line utility for ingesting objects into a Fedora repository. Behind the scenes, Administrator uses Fedora API-M, and the appropriate SOAP calls are made to the repository to accomplish the ingest. Objects are ingested as XML files. Please see the the fedora-ingest utility in the Fedora Command Line Utility Guide.
Export an Object via Command Line
The Fedora Administrator client provides a command line utility for exporting objects from a Fedora repository. Behind the scenes, Administrator uses Fedora API-M, and the appropriate SOAP calls are made the the repository to accomplish the export. Objects are export as XML files. Please see the the fedora-export utility in the Fedora Command Line Utility Guide.
Ingest/Export via Your Own SOAP Client
Of course, you can write your own client to perform ingest and export operations on a Fedora repository. To do this, you must familiarize yourself with the operation syntax as expressed in the WSDL for API-M.
Related Information
...