Features for QVCS-Enterprise 2.1, What should be in 2.1? Options

[Jim Voris]

Please pick the feature that is most important to you. If you choose other, please enter a reply to describe what 'Other' feature you would like.

[J Williams]

Please pick the feature that is most important to you. If you choose other, please enter a reply to describe what 'Other' feature you would like.

Merging tool!

[TGB]

Please pick the feature that is most important to you. If you choose other, please enter a reply to describe what 'Other' feature you would like.

Jim: I realize this is a lot to ask of the Enterprise product, but the ability to do all four of the first items you list in your poll, provided the user has been afforded PROJECT_ADMIN rights, would round out the Enterprise version rather nicely, don't you think.

I understand that the Enterprise product's architecture makes this a significant task. But if you ask me, I will tell that even the most polished and forward thinking users will not get it right the first time. They will want to rename both files and directories, AND move files from directory to directory in addition to moving and re-arranging the directory structure itself.

As it stands with v2.1.21 of the QVCSe product, the only way to do this re-shuffling of the deck if you will, is to declare a time-out to the users, and gingerly ask the users to log out, shut down the server and move the files around manually inside the qvcsProjectsArchiveData folder. If the need expressed by the user community for a major reshuffling of the archive tree structure is immediate, then costly delays caused by having to take down the QVCS Server are a concern. I rarely expect this to be the case and that most if not all such reorganizations can and will be done after-hours.

To further complicate matters, once the work to re-shuffle the contents in the qvcsProjectsArchiveData has been completed, the qvcsProjectsReferenceCopies (or alternate mirror directory) then needs to be rebuilt from scratch if there have been any directory renames/moves. The final step then is to delete the qvcs.fileIDStore.dat file in the qvcsMetaData folder. I now do this by renaming the qvcs.fileIDStore.dat.old to qvcs.fileIDStore.dat.older, renaming the current qvcs.fileIDStore.dat to qvcs.fileIDStore.dat.old then restart the QVCS Enterprise Service. Is it manageable for the ADMIN? Of course it is, and with a bit of practice it gets to be a routine operation, and it works beautifully.

The problem is that the user would like to manage their affairs themselves. They see a beautiful UI and expect to be able to drag and drop, hit F2 to rename a file or directory, and shuffle the deck as they please. As long as this reorg work is done with the agreement and support of the other members of the QVCS user community, then such actions would be entirely plausible.

I vote for all four of the first choice in the following order
1) Rename file
2) Rename directory
3) Move file
4) Move directory (and all subsidiary child directories along with the parent directory being moved)

My 4 cents if you will
Thank you Jim!
Ted

[Jim Voris]

Of your 4 top picks, 2 are already supported in the product:

You can rename files (select a file and choose from the context menu).
You can move files (via drag-and-drop, though the drag-and-drop in Java is finicky).

The other two are in current development -- (still a long way off), with the rename directory likely to appear before moving directories.

[TGB]

Of your 4 top picks, 2 are already supported in the product:

You can rename files (select a file and choose from the context menu).
You can move files (via drag-and-drop, though the drag-and-drop in Java is finicky).

The other two are in current development -- (still a long way off), with the rename directory likely to appear before moving directories.

Thanks very much Jim!
Ted