Suggestion: allow binding the file extension

[julianpoemp]

Octra uses file extensions for filtering possible file format converters before testing the filtered converters . If the user opens Octra provided by the switchboard, Octra receives URL query parameters without the original filename and extension.

At the moment Octra tries to determine the file extension using the mime type, but this can be error-prone. What if the user doesn't select the correct mime type manually? E.g. if a user uploads a TextGrid file its mime type is text/plain. Because Octra doesn't know it's a TextGrid file it reads the text file as plain text and shows an invalid representation.

Would it be possible to introduce a new bind value type extension? For example:

{
  "name": "transcript_ext",
  "bind": "transcript/extension"
}

I know that you don't want to preserve the original file name due privacy but perhaps allowing to preserve the file extension would be an option. Because the mime type is already provided I don't see an issue to provide the extension, too.