Download BSCW User Manual

Transcript
As the manager of a folder you may additionally impose automatic versioning on all documents of the folder. Uploading of new documents and editing or replacing of existing documents will automatically generate documents under version control.
8.3.1
Imposing version control
Establishing version control for a document may be thought of as creating a new object of the
type ‘Document under version control’ and using the existing document as the initial version.
•
Select
•
Enter description, state and number of the original version into the ‘Start Version Control’ form.
Change
Version Control
in the document’s action menu.
Version control is indicated by a few changes in the document’s entry in the folder listing:
o A version number is inserted after the document name.
o
Revise
replaces
Replace
in the action menu of the document.
When a document is under version control, some BSCW actions only concern the current version of the document:
•
Clicking the document name or the icon downloads the current version.
•
Actions such as
sion.
Send to
Converter
or
Send to
Archive
concern the current ver-
You may revoke version control for a document only by destroying all its versions (see 8.3.5
“Managing versions” on page 145).
Instead of imposing version control on single documents you may also put all documents of a
folder under version control. Details are to be found in 8.3.6 “Automatic versioning” on page
146.
8.3.2
Creating a new version
You may create a new version of a document under version control as you would
Replace ordinary documents.
Edit
or
If you edit a text or HTML document under version control directly on the server, a new version is created automatically. Its version information should be completed in order to inform
the members of the workspace (see next section).
You explicitly create a new version of a document under version control as follows.
•
Select
Change Revise in the action menu of the
Change Replace action of ordinary documents.
•
The ‘Revise’ form lets you upload a file as the new version. The form further offers
default values for the new version number and the version state. These values may be
modified, e.g., an out-of-sequence version number may indicate that the current version is a significant change of the preceding version.
•
Entering instructive information in the field ‘Changes made in version version-number’ will help the members of the workspace understand the version history and later
on to find a specific older version.
Document and Content Management
document; this action replaces the
143