tfnico's blog

This is a from an internal discussion at work.. Jahia seems nice on the demo, but they are quite outdated on the open source part (using old stuff like struts and ant, no JSR-170). Same thing goes for the very popular Liferay. Swedish SiteVision is also good, but Objectware have alread got the under their hood. Magnolia as well, but the (like us) are based on persisting the content with Jackrabbit, and at this point there is no DBMS support there (though this is right around the corner). Magnolia's developers, the commercial company Obinary, are offering their customers an other JSR-170 compliant repository: CRX from Day. I suspect that the CRX is heavily based on Jackrabbit, since the Day developers are the core of the Jackrabbit crew. Here's an incomplete overview: Company Open Source produt Commercial product ------------------------------------------------------------- Obinary Magnolia Compass Day Jackrabbit CRX S...

Some thoughts from the early planning at P... Clarification on the component model We need to define the components with all their properties, relations and functions. Perhaps some patterns from the JSF model can be used. How is Content stored in the repository? Same way as in View? Should we seperate the Content-objects from Areas until they are published? This is related to workflow and document process routines, I guess. Note that it is important to maintain a modifiable workflow in the tools. Some smaller business will require a 1-step towards publishing an article, larger enterprises will need an x-step process involving collaboration from several stakeholders (author, publisher, editor). Area is a meta-wrapper for content which describes how the Content will appear live (online). Different sorts of Areas include Site, Page, Frame, Category, and so on. Literally all sorts of seperating folders that show up in the site map. Traditionally, an object in a CMS (an article) i...

Note that the posts below are continually edited, even if this blogger doesn't update the timestamps for when they were last edited.

A gave me some input on how to disposition the thesis State of art. Describe the existing systems. Theory. I've found an increasing amount of WCMS (as you can see on my links), and a lot of these are based on open source, particularly php, but I believe java will soon catch up ( http://theserverside.com/news/thread.tss?thread_id=33163 ). Also note in the discussion between KM and CM, the CMS fall into categories like Groupware, e-Learning, Portals and Wiki. These are classical KM IT-tools, but still the KM protectors have a belief that CM is nothing but the treatment of data and information. Au contraire (*sp), but we've found our own word for that: Content Repository, and about everyone who are dealing with CMS these days are very excited about the coming Content Repository standards and implementations, either you're talking about WedDAV or Jackrabbit. Also bring in discussion on the work of others on the subject. Write down summaries of the articles and books I re...

Originally, my problem defintion was something like: The development and analysis of a knowledge management system. Now it turns out that what we are producing at P is purerly a web content management system (WCMS). This might sound rather dull and unsophisticated, but it is important to note that "P Portal" is a general , but customizable WCMS. I will try to elaborate on these two terms: A WCMS is often developed inside the organization for use in that organization only, and it satisfies the organizations need for web content. An example is a small business hiring a web-designer that makes a small website, where news can be added on the front page with the help of a simple form. Another example is a larger corporation hiring in CMS consultants to produce a WCMS which is seamed into the existing CMS (also known as ECM-system). A general WCMS is what is often referred to as a (W)CMS package, something you buy, install and start using the way it is off the self - out of the b...

Task definition for T Development and analysis of a Knowledge Management System. The case of research is the software produced by a company called P. The thesis will consist of an analysis and development of a knowledge management system, P Portal . The solution should be possible to re-use in several different organisations. P Portal is a publication tool developed in Java 2 Enterprise Edition through design and programming of Servlets and JSP-pages. The solution should be module-based around a central core so that different modules can be added at choice to expand the functionality of the portal. The thesis will describe the process of development of the portal and the different modules. Documentation will be included on how the solution effects the targeted organisations as a knowledge management system. P is an established company with several large customers using version 2.0 of it's software for their online portals. T's task wil consist of developing new and improved fu...

To anonymize and ease the content of this blog, following abbreviations are used: T - Me (Thomas Ferris Nicolaisen, no secret :) ) A - My master advisor P - The company where my master thesis has been externalized S - The external advisor at the company U - The university I'm studying at