Documentation

This page contains documentation produced in the DOMS project.

Design

The top level design documentation will be available here.

• The used modules, and the big lines about how they should be deployed and interact

• High Level Design Documentation

• Design of datamodel views

• User system preliminary design

Packages

Bitstorage

• Low level bitstorage webservice design

ECM

• RELEASE NOTES
• INSTALL GUIDE
• ?

IP-Role Mapper

• Usage

• Configuration

• Installation

Update tracker

DOMSServer

DOMS Server API

DOMSClient

Ingest

DOMS-GUI

OAI-PMH handling

Summa integration

APIs

Note: APIs below here are abandoned.

The DOMS-related API documentation is a work in progress.

• Fedora 3.0 API as used by DOMS

• The LDAP authentication API as used by DOMS

• API for bitstorage as used by DOMS

• API for file characterisation as used by DOMS

• API for getting a PID as used by DOMS

• API for searching, as used by DOMS

• API for requests to the Resource index

• API for getting a new object, cloned from a template

• API for adding information to objects, currently files

Data Model

The data model documentation is a work in progress.

• Data Model

• Data Model for De Danske Aviser in MiniDOMS

• Data Model for TV2 Reklamer in DOMS

• Data Model for the olde MiniDOMS is available at http://merkur/domswiki/MiniDOMSDataModel (Notice, you are now leaving the domswiki, going to the barren wastelands of the old abandoned MiniDOMS merkur-wiki.)

Data Provider

• DOMS as an OAI-PMH repository

GUI Code Docs

• Understanding gained from Mjølner

Fedora 3 Project

• Main document for the Fedora team

Picture video for wowza

• Picture video script

Deployment History

"Runtimes" for parts of deployment

Useful for those tasks that may be done for deploying DOMS with Radio/TV-recordings and metadata for 2005-2010.

Examples of how long runs and batches take: