|
Size: 1994
Comment:
|
← Revision 12 as of 2010-03-17 13:09:04 ⇥
Size: 1984
Comment: converted to 1.6 markup
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| Those trained by the academic tradition of the western like to think in terms of categories and collections. Categories in Fedora is modelled by the Content Models, but there is no system in place for Collections. But Fedora allows for RDF relations between objects, and with that we can easily model collections. | Those trained by the academic tradition of the western world like to think in terms of categories and collections. Categories in Fedora are modelled by the Content Models, but there is no system in place for Collections. But Fedora allows for RDF relations between objects, and with that we can easily model collections. |
| Line 5: | Line 5: |
| There are no inherent semantic meaning attached to collections. They are a way to group objects, pertaining to some criteria. | There is no inherent semantic meaning attached to collections. They are a way to group objects, pertaining to some criteria. |
| Line 7: | Line 7: |
| In the doms-relations namespace (see DomsNameSpaces) we define a reserved relation "isPartOfCollection". All objects must have at least one such relation to at Collection object (ie. an object of ContentModel_Collection). This includes the collection objects themselves, and as such there is a hirachy of collections. | Content Models are also part of collections, preferably the collections containing objects that use them. Template objects are also part of collections. |
| Line 9: | Line 9: |
| At the top, we have defined a special collection object, called "doms:Root_Collection". This collection contains itself, and all the first-level collections in DOMS. First-level collections are those that are directly part of "doms:Root_Collection". First-level collections can contain second-level collections, which for all purposes are identical to first-level collections, except that they are not part of "doms:Root_Collection". Infinite levels of collections are possible, and the level of a collection is simply the number of "doms-relations:isPartOfCollection" relations that must be followed to get to "doms:Root_Collection". | A special collection [[DataModel/DOMS Base Collection| doms:DOMS_Base_Collection]] contains the base objects of the DOMS system, described in DataModel. This collection will always be present. |
| Line 11: | Line 11: |
| Only "doms:Root_Collection" is allowed to contain itself, all other collections must be part of another collection. An object can be part of several collections. A collection could thus be both a second level collection and a third level collection. This is perfectly allowed, and raise no problems. Content Models are also part of collections, preferably the collections containing objects that use them. | |
| Line 13: | Line 12: |
| A special collection "doms:DOMS_Base_Collection" contain the base objects of the DOMS system, described in DataModel. This collection will always be present. | == The Collection Hierarchy == In the doms-relations namespace (see DomsNameSpacesAndSchemas) we define a reserved relation "isPartOfCollection". All objects must have at least one such relation to a Collection object (ie. an object of [[DataModel/ContentModel Collection| doms:ContentModel_Collection]]). This includes the collection objects themselves, and as such there is a hierarchy of collections. At the top, we have defined a special collection object, called [[DataModel/Root Collection| doms:Root_Collection]]. This collection contains itself. Collections can contain other collections, but cycles in the graph is explictly forbidden. The only accepted cycle is the root collection that contain itself. Aside from forbidding cycles, there are no requirements for the structure of the graph. We envisage two ways to use collections 1. As a strict hierarchy, modelled on the organisational structure and the areas of responsibility. Few collections, and objects are not part of many collections. 1. As a way of adding tags (subjects) to the objects. There will be many collection objects, and objects will be part of many collections. |
Collections
Those trained by the academic tradition of the western world like to think in terms of categories and collections. Categories in Fedora are modelled by the Content Models, but there is no system in place for Collections. But Fedora allows for RDF relations between objects, and with that we can easily model collections.
There is no inherent semantic meaning attached to collections. They are a way to group objects, pertaining to some criteria.
Content Models are also part of collections, preferably the collections containing objects that use them. Template objects are also part of collections.
A special collection doms:DOMS_Base_Collection contains the base objects of the DOMS system, described in DataModel. This collection will always be present.
The Collection Hierarchy
In the doms-relations namespace (see DomsNameSpacesAndSchemas) we define a reserved relation "isPartOfCollection". All objects must have at least one such relation to a Collection object (ie. an object of doms:ContentModel_Collection). This includes the collection objects themselves, and as such there is a hierarchy of collections.
At the top, we have defined a special collection object, called doms:Root_Collection. This collection contains itself. Collections can contain other collections, but cycles in the graph is explictly forbidden. The only accepted cycle is the root collection that contain itself.
Aside from forbidding cycles, there are no requirements for the structure of the graph. We envisage two ways to use collections
- As a strict hierarchy, modelled on the organisational structure and the areas of responsibility. Few collections, and objects are not part of many collections.
- As a way of adding tags (subjects) to the objects. There will be many collection objects, and objects will be part of many collections.