Archiving info here so we remember it.

> > e) During the training week, I was trying to use the pset code with a > test
5.3 build.  5.3 had some issues - no preview link, item templates > tab doesn't
work, no way to add a non-UDCT to a section - which I'm > assuming will be fixed
or explained.  However, I discovered one > disturbing thing; the pset code
compiles with 5.3, but if you try to > create a Story content item (the content
item used in the pset), you > get an error.  I traced this down to the fact that
every content item, > including assets, now needs to define a content bundle,
and it's not > immediately obvious how to do this (I know it's done in >
PageCreate.java, but I had problems getting text assets to define a >
ContentBundle).


ML will require a nontrivial upgrade script that invents a bundle in
between existing items and their parent folder.

Whether a bundle is required as the parent of an item or not is largely
determined by the ItemResolver (MultilingualItemResolver). For DP we use
a subclass of the CMS MultilingualItemResolver that treats assets
specially and allows for assets that are not in bundles, but directly in
folders.

David