NIH | National Cancer Institute | NCI Wiki  

Error rendering macro 'rw-search'

null

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

If both of the following conditions are true, you can upload a data file to an existing collection in DME: 

  • If your user account has the Write or Own permission level on that existing collection.
  • If that existing collection has been configured to contain data files. 

The dm_register_dataobject_presigned command gets a pre-signed URL from DME and uses it to upload data directly to the NCI Data Vault, instead of through DME.

To register a data file:

  1. In your file system, create a JSON file that specifies the metadata for the new data file, as follows:

    { 
        "generateUploadRequestURL" : true,
        "metadataEntries": [
          {
            "attribute": "description",
            "value": "my-dataObject-description"
          },
          {
            "attribute": "my-second-attribute-name",
            "value": "my-second-attribute-value"
          }
        ]
    }
  2. Run the following command:

    dm_register_dataobject_presigned [optional parameters] <description.json> <destination-path> <source-file>

    The following table describes each parameter:

    ParameterDescription
    [-h]
    If you want to print a usage (help) message for this command, specify this option.
    [-D <REST-response>]

    An optional parameter, specifying a path and filename in your file system. The system always creates a response file:

    • If you specify this parameter, the system saves the response from the server to the specified file in the specified location.
    • If you omit this parameter, the system saves the file as dataObject-registration-response-header.tmp in your home directory.
    [-o output-json-file]

    An optional parameter, specifying a path and filename in your file system. The system always creates an output file: 

    • If you specify this parameter, the system saves the output to the specified file in the specified location.
    • If you do not specify this parameter, the system saves the output as dataObject-registration-response-message.json.tmp in your home directory. 

    If the command is successful, the output file is empty.

    <description.json>
    A path to the JSON file that specifies the metadata for the new data file.
    <destination-path>
    A path within DME, including the name of the file you intend to upload. Specify where you want the system to create the new data file.
    <source-file>

    A path in your file system, specifying the data file that you want to upload.

For example, the following command uploads the data.txt file from the JaneDoe folder in the file system to the Project_New collection in DME:

dm_register_dataobject_presigned /cygdrive/c/Users/JaneDoe/my-metadata.json /Example_Archive/PI_Lab1/Project_New /cygdrive/c/Users/JaneDoe/data.txt

For instructions on performing similar tasks in the GUI, refer to Registering Data via the GUI

  • No labels