Data App -has a-> Data Unit

Created by Hevok on Dec. 18, 2012, 3:01 a.m.

Data App

The data app controls the management of Content in Denigma. It also provides the universal Data Entries. A data entry is the fundamental unit for data acquisition. The process of data acquisition is the assembly of signals/information that measure real world physical conditions and converts them into a digital data structure that can be used and manipulated effectively by Denigma.

One schema that fits everything.

Any data entry can be associated with any kind of tag, with specified categories and only one parent entry, but it can have multiple Relationships to any other entry.


Update (Admin) | View

has a

A relationship where one object (composited object) "belongs" to (is part or member of) another object (composite type).

Categories: Relationship

Update (Admin) | View

Data Unit

The Blog and Wiki, Todo as well as associated News and Tutorials and DEPs, Documentation app and several others follow the same pattern: Each one contains a data entry which has a Title, a text and tags associated. Tags themselves can be data entries or linked to corresponding data entries. Further, there is meta data associated with each entry such as date of creation (created), update (updated). Moreover, images (multiple) may be associated with an entry of which the first one will be the main one. A thumbnail view of images must be accessible.

Another field might declare whether it is drafted or not, but this is not necessary. Each entry content (text) needs to be rendered in HTML and have automatically assigned hyperlinks and should allow to use multiple markup languages.

It is therefore proposed to have a single data controlling app which eliminates the redundancy between all these different apps. Either tags or another table (maybe it can be called type or category) declares what type of entry it is. The simplest solution is that tags declare also the type of a data entry, e.g. whether it is a news or a tutorial. An immediate implementation of this concept was done by using the blog as the data-driving app. The tutorial should actually be part of the docs.

A data unit is a coherent/consistent defined piece of information (like a quark). In such a data unit represents the fundamental constituent of a database. A data unit can be for instance be a single row in a relational database table, while the columns are the attributes of this unit. In other database types a data unit is even more obvious (e.g. document storage or nodes in graph databases). These attributes should have meaningful names and follow a logical convention. Many attributes can be represented by synonyms. For example a name, title or label have very often exactly the same function. Similar text, body, content, description are mostly always the main textual part of a data unit. Data Entries define which attributes are synonymous.

Data units can be exchanged between databases. Thus, it enables the exchange of information between different databases even with those that define different schema. Therefore, Data unit enables Database Synchronization.

Categories: Concept

Update (Admin) | View

Comment on This Data Unit