Date: Thu, 28 Mar 2024 12:13:27 -0400 (EDT) Message-ID: <815922523.28276.1711642407006@lyrasis1-roc-mp1> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_28275_1643081429.1711642407006" ------=_Part_28275_1643081429.1711642407006 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This document describes the demonstration objects that are distr= ibuted with Fedora.
After installing Fedora, you'll find these objects, in several formats, =
in your $FEDORA_HOME/client/demo di=
rectory.
On this page:
These objects can be ingested into the repository in one of two ways.
Once ingested, the demo objects can be viewed in a web browser using API= -A-LITE. For example, to view the demo:5 object:
http://localhost:8080/fedora/objects/demo:5
All demo objects are intended to work when the Fedora repository server = is in a stand-alone condition (e.g., if the repository is running without a= network connection, or if the repository is behind a firewall and not set = up to receive outside connections)
The Fedora data object demo:18 demonstrates the simples= t Fedora digital object scenario. It is the case where we aggregate content= in the Fedora object, and let Fedora's default object behaviors provide ac= cess to the content. This is an example of a Fedora digital object that onl= y has default dissemination services. In this case, there are 3 datastreams= in the object, one for each format of a particular document (in this case = the Fedora paper presented at ECDL2002). We can use the basic Fedora object= dissemination service (also called "datastream disseminations") which are = part of the basic content model shared by all objects. The basic content mo= del is dynamically associated with every object in the repository (though i= t may optionally be statically associated). It has a default service defini= tion (sDep) which provides basic operations for every object which includes= the ability to list items in the object, get an item, get the disseminatio= n index, get the Dublin Core record, and retrieve other information about t= he object. The results of these operations can be returned as either HTML (= method names begin with "view...") or XML (method names begin with "get..."= ). The end result is that the object is simply a container for content and = metadata. The user can view the contents and get any item from the object. = While this scenario may be easy to implement and useful, it does not take a= dvantage of Fedora's extensible service features where custom operations ca= n be associated with an object.
There are two demonstrations of using Fedora to display XML content styl= ed using XSL Formatting Objects. First, the Fedora data object demo= :21 shows the transformation of native formatting object document = stored as an inlined XML datastream into PDF. Second, the Fedora data objec= t demo:26 shows the use of formatting objects to process T= EI documents.
The Fedora data object demo:5 demonstrates the UVA Simp= le Image behaviors by associating a simple dissemination with the object th= rough its content model. There are 4 Datastreams in the object, one for eac= h of four different image resolutions. The object is linked to one dissemin= ation service which provides four behavior methods: getVeryHigh, getHigh, g= etMedium, and getThumbnail. The fulfillment of the service contract entails= the Fedora HTTP Image Getter resolving the URL of the appropriate datastre= am for each of the UVA Simple Image behaviors. There are no transformations= performed on the datastreams. This object shows how a service definition c= an be used to create a normalized set of methods for a particular type of o= bject, an image object in this case, which is defined by a content model. T= he idea here is that the Simple Image service definition provides a standar= d set of dissemination services that can be used on any image object that c= onforms to the standard image content model. As we will see later, differen= t variants of image objects can subscribe to the same service definition, a= nd in some cases the datastreams will be dynamically transformed by a servi= ce to provide the appropriate image disseminations. This demo shows a simpl= e one-to-one mapping of the datastreams in the object to the behavior metho= ds.
The Fedora data object demo:14 demonstrates the Documen= t Transformation behaviors. There are 3 datastreams in the object, one XML = source document, and two XSLT stylesheets. The object's content model provi= des one dissemination service which is associated with the "Document Transf= orm" service definition and the Fedora Local Saxon Service (service deploym= ent). Two services are available: getDocumentStyle1 and getDocumentStyle2. = When these methods are run the repository mediates access to the Fedora Loc= al Saxon Service to produce the appropriate transformation on the XML sourc= e in the object. The dissemination result will be one of two document style= s.
This demo illustrates the use of the Resource Index search service to fu= lfill collection behaviors.
For this demo to work, the = Resource Index must be enabled prior to ingesting these objects.
A series of data objects (demo:SmileyBucket, demo:SmileyKeychain, etc.) = subscribe to the image behaviors defined by the sDef object demo:DualResIma= ge. Each of these image objects also use the RELS-EXT datastream to assert = its membership in the demo:SmileyStuff collection. The demo:SmileyStuff col= lection subscribes to sDef object demo:Collection, which defines two method= s: list and view. The collection object uses the demo:DualResImageCollectio= n sDep to implement those behaviors.
To see the dynamic HTML listing of collection members in action, you can= visit:
http://hostname/fedora/get/demo:SmileyStuff/demo:Collection/view
This dissemination first requests the list of members of the demo:Smiley= Stuff collection using the local risearch service. Then it uses the local saxon service to transform the X= ML results into a human-readable HTML page. The query text and the styleshe= et are both datastreams of the SmileyStuff collection and act as inputs to = the list and view behaviors, respectively.