'Missing' is a very confusing status.

Fil · Post by **Fil** » Fri Nov 19, 2004 9:22 am

I have recently installed and setup Vault onto our network and have been adding in all our project files into the repository.

Every file I have added has the status 'Missing'. To me this is confusing - the file is not missing it is 'Stored' as in stored in the repository.

I am now going to have to spend time explaining to everyone who is about to use this system that the term 'Missing' does not indicate the file is missing, it simply means you haven't got a local copy which is why we have a repository in the first place is it not!!! To store the files away!

Is there any way I can get into the system.. any sort of patch or anything that can change the status of 'Missing' to something that actually makes sense? 'Stored' might be a good one. Or how about offering the choice of status term used on files that are not checked out to anyone.

We will operate on a "remove local copy on check-in" basis, does this mean that all checked-in files will always display "Missing".

I am intending to operate the system on a "live to developers" basis on 1st December this year. It would make my life a lot easier if I didn't have to explain the 'Missing' status to everyone. It would also make our developers lives a little less confusing.

Post by **jclausius** » Fri Nov 19, 2004 10:28 am

Fil:

If a file appears in the tree, it is stored in the repository. Using the status to display stored is redundant.

In Vault, the status column applies to the state of file file as it exists on your local disk.

For example -
Edited - the file on disk is edited from the file in the repository.
Old - the file on disk is older than the one in the repository.
More recent - file on disk is newer than the one in the repository.
Missing - file on disk is not found

There is a small work around. If the status is confusing, you could configure the client to not show the status column. See the Options -> File List Columns, and disable the Status column.