This page is a work in progress.
The following command recursively copies all files in the <source-path> to the archive's <destination-path>. Metadata can be provided for every directory and file in a specific metadata file called <[directory,filename]>.metadata.json. The metadata file should exist in the same path in its corresponding directory/file. For example, the metatadata for the file foo.txt should be foo.txt.metadata.json.
dm_register_directory [OPTIONS] <source-path> <destination-path>
The following table describes each option:
| Option | Description |
|---|---|
-a[ARCHIVE_TYPE] | The type of the archive. Valid options are "S3" and "POSIX". |
-c | Turn off checksum calculation. |
| -d | Print the files to be included in registration an exit |
| -e[EXCLUDE_FILE_PATH] | Exclude the files that match the patterns specified in the file EXCLUDE_FILE_PATH |
| -h | Print a usage message |
| -i[INCLUDE_FILE_PATH] | Include the files that match at least one of the patterns specified in INCLUDE_FILE_PATH |
| -l[FILES_LIST] | Register the files mentioned in the FILE_LIST only. Each line in the FILES_LIST file contains a relative path to the source-path. All collections should be registered before using this option. |
| -m | Register metadata only. Do not register files. |
| -s | Skip confirmation prompt and register directly |
| -t[NUM_THREADS] | The number of threads to use while uploading files to cleversafe. This number should be between [1, 32]. |
The following table describes each parameter:
| Parameter | Description |
|---|---|
<source-path> | (TBD) |
<destination-path> | (TBD) |
For example, (TBD).
For instructions on performing the same task in the GUI, refer to the following pages:
- Registering a Collection from the Register Collection Page
- Registering a Collection from the Browse Page
