RON Containers: Folders vs App. Systems

Question

RON Best Practices
In our environment we are not using Designer as a development environment, rather we are using Designer to hold server data models of current applications (OTS packages) and various data flow diagrams. There are only two of us that use Designer.
Our existing repository is organized via development areas: Applications and Sub-Applications.
We are implementing the new Designer 10g repository and would like to take advantage during the migration process and reorganize/optimize how we are storing our metadata.
When creating a child container off the Global Workarea, the option is to create a Folder or Application System.
Any pros or cons in using the Folder option to create the categories, then creating child Application Systems under each folder as applicable?
Or should we use the Application System option and create child application systems.
For example: Container Merchandising would hold one or more Application Systems that are classified as Merchandising apps.
Thank you for any perspectives.

Answer 1

I would create Containers (Application Systems) for your business areas. like Merchandising.
Don't create sub applications you can segregate the DB elements by creating database definitions and creating implementations of database elements (ex. tables, views)via the schema owners.
Application Systems are used to capture Designer elements. These are definable objects within the Designer Repository (SCM).
Folders should be used for non Designer objects.
Mark A. Kramm
www.CDA-llc.com