As I mentioned in my previous post one of the problems that we run into with mapping context to content is the multi bucket problem. Consider thefollowing. At home I organize allmy clothes into buckets.
Each bucket has adifferent item of clothing in it e.g. one bucketcontains all my shoes; another bucket contains all my pants; yetanother buckethas all my jackets.
How let's imaginefor a moment that these are very sophisticated buckets.These buckets have the ability to classify all of the items containedwithin aswell as matching items together. For example my shoe bucket has theability toclassify all of my shoes by color and size as well as matching all ofmy leftshoes with their corresponding right shoes. To top it off these bucketshave a shinnypanel on the front that gives me detailed information about any item inthebucket. So with my bucket of shoes I can see from the front panel allthe informationthat i need about a certain shoe, such as when I bought it, how often Ihaveworn it etc.
This simple storyserves to illustrate the problems inherent in anyrepository based information management system. However, there are acouple oflessons to be learned from this simple analogy.
- No onebucket can be responsible for management relationships between theitems in its bucket and the items in another bucket as the wouldquickly be unmanageable for all but the smallest number of bucket items
- I could put all my clothes into onebucket and call it a clothes bucket, however by treating all of clothesas just generic clothes items I lose a lot of flexibility I has in themulti bucket scenario.