A group of scientists put five monkeys in a cage. In the center of the cage was a step ladder, and a banana was hung from the very top. The monkeys scurried up the ladder to retrieve the banana and then the scientists sprayed them with freezing cold water to prevent them from reaching it. Each time they tried to go up the ladder, they were again sprayed until none of the monkeys went up the ladder.
The scientists removed one monkey from the cage and replaced it with a new monkey. The new monkey saw the banana, saw the ladder and attempted to go up. The four original monkeys, afraid of being sprayed with water, assaulted the new guy to prevent him from going up the ladder. He had no idea why he was being attacked but he didn't go up the ladder again.
A second original monkey was removed from the cage and replaced with a new one. Same thing: the new monkey attempts to go up the ladder to retrieve the banana, and once again, this newest monkey is assaulted. Except this time, the first new monkey takes part in the beating of the newest monkey. He has no idea why he is participating in the beating, but nevertheless it happened to him.
This process of bringing in new monkeys continues until there are no original ones in the cage that were sprayed with cold water. But no monkey in this now completely new group dares go up the ladder out of fear of being assaulted, not sprayed with cold water. Again, it's always been done this way!
Thanks to my co-worker Mark for pointing out this story. I'm sure several of you already knew of its existence. I sure felt this applied to the business of content management and incorporating new systems in general for companies. Think about content server's WebDAV capability. You install content server at company X. "Can we still look at it with folders?" they ask? Why? Because that's how they do it today, that's how they've always done it…
With the newer versions of Site Studio (10gR3, at least 10.1.3.3.3+) there is a handy way to set the default link format for your site. You can do this through the Site Studio Designer and the setting is persisted in your Project XML file in Content Server. This is pretty handy if you want to do things like using one manner of linking to data files for 90% of your content creation work.
When oracle released the 10.1.3.3.3+ site studio product they delivered a new contributor application along with new data file formats. Inside these data files the structure has changed from previous versions. Here is an example of the new format:
<?xml version="1.0" encoding="UTF-8" ?>
As you can see a near full path is embedded in the xml file. In this case if I were to change the security group of this image from public to secure the page using this data file would render with a missing image. The same is also true of the doc type and/or account. What can we do about this?
The documentation mentions that the function ssWeblayoutUrl() is able to work with the dDocName: This script extension is used to determine the full web address of a file from either the path or dDocName. This is most typically used for paths to images in data files.
Great. It turns out that through the use of a configuration variable added to config.cfg or through the admin server under general configuration week in control what gets embedded in data files. Note: this is available in build 251 or higher.
On a related note, check out another blog post starring ssWeblayoutUrl over at Web Monkey Magic.
There are often a wide variety of reasons why someone may want to keep only the latest n revisions of content in their content server. These reasons range all over from keeping disk usage in check to a form of security/retention management. Whatever your reason the process is pretty straight forward. I am going to show you how to setup archiver to take out all but the latest X revisions. In a later post we can talk about various ways to enact that archive on a scheduled basis.
So, simply put, the secret to this is the Revision Rank (dRevRank) field. A lot of times in the past I've tried looking at dRevLabel, dID, dDocID, but nope, the special field you want is Revision Rank. Use the following steps to set up your archive:
Upon selecting "Export" you will be prompted deleting the revisions from content server during the export process. If you place a check mark in the check box the content will be REMOVED from content server. The content will continue to exist in the archive you just exported as long as you don't crack that open and delete it in there as well.