The DBPTK now allows to include in SIARD files from the files system that were originally referred on the database. This feature makes the external files become BLOBs of the database, but looses the original filenames. The filenames are afterwards important to download the BLOB on the SIARD web viewer, and in a global way may have important hints on its content and file format.
Another general feature could be to add rendering hints into the column metadata of BLOB columns, that could allow to define possible file name extensions, file format or file format family. Knowing that a column refers to an image may be important to better render the information on a Web viewer.
So there are two suggestions on this issue:
- Adding new optional fields to the table cell for file name and file format.
- Adding new optional element to metadata column to add rendering hints like file name extension (e.g. .pdf), file format mimetype (e.g. application/pdf) and file format family (e.g. image).
The DBPTK now allows to include in SIARD files from the files system that were originally referred on the database. This feature makes the external files become BLOBs of the database, but looses the original filenames. The filenames are afterwards important to download the BLOB on the SIARD web viewer, and in a global way may have important hints on its content and file format.
Another general feature could be to add rendering hints into the column metadata of BLOB columns, that could allow to define possible file name extensions, file format or file format family. Knowing that a column refers to an image may be important to better render the information on a Web viewer.
So there are two suggestions on this issue: