Dataset management for file sets and PostgreSQL

[saxondigital]

Proposed properties of dataset management:

• DB viewer to navigate datasets within the GUI.
• Each dataset would have its on directory structured similar to existing 'usr' folder.
• Allow for sharing external assets across multiple datasets such as texture maps.
• PostgreSQL DB support for external file path or URL to load textures or other external assets.
• Allow the directory to be compressed into a ZIP file.
• Allow user to choose specific file or the directory to load entire dataset at once.
• Dataset browser to visually choose a dataset represented as a node tree.
• Scene table to hold a list of the assets in the dataset, support imbedding other scene tables.

[saxondigital]

Scene table(s) contain a list of assets to compose the scene from. Essentially a list of all tables and locations of these tables. May also include external references such as URL's (or file paths) to remote locations to fetch data from, such as other sub-scenes and/or multimedia assets such as images, video, audio, 3D models, etc…. Paths can be either absolute or relative to the app or user directory.

It is not necessary that the scene table directly reference every asset. For example it may reference a directory or database and specify loading all assets from this location or it could specify another table that has a list of assets, such as a texture_id table the maps images or video files.

[saxondigital]

--- np_texture table --- Texture map table to associate texture_id with the file(s) that represent the texture. This could be a single image or video (image sequence, stream, AV file, input capture device or screen raster.) The table may contain metadata about the file such as size, file format, cropping (and possibly related files, such as models, audio, etc.)

[saxondigital]

Direct support for .bat/ csv tables on remote server via CURL

[saxondigital]

Dataset management

[saxondigital]

297 Individual Dataset Folders