3.2.1 - Set Version Control
Action Option -SV (-SetVersion) :
creates a new or updates an existing DOI/Version control record for the specified dataset.
Available mode options:
allows any specialist to set GDEXDB information, regardless of dataset ownership |
|
skips trimming of spaces and comments from input values, speeding up input file processing |
|
adds a new version control record to GDEXDB |
If a version index is provided and already exists in GDEXDB, the record is updated. A new record is created when no index is given (or it is 0) and Mode option -NV (-NewVersion) is present.
A newly created record with no DOI number is in Pending status and can only transition to Active once a DOI number is supplied. When an active record is created with a new DOI number, the version control index is auto-generated.
EXAMPLE 3. To place d999009 under DOI/Version control:
If d999009’s data are substantially updated to a new version, run the same command with a new DOI number. The previous active record is automatically moved to History status and its DOI is superseded. Only one active version control record may exist per dataset.
For minimal data changes under the same DOI, run the same command with the existing DOI number to create a new internal version index. The previous record is again moved to History.
One common minimal-change case is replacing erroneous Web files. First, move the affected files to different names using Action -MV (their type is automatically set to ‘V’ for Version-controlled). Optionally create a new internal version at this point, then archive the replacement Web files.
Note: Review the use cases above to ensure DOIs in GDEX are handled consistently.