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).

Comments

Popular posts from this blog

Open source CMS evaluations

I have now seen three more or less serious open source CMS reviews. First guy to hit the field was Matt Raible ( 1 2 3 4 ), ending up with Drupal , Joomla , Magnolia , OpenCms and MeshCMS being runner-ups. Then there is OpenAdvantage that tries out a handful ( Drupal , Exponent CMS , Lenya , Mambo , and Silva ), including Plone which they use for their own site (funny/annoying that the entire site has no RSS-feeds, nor is it possible to comment on the articles), following Matt's approach by exluding many CMS that seem not to fit the criteria. It is somewhat strange that OpenAdvantage cuts away Magnolia because it "Requires J2EE server; difficult to install and configure; more of a framework than CMS", and proceed to include Apache Lenya in the full evaluation. Magnolia does not require a J2EE server. It runs on Tomcat just like Lenya does (maybe it's an idea to bundle Magnolia with Jetty to make it seem more lightweight). I'm still sure that OpenAdvant

What I've Learned After a Month of Podcasting

So, it's been about a month since I launched   GitMinutes , and wow, it's been a fun ride. I have gotten a lot of feedback, and a lot more downloads/listeners than I had expected! Judging the numbers is hard, but a generous estimate is that somewhere around 2000-3000 have listened to the podcast, and about 500-1000 regularly download. Considering that only a percentage of my target audience actively listen to podcasts, these are some pretty good numbers. I've heard that 10% of the general population in the western world regularly listen to podcasts (probably a bit higher percentage among Git users), so I like to think I've reached a big chunk of the Git pros out there. GitMinutes has gathered 110 followers on Twitter, and 63, erm.. circlers on Google+, and it has received 117 +'es! And it's been flattr'ed twice :) Here are some of the things I learned during this last month: Conceptually.. Starting my own sandbox podcast for trying out everythin

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

The academical approach

Oops, seems I to published this post prematurely by hitting some Blogger keyboard shortcut. I've been sitting for some minutes trying to figure out how to approach the JavaZone talk mentioned in my previous blog-post. Note that I have already submitted an abstract to the comittee, and that I won't publish the abstract here in the blog. Now of course the abstract is pretty detailed on what the talk is going to be about, but I've still got some elbow room on how to "implement" the talk. I will use this blog as a tool to get my aim right on how to present the talk, what examples to include, what the slides should look like, and how to make it most straightforward and understandable for the audience. Now in lack of having done any presentations at a larger conference before, I'm gonna dig into what I learned at the University, which wasn't very much, but they did teach me how to write a research paper, a skill which I will adapt into creating my talk: The one

Git Stash Blooper (Could not restore untracked files from stash)

The other day I accidentally did a git stash -a , which means it stashes *everything*, including ignored output files (target, build, classes, etc). Ooooops.. What I meant to do was git stash -u , meaning stash modifications plus untracked new files. Anyhows, I ended up with a big fat stash I couldn't get back out. Each time I tried, I got something like this: .../target/temp/dozer.jar already exists, no checkout .../target/temp/core.jar already exists, no checkout .../target/temp/joda-time.jar already exists, no checkout .../target/foo.war already exists, no checkout Could not restore untracked files from stash No matter how I tried checking out different revisions (like the one where I actually made the stash), or using --force, I got the same error. Now these were one of those "keep cool for a second, there's a git way to fix this"situation. I figured: A stash is basically a commit. If we look at my recent commits using   git log --graph --