File Upload Box
Overview of the file upload box tool in Ango Hub
The Upload Box tool allows you to add a classification where users can upload a file while labeling a task.
Each upload box can contain one file per task. If you need to collect more than one file, add multiple upload boxes to the project, or ask users to upload one archive file containing all required files.
How to add an Upload Box tool to a project
From your project's Settings tab, enter the Category Schema section. Click on Add category, then pick Upload box. An Upload box tool will appear in your ontology:
Upload Box Settings
Title
The upload box's title. This text will appear immediately above the upload box itself.
Required
Whether or not the user is required to upload a file to this box before submitting the task.
Data storage
By clicking on Pick folder, you're able to select the storage integration (e.g. AWS S3, GCP, Azure), bucket or Azure container, and subfolder where uploaded files will be written. When selecting a bucket or container, you can pick one from the list or switch to search mode and type the name manually. Manual search is useful when the connected storage does not allow Ango Hub to list buckets or containers, but does allow access to the one you enter. Please note: Ango Hub must have write permissions to the bucket or container you are pointing to. See our page on storages for more.
Accepted Formats
You may optionally list the file extensions you'd like to accept for this upload box. For example, .jpg and .png. If you leave this blank, any file extension will be accepted.
Enter extensions with the dot, such as .pdf, and use lowercase extensions.
Filename
If you fill in this field, the uploaded file will be saved with this filename. The filename is also shown to users in the upload box. If you leave this blank, Ango Hub generates a filename from the upload box title, upload time, and original filename.
Where uploaded files are stored
If you configure Data storage, uploaded files are written to the selected storage integration, bucket or Azure container, and folder. Ango Hub also adds project and task-specific path segments so that files from different projects and tasks do not overwrite each other.
If you do not configure Data storage, uploaded files are stored in Ango Hub's default storage for upload-box files.
The final object path is built as follows:
If you do not select a storage folder, the path in Ango Hub's default storage is:
For example, if your selected folder is uploads/evidence, the project ID is PROJECT_ID, the task ID is TASK_ID, and the uploaded filename is evidence.pdf, the uploaded object will be written under:
If you are using your own storage integration, Ango Hub needs write access to the selected bucket or Azure container and folder. If Ango Hub cannot create the upload URL or write the file, the user will see a file upload failure.
How a user can upload a file on the upload box
When the user is in the task, they will see the upload box as a classification.
They can drag and drop a file onto the upload box, or click on the box to open their OS's file picker.
If the upload box already has a file, uploading another file replaces the answer for that upload box.
Once a file has been uploaded, the user will see a link to the uploaded file and a delete button. Deleting the answer removes the file from the task's answer, but does not necessarily delete the object from the underlying storage bucket or container.
Export format
Upload box answers are exported in the task's classifications list, like other classification answers.
In the export, the classification's tool is upload-box, and the answer is a signed URL to the uploaded file.
Because the exported answer is a signed URL generated at export time, it may expire. If you need long-term access to uploaded files, use your storage provider's object path or bucket tooling as the durable source of truth.
See Classifications in the Ango Export Format for the full classification export structure.
Last updated