Page History

...

Audience: This tutorial is intended for repository administrators or content developers who will be using the Fedora software.

Table of Contents  
1 What is this document and who should read it?
2 What is Fedora and what does it do?
3 Why should you use Fedora?
4 How should you read this document?
5 Conventions used in this document
6 Getting Started: Using Fedora for Aggregating Content
6.1 Some basic definitions
6.2 Example 1: Making a document available in multiple formats
6.3 Example 2: Creating a surrogate for distributed content
7 Using Fedora to produce dynamic content
7.1 Example 3: Using SDefs, SDeps and CModels
7.1.1 Ingesting pre-defined SDef, SDep and CModel objects
7.1.2 Creating a digital object with appropriate datastreams
7.1.3 Linking the digital object to the Content Model
7.2 Example 4 - Modifying Example 3 using a redirect datastream
8 What's next?

 
Figures

Figure 1 - Fedora repository as mediator for services and content
Figure 2 - Fedora Administrator Login Screen
Figure 3 - New object dialog
Figure 4 - Configuring an object
Figure 5 - Datastream display
Figure 6 - Adding a new managed content datastream
Figure 7 - Complete datastreams for example 1
Figure 8 - Example 1 digital object and datastreams
Figure 9 - Adding a datastream with type Redirect
Figure 10 - Example 2 datastream display
Figure 11 - Example digital object and redirected datastream
Figure 12 - Abstract View: Key Fedora Components for Producing Disseminations of Content
Figure 13 - Relationships between Data objects and CModel/SDef/SDep objects for CMA
Figure 14 - Dynamic dissemination access
Figure 15 - Example 3 Linking a Digital Object to a Content Model
Figure 16 - Example 3 dissemination via CMA
Figure 17 - Dissemination with redirect datastream

...

{center}
!worddava87ec66bf28c396bfd9dcd6fac7dd9dd.png|height=228428,width=289489!
*Figure 2 - Fedora Administrator Login Screen*
{center}

...

This section describes how to create digital objects in Fedora that aggregate data from multiple sources. The examples demonstrate how to do this with both local data and data from networked sources. This section provides the foundation for the next section, which describes how to use Fedora to create dynamic content by exploiting web services. Make sure you understand the basic concepts here, before moving on to that next section

*Some

...

Basic Definitions

To understand content aggregation in Fedora, you need to be comfortable with two terms: 1.

1. Digital Object

...

1. — This is the basic unit for information aggregation in Fedora. At a minimum a digital object has:

   ...

   1. 1. An identifier or PID (Persistent Identifier).

   ...

   1. 1. The PID provides the key by which the digital object is accessed from the repository.

   ...

   1. 1. Dublin Core metadata that provides a basic description of the digital object.

   ...

   1. Datastream

   ...

   1. — A component of a digital object that represents a data source. A digital object may have just the basic Dublin Core

   ...

   1. Datastream, or any number of additional

   ...

   1. Datastreams. Each

   ...

   1. Datastream can be any

   ...

   1. MIME-typed data or metadata, and can either be content managed locally in the Fedora repository or by some external data source (and referenced by a URL). When you create a new

   ...

   1. Datastream in a digital object, you assign it to one of four types, or control groups, depending on the nature of the data that it represents.

      ...

      1. 1. Managed Content (M): Datastream content is stored and managed within the Fedora repository's persistent storage. The content can be any MIME type including XML.

      ...

      1. 1. Inline XML (X): A special case of M, restricted to well-formed XML. In this case, the

      ...

      1. 1. Datastream content is stored as part of the XML structure of the digital object itself and is thus included when the digital object is exported (e.g., for archival purposes).

      ...

      1. 1. Externally Referenced (E): Datastream content is external to the Fedora repository and is referenced by a URL that is recorded within the digital object. The content can be any MIME type including XML.

      ...

      1. 1. Redirected Content (R): Like E, but

      ...

      1. 1. Datastream content is delivered to the client without any mediation by Fedora; i.e., via an HTTP redirect. You should use this

      ...

      1. 1. Datastream type when the external content is a web page with relative links or it is streaming audio or video. The content can be any MIME type including XML.

      Decisions about what to include in a digital object and how to configure its datastreams Datastreams are basic modeling choices as you develop your repository. The examples in this tutorial demonstrate some common models that you may find useful as you develop your application.

      Example 1: Making a

      ...

      Document Available in Multiple Formats

      It is often useful to provide access to a digital document in several formats. For example an ePrints server might provide html for those who wish to render the document in a browser, pdf for those who wish to view the document with author-determined formatting, and TeX for those who wish to access and use the document source. This example demonstrates how to construct a digital object where each datastream corresponds to an available format. More advanced techniques, demonstrated later in this tutorial, make it possible to achieve the same results by generating formats dynamically from a single base format. But for now, we'll stick to simple static aggregation.
      Start by selecting File/New/Data Object in the Admin GUI. Complete the New Object dialog box as shown in Figure 3.
      
      
      Figure 3 - New object dialog
      Check the box for Use Custom PID and enter demo:100. Note that when you do not assign your own PID, the Fedora repository will create one for you. Select the Create button and you should see a window like that in Figure 4. Observe that the PID of the created object (in this case demo:100) is displayed in the title bar.
      
      
      Figure 4 - Configuring an object
      
      
      Since our task here is to define the datastreams in the object, click on the Datastreams tab and you will see a window like that in Figure 5. Note that at this point there is only one datastream in the object - the DC datastream for basic descriptive metadata that was automatically created by Fedora. You can select that datastream and select the Edit button to see the default contents of this Datastream, with the DC title and identifier fields already filled in.
      
      
      Figure 5 - Datastream display
      
      A few points to note about what you have done so far:

      ...