Fenix functional content architecture

From Giews

1 Introduction
2 info
3 tree
4 defaulttree
5 pattern
6 dataset
7 dataset_content
8 pattern_dataset_content
9 content
10 DataState

[edit] Introduction

Look at the history of this page (Revision 12 October 2007). In a meeting with Fabio and Erik, option 2 is chosen. This page reflects option 2 and a restructuring of the model in more packages.

[edit] info

The package info replaces the package contentdefinition. The Fenix definitions of content (data) is reflected in 4 packages. The diagram shows the packages and the associations.

[edit] tree

This diagram is just a model of a tree. The user can change and extend this. Fenix will provide the user with a default structure, a filled tree. The tree will be filled with the defaulttree.

[edit] defaulttree

Fenix offers a defaulttree to the user which is shown below. The defaulttree is an xml file which will be used to fill the initial tree of the user. Initially means when User is starting for the first time working with Fenix. User can later on change its tree.
The defaulttree will be used to fill the above showed model of tree.
Issue: the more a user changes its tree, the more this tree will be incompatible with high level analysis like Shirly is making. A high level analysis is assuming that a certain organization is in place before being able to determine certain relations/correlations.

This is the first draft after sessions with the economists. To be refined.

[edit] pattern

A FenixPattern is essentially a parent-child pattern. Parent is for example Trade with four subtypes. Or for example Price, which has for children: InternationalPrice, RetailPrice, WholesalePrice and ProducerPrice. Shown here are 2 instances of the FenixPattern. More will be added.
The parent of a FenixPattern is always a Leaf in the Tree.
The child of a FenixPattern is always a Dataset.
An instance of FenixPattern can be Price, Trade and other still to be defined patterns.
A FenixPattern is not changeable by the user. An instance of FenixPattern has a initial position in the defaulttree. The user can move the position of a FenixPattern in his/her tree.
Exception to FenixPattern is FlexData. Flexdata is just an entity, not following the parent-child pattern.

[edit] dataset

This diagram shows only the model of the different types of dataset.
A Dataset is always a Resource and has therefore alway the metadata attributes of a Resource.
Each Dataset has specific metadata attributes.
DatasetGroup is just a list of Datasets. Useful when uploading a zipfile. A zipfile contains more datasets.
TODO: add more types of datasets.

[edit] dataset_content

Each dataset contains one or more records of a corresponding type.
This structure is not changeable by the user.

[edit] pattern_dataset_content

This diagram shows classes from 3 packages and is therefore an overview diagram.

[edit] content

This models all the content of Fenix. It models actually one record of a dataset.
This structure is not changeable by the user.
TODO: add more non spatial types.