Improve ProVision's Project Inventory Folder Structure Capabilities (KE)

[#1]

Background:

In our group of 2 persons (more to be added), we are having difficulty in working with the folders of Project Inventory Folder Structure (PIFS) when using KE. We use PIFS to organize models of each project using "folder-subfolder" feature.
Here are some issues:

1. Since the entire notebook cannot be checked out for "Read Only" one must click individual models to checkout. As a consequence the PIFS does not get checked on Read Only. Enhancement Request: Allow checking out the entire notebook for "Read Only" that includes folders of PIFS
2. After checking out the entire notebook for lock, there is no quick way to unlock other out-of-scope-of-work models. Enhancement Request: Allow unlocking of the models using PIFS by right clicking top folders or a group of top folders. This way all models in the Folder and sub-folders will get released.
3. The models of PIFS are coupled with the Publish Structure (See Report -> Publish-> (Create, Modify)). This poses a problem because one cannot use same names in the Publish List and PIFS folder. Enhancement Request: Allow the user to use same names.
4. It is not clear what is the resulting PIFS if person A checks out the entire notebook for lock, modifies PIFS and models, releases the un-needed models, and subsequently person B checks out the entire notebook for lock, works on the models and PIFS, and checks-in the notebook. Which PIFS prevails? Enhancement Request: Have option to display both common and local/personal PIFS. This way each user can work with their personal PIFS (local) as well as the KE PIFS (common)
5. Enhancement Request: A mechanism should be setup to check-in, or incrementally checkout models using PIFS, rather than clicking on each model using the Model inventory.
6. The client ProVision's Project, Model or Object Inventory Index currently does not show who locked the model. Enhancement Request: Please add a column to show the lock status on all three.
7. Enhancement Request: Allow creation of PIFS's content using Publish List (drag/drop) and vis-a-vis.
8. Summary: Sharing models using KE is not easy. Enhancement Request: Make sharing easy and fast.

[#2]

While I support the intent here there are some basic issues with the Project Inventory that need to be sorted out.

Example 1 - export a pvw file of a notebook, open the fiel as a new notebook and the Project Inventory has corrupted (missing folders).  John Russel from iOctane will be reporting this to Metastorm.  Both repositories were using a standard enterprise modelling language, and both clients were PV6.2 SR 4. He sent me a copy of a notebook and then we tried to use the project invenotry to look at the content of the notebook - they were not the same.

Example 2 - entire project inventory goes missing in action, not sure why or how but always involved KE (there on full checkin, not there on next full check out).

Example 3 - Re-arranging the sort order of models within the inventory or the order / level of folders is near impossible - and when you can change it the result is unpredictable.  Reported as a case by Telecom NZ

[#3]

Hi Raj, All very good ideas for the Project inventory. In fact, as we release our new versions of the Model Explorer, for viewing KE models in the Smart Business Workspace, we plan to leverage the Project Inventory more than we've had in the past. These suggestions will be very valuable for management and maintenance of those folders. I'll talk to development and plan to add much of this in future releases.