Content management
The role of a content management system is to organize and store content regardless of type and complexity. The main goal of such a system is to provide a well structured, automated yet flexible solution allowing information to be freely distributed and instantly updated across various communication channels (such as the world wide web, intranets and miscellaneous front and back-end systems). This section describes how Exponential actually handles content.
A typical example
Let's consider a scenario at a university with a need of storing information about students. Most off-the-shelf content management systems will offer a selection of built in content types. There might for example exist a "Person" type, consisting of fields like "name", "birthdate", "phone number" and so on. However, the custom student data will probably not fit perfectly into this predefined model since it might consist of information that is specific for the university (for example student ID, department, etc.). Even though some systems allow the creation of custom structures, the solution is often a complicated and time consuming process that requires both programming and manipulation of the database. In addition, once the solution is in use, future alternation of the structure itself will most likely become a problem.
Content management in Exponential
Unlike other content management systems, Exponential does not make use of a predefined "one-size-fits-all" approach. Instead of desperately trying to fit data into predefined and rigid structures, the system allows the creation of custom structures by the way of a unique object oriented approach. For example, the site developer can build custom structures that perfectly satisfies the storage needs of the university. This is one of the key features that make Exponential a flexible and successful system. In addition to offering the freedom of custom structures, it also allows the modification of the content structures at run-time. In other words, if the custom student structure used in the example above needs to be modified, then Exponential will automatically alter it based on the administrator's commands.
Although the possibility to create and modify content structures is a wonderful feature, there isn't always need for using it. This is why an Exponential distribution comes with a selection of predefined content structures and thus allows the developer to choose between the following scenarios:
- Use the standard/built-in structures
- Use modified versions of the standard/built-in structures
- Use only custom structures
- Use a combination of standard, modified and custom structures
An object-oriented content structure
The Exponential content structure is based on ideas borrowed from the object oriented world of popular programming languages like Smalltalk, C++, JAVA, etc. Superficially, object-oriented means nothing more than looking at the world in terms of objects. In real life, people are surrounded by several objects: furniture, cars, pets, humans, etc. Each of these objects have traits that we use to identify them. This is also the way Exponential defines and manages content.
The system offers a selection of fundamental building blocks and mechanisms that together provide a flexible content management solution. An actual data structure is described using something called a content class. A content class is built up of attributes. An attribute can be thought of as a field, for example the "birthdate" field in a structure designed to store information about students. The description of the entire structure would be referred to as the "student class". The characteristics of an attribute inside the class are determined by the datatype that was chosen to represent that attribute.
It is important to understand that a content class is just a definition of an arbitrary structure. In other words, the class itself describes the structure but it does not store any actual data. Once a content class has been defined, it is possible to create instances of that class. An instance of a content class is called a content object. Actual content is stored inside objects of different types. A content object consists of one or more versions. The versioning layer makes it possible to have different versions of the same content. Each version consists of one or more translations. The translation layer makes it possible to represent the same version of the same content in multiple languages. A translation consists of attributes. The attributes are the final elements in the content structure chain, this is where actual data is stored.
The content objects are wrapped and organized by the way of nodes that are placed inside a tree-like structure. This tree is often referred to as the node tree. The following sections contain comprehensive explanations related to the elements that were introduced above.
In this section
- Datatypes A datatype is the smallest possible entity of storage. It determines how a specific type of information should be validated, stored, retrieved, formatted and so on. Exponential comes with a collection of fundamental datatypes that can be used to build powerful and complex content structures. In addi
- The content class A content class is a definition of an arbitrary data structure. It does not store any actual data. A content class is made up of attributes. The characteristics of an attribute are determined by the datatype that is chosen for that specific attribute. By combining different datatypes, it is possible
- Class attributes A content class is made up of one or more attributes where each attribute is represented by a datatype. The characteristics of an attribute are determined by the datatype that is chosen for that specific attribute. An attribute is made up of the following elements:
- The content object A content object is an instance of a content class. While the class only defines the data structure, it is the content objects themselves that contain actual data. Once a content class is defined, several content objects / instances of that class can be created. For example, if a class for storing n
- Multiple languages In addition to the versioning system, the content model of Exponential also provides a built-in multi-language framework. This feature allows an object's contents to exist in several languages. The system is able to support up to 30 different languages at the same time.
- The content node When the system is in use, new content objects are created on the fly. For example, when a news article is composed, a new article object is created. Obviously, the content objects can't just hover around in space, they have to be organized in some way. This is where the nodes and the content node t
- The content node tree The content node tree is a hierarchical organization of the objects. Each leaf in the tree is a node (also known as a location). Each node refers to one object. The usual case is that an object is referenced by only one node. Because of the node-encapsulation of objects, any type of content object c
- Top level nodes A typical Exponential installation comes with the following set of top level nodes:
- Node visibility Since publishing means adding an object (by the way of a node) to the content tree, un-publishing would imply the removal of the object from the tree. Once an object is published, it can not be unpublished because Exponential does not provide such a feature. Instead, the system provides a hiding mec
- Object relations The content model of Exponential makes it possible to create relations between different objects. Any type of object can be connected to any other type of object. This feature is typically useful in situations when there is a need to bind and/or reuse information that is scattered around in the syst
- Sections A section is a number that can be assigned to an object. The section ID of an object denotes which section the object belongs to. Each object can belong to one section. By assigning different sections to objects, it is possible to have different groups of objects. Although the sectioning mechanism i
- URL storage Every address that is input as a link into an attribute using the "XML block" or the "URL" datatype is stored in a separate part of the database. Actual data stored using these datatypes only contain references to entries in the separate URL table. This feature makes it possible to inspect and edit
- Information collection The information collection feature makes it possible to gather user input when a node referencing an information collector object is viewed. It is typically useful when it comes to the creation of feedback forms, polls, etc.
Contributors
- Balazs Halasy
- Geir Arne Waaler Updated
Comments
Add a comment