Page Comparison

...

File objects are objects of type "doms:ContentModel_File". They must contain a datastream CONTENTS that refers to a binary file by URL. They must also contain a datastream CHARATERISATION that contains characterisation information for the file (the specification for this is still under development). Specialisations of this datamodel should contain specialisations of the allowed mime types for the CONTENT datastream. File objects should describe technical aspects of files, but not bibliographic metadata. This will allow migration of a file without having to update the bibliographic metadata objects.'

Designing a datamodel

To design at datamodel for a collection in DOMS, the following workflow is suggested:

• Identify files in the collection.
• Identify bibliographic objects

...

Draw model

Identify metadata and format for each object

Identify licenses

Identify views

Implementing a datamodel

Create content model objects

Write schemas

Write mime types

Write OWL Lite

Write views

Create license objects

Write XACML

...

• . It may be relevant to think of elements of FRBR and object oriented modelling at this stage.
• Draw the diagram as interconnected boxes for each element.

TODO: Insert example drawing.

• For each line in the diagram, define a name and a direction for the relation. Note that standards may exist for common relations.
• For each box in the diagram, define what datastreams should exist, with what XML schema

TODO: Insert example drawing.

• For each object, identify the license for accessing the object
• Identify whether, and how, some blocks in the diagram should be grouped when disseminating objects.

TODO: Insert example drawing.

Implementing a datamodel

Once the datamodel has been designed, the model can be implemented in DOMS. The following workflow is suggested:

• For each object in the diagram, create a content model object. In that content model object:
  • For each datastream
    • Define the datastream in the DS-COMPOSITE-MODEL datastream of the content model
    • If the datastream is an XML metadata datastream, refer to the XML schema in the DS-COMPOSITE-MODEL
    • If the datastream is an externally referenced binary stream, define the allowed mime types
  • For each outgoing relation
    • Define the relation in the ONTOLOGY datastream if the content model
    • Define the cardinality of the realtion (how many relation may/must be present of this type)
    • Define the content model of the object of this relation (what kinds of objects may we refer to)
• For each identified view
  • In the content models for this view, define the entry objects and the relations that define the angles in the VIEW datastream.
• For each different license for the collection
  • Define a LICENSE object
  • Express the license in XACML in the LICENSE datastream.
• For each object in the diagram
  • Create one or more template objects, containing a prototype of the object
  • Set the right license in that template object in the RELS-EXT datastream and the LICENSE datastream
  • Set the http://doms.statsbiblioteket.dk/relations/default/0/1/#isTemplateFor relation in the RELS-EXT datastream.

TODO: Insert examples