2. SEASR: @ Work – Fedora Components
• Quick Introduc.on of Fedora
– Repository Server for digital content and metadata
– Digital Objects
– Services and Interfaces Provided
– Applica.on Programmers Interface
• SEASR Fedora Components
• Move Content from Zotero to Fedora using SEASR
web service end‐point running as a data flow.
• Search and Browse Fedora Repository using a
SEASR web based applica.on interface running as
a data‐flow
3. SEASR: @ Work – Fedora Components
• About FedoraCommons :
• Fedora Commons is a non‐profit organiza.on
providing sustainable technologies to create, manage,
publish, share and preserve digital content as a basis
for intellectual, organiza.onal, scien.fic and cultural
heritage by bringing two communi.es together.
• Communi.es of prac.ce that include scholars, ar.sts,
educators, Web innovators, publishers, scien.sts,
librarians, archivists, publishers, records managers,
museum curators or anyone who presents, accesses,
or preserves digital content.
• SoRware developers who work on the cuSng edge of
open source Web and enterprise content technologies
to ensure that collabora.vely created knowledge is
available now and in the future.
• Fedora Commons is the home of the unique Fedora
open source soRware, a robust integrated repository‐
centered plaUorm that enables the storage, access and
management of virtually any kind of digital content.
• Reference; hWp://www.fedora‐commons.org/about
4. SEASR: @ Work – Fedora Components
• Fedora’s Digital Object Model:
Digital Object Iden.fier
Abstrac5on: Persistent ID (PID)
–
The object model is the same whether the object
is data, behavior defini.ons, or behavior
Descrip.ve: key metadata and
mechanism. It also does not maWer what kind of
rela.onships to other objects
data the digital objects is represen.ng—text,
images,maps, audio, video, geospa.al data are all
the same to Fedora.
FOXML Metadata
Flexibility:
–
Object Proper.es
Implementers of Fedora can design their content
models to best represent their data and the
Rela.onship Metadata
presenta.on requirements of their specific use
case.
Item Perspec.ve: sets of content or
Generic:
–
Metadata and content are .ghtly linked within the
metadata items
digital object.
Aggrega5on:
–
Datastream (item)
Fedora objects can refer to data that is stored
locally or that is stored on any web accessible Datastream (item)
server.
Datastream (item)
Extensibility:
–
Fedora’s behavior interfaces are extensible
because services are directly associated with data
Service Perspec.ve: methods for
within a Fedora object. As the services change, the
objects change along with them.
dissemina.ng “views” of content
Default Disseminator
Custom Disseminator
Reference: (pages 6,7, & 9)
Custom Disseminator
hWp://www.fedora‐commons.org/documenta.on/2.2.3/userdocs/tutorials/tutorial1.pdf
5. SEASR: @ Work – Fedora Components
Fedora’s Preserva5on & Archive:
• This diagram shows in very general terms the structure of the
XML: en.re repository. Users interact with the content of the
–
Fedora objects’ XML and the schema upon which repository by means of client applica.ons, web browsers,
they are based are preserved at ingest, during
batch programs, or server applica.ons. These applica.ons
storage, and at export
access the repository’s data by means of the four APIs by which
Content Versioning:
–
Fedora is exposed: management, access, search, which are
Fedora repositories offer implementers the op.on of
versioning data objects. When a data object is exposed via HTTP or SOAP, and the OAI provider API, which is
versioned, the object’s audit trail is updated to exposed via HTTP.
reflect the changes made to the object, when the
change was made and by whom and a new version
of the modified data is added to the object’s XML.
This new datastream cascades from the original and
is numbered to show the rela.onship between
original and version. This allows users to retrieve
older versions of a data object by performing a date/
.me search and retrieval, or the most current
version if the date/.me criteria are not included in
the search.
Object to Object Rela5onships:
–
Rela.onships between objects can be stored via the
metadata included in the objects. This allows
implementers to link together related objects into
parent/child rela.onships.
Event History:
–
Every object in a Fedora repository contains an audit
trail, which preserves a record of every change made
to the object.
Distributed Repositories
•
Dynamic Data Transforma5on
•
Web Services (HTTP/SOAP)
•
Reference: (pages 7,8 & 14)
hWp://www.fedora‐commons.org/documenta.on/2.2.3/userdocs/tutorials/tutorial1.pdf
6. SEASR: @ Work – Fedora Components
Fedora’s “Bigger Picture”
Where could SEASR fit into the bigger picture?
Reference: (page 15)
hWp://www.fedora‐commons.org/documenta.on/2.2.3/userdocs/tutorials/tutorial1.pdf
8. SEASR: @ Work – Fedora Components
• Two Examples uses:
– Upload web service end‐point for Fedora from
Zotero running as persistent data flows.
– Search & Browse simple example that provides
web pages that act as a user‐interface for
exploring a Fedora repository.
15. SEASR: @ Work – Fedora Components
• Two Examples uses:
– Upload web service end‐point for Fedora from
Zotero running as persistent data flows.
– Search & Browse simple example that provides
web pages that act as a user‐interface for
exploring a Fedora repository.
16. SEASR: @ Work – Fedora Components
Building a Web –based Applica5on :
Capture Input from a Client Request that are evaluated and
cause a Response to be computed, generated, & delivered back
to the client
Response Object
Request Response
Processing
Cycle
Processing
Cycle
Processing
Cycle
