TableOfContents

ImageLink(http://merkur/viewvc/trunk/docs/datamodel/fig/DOMSBaseCollection.png?root=doms&view=co,alt=DOMS base collection,width=1024)

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.

1. DOMS Content Models

Fedora provides a repository for digital objects. All objects in the repository can, in principle, be unique, but Fedora provides a way of specifying that an object has a given type. Unfortunately, the type-definitions in Fedora, called Content Models, are rather simplistic by default. We use them as the basis of our type system, with certain enhancements.

For our purposes, there are two kinds of digital objects in Fedora

• Data objects
• Content Model objects

The Content Model object, as used in DOMS, describes the compulsary and legal content of an object of this type. It contains the information nessesary to verify if the given object is indeed of this type.

A data object can specify the Content Model describing its contents, via a fedora-model:hasModel relation. It can only have one such relation, and in DOMS we require it to be present. A data object will be said to "suscribe" to a Content Model.

1.1. Inheritance

A type system that does not allow for inheritance, will have limited use. In spite of this, the Fedora Content Models do not provide this functionality. We have built our own inheritance system for Content Models to compensate for this lack.

The special Content Model object "ContentModel_DOMS" is the root object. All Content Models must have an "extendsModel" relation to this object, possibly through a number of other Content Models. The complete description of a data object is defined as the set of the descriptions in the Content Model specified with "hasModel" and all Content Models that can be reached from this, by following "extendsModel" relations.

A Content Model can "extend" more than one other Content Model. When determining the inheritance tree, and which Content Models that override each others, questions can arise. From the starting Content Model, perform a Breadth-first search of the inheritance tree. The requirements from the content models should be combined, and if conflicts arise, the content model visited first has precedence.

1.2. Using a Content Model

A content model contain a plethora of information in many separate datastreams. To properly interface with the DOMS system, one must know how to interpret this information.

The important datastreams are detailed in the following sections

1.2.1. DS-COMPOSITE-MODEL

Fedoracontrolled structural datastream. Lists the required datastreams in the suscribing data objects and the MIME-type, which will almost always be text/xml

Example of the contents of a DS-COMPOSITE-MODEL datastream can be seen below

                <dsCompositeModel
                        xmlns="info:fedora/fedora-system:def/dsCompositeModel#">
                    <dsTypeModel ID="DC">
                        <form MIME="text/xml"/>
                    </dsTypeModel>
                    <dsTypeModel ID="RELS-EXT">
                        <form MIME="application/rdf+xml"/>
                    </dsTypeModel>
                    <dsTypeModel ID="POLICY">
                        <form MIME="text/xml"/>
                    </dsTypeModel>
                    <dsTypeModel ID="AUDIT">
                        <form MIME="text/xml"/>
                    </dsTypeModel>
                </dsCompositeModel>

1.2.1.1. Inheritance rules

As this datastream is fedora-controlled, it does not respect our inheritance system. Therefore, it only mentions the datastreams that this particular content model requires to be present. When walking the inheritance tree, concatenate the lists and remove duplicates. In case of different MIME-types, the first visited content model has precedence.

1.2.2. SCHEMABINDINGS

DS-COMPOSITE-MODEL lists the required datastreams, but make no statements about their contents. SCHEMABINDINGS does, albeit indirectly. For each required datastream in a suscribing object, it gives the name of a datastream in this Content Model containing a sort of schema for the contents. By "sort of schema", there is meant something that can be used both for validation of the contents and provides enough information to construct some human understandable interface to the contents.

At the moment there are two such schema lanquages, [http://en.wikipedia.org/wiki/XML_Schema_(W3C) "xsd"] and [http://en.wikipedia.org/wiki/Web_Ontology_Language "owl"] lite. Owl lite is only ever used to express requirements about the RELS-EXT datastream. All other datastreams must be describable by xsd schemas.

1.2.2.1. RELS-EXT Schema

As mentioned, owl lite is used to describe the RELS-EXT datastream. An example of how such a description could look can be seen below, taken from ContentModel_Text

                <rdf:RDF
                        xmlns:owl="http://www.w3.org/2002/07/owl#"
                        xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
                        xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
                        xmlns:doms="http://developer.statsbiblioteket.dk/DOMS/relations/default/0/1/#"
                        xmlns:fedora-model="Unknown">

                    <owl:Class rdf:ID="doms:ContentModel_Text">
                        <rdfs:subClassOf>
                            <owl:Restriction>
                                <owl:MinCardinality rdf:datatype="xsd:nonNegativeInteger">1</owl:MinCardinality>
                                <owl:onProperty rdf:resource="doms:hasPreservationFile"/>
                            </owl:Restriction>
                        </rdfs:subClassOf>
                    </owl:Class>

                    <owl:ObjectProperty rdf:ID="doms:hasPreservationFile">
                        <rdfs:domain rdf:resource="doms:ContentModel_Text"/>
                        <rdfs:range rdf:resource="doms:ContentModel_TextPreservationFile"/>
                    </owl:ObjectProperty>

                </rdf:RDF>

The way to interprete this is as follows; The ObjectProperty block define a relation. It's name is "doms:hasPreservationFile". It must have as the origin an object with the contentmodel doms:ContentModel_Text, and point to an object with the contentmodel doms:ContentModel_TextPreservationFile. The owl:Class block define that objects subscribing to doms:ContentModel_Text must have 1 or more of these relations.

This is the extend to which we use owl, and the schemas for RELS-EXT will allways be interpreted this way.

1.2.2.2. Schema Objects

Many of the schemas used in DOMS need to be referenced many times. To avoid duplication, we have made objects containing only schemas, suscribing to the Content Model ContentModel_Schema. The describing datastream in a schemabinding might contain the schema directly, or it might contain the URL to the datastream that does. Either way, it should be invisible to programs accessing the datastream through the API.

1.2.2.3. Inheritance rules

When climbing the inheritance tree, the first time a SCHEMABINDING datastream encounted has precedence. The following content models can only define schemas for datastreams not mentioned by this content model.

A SCHEMABINDING datastream is intrinsically linked with the content model object in which it is defined. So, the schema datastreams linked in the SCHEMABINDINGS datastream, should be found in the same content model as the datastream itself. These do not inherit or override, and the names are only local to the content model itself.

1.2.3. VIEW

A view is a way of combining objects in the DOMS into a domain-relevant group. It is a way of seeing a number of objects as related - as a whole; information that can be useful for the GUI-generator when generating GUI-windows.

Those views that we imagine as being suitable for a screen or window in the GUI, are called main views. Each main view contains an object that the main view is centered around. We call this the main object, and the ID of this view is the ID of the main object. Views of other objects are simply called views. The main object is the object that represents the main view - other objects in that view are related to the main object and would presumably be relevant to edit in the GUI at the same time. For a CD modelled in DOMS, for example, a CD object would be the main object, and objects for tracks, cover, lyrics and so on would constitute the rest of the main view.

We imagine that results appearing in searches in the GUI will all be main views. In fact every view that will be the basis for a screen/window will be a main view.

A view for an object O is represented by a Datastream VIEW on the Content Model object for O. This Datastream also mark the object as Main, if this is the case. Please note that the view is defined on Content Model level, so the same rules are used to generate the view for all objects using that Content Model. When creating totally new objects in the GUI, they should subscribe to main view content models from the current collection.

The datastream will just contain a list of relation names and reverse relation names. Following these relations will give you the view.

Definitions:

• 1-step relations (relations on a content model c of the form "x rel y", meaning that if an object x with content model c has relation rel to another object y, then y will be part the view too. Examples of rel for a CD modelled in DOMS could be hasTrack, hasLyrics,..)

• reverse relations (relations of the type "y rel x" on a content model c, where x has model c and y therefore will be included in the view for x)

In addition, we suggest to augment the 1-step approach with the idea of "includes". What this means is that when object O has a view defined by following relations from O once, and an object P is in the view of O, then the view of P will be included in the view of O.

View datastream contain xml of the form

<?xml version="1.0" encoding="UTF-8"?>
<view:views  xmlns:view="http://doms.statsbiblioteket.dk/types/views/0/1/#">
  <view:view name="GUI" mainobject="true">
    <view:relations>
      <doms:hasFile xmlns:doms="http://doms.statsbiblioteket.dk/relations/default/0/1/#"/>
    </view:relations>
    <view:inverse-relations>
      <doms:isPartOfCollection xmlns:doms="http://doms.statsbiblioteket.dk/relations/default/0/1/#"/>
    </view:inverse-relations>
    <view:datastreams>
      <view:datastream>DC</view:datastream>
    </view:datastreams>
  </view:view>
</view:views>

As can be seen, it describes all relations to be followed outwards, both directly and reverse. When including the object, only the named datastreams from the datastreams tag should be used. There can be several views, with different views in an object. The GUI should use the view with the name "GUI".

1.2.3.1. Inheritance rules

Views are inherited when Content Models extends each other. Keep three seperate lists, one for datastreams, one for relations and one for inverse relations. Just concatenate the entries from all parent content models to these lists, and remove duplicates. Then use these three lists to generate the list of objects in the view.

1.3. Predefined Content Models

Shorthand:

• myObject.myDatastream means the Datastream myDatastream in the Object myObject.
• $variable introduces a variable.

1.3.1. ContentModel_DOMS

ContentModel_DOMS is the root of the content model inheritance tree. All content models derive from this model. As all objects in DOMS must have a content model, all objects must adhere to the restrictions defined in this content model.

The following variables are used:

• $Title: A human readable title
• $PID: A generated PID for this object

• $ContentModel: The content model for this object, must derive from ContentModel_DOMS

• $Collection: The collection that this object belongs to. An object with a Content Model that derives from ContentModel_Collection

• $LicenseObject: The License object that govern access to this object. An object with a Content Model that derives from ContentModel_License

Requirements for objects described by ContentModel_DOMS

• Datastreams

  • DC: Fedora required datastream with the [http://dublincore.org/schemas/xmls/qdc/dc.xsd Dublin Core schema].

    • dc:title = $Title
  • RELS-EXT: Fedora controlled relations between objects.
    • oai:itemID = $PID
      • (only required on harvested objects)

    • fedora-model:hasModel -> $ContentModel

    • doms:hasLicense -> $LicenseObject

    • doms:isPartOfCollection -> $Collection

  • AUDIT: Fedoracontrolled audit trail
  • STATE: The state of the object, (Values = draft | intermediate | published)
  • POLICY Fedoracontrolled datastream describing the rights and restrictions on this object

    • ContentLocation URL = $LicenseObject.LICENCE

1.3.2. ContentModel_File

Extends ContentModel_DOMS

In DOMS, we have found it beneficial to separate the abstract concept of "Image" or "Audio" from the concrete implementations such as "jpeg" and "mp3". The metadata about the image will be relevant no matter the manifestation of the image, and as such should not reside along with the technical metadata about the manifestation. To support this separation, we have introduced the concept of File objects.

A File object is an object, that contain a link to the file (in Bitstorage), and the technical metadata about this file. Only File objects are allowed to reference a file in Bitstorage. File objects must all have a Content Model that extends ContentModel_File.

The following variables are used:

• $OrigFile: An object with the Content Model that derives from ContentModel_File;

Requirements for objects described by ContentModel_File

• ObjectProperties

  • External Properties

    • http://doms.statsbiblioteket.dk/extproperties/#pronomID : The pronom ID of the file

• Datastreams
  • RELS-EXT

    • (optional) doms:hasOriginal -> $OrigFile

  • CHARACTERISATION: The output of the characterisation tools. Schema attachment:Characterisation.xsd
  • CONTENTS: Datastream containing the file

    • ContentLocation URL = The file in Bitstorage

  • ORIGIN: Metadata about the creation of the file, in the Premis [http://www.loc.gov/standards/premis/v1/Event-v1-1.xsd schema]

The characterisation datastream could look like this.

<?xml version="1.0" encoding="UTF-8"?>
<char:characterisation xsi:schemaLocation="http://doms.statsbiblioteket.dk/types/characterisation/0/1/# http://developer.statsbiblioteket.dk/DOMS/types/characterisation/0/1/characterisation/characterisation-0-1.xsd"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:char="http://developer.statsbiblioteket.dk/DOMS/types/characterisation/0/1/#"
  xmlns:jhove="">
  <char:characterisationRun>
    <char:tool>JHove</char:tool>
    <char:output>
      <jhove:...>
      </jhove:...>
    </char:output>
  </char:characterisationRun>
</char:characterisation>

1.3.3. ContentModel_ImagePreservationFile

Extends ContentModel_File

Requirements for objects described by ContentModel_ImagePreservationFile

• Datastreams
  • PRONOMID: must be "fmt/10" (tiff version 6)

1.3.4. ContentModel_TextPreservationFile

Extends ContentModel_File

Requirements for objects described by ContentModel_TextPreservationFile

• Datastreams
  • PRONOMID: must be "x-fmt/16" (Utf8) or "fmt/95" (pdf-a)

1.3.5. ContentModel_VideoPreservationFile

Extends ContentModel_File

Requirements for objects described by ContentModel_VideoPreservationFile

• Datastreams
  • PRONOMID: must be "x-fmt/385" (mpeg1) or "x-fmt/386" (mpeg2)

1.3.6. ContentModel_AudioPreservationFile

Extends ContentModel_File

Requirements for objects described by ContentModel_AudioPreservationFile

• Datastreams
  • PRONOMID: must be "fmt/2" (Bwf version 1) or "fmt/6" (wav)

1.3.7. ContentModel_Image

Extends ContentModel_DOMS

The following variables are used:

• $ImageFile: An object with the Content Model ContentModel_ImagePreservationFile

Requirements for objects described by ContentModel_Image

• Datastreams
  • RELS-EXT

    • doms:hasPreservationFile -> $ImageFile

1.3.8. ContentModel_Audio

Extends ContentModel_DOMS

The following variables are used:

• $AudioFile: An object with the Content Model ContentModel_AudioPreservationFile;

Requirements for objects described by ContentModel_Audio

• Datastreams
  • RELS-EXT:

    • doms:hasPreservationFile -> $AudioFile

1.3.9. ContentModel_Video

Extends ContentModel_DOMS

The following variables are used:

• $VideoFile: An object with the Content Model ContentModel_VideoPreservationFile;

Requirements for objects described by ContentModel_Video

• Datastreams
  • RELS-EXT:

    • doms:hasPreservationFile -> $VideoFile

1.3.10. ContentModel_Text

Extends ContentModel_DOMS

The following variables are used:

• $TextFile: An object with the Content Model ContentModel_TextPreservationFile;

Requirements for objects described by ContentModel_Text

• Datastreams
  • RELS-EXT:

    • doms:hasPreservationFile -> $TextFile

1.3.11. ContentModel_License

Extends ContentModel_DOMS

Requirements for objects described by ContentModel_License

• Datastreams

  • LICENCE: XACML describing the license. [http://www.oasis-open.org/committees/download.php/915/cs-xacml-schema-policy-01.xsd Schema]

  • DC: The DC datastream (probably the description field) is used to describe the human readable version of the license

1.3.12. ContentModel_Schema

Extends ContentModel_DOMS

Requirements for objects described by ContentModel_Schema

• Datastreams
  • SCHEMA: The xsd schema inlined.

1.3.13. ContentModel_Collection

Extends ContentModel_DOMS

Requirements for objects described by ContentModel_Collection: None

2. Collections

The DOMS system will be a system that models several collections of digital objects. Each object belongs to one or more collections. This is represented by having one or more "isPartOfCollection" relations to the parent collections. This goes for a collection object as well - it belongs to another collection. One collection has special status though: the "doms:Root_Collection" does not belong to any other collection, and is thus the bottom element for the "isPartOfCollection" relation. Every other collection has a "isPartOfCollection" relation to "doms:Root_Collection".

In addition, DOMS contains another special collection - the "doms:DOMS_Base_Collection". This collection provides objects such as content models and licenses that are utilized by (and mandatory for) the other collections in the DOMS. This collection is meant to be ingested as the first collection in the DOMS.

2.1. Technical Metadata

A file object should contain technical metadata. In this context it refers

• A datastream with the output of the characterisation tools used on this file upon ingest, called CHARACTERISATION
• A datastream with the metadata about the origins of the file, called Origin

In addition, it must have a relation "hasOriginal" if it was migrated from another file that exists in DOMS.

3. Licenses

Licenses, in DOMS, have, as their only purpose, to restrict who can view what material. They are only a concern for people using the material in DOMS, not users working with the GUI, or otherwise administrating the contents.

Licenses are implemented by using the Fedora XACML engine. When a user authenticates with the Fedora server (or with a server passing authentication tokens to the DOMS), he gets a number of attributes. Each of these attributes name one license that the user can access material under.

Each data object in DOMS has a POLICY datastream. This datastream is just an URL, referring to a License object's LICENCE datastream. This datastream is an XACML stream, that evaluates if the user posses the attribute that specify that the user can use this License. If yes, the user is granted access to the original object, otherwise he is denied.

4. Audit Trail

Each user that will use the GUI will need to login. They will authenticate with some external server, probably the SB LDAP server. The access control is not really a concern for the DOMS system. As such, all GUI users will have equal and full access to the DOMS repository.

Audit trails, however, are a concern. Each change to a datastream in a data object will, per default Fedora behaivour, create a new version of this datastream, marked with the creation time and the username. For this reason the Fedora operations PurgeObject and PurgeDatastream are blocked, as they destroy the audit trail. Real deletion of information is not possible, but both objects and datastreams can be marked as "deleted", again per standard Fedora behaviour. Any tools working with or on DOMS should respect this flag. The GUI should only concern itself with the most recent version of a datastream.

= Working with the Datamodel or How to work without transactions=

The STATE datastream, present in all data objects are the key. To emulate a transaction, follow these steps:

1. Ingest any new objects, with STATE=draft
2. change the STATE of all involved objects with STATE=published to STATE=intermediate
3. Perform all changes that must be performed
4. Change the objects back to STATE=published. This will provoke a validation of the objects by the DOMS system. If the objects failed the validation, the STATE will not change

DOMS only try to enforce a structure on objects with STATE=published. By marking objects as intermediate, the system will disregard them, without losing the relations to them.