{"_id":"595f512822f644002d08c475","project":"55faf11ba62ba1170021a9a7","version":{"_id":"55faf11ba62ba1170021a9aa","project":"55faf11ba62ba1170021a9a7","__v":40,"createdAt":"2015-09-17T16:58:03.490Z","releaseDate":"2015-09-17T16:58:03.490Z","categories":["55faf11ca62ba1170021a9ab","55faf8f4d0e22017005b8272","55faf91aa62ba1170021a9b5","55faf929a8a7770d00c2c0bd","55faf932a8a7770d00c2c0bf","55faf94b17b9d00d00969f47","55faf958d0e22017005b8274","55faf95fa8a7770d00c2c0c0","55faf96917b9d00d00969f48","55faf970a8a7770d00c2c0c1","55faf98c825d5f19001fa3a6","55faf99aa62ba1170021a9b8","55faf99fa62ba1170021a9b9","55faf9aa17b9d00d00969f49","55faf9b6a8a7770d00c2c0c3","55faf9bda62ba1170021a9ba","5604570090ee490d00440551","5637e8b2fbe1c50d008cb078","5649bb624fa1460d00780add","5671974d1b6b730d008b4823","5671979d60c8e70d006c9760","568e8eef70ca1f0d0035808e","56d0a2081ecc471500f1795e","56d4a0adde40c70b00823ea3","56d96b03dd90610b00270849","56fbb83d8f21c817002af880","573c811bee2b3b2200422be1","576bc92afb62dd20001cda85","5771811e27a5c20e00030dcd","5785191af3a10c0e009b75b0","57bdf84d5d48411900cd8dc0","57ff5c5dc135231700aed806","5804caf792398f0f00e77521","58458b4fba4f1c0f009692bb","586d3c287c6b5b2300c05055","58ef66d88646742f009a0216","58f5d52d7891630f00fe4e77","59a555bccdbd85001bfb1442","5a2a81f688574d001e9934f5","5b080c8d7833b20003ddbb6f"],"is_deprecated":false,"is_hidden":false,"is_beta":true,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"category":{"_id":"55faf932a8a7770d00c2c0bf","pages":["56268a69b1c2630d00b112b0","56268a85c2781f0d00364bbc","56268a92c2781f0d00364bbe","5637e0a0cfaa870d00cdeb6a","5637e0c3fbe1c50d008cb06a","5637e164f7e3990d007b2c41"],"version":"55faf11ba62ba1170021a9aa","__v":6,"project":"55faf11ba62ba1170021a9a7","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-09-17T17:32:34.286Z","from_sync":false,"order":8,"slug":"bring-your-private-data","title":"BRING YOUR PRIVATE DATA"},"user":"566590c83889610d0008a253","githubsync":"","__v":0,"parentDoc":null,"updates":[],"next":{"pages":[],"description":""},"createdAt":"2017-07-07T09:15:20.025Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"settings":"","results":{"codes":[]},"auth":"required","params":[],"url":""},"isReference":false,"order":5,"body":"##Overview\n\nOnce you connect your cloud storage with the CGC, you are able to upload files from that volume to your projects.\n\n##Prerequisite\n\nTo upload files from a volume to the CGC, you need to have a connected Amazon Web Services (AWS) or Google Cloud Storage (GCS) volume. Learn more about [connecting your cloud storage volume](doc:connect-cloud-storage-overview).\n\n## PROCEDURE\n1. From the main menu bar select **Data** > **Volumes**. The list of attached volumes opens.\n2. Click the name of the volume that contains the files and/or folders you want to import.\n3. Select the checkboxes next to the items you want to import.\n4. In the top-left corner above the files list, click **Import** to and select the project where you want to store the imported items.\n5. (Optional) To import the items into a specific folder within the target project, select the folder in the **Select destination** box. You can also create a new folder by clicking **New folder** in the bottom-left corner.\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/9ad95f3-upload-from-a-volume-1.png\",\n        \"upload-from-a-volume-1.png\",\n        480,\n        531,\n        \"#f3f6f8\"\n      ]\n    }\n  ]\n}\n[/block]\n6. (Optional) In the **Tag files** field add the keywords (tags) that describe the imported items.\n7. (Optional) Click <img src=\"https://files.readme.io/d5f2092-cog.png\"\nheight=\"12px\" width=\"auto\" align=\"inline\" style=\"margin:1px\"/> to set additional options:\n    * **Resolve naming conflicts** - Select the action to be taken if a naming conflict occurs. Available actions are **Skip** (default option), **Auto-rename** and **Overwrite**. Read more about naming conflicts resolution [below](#section-resolving-naming-conflicts).\n    * **Preserve folder structure** - If enabled, the imported items will be an exact mirror of the file/folder structure on the volume. Otherwise, the items will be \"flattened\" when imported from the volume, i.e. only files will be imported, with no folder structure.\n8. Click **OK**. The import procedure starts.\n\n## RESOLVING NAMING CONFLICTS\n\nNaming conflicts happen when you try to import an item (file or folder) from a Volume to a project's root folder or subfolder, where an item with the same name already exists. The list below illustrates the possible cases of naming conflicts and the way they are resolved depending on which option is selected in the **Resolve naming conflicts** dropdown:\n\n1. Importing a **file** that has the same name as an existing **file** at the destination path:\n    * **Skip** (default): The file won't be imported. This is the default behavior.\n    * **Auto-rename**: The imported file will be automatically renamed by adding a prefix (underscore and serial number).\n    * **Overwrite**: The existing file will be overwritten by the file imported from the volume.\n2. Importing a **file** that has the same name as an existing **folder** at the destination path:\n    * **Skip** (default): The file won't be imported.\n    * **Auto-rename**: The imported file will be automatically renamed by adding a prefix (underscore and serial number).\n    * **Overwrite**: The file won't be imported.\n3. Importing a **folder** that has the same name as an existing **folder** at the destination path:\n    * The content of the folder that is being imported will be merged with the content of the existing folder, regardless of the option selected in the **Resolve naming conflicts** dropdown. Any conflicts related to files within the folders will be handled according to file naming conflict resolution rules described above.\n4. Importing a **folder** that has the same name as an existing **file** at the destination path:\n    * The folder and the files it contains won't be imported. This is the default, non-configurable behavior, regardless of the option selected in the **Resolve naming conflicts** dropdown.\n\nThe following table illustrates the entire naming conflict resolution mechanism:\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/9523ddc-conflict-resolution-matrix.png\",\n        \"conflict-resolution-matrix.png\",\n        471,\n        296,\n        \"#ebebeb\"\n      ]\n    }\n  ]\n}\n[/block]\n##Resources\n\n* [Connecting cloud storage overview](doc:connect-cloud-storage-overview)\n* [Volumes](doc:volumes)\n* [Attach an Amazon Web Services (AWS) volume](doc:attach-an-amazon-web-services-aws-volume) \n* [Attach a Google Cloud Storage volume](doc:attach-a-google-cloud-storage-volume)","excerpt":"","slug":"upload-from-a-volume","type":"basic","title":"Import from a Volume"}

Import from a Volume


##Overview Once you connect your cloud storage with the CGC, you are able to upload files from that volume to your projects. ##Prerequisite To upload files from a volume to the CGC, you need to have a connected Amazon Web Services (AWS) or Google Cloud Storage (GCS) volume. Learn more about [connecting your cloud storage volume](doc:connect-cloud-storage-overview). ## PROCEDURE 1. From the main menu bar select **Data** > **Volumes**. The list of attached volumes opens. 2. Click the name of the volume that contains the files and/or folders you want to import. 3. Select the checkboxes next to the items you want to import. 4. In the top-left corner above the files list, click **Import** to and select the project where you want to store the imported items. 5. (Optional) To import the items into a specific folder within the target project, select the folder in the **Select destination** box. You can also create a new folder by clicking **New folder** in the bottom-left corner. [block:image] { "images": [ { "image": [ "https://files.readme.io/9ad95f3-upload-from-a-volume-1.png", "upload-from-a-volume-1.png", 480, 531, "#f3f6f8" ] } ] } [/block] 6. (Optional) In the **Tag files** field add the keywords (tags) that describe the imported items. 7. (Optional) Click <img src="https://files.readme.io/d5f2092-cog.png" height="12px" width="auto" align="inline" style="margin:1px"/> to set additional options: * **Resolve naming conflicts** - Select the action to be taken if a naming conflict occurs. Available actions are **Skip** (default option), **Auto-rename** and **Overwrite**. Read more about naming conflicts resolution [below](#section-resolving-naming-conflicts). * **Preserve folder structure** - If enabled, the imported items will be an exact mirror of the file/folder structure on the volume. Otherwise, the items will be "flattened" when imported from the volume, i.e. only files will be imported, with no folder structure. 8. Click **OK**. The import procedure starts. ## RESOLVING NAMING CONFLICTS Naming conflicts happen when you try to import an item (file or folder) from a Volume to a project's root folder or subfolder, where an item with the same name already exists. The list below illustrates the possible cases of naming conflicts and the way they are resolved depending on which option is selected in the **Resolve naming conflicts** dropdown: 1. Importing a **file** that has the same name as an existing **file** at the destination path: * **Skip** (default): The file won't be imported. This is the default behavior. * **Auto-rename**: The imported file will be automatically renamed by adding a prefix (underscore and serial number). * **Overwrite**: The existing file will be overwritten by the file imported from the volume. 2. Importing a **file** that has the same name as an existing **folder** at the destination path: * **Skip** (default): The file won't be imported. * **Auto-rename**: The imported file will be automatically renamed by adding a prefix (underscore and serial number). * **Overwrite**: The file won't be imported. 3. Importing a **folder** that has the same name as an existing **folder** at the destination path: * The content of the folder that is being imported will be merged with the content of the existing folder, regardless of the option selected in the **Resolve naming conflicts** dropdown. Any conflicts related to files within the folders will be handled according to file naming conflict resolution rules described above. 4. Importing a **folder** that has the same name as an existing **file** at the destination path: * The folder and the files it contains won't be imported. This is the default, non-configurable behavior, regardless of the option selected in the **Resolve naming conflicts** dropdown. The following table illustrates the entire naming conflict resolution mechanism: [block:image] { "images": [ { "image": [ "https://files.readme.io/9523ddc-conflict-resolution-matrix.png", "conflict-resolution-matrix.png", 471, 296, "#ebebeb" ] } ] } [/block] ##Resources * [Connecting cloud storage overview](doc:connect-cloud-storage-overview) * [Volumes](doc:volumes) * [Attach an Amazon Web Services (AWS) volume](doc:attach-an-amazon-web-services-aws-volume) * [Attach a Google Cloud Storage volume](doc:attach-a-google-cloud-storage-volume)