Replies: 1 comment 1 reply
-
Adding this as an API endpoint wouldn't hurt, I guess. There will only always be the problem that BIIGLE won't touch the original files and if you want to rename files in BIIGLE, you have to update the original files manually. I'd be hesitant to offer this feature in the UI since then users will try to rename the files and then be confused why they suddenly no longer see their files in the annotation tool (because the original was unchanged). As a workaround you can also edit the database directly. If you only update the |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I've come across existing images that I would like to rename without breaking file metadata, annotations, image lables etc.
It could be nice to have an API endpoint
PUT api/v1/image/:id/
or perhaps a batch volume endpoint
PUT api/v1/volume/:id/filenames
At the moment the only way I found would be to edit the database at
images.filename
, and I can't tell if it will risk corrupting the filemetadata entries.I understand that changing an image filename in a volume will require also manually renaming the original file on the storage-side.
Beta Was this translation helpful? Give feedback.
All reactions