DO NOT PANIC

A definition: A datamodel describes the content of a collection. A content model describes the content of a data object. So, a data model is a set of content models, that together describe the collection.

The DOMS datamodel describes how the Type system underlying DOMS is realised in Fedora 3. The figure above will serve as a guide through the following sections.

The entire DOMS datamodel is, in its entirety, a complex system. For proper understanding, the various components have been detailed in seperate documents. Firstly, it consist of a number of extension to the Fedora system. Secondly, it consist of a number of predefined objects. These objects make use of the extensions to Fedora. Thirdly, it consist of a number of policies for how certain tasks are achived. And fourthly, it consist of a number of API interfaces.

Fedora and DOMS are big on namespaces. To ease writing the documentation, a namespace document, DomsNameSpaces, have been written. All namespaces should be defined there, and all shorthand refer to the namespaces defined therein.

Fedora extensions

• FedoraOntology - Detailing the Ontology lanquage

• FedoraTypeChecking - Detailing the extensions to the DS-COMPOSITE stream

• FedoraViewBlobs - Detailing the View system, which allows you to view many objects as one

• FedoraObjectTemplates - Detailing the prototype system for content models

• FedoraLicensePolicies - Detailing the License system, and how it interacts with the Search system

• FedoraTransactionsReplacement - Detailing the use of the STATE datastream to allow for some transaction-like processes

Predefined objects

• DomsPredefinedObjects - The predefined content models and other objects in the doms system

Doms policies

• DomsFileHandling - Detailing how we expect to handle file objects in Fedora.

• DomsCollections - Detailing the use of collection objects in DOMS

• DomsAuditTrail - Detailing how DOMS logs changes and new versions

API documentation

• Refer to the overall [Documentation] page