Differences between revisions 4 and 5
Revision 4 as of 2009-06-23 13:12:06
Size: 1993
Editor: jrg
Comment:
Revision 5 as of 2009-06-23 13:49:14
Size: 2938
Editor: jrg
Comment:
Deletions are marked like this. Additions are marked like this.
Line 8: Line 8:
Program sources for our DOMS are accessible at {{{<TODO: source forge URL>}}}. Program sources for our DOMS are accessible at {{{<TODO: SOURCE FORGE URL>}}}.
Line 33: Line 33:
=== System structure ===
Line 34: Line 35:
Our system is available as several different packages, each containing part of the DOMS, and each part interacting with the others.
Line 35: Line 37:
=== System structure === The packages comprised by the DOMS are the following.
 * Fedora ECM
 * Interface to bitstorage
 * Interface to search engine
 * OAI-PMH handling
 * The DOMS GUI

In addition, the following separate projects are needed:
 * Fedora repository (available at: {{{<TODO: INSERT URL>}}})

Finally, you may need:
 * A bitstorage that the system will use
 * A search engine that the system will interface to

The figure below illustrates how the different modules make use of each other.

{{{<TODO: INSERT FIGURE>}}}
Line 39: Line 58:
The metadata stored by the DOMS is represented as objects inside a Fedora repository.

{{{<TODO: ADD MORE INFO>}}}

Line 41: Line 65:
{{{<TODO: ADD MORE INFO>}}}
Line 43: Line 68:
== Usage of a Fedora repository (separate project) == == Usage of a Fedora repository ==

{{{<TODO: ADD MORE INFO>}}}
Line 46: Line 73:
== Usage of the Fedora ECM (seperate package) == == Usage of the Fedora ECM ==

{{{<TODO: ADD MORE INFO>}}}
Line 51: Line 80:

== Interfacing with a bitstorage (separate package) ==
{{{<TODO: ADD MORE INFO>}}}
Line 55: Line 83:
== Handling OAI-PMH requests (separate package) == == Interfacing with a bitstorage ==

{{{<TODO: ADD MORE INFO>}}}
Line 58: Line 88:
== Interfacing to search engines (seperate packages) == == Handling OAI-PMH requests ==

{{{<TODO: ADD MORE INFO>}}}
Line 61: Line 93:
== Usage of the DOMS GUI (separate package) == == Interfacing to search engines ==

{{{<TODO: ADD MORE INFO>}}}


== Usage of the DOMS GUI ==

{{{<TODO: ADD MORE INFO>}}}
Line 65: Line 104:

{{{<TODO: ADD MORE INFO>}}}

High Level Design Documentation

work in progress

Introduction

A DOMS is a Digital Object Management System. This document describes the open source DOMS developed at the State and University Library in Aarhus, Denmark. Program sources for our DOMS are accessible at <TODO: SOURCE FORGE URL>.

The DOMS aims at fulfilling the following objectives.

  • Stores and handles digital material and metadata, with a view to long-term preservation
  • Supports re-use of components in new collections of material
  • Supports a common index with possibility for relations between objects
  • Is modular with possibility for additions to the system
  • Can be monitored and maintained by non-developers

What is not part of the objectives:

  • Establishing work flow systems and ingest systems
  • Handling authorisation

Overview of a DOMS system

Our DOMS keeps its data in two different kinds of storage:

  1. A Fedora repository
  2. A bitstorage

The Fedora repository keeps metadata, and the bitstorage keeps the actual digital material files. If, for example, we were to store audio CDs in a DOMS, the actual digitized tracks, along with scanned cover art, could be stored as files in the bitstorage. The Fedora then would keep an object (or a cluster of objects) representing the CD, and containing information about for example artist(s), production year and record label, as well as information relating this CD to the digitized material in the bitstorage.

System structure

Our system is available as several different packages, each containing part of the DOMS, and each part interacting with the others.

The packages comprised by the DOMS are the following.

  • Fedora ECM
  • Interface to bitstorage
  • Interface to search engine
  • OAI-PMH handling
  • The DOMS GUI

In addition, the following separate projects are needed:

  • Fedora repository (available at: <TODO: INSERT URL>)

Finally, you may need:

  • A bitstorage that the system will use
  • A search engine that the system will interface to

The figure below illustrates how the different modules make use of each other.

<TODO: INSERT FIGURE>

DOMS objects

The metadata stored by the DOMS is represented as objects inside a Fedora repository.

<TODO: ADD MORE INFO>

Datamodels

<TODO: ADD MORE INFO>

Usage of a Fedora repository

<TODO: ADD MORE INFO>

Usage of the Fedora ECM

<TODO: ADD MORE INFO>

Validation

<TODO: ADD MORE INFO>

Interfacing with a bitstorage

<TODO: ADD MORE INFO>

Handling OAI-PMH requests

<TODO: ADD MORE INFO>

Interfacing to search engines

<TODO: ADD MORE INFO>

Usage of the DOMS GUI

<TODO: ADD MORE INFO>

The included testbed

<TODO: ADD MORE INFO>

HighLevelDesignDocumentation (last edited 2010-03-17 13:09:36 by localhost)