# File Explorer Plugin

The File Explorer Plugin is a plugin made, published, and officially supported by Ango AI that allows you to browse a folder in your AWS S3 bucket and quickly import it into Ango Hub.

<table data-card-size="large" data-view="cards"><thead><tr><th align="center"></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td align="center">File Explorer</td><td data-object-fit="contain"><a href="https://angohub-docs-assets.s3.eu-central-1.amazonaws.com/plugin-icons-banners/file-explorer.png">https://angohub-docs-assets.s3.eu-central-1.amazonaws.com/plugin-icons-banners/file-explorer.png</a></td></tr></tbody></table>

## Plugin Functionality

The plugin hooks into your AWS S3 private buckets and allows you to bulk import a folder of your choice in the bucket. Optionally, you can assign all assets imported this way to one or more specific batches, it has duplicate prevention, and more.

## Using the File Explorer Plugin

From the Plugin Directory, search for *File Explorer Plugin* and install the plugin to your organization. More information on installing plugins can be found on the Installing Plugins page.

### Usage

First, ensure you have created a storage integration between Ango Hub and the private assets where the files you wish to import are being stored. [More information on how to do so can be found here](https://docs.imerit.net/data/storages/importing-private-cloud-assets-aws).

Then, navigate to the project where you'd like to import the assets.

Enter the *Settings* tab, then the *Plugins* section.

Find the *File Explorer Plugin* and click on *Open.* A dialog will appear:

<figure><img src="https://3895963154-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTcOUG6rfWxqGM0N4db2P%2Fuploads%2FJQ1bfhi7dRCxPM0aRxFN%2Fimage.png?alt=media&#x26;token=db4236df-ea9d-43e2-aeb3-e54e21a613af" alt=""><figcaption></figcaption></figure>

From the *Storage* dropdown, pick the storage to the bucket from which you wish to import the assets.

In the *Bucket Name* area, type in the full name of the bucket you are connecting to. For example, `acme-private-assets`.

Then, click on *Select Folder*. A dialog will pop up, from which you will be able to pick a folder, from within your bucket, to import. Navigate to the folder you'd like to import and press *Select Current Folder.*

In *Batch*, you may pick one or more batches to which assets imported in this session will be assigned.

In the Config JSON area, you can tweak a number of settings. By default, they are:

```json
{
  "upload_subfolders": false,
  "prevent_duplicates": false,
  "assign_folder_names_as_batch_name": "do_not_assign",
  "accepted_extensions": [],
  "ignored_extensions": [],
  "start_index": null,
  "end_index": null,
  "video_frame_step": null,
  "video_frame_rate": null
}
```

* `upload_subfolders`: Enabling this will cause the plugin to import all files, recursively, including those in subfolders.
  * Example: `"upload_subfolders": true`
* `prevent_duplicates`: Enabling this will prevent the plugin from importing an asset, if an asset with the same name already exists in the project.
* `assign_folder_names_as_batch_name`: Enabling this will assign each asset a batch depending on where it was located. For example, if the asset was located in the `plugin-import/nifti` folder, that will be its batch name. You don't need to create the batches in advance -- the plugin will create them for you.
* `accepted_extensions`: Whitelist here the extensions of the files you wish to import. For example, adding ".jpg" or "jpg" will import only files ending with the ".jpg" extension.
* `ignored_extension` works similarly, except it's a file extension blacklist.
* `start_index` and `end_index`: By setting the start and end indexes, you may choose to only upload a section of the data in the folder. Index values start at 0 and end with the total number of assets. Setting an index to `null` equals setting it to the first (in the case of `start_index` or the last (in the case of `end_index`) asset in the list. Setting both to `null` uploads all assets.\
  For example, assuming your assets are `Asset-1`, `Asset-2`, ... `Asset-10`,\
  \
  start\_index = 1, end\_index = 4 → uploads Asset-2, Asset-3, Asset-4

  start\_index = null, end\_index = 4 → uploads Asset-1, Asset-2, Asset-3, Asset-4

  start\_index = 1, end\_index = null → uploads Asset-2, Asset-3, …, Asset-10

  start\_index = null, end\_index = null → uploads Asset-1, Asset-2, …, Asset-10

Click on *Run.* The assets will be added to your project.

You may check the progress of the conversion from the *Plugin Sessions* dialog. More information on checking plugin progress [here](https://docs.imerit.net/plugins/introduction-to-plugins/monitoring-plugin-progress).

{% hint style="info" %}
If the assets do not appear, it might be because you have reached your organization's asset limit. Make sure to check the *Usage* tab of your [Organization page](https://hub.ango.ai/organization).
{% endhint %}

{% hint style="info" %}
Depending on the number and size of the assets, it may take a long time for the assets to appear in your project. You may check the progress from the [*Plugin Sessions*](https://docs.imerit.net/plugins/introduction-to-plugins/monitoring-plugin-progress) dialog.
{% endhint %}
