Use of multiple categories

abrown

We're trying to manage the growth in the number of categories that user groups request.Each group seems to want to do their own thing and have their own unique category - but, of course they are not as unique as they think. I am resisting, and suggesting instead that we apply a more generic category (a Dublin core-based category with about 10 fairly general attributes) more broadly - almost universally, in fact. We would then apply one or more smaller, increasingly focused categories to characterize what is really different about the item.I believe that this will allow better searching in the case of both general search (a "universal" metadata set) _and_ specific search (a small pool of attributes understoof and used by domain experts who know exactly what they are looking for).Has anyone else fought these battles? Are there any advantages or disadvantages either way that I cannot see?Thanks,Allen Brownanb@nortelnetworks.comvoice: (613) 763-2557

Magnus_Salgo_(IDNordicAdmin_(Delete)_2300172)

We have defined something for a customer called a document typeOne document type contains of one or more categories.In the document type we define what fields are displayed and compulsory.==> we will use maybe just one category with 20 fieldswhere some of them are attributes we have done our own to support - fetching registration number from another system - a status attribute that should have different values dependent where the document is storedetc...We have also changed the way categories are displayed so you get all attributes on the same page where you add the document .....Some end users complains on the version 9 way with a special popup windowRegardsMagnus S?lg?