Importing Assets

Ways in which you can import assets (files) in Ango Hub.

Ango Hub provides four methods to import assets for labeling.

Methods to Import Assets to Ango Hub

Browser Import

The Browser Import method is a drag-and-drop interface, through which files can be imported directly from your system.

If Ango Hub was installed on-premises, assets imported this way will be copied to the /uploaded-data/ folder within Ango Hub's root. If you are using Ango Hub on the cloud, assets imported this way will be uploaded to Ango's AWS encrypted cloud storage in Germany.

Click for information on browser import.

Cloud Import

You may alternatively upload a JSON containing the file paths and their external IDs. This is what we call Cloud Import. Assets imported this way are not copied over, and are simply fetched as necessary to display them. More details on this method can be found in the pages below:

• Upload public cloud assets

• Upload private cloud assets

  • From AWS S3

  • From GCP

SDK Import

By using our SDK, you can import assets, either from your local machine or from a cloud storage location such as an AWS S3 bucket or Azure storage, directly from your Python script. See our SDK documentation for the functions upload_files and upload_files_cloud for more.

Asset Builder

Ango Hub provides an asset builder with which you may create custom assets using the information contained in a .csv you have imported. See the Asset Builder page and upload_files_with_asset_builder function for more.

Audio files must have a constant bitrate.

Otherwise, the annotation timings will not be correct in the final export.