Skip to main content

Improving problem description

This week is set off for improving the chapter on problem description. Every thesis has a "problemstilling", a problem which the thesis should solve. A goal, or a challenge. Currently the chapter looks a little something like this:

Challenges

What are the challenges that have pushed forth content management. What are the problems IT-departmens suffer from today related to web content. Issues on web-management.

The issues of web content management

Content is not maneuvrable. There is too much of it, too many web pages with too many attached documents. Often a corporation will put much resource into sustainin a site map and a navigation tree, but if these are made manually, it will be a lot of work and no guarantee to be correct. Searching is a great shortcut to make all content available, but searching the right way is easier said than done. Does the search engine check if the search word was incorrectly spelled? Are there any synonyms of the search word which should be checked?


Content is useless. The web page is full of dead links. There exists many pages and documents which are not linked to at all, and therefore never will be accessed. It is safe to say that content which is not accessed and used has no value.


Content is not automatically accessible. No XML export. Recently many news-sites have offered the option of subscribing via popular RSS-feeds. By subscribing to these feeds in RSS-readers or news-aggregators, the process of collecting news from these sites is turned from a pull-protocol (actively surfing around on news-sites) into a push-protocol (content is pushed to the reader, like mail to a recipient).


Content has no meta information. There has a been a noteworthy increase in the ability to tag or label various data objects with meta data, like in the header of a HTML-page, or in the properties of a Word-document. It is difficult to force users into actually using these features manually. If the title of this document is "Content Management", why should I write in its meta-data that it is about the same topic? A possible solution to the meta-problem lies in automatically tagging content [HP, 2004].


Content is technically unaccessible. Dependancy to specific software or platform restricts the numbers of users.


-------

So I need to come up with something more completing this chapter. A good CMS doesn't produce the problems mentioned above. CMS-es like this already exist, I'm sure. And the goal of the thesis could indeed be to present a CMS solving these, by the use of open standards. To get the open source bit in, I should add something about functionality and customization (functionality is content too!, like Boiko said). A old rusty CMS, or even a modern one (but not a tidy one) can be quite hard to extend, having components which are not reusable. Content is not reusable.

Interestingly, I'm not the only one who's been asking questions about meta-data. Seth Cambridge is another blogger I just added to my bloglines. But still it remains a problem that so much of the CMS theory landscape remains opinions through blogs and online articles, mediums not really appreciated by the people who will judge my thesis. I might have to get back to basis and read up on some ancient IT-theory I can reuse in this context (but I haven't really got time to do that).

Popular posts from this blog

Encrypting and Decrypting with Spring

I was recently working with protecting some sensitive data in a typical Java application with a database underneath. We convert the data on its way out of the application using Spring Security Crypto Utilities. It "was decided" that we'd be doing AES with a key-length of 256, and this just happens to be the kind of encryption Spring crypto does out of the box. Sweet!

The big aber is that whatever JRE is running the application has to be patched with Oracle's JCE in order to do 256 bits. It's a fascinating story, the short version being that U.S. companies are restricted from exporting various encryption algorithms to certain countries, and some countries are restricted from importing them.

Once I had patched my JRE with the JCE, I found it fascinating how straight forward it was to encrypt and decrypt using the Spring Encryptors. So just for fun at the weekend, I threw together a little desktop app that will encrypt and decrypt stuff for the given password and sa…

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 https://github.com/tfnico/config-mr.git 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:

config-atom.git
    -> ~/.atom/*

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

config-tmuxinator.git  
    -> ~/.tmuxinator/*

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

config-bin.git   
    -> ~/bin/*

config-git.git          
    -> ~/.gitconfig

config-tmux.git  
    -> ~/.tmux.conf    

config-zsh.git
    -> ~/.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…

Always use git-svn with --prefix

TLDR: I've recently been forced back into using git-svn, and while I was at it, I noticed that git-svn generally behaves a lot better when it is initialized using the --prefix option.

Frankly, I can't see any reason why you would ever want to use git-svn without --prefix. It even added some major simplifications to my old git-svn mirror setup.

Update: Some of the advantages of this solution will disappear in newer versions of Git.

For example, make a standard-layout svn clone:

$ git svn clone -s https://svn.company.com/repos/project-foo/

You'll get this .git/config:

[svn-remote "svn"]
        url = https://svn.company.com/repos/
        fetch = project-foo/trunk:refs/remotes/trunk
        branches = project-foo/branches/*:refs/remotes/*
        tags = project-foo/tags/*:refs/remotes/tags/*

And the remote branches looks like this (git branch -a):
    remotes/trunk
    remotes/feat-bar

(Compared to regular remote branches, they look very odd because there is no remote name i…

Considerations for JavaScript in Modern (2013) Java/Maven Projects

Disclaimer: I'm a Java developer, not a JavaScript developer. This is just what I've picked up the last years plus a little research the last days. It's just a snapshot of my current knowledge and opinions on the day of writing, apt to change over the next weeks/months.

We've gone all modern in our web applications, doing MVC on the client side with AngularJS or Ember, building single-page webapps with REST backends. But how are we managing the growing amount of JavaScript in our application?
You ain't in Kansas anymore So far we've just been doing half-random stuff. We download some version of a library and throw it into our src/main/webapp/js/lib, or we use it from a CDN, which may be down or unreachable when we want to use the application..

Some times the JS is minified, other times it's not. Some times we name the file with version number, other times without. Some times we get the latest library of master branch and name it with the commit-id in the fi…

Microsoft ups their Git efforts another notch

This week Microsoft announced first class Git support embedded in the coming version of Visual Studio.

Now, it's not completely shocking. We could have seen it coming since Microsoft started offering Git repos on CodePlex, and more recently offering a Git client for TFS. In any case, these are some big news. Scott Hanselman weighs on some features and some more background here.

For those who are a bit unaware of what the Git situation on Windows looks like these days, I've dotted down these notes:
Some explanation on these:

msysGit has long been The Way to use Git on Windows. It's basically a port of Git itself, so it's a command-line tool.GitExtensions (includes Visual Studio integration), TortoiseGit, Git Shell, posh-git and most other tools are powered by msysGit.libgit2 is a native library for doing Git stuff. It is developed completely separate from Git itself. The above tools could (and should) probably use libgit2 instead of hooking onto and around msysGit.Github…