Skip to end of metadata
Go to start of metadata
This is the home of the technical descriptions of the modules making up the DOMS

The descriptions currently covers.

Authentication ~ (Asger)
Brodcast Extraction Service (BES) ~ (Colin, semi DOMS)
DOMS Central ~ (Asger)
DOMS Client ~ (Asger, Thomas)
Doms ECM Ontology
DOMS Surveillance ~ (Kåre)
Doms Views and Update Tracking
Enhanced Content Models (ECM) * (Asger)

Enhanced Content Models is a framework for describing content models in a machine readable way. This enables services to validate objects in Fedora, and to have services understand data models and act on them. For instance, the GUI provided with DOMS automatically generates a user interface for editing metadata for any data model defined in DOMS.

GUI ~ (Esben & Asger)

A module providing a Graphical user interface that will enable the user to change create modify and delete metadata.

Ingester ~ (Thomas)
Migrated Documentation
PID Generator
SUMMA Storage API Implementations for DOMS * (Thomas)

The SUMMA Storage API Implementation (SSAI) is a piece shim code that enables the two systems to communicate.

VHS Ingest Monitor

For which there is a full and complete description on those sites not marked.

Sites marked "~" are incomplete and those marked "*" are complete but not yet approved by the module owner.

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 http://sourceforge.net/projects/doms.

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
  • Handles metadata for access rights, and integrates with certain authentication systems

What is ''not'' part of the objectives:

  • Establishing work flow systems and data-specific ingest systems

A brief technical overview of the individual parts of can be found as children to this document.

Overview of a DOMS system

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 a metadata object (or a cluster of metadata 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 that form the DOMS are the following:

1. The DOMS server interface
1. DOMS Front end Services:

  • DOMS Ingest System
  • Interface to the Summa search engine
  • OAI-PMH
  • The DOMS GUI
    1. The DOMS backend:
  • Fedora ECM (Enhanced Content Models)
  • Interface to bitstorage
  • An update tracker

In addition, the following separate projects are needed:

Finally, you may need:

Insert the completed DOMS_diagram when it is finished.

DOMS objects

The metadata stored by the DOMS is represented as objects inside a Fedora repository.
Each metadata object in the repository contains the following:

  • A PID (persistent identifier of the object)
  • Metadata as XML
  • Relations to other objects (optional)

In addition to objects containing ''descriptive metadata'' (metadata like artist in the CD example above), there are objects that we call ''file objects''. All relations to data in a bitstorage come from file objects, and these objects instead of descriptive metadata contain ''technical metadata'' about the files they point to (things like sample rate, for sound files).

In addition to the objects that contain metadata, i.e. which represent the content of the DOMS, there are a number of special objects in a DOMS. These special objects are:

  • ''Content model'' objects, each acting as a type or class for other objects
  • Basic ''collection'' objects, all objects belong to a collection
  • ''License'' objects, every content model relates to a license
  • ''Template'' objects, that are templates for generating new objects in the repository

A DOMS comes preloaded with some special objects, defined in the ''base collection''. These base objects are meant as a base for defining your own data models (see below) for specific collections.

The figure below shows the objects in the base collection, and their relations.

attachment:DOMSBaseCollection.png

Content models are related in a hierarchy with ContentModel_DOMS at the top. Similarly, collections are related by the ''isPartOfCollection'' relation, and at the top of this hierarchy is Root_Collection.

The file objects mentioned earlier have the content models (via relation ''hasModel'') that extend ContentModel_File. That is, each has a content model for either image, text, audio, or video. Finally, ContentModel_License is the content model of all licenses, and we include Open_License, which is the license of all content models in the base collection.

Data Models

For each collection that is to be stored in DOMS, a ''data model'' must be defined.

A datamodel is a description of the formats of data and metadata, and how this data is organised in Fedora objects. In practice, this is done by formal descriptions of content models, defined by Enhanced Content Models. Having a formally described model allows us to validate our data, and to use data model aware software that integrates with our repository.

The DOMS data model, as described above, defines some structure that '''must''' be true for each collection. This includes relations to one or more collections, a license for each object, and the requirements for separate file objects containing technical metadata for each file we store in Fedora.

We also assume Dublin Core as one minimal metadata format for each object.

However, the model is flexible, and a data model for a specific collection ''may'' define additional metadataformats and relations that describe the formats and structure for that particular collection.

Summa Integration

The JSON-api is used. Documentation can be found here:

http://summa.svn.sourceforge.net/viewvc/summa/trunk/Core/src/main/java/dk/statsbiblioteket/summa/search/api/document/DocumentKeys.java?revision=HEAD&view=markup

 

Format names in broadcast metadata

  • mpeg1

  • mpeg2

  • asf

  • wav

  • mp4

  • mpegts-singlechannel-audio

  • mpegts-singlechannel-video

  • mpegts-multichannel-video

 

 

  • No labels