Skip to main content

New background-introduction

I went through my intro and have started to rewrite the whole thing. Posting it here to show A. The difference is that this intro takes a more top-down, basical approach.


The last ten years have seen revolution after revolution within information technology and telecommunications. The rise of the Internet, the success of the World Wide Web, the availability of personal computers and server performance, more recently the circulation of mobile devices and the distribution of broadband Internet are all trends of the new technological infrastructure which supports the world of modern assets which is electronical or digital data and information.

As to illustrate the increase in digital capability in containing data, one might consider the fact that the information estimated lost in the burning of the Great Library of Alexandria would fit on one single DVD. As storage space has grown, and network bandwidth has widened, the mass of digital information has exploded, both internally on intranets, and on the Internet. Users of the Internet have been most significantly effected by the increase in e-mail traffic and the amount of documents and pages available on the World Wide Web.

The value of information is only equal to that of its use. To use information, it must be found, recovered, formatted and presented. Information which is stored but never used is worthless. Digital information is enabled by the use of Information Systems. Before one can define the particular kind of Information System referred to as the Content Management System, one needs to define content itself, and seperate it from data and information.


Data, information. content and knowledge are four ambigous concepts which are regularly applied in Information Systems. If allowed to delimit the definition to digital representation, we leave out the definition of knowledge for now, focusing on the other three. These terms have various meanings, and are potential candidates for extensive ontological discussion. To avoid confusion, the meanings of these terms as used in this paper are defined as follows:


The basic unit of digital representation which can be used to construct information and content with more value for the consmer. Data is raw and granular. It does not inherently have any meaning, meta-data is not self-contained.

Data is a set of symbols, ranging from a numeral value to a string of words, or even a large series of encoded symbols that compose a binary value representing sound or picture. One often mentions data processing, feeding data as input to a program or algorithm, the output being either new data, information or content. Imagine calculating the mean of a hundred numerical values into one number. Data has been processed, but no meaning has been added. Had the value been wrapped with the context that this is the average temperature for the last three months, it could have been considered information.


One definition of information is data with meaning (Davenport and Prusak, 1998 [fix]). The same information can be conveyed with different data. Pieces of data combined with meta-data to form a package of meaning that can be conveyed. Bob Boiko includes all the common forms of recorded communication. Liz Orne ([Boiko 2002]: Orna, E (2004) Information Strategy in Practice, Aldershot: Gower, p. 7). describes it as knowledge transformed into a transportable format, visible or audible.


This is perhaps the vaguest term which we must define. Ideas include

  • Information put to use [boiko 2002]

  • Information with human meaning and context [wikipedia]

  • Information with an intended consumer, artificial or real [personal note]

  • Information with a purpose (the now disbanded ContentWatch organization's definition [Boiko 2002, p. 8]) .

The definition used in this paper is streamlined for how content can be handled by an Information System. A collection or subset of information intended for a given audience or non-human consumer with a context of location, period and situation.

Content management

Now that the definition is in place, the segment of Information Systems known as Content Management Systems can be defined. Note that in the industry of content management, the use of the term is indeterminate. Some CMS vendors claim their services feature knowledge management or enterprise content management. On the other side of the scale, many lightweight web applications claim to do content management when they actually are providing what is by most percieved as web content management, or perhaps merely weblog or wiki functionality.

Content management means different things for different actors. The basic lifecycle of content is production and consumption. For the producer, the processes of content management includes creation, formatting, structuring and integration of content. For the consumer, it includes search, export, and display. The sum of these processes make out content management. A content management system (CMS) is a suite of tools designed to assist and support these processes.

Web content management

As pointed out earlier, the explosion of digital information has been most significant on the World Wide Web. To manage this mass of online content and use, a new breed of information systems has evolved; the Web Content Management System (WCMS). The responsibility of such a system is similar to that of the CMS, only it is delimited to content which consumption is done by way of the World Wide Web. [See “Why only a web content management system” to see how WCMS has become detached from the CMS].


Popular posts from this blog

Managing dot-files with vcsh and myrepos

Say I want to get my dot-files out on a new computer. Here's what I do:

# install vcsh & myrepos via apt/brew/etc
vcsh clone mr
mr update

Done! All dot-files are ready to use and in place. No deploy command, no linking up symlinks to the files. No checking/out in my entire home directory as a Git repository. Yet, all my dot-files are neatly kept in fine-grained repositories, and any changes I make are immediately ready to be committed:

    -> ~/.atom/*

    -> ~/.mrconfig
    -> ~/.config/mr/*

    -> ~/.tmuxinator/*

    -> ~/.vimrc
    -> ~/.vim/*

    -> ~/bin/*

    -> ~/.gitconfig

    -> ~/.tmux.conf    

    -> ~/.zshrc

How can this be? The key here is to use vcsh to keep track of your dot-files, and its partner myrepos/mr for operating on many repositories at the same time.

I discovere…

The End of GitMinutes (my podcast)

I'm just about ship GitMinutes episode 46, which is going to be the final episode. I'll just paste the outro script here, as it sums up the sentimental thoughts pretty well:

I’m happy to have finally finished [publishing the last episodes from Git-Merge 2017], just in time before Git-Merge 2018 takes place in March. I won’t be going there myself, so I’m counting on someone else to pick up the mic there.

It’s sad to be shipping this one as it is probably the last GitMinutes episode ever. To go a bit down memory lane, 6 years ago, my daughter was born, and as I used a little of that paternity leave to set up my podcasting infrastructure and produce the first few episodes. Initially it was just going to be 10 episodes and call the experiment finished. Instead, I got to 46 episodes, the last dozen or so lazily tailing the last few Git-Merge conferences.

To every one of my guests, thank you so much again for coming on to share your passion in this little niche of computer science a…

Using Voice-Chat for Gamers in Distributed Teams

This is a post going into the usefulness of live voice-chat tools in distributed teams.

If you've ever seen the Leeeeeroooooyy Jeeeenkiiins video of World of Warcraft fame, you've heard this kind of tool in action. It's how the participants in the video are speaking with each other - this is not a feature built into the World of Warcraft game - it's a separate team-oriented VoIP software, and it's all about letting gamers communicate orally while gaming. 

Since these tools are for gamers, they have to be
fast (low latency)light (as not to steal CPU-cycles from heavy games graphics) moderate in bandwidth usage (as not to affect the game server connection) There are several options around: TeamSpeak, Ventrilo, more recently the massively grown Discord, and finally Mumble, which is the open-source alternative of the gang.
A few years ago, when I joined eyeo (a distributed company), several of the operations team were avid gamers, and had a TeamSpeak server set up…

Joining eyeo: A Year in Review

It's been well over a year since I joined eyeo. And 'tis the season for yearly reviews, so...

It's been pretty wild. So many times I thought "this stuff really deserves a bloggin", but then it was too inviting to grab onto the next thing and get that rolling.

Instead of taking a deep dive into some topic already, I want to scan through that year in review and think for myself, what were the big things, the important things, the things I achieved, and the things I learned. And then later on, if I ever get around to it, grab one of these topics and elaborate in a dedicated blog-post. Like a bucket-list of the blog posts that I should have written. Here goes:
How given no other structures, silos will grow by themselves This was my initial shock after joining the company. Only a few years after taking off as a startup, the hedges began growing, seemingly almost by themselves, and against the will of the founders. I've worked in silos, and in companies without the…

Working in Teams over Working as Individuals

I recentlypostedthis sketch on Twitter:

Thanks to a few mighty retweets, it gathered a lot of views (9000 impressions, whatever that means). While that's fun and all, I still felt a bit sad that such an awfully simple insight can garner much more popularity than a thorough blog post that I put some hours into.

So, rather than let Twitter get away with this, I'll steal my own content back into the blog :)

The thread went like this:

Pondering how to battle individualism in companies. For some, it is counter-intuitive that teams can be more responsive, faster and even more accountable than single individuals.

Having "teams" in place is no guarantee that team work is happening. Be wary of too large teams, "I/me/mine", personal contact details instead of team point of contact. Good team is sailing crew, not galley slaves.

Beware heroes, go-to persons, calling in favors and other shadow handling of work. Real teams make the work explicit, both requests/needs and re…