|
Size: 4476
Comment:
|
← Revision 90 as of 2010-03-17 13:13:00 ⇥
Size: 5322
Comment: converted to 1.6 markup
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| = Doms Data Model = | = DON'T PANIC = |
| Line 3: | Line 3: |
| In the following these shorthands will refer to the following namespaces * rdf - http://www.w3.org/1999/02/22-rdf-syntax-ns# * rdfs - http://www.w3.org/2000/01/rdf-schema# * owl - http://www.w3.org/2002/07/owl# * fedora-model - info:fedora/fedora-system:def/model# * doms-relations - http://doms.statsbiblioteket.dk/relations/default/0/1/# * doms - Standard prefix for PIDs. It is not a namespace |
'''A definition: A ''datamodel'' describes the content of a collection. A ''content model'' describes the content of a data object. So, a datamodel is a set of content models, that together describe the collection.''' |
| Line 11: | Line 5: |
| '''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 realized in Fedora 3. 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 extensions 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, DomsNameSpacesAndSchemas, have been written. All namespaces should be defined there, and all shorthands refer to the namespaces defined therein. |
| Line 14: | Line 12: |
[[ImageLink(http://merkur/viewvc/trunk/docs/datamodel/fig/DOMSBaseCollection.png?root=doms&view=co,alt=DOMS base collection,width=256)]] 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. == DOMS Content Models in general == |
== Content Models in general == |
| Line 31: | Line 20: |
| 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. For more detail on this, see FedoraOntology and FedoraTypeChecking | The Content Model object, as used in DOMS, describes the compulsory 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. For more detail on this, see FedoraOntology and FedoraTypeChecking |
| Line 42: | Line 31: |
| == DOMS Base Collection == | |
| Line 44: | Line 32: |
| Doms come shipped with a base collection of objects, representing the base types. The objects in the base collection will be detailed in the following. | == 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 * FedoraImportExport - Detailing use of Import and Export of objects using content models * FedoraLicensePolicies - Detailing the License system, and how it interacts with the Search system * FedoraState - Detailing the use of object states to allow controlling validity, availability and deletions. == 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 |
| Line 47: | Line 53: |
| * [:DataModel/ContentModel_DOMS: doms:ContentModel_DOMS] DONE * [:DataModel/ContentModel_File: doms:ContentModel_File] Almost DONE * [:DataModel/ContentModel_AudioPreservationFile: doms:ContentModel_AudioPreservationFile] DONE * [:DataModel/ContentModel_ImagePreservationFile: doms:ContentModel_ImagePreservationFile] DONE * [:DataModel/ContentModel_VideoPreservationFile: doms:ContentModel_VideoPreservationFile] DONE * [:DataModel/ContentModel_TextPreservationFile: doms:ContentModel_TextPreservationFile] DONE * [:DataModel/ContentModel_Audio: doms:ContentModel_Audio] DONE * [:DataModel/ContentModel_Image: doms:ContentModel_Image] DONE * [:DataModel/ContentModel_Video: doms:ContentModel_Video] DONE * [:DataModel/ContentModel_Text: doms:ContentModel_Text] DONE * [:DataModel/ContentModel_License: doms:ContentModel_License] DONE * [:DataModel/ContentModel_Schema: doms:ContentModel_Schema] DONE * [:DataModel/ContentModel_Collection: doms:ContentModel_Collection] DONE |
|
| Line 61: | Line 54: |
| * [:DataModel/Root_Collection: doms:Root_Collection] * [:DataModel/DOMS_Base_Collection: doms:DOMS_Base_Collection] * [:DataModel/Open_License: doms:Open_License] * [:DataModel/View_Schema: doms:Schema_View] * [:DataModel/Schema_OAIDublinCore: doms:Schema_OAIDublinCore] |
== Working with the Data model == Doms contains a number of content models. These are meant to serve as the basic buildingblocks for data models for new collections. A datamodel is, of course, not restricted to use only these content models, it can, and should, define it's own. All new content models, should extend doms:!ContentModel_DOMS, and all objects that need to reference files outside Fedora should have a content model that derive from doms:!ContentModel_File and so on. The content models that provide extra meaning are optional to use, and should at least be extended for the relevant collection. Most data models are structured around some realworld concept, like a CD, modelled as a digital object. This object will be described by a content model that is totally collection specific, only extending doms:!ContentModel_DOMS. It will probably have relations to digital objects, like tracks. These will be described by a content model that extends doms:!ContentModel_Audio. Each of these will tracks must then reference a audio preservation file object, or some subtype of this. This is the best practice for constructing data models. |
DON'T PANIC
A definition: A datamodel describes the content of a collection. A content model describes the content of a data object. So, a datamodel is a set of content models, that together describe the collection.
The DOMS datamodel describes how the Type system underlying DOMS is realized in Fedora 3.
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 extensions 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, DomsNameSpacesAndSchemas, have been written. All namespaces should be defined there, and all shorthands refer to the namespaces defined therein.
Content Models in general
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 compulsory 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. For more detail on this, see FedoraOntology and FedoraTypeChecking
A data object can specify the Content Model describing its contents, via a fedora-model:hasModel relation, and in DOMS we require it to be present. A data object will be said to "subcribe" to a Content Model. Content Model inheritance, as specified in FedoraOntology, will be used.
The special Content Model object "doms:ContentModel_DOMS" is the root object. All Content Models must have an "doms-relations: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 "fedora-model:hasModel" and all Content Models that can be reached from this, by following "doms-relations:extendsModel" relations.
A Content Model can "extend" more than one other Content Model. There is no overriding of Content Models, a subscribing object must be valid in regards to all the Content Models in the inheritance tree.
Content Models have two datastreams in particular that are interesting. These are the ONTOLOGY and DS-COMPOSITE. The Ontology defines the the allowed relations in subscribing objects, and the DS-COMPOSITE defines the required datastreams and any restrictions they must adhere to.
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
FedoraImportExport - Detailing use of Import and Export of objects using content models
FedoraLicensePolicies - Detailing the License system, and how it interacts with the Search system
FedoraState - Detailing the use of object states to allow controlling validity, availability and deletions.
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
Working with the Data model
Doms contains a number of content models. These are meant to serve as the basic buildingblocks for data models for new collections. A datamodel is, of course, not restricted to use only these content models, it can, and should, define it's own. All new content models, should extend doms:ContentModel_DOMS, and all objects that need to reference files outside Fedora should have a content model that derive from doms:ContentModel_File and so on. The content models that provide extra meaning are optional to use, and should at least be extended for the relevant collection.
Most data models are structured around some realworld concept, like a CD, modelled as a digital object. This object will be described by a content model that is totally collection specific, only extending doms:ContentModel_DOMS. It will probably have relations to digital objects, like tracks. These will be described by a content model that extends doms:ContentModel_Audio. Each of these will tracks must then reference a audio preservation file object, or some subtype of this. This is the best practice for constructing data models.