{"_id":"5b0e13ffc4664e0003c75cf3","version":{"_id":"5b0e13ffc4664e0003c75a67","project":"5b0e13ffc4664e0003c75a66","__v":4,"createdAt":"2015-09-17T16:58:03.490Z","releaseDate":"2015-09-17T16:58:03.490Z","categories":["5b0e13ffc4664e0003c75a68","5b0e13ffc4664e0003c75a69","5b0e13ffc4664e0003c75a6a","5b0e13ffc4664e0003c75a6b","5b0e13ffc4664e0003c75a6c","5b0e13ffc4664e0003c75a6d","5b0e13ffc4664e0003c75a6e","5b0e13ffc4664e0003c75a6f","5b0e13ffc4664e0003c75a70","5b0e13ffc4664e0003c75a71","5b0e13ffc4664e0003c75a72","5b0e13ffc4664e0003c75a73","5b0e13ffc4664e0003c75a74","5b0e13ffc4664e0003c75a75","5b0e13ffc4664e0003c75a76","5b0e13ffc4664e0003c75a77","5b0e13ffc4664e0003c75a89","5b0e13ffc4664e0003c75a8a","5b0e13ffc4664e0003c75a9d","5b0e13ffc4664e0003c75a9e","5b0e13ffc4664e0003c75a9f","5b0e13ffc4664e0003c75aa0","5b0e13ffc4664e0003c75aa1","5b0e13ffc4664e0003c75aa2","5b0e13ffc4664e0003c75aa3","5b0e13ffc4664e0003c75aa4","5b0e13ffc4664e0003c75aa5","5b0e13ffc4664e0003c75aa6","5b0e13ffc4664e0003c75aa7","5b0e13ffc4664e0003c75aa8","5b0e13ffc4664e0003c75aa9","5b0e13ffc4664e0003c75aaa","5b0e13ffc4664e0003c75aab","5b0e13ffc4664e0003c75aac","5b0e13ffc4664e0003c75aad","5b0e13ffc4664e0003c75aae","5b0e13ffc4664e0003c75aaf","5b0e13ffc4664e0003c75ab2","5bb3374f4306ad0003eb18e7","5bbf3c5373e72a000318362b","5bc065567d1cb0000384c649","5cbf19a5f9181f0033fbb968"],"is_deprecated":false,"is_hidden":false,"is_beta":true,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"category":{"_id":"5b0e13ffc4664e0003c75a6c","version":"5b0e13ffc4664e0003c75a67","__v":0,"project":"5b0e13ffc4664e0003c75a66","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-09-17T17:32:34.286Z","from_sync":false,"order":10,"slug":"bring-your-private-data","title":"BRING YOUR PRIVATE DATA"},"parentDoc":null,"__v":0,"project":"5b0e13ffc4664e0003c75a66","user":"554340dfb7f4540d00fcef1d","githubsync":"","metadata":{"title":"","description":"","image":[]},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2015-11-02T22:16:35.232Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":3,"body":"To copy files over from a public or private FTP or HTTP(S) server, use the FTP/HTTP(S) import tool. It runs in the background on the Platform and does not depend on your local network speed. This allows you to multitask as your files are added to your project.\n\nTo import files from an FTP or HTTP(S) server:\n\n1. [Navigate to the desired project](doc:view-a-project). \n2. Go to the **Files** tab in the project and click the **+ Add Files** button.\n2. Click **FTP or HTTP(S) server** on the sidebar to the left, as shown below.\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/4d0eedc-upload-from-an-ftp-server-1.png\",\n        \"upload-from-an-ftp-server-1.png\",\n        1126,\n        682,\n        \"#f0f0f1\"\n      ],\n      \"border\": true\n    }\n  ]\n}\n[/block]\n3. Type in or paste the URL of the file(s) you want to import. You can also click **Browse** to navigate to a text file on your computer that contains these URLs.\n[block:callout]\n{\n  \"type\": \"info\",\n  \"body\": \"You can upload a single file, a directory (in the case of FTP), or an index page (in the case of HTTP(S)).\\n\\nYou can also upload a list of URLs. They will all be uploaded in the same job.\",\n  \"title\": \"Types of uploads\"\n}\n[/block]\n5. Once you enter a URL or select a text file, you will see the option to enter tags. Enter tags in the **Tag** files box. You can separate tags with commas or by hitting the return key. All tags which are already in the selected project will be autosuggested in the drop-down menu, as shown below.\n[block:callout]\n{\n  \"type\": \"success\",\n  \"title\": \"Tagging files\",\n  \"body\": \"You can also tag files as you upload them [via the Uploader](upload-via-the-uploader) or [via the command line](upload-via-the-command-line).\\n\\nLearn more about [tagging your files](tag-your-files) in general on the Platform and how tags are beneficial to organizing your data.\"\n}\n[/block]\n6. **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).\n7. **Preserve folder structure** - If enabled, the imported items will be an exact mirror of the file/folder structure on the server. Otherwise, the items will be \"flattened\" when imported from the server, i.e. only files will be imported, with no folder structure.\n8. Click **Import** to start the upload.\n9. Click **Import more files** if you have more URLs to import. If you're finished uploading, click **Done** to close the dialog.\n[block:callout]\n{\n  \"type\": \"success\",\n  \"body\": \"You can track the import progress under the import status icon on the right-hand side of the main menu.\",\n  \"title\": \"Track your progress\"\n}\n[/block]\n\nWhen the upload completes, review your files in the **Files** tab of the project.\n \n##Accessing password-protected FTP and HTTP(S) servers\n\nThe FTP/HTTP(S) tool can submit usernames and passwords to the server. To do this, you should include the username and password in the links that you pass to the tool, using the standard HTTP syntax: `http://username:password:::at:::example.org/sample/`.\n\nPasting in a link formatted in this way will attempt to authenticate with the server `example.org` using the credentials `username` and `password` and then try to fetch everything that is hosted under the `directory/sample/`.\n\n##Troubleshooting\nIf the FTP import tool fails to import all the files whose links you provided, please retry by providing shorter lists of FTP links.\n\n## RESOLVING NAMING CONFLICTS\n\nNaming conflicts happen when you try to import an item (file or folder) from an FTP/HTTP server 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 server.\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/ae02f2e-conflict-resolution-matrix.png\",\n        \"conflict-resolution-matrix.png\",\n        471,\n        296,\n        \"#ebebeb\"\n      ]\n    }\n  ]\n}\n[/block]","excerpt":"<a name=\"top\"></a>","slug":"upload-from-an-ftp-server","type":"basic","title":"Import from an FTP or HTTP(S) server"}

Import from an FTP or HTTP(S) server

<a name="top"></a>

To copy files over from a public or private FTP or HTTP(S) server, use the FTP/HTTP(S) import tool. It runs in the background on the Platform and does not depend on your local network speed. This allows you to multitask as your files are added to your project. To import files from an FTP or HTTP(S) server: 1. [Navigate to the desired project](doc:view-a-project). 2. Go to the **Files** tab in the project and click the **+ Add Files** button. 2. Click **FTP or HTTP(S) server** on the sidebar to the left, as shown below. [block:image] { "images": [ { "image": [ "https://files.readme.io/4d0eedc-upload-from-an-ftp-server-1.png", "upload-from-an-ftp-server-1.png", 1126, 682, "#f0f0f1" ], "border": true } ] } [/block] 3. Type in or paste the URL of the file(s) you want to import. You can also click **Browse** to navigate to a text file on your computer that contains these URLs. [block:callout] { "type": "info", "body": "You can upload a single file, a directory (in the case of FTP), or an index page (in the case of HTTP(S)).\n\nYou can also upload a list of URLs. They will all be uploaded in the same job.", "title": "Types of uploads" } [/block] 5. Once you enter a URL or select a text file, you will see the option to enter tags. Enter tags in the **Tag** files box. You can separate tags with commas or by hitting the return key. All tags which are already in the selected project will be autosuggested in the drop-down menu, as shown below. [block:callout] { "type": "success", "title": "Tagging files", "body": "You can also tag files as you upload them [via the Uploader](upload-via-the-uploader) or [via the command line](upload-via-the-command-line).\n\nLearn more about [tagging your files](tag-your-files) in general on the Platform and how tags are beneficial to organizing your data." } [/block] 6. **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). 7. **Preserve folder structure** - If enabled, the imported items will be an exact mirror of the file/folder structure on the server. Otherwise, the items will be "flattened" when imported from the server, i.e. only files will be imported, with no folder structure. 8. Click **Import** to start the upload. 9. Click **Import more files** if you have more URLs to import. If you're finished uploading, click **Done** to close the dialog. [block:callout] { "type": "success", "body": "You can track the import progress under the import status icon on the right-hand side of the main menu.", "title": "Track your progress" } [/block] When the upload completes, review your files in the **Files** tab of the project. ##Accessing password-protected FTP and HTTP(S) servers The FTP/HTTP(S) tool can submit usernames and passwords to the server. To do this, you should include the username and password in the links that you pass to the tool, using the standard HTTP syntax: `http://username:password@example.org/sample/`. Pasting in a link formatted in this way will attempt to authenticate with the server `example.org` using the credentials `username` and `password` and then try to fetch everything that is hosted under the `directory/sample/`. ##Troubleshooting If the FTP import tool fails to import all the files whose links you provided, please retry by providing shorter lists of FTP links. ## RESOLVING NAMING CONFLICTS Naming conflicts happen when you try to import an item (file or folder) from an FTP/HTTP server 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 server. 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/ae02f2e-conflict-resolution-matrix.png", "conflict-resolution-matrix.png", 471, 296, "#ebebeb" ] } ] } [/block]