DOMS Contents Description

This document was imported from: contentsDescription.tex

Author: bam

Object Types

All objects to be ingested in the DOMS must implement the SB type, which is summarised in fig. 1. The PID of an object is 'projectname:objectname', i.e. the left side should be a known project; the right side should be 'project' for a project object and an object name for non-project objects. 'Known' projects should be specified in Fedora properties.

We do not have a final DOMS Dublin Core description (Language? Should format and rights be described in DC as well as in RELS-EXT? We talked about letting the Fedora Dublin Core be a simple 'title-holder' and then introduce an SB Dublin Core datastream. Why was that and should we?); a good suggestion can be found on SB DOMS object structure.

SB_types.png

Figure 1.

All other types of objects are additions to the SB type and are summarised in figures 2, 3, 4, 5, 6, 7, 8 and 9.

We are still missing descriptions of type, rights and technical datastreams. These are necessary to define for the validation iteration

Type_type.png

Figure 2.


Type_rights.png

Figure 3.


Type_non-project.png

Figure 4.


Type_file.png

Figure 5.


Type_image.png

Figure 5.


Type_audio.png

Figure 6.


Type_video.png

Figure 7.


Type_text.png

Figure 8.


http://merkur/viewvc/trunk/docs/legacy/typeHierarchy.png?root=doms&view=co

Figure 9. DOMS object type hierarchy. Original xfig source.


ActionSalvageDataModel/DOMSContentDescription (last edited 2010-03-17 13:12:49 by localhost)