1. Reply

    Great topic Kristian. I believe integration is a key element for the higher level intranets. There is a risk that more collaboration tools will recreate the just teared down silos. Looking forward to your next post in this series. Cheers, Bas.

    • Reply

      Thanks Bas!

      I agree, to reach the next level, the intranet should integrate information and tasks in context based, process-driven user interface. Collaboration tools are great for teams, but for the organization as a whole… I share your view that there is a great risk that collaboration tools will create new information silos.

  2. Reply

    Great work Kristian. You’ve created a mini-internet on your intranet, sensibly mirroring and reusing tools and technology currently in use “on the outside”… Like Baz, i’m also looking forward to the other posts in the series.

    One thing which I’m wondering is is how you are going to deal with content that’s reached the end of it’s life-cycle (deleted content) – obviously the URL service is giving you persistant URLs during the life-cycle, but what happens next? how do you manage the tidying up afterwards?


    • Reply

      Thanks James!

      Good question. You made me think about theURL-service and content life-cycle a lot. And got a few good ideas I think we’re going to implement.

      I guess we will never re-use a shortened URL. As the URL-service basically is a re-direct service we can inform (with text/pictures) the users that they are about to be redirected to archived information or that the information they have requested is deleted and therefore not longer available. This means that we have to store the status (active/archived/deleted) of the shortened links resource. As the URL-service has a look-up part we can implement it in our CMS, so that the user are aware of the linked resource sstatus even before clicking on the link.

Leave a comment

Your email address will not be published. Required fields are marked *