Describe the bug
When exporting using the "VoTT JSON" provider, the provider exposes an option to "Include Images". Upon using this export provider though, I was surprised to find that the exported JSON still references the original files even though all the images have been copied into the export directory. This is different from issues like #752 and #762 because those are related to the actual VoTT project file (.vott), not a JSON export file.
To Reproduce
Steps to reproduce the behavior (assuming you have a project with labelled data):
Go to Export Settings
Select the VoTT JSON provider
Enable "Include Images"
Save your export settings
Go back to project and run an export
Examine the JSON file that was output and check the path property on the assets. The path will be to the original image instead of the copied export image.
Expected behavior
The expected behavior is that the exported folder is all I'd need to have for copying a project and using with another tool. Instead, I'm required to include the original asset folder and/or fix the path to the file for each asset using another script. To me, the optimal solution is for the JSON file to contain relative paths to the included images if the "Include Images" option was enabled, if not, reference the original file.
Desktop (please complete the following information):
Describe the bug When exporting using the "VoTT JSON" provider, the provider exposes an option to "Include Images". Upon using this export provider though, I was surprised to find that the exported JSON still references the original files even though all the images have been copied into the export directory. This is different from issues like #752 and #762 because those are related to the actual VoTT project file (.vott), not a JSON export file.
To Reproduce Steps to reproduce the behavior (assuming you have a project with labelled data):
Expected behavior The expected behavior is that the exported folder is all I'd need to have for copying a project and using with another tool. Instead, I'm required to include the original asset folder and/or fix the path to the file for each asset using another script. To me, the optimal solution is for the JSON file to contain relative paths to the included images if the "Include Images" option was enabled, if not, reference the original file.
Desktop (please complete the following information):