|
Size: 570
Comment:
|
Size: 1993
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 5: | Line 5: |
| == 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 |
|
| Line 6: | Line 24: |
Our DOMS keeps its data in two different kinds of storage: 1. A Fedora repository 1. 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. |
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:
- A Fedora repository
- 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
DOMS objects
Datamodels
Usage of a Fedora repository (separate project)
Usage of the Fedora ECM (seperate package)
Validation
Interfacing with a bitstorage (separate package)
Handling OAI-PMH requests (separate package)
Interfacing to search engines (seperate packages)
Usage of the DOMS GUI (separate package)