|
From: Laszlo K. <las...@su...> - 2000-11-24 16:28:00
|
Hi, here is another issue from our very long email. How do we deal with category trees? I see category trees as generic empty content lists. These are the possibilities we discussed: 1. Enforce a category tree and ignore all docs that don't fit into it. 2. Enforce a tree and put all docs that don't fit into an Other section of the Content List. 3. Supply a tree (installed) and OMF files come with new categories, extend the Categories in the Content List with them (don't modify the category tree). 4. Recommend a set of categories on the project web site, but don't supply any tree. Build the content list(s) from whatever comes in the OMF files. 5. Don't recommend any categorization, but keep support in the OMF files to specify categories. Extend the Content List with whatever comes in the OMF files. 1. and 5. are there for completeness only. I suppose nobody thinks they would be a way to go. So what do people think? Which is the best way to do it? Any other ideas? Laszlo |