What is the best way to Categorize Projects in SCM
Scenario is
Project Stream
Portal Projects (Component)
ams folder
NMS folder
upto 150 Projects folders
Mobile Component
upto 10 folders
BPM
upto 20 folders
Currently the issue is that Keeping all projects in single component i am getting all incoming project changes and also i am unable to see history of individual Project Folder.
Solution is : to keep all projects in separate Component but different components contain same project Names as well.
Is it right approach to divide categories (Portal, BPM) in Streams and then categorize folders in component ?
Project Stream
Portal Projects (Component)
ams folder
NMS folder
upto 150 Projects folders
Mobile Component
upto 10 folders
BPM
upto 20 folders
Currently the issue is that Keeping all projects in single component i am getting all incoming project changes and also i am unable to see history of individual Project Folder.
Solution is : to keep all projects in separate Component but different components contain same project Names as well.
Is it right approach to divide categories (Portal, BPM) in Streams and then categorize folders in component ?
One answer
There is no right or wrong. You choose the approach to break down into components. One way is to pool the projects by dependency or architectural categorization. So put stuff in a component that belongs closely together and strongly depends on each other. The JKE Banking example that ships with CLM shows an approach.
Please be aware that you can have no overlapping names in components, because that would prevent loading the components.
Please be aware that you can have no overlapping names in components, because that would prevent loading the components.