Working with IBM Aspera Files |
You can use Drive to collaborate across your team, with clear "ownership" while a user is editing a document. With the checkin/checkout feature, users check out a copy of a file, make local changes, and then check in the edited file. While the first user has the file checked out, other users can view but not modify the master copy.
Drive's checkin/checkout feature takes place in a window called Remote View:
Drive's Remote View lets you see the contents of a Files workspace, outside of the Files interface.
Remote View Versus Finder
In appearance, Drive's Remote View closely resembles Finder, the Mac OS X file browser. The most crucial difference is that Drive checkin/checkout functions are performed in Remote View. In Finder, you can see the current contents of a Files location, but not the checkin/checkout status of those contents.
When you do this, Drive downloads a copy of the file to your local computer and places a lock on it, so that others can't edit it until you check it back in.
The file opens in the default application for that file type.
When you do this, Drive uploads your edited copy to the Files workspace and releases the lock. Now others can see or check out the version with your changes.
To check in content that is not yet stored in Files, the process is almost the same as for existing content in Files.
Drive alerts you that reverting will discard any changes you have made to the file.
Opening a file through Drive and checking it out look very similar in behavior: in both cases, Drive downloads a local copy to your computer and opens it in the default application. But with checkout, Drive also places a lock on the file so that other users cannot edit it.
If you double-click a file, this opens it but does not check it out. Take care to note the difference in your collaboration workflow.
You can use Drive to see who has a particular file checked out from the Files repository.
The entry in Remote View shows you which user has checked out the file.