np_assets table to keep track of data and media

[saxondigital]

Assets include tables, images, 3D models and more. We need a method to transact with assets for import, update and export.

Key considerations include:

• Identifier - file_id, url_id, device_id, record_id, etc.
• Category - type and sub-types:
  • Native Scene Graph (NSG)
    • Table - CSV, SQL, Neo4J
    • Network - OSC, socket, REST (JSON)
    • Plugin - Python, .dll/.dylib/.so
  • 3rd Party Data
    • Map 3rd party asset <-> Native Scene Graph.
      • Sample, convert, transcode, remap, custom scripts, etc.
  • Includes our ative types, and a lot more types of: DB's, media, network protocals....
• Location - DB, file, network, live IO
  • Connection
    • local/network file path
    • DB server (local/remote)
    • Network
      • address (URL, IP, PORT...)
      • devices (IP, port, local HW),
      • availability (on/offline), bandwidth.
    • login credentials
    • HW IO devices (audio, video, sensors, etc.)
• Metadata
  • Linked with ref_id's (foreign keys, eg ext_tbl_id = np_models, ext_rec_id = np_models_id )
  • user / ownership (groups, hierarchies)
  • data structure - tree, graph...
  • Versions
    • Original, master, copy, dub (Lg, Med, Sm)
    • Tracks, eg. DCI (J2K, ac3, dts, subs - fr...)
    • Time - live, stored (created, modified, versions, etc.)
  • sub-sampling (search queries, thumbnails, previews, etc.)
• Other considerations:
  • GUI interface - user dialogs and tags
  • User groups - teams, organization, privileges, priority...

Example use case(s):

• Loading a dataset from local file and/or DB with live connections (video, RSS, REST, MQTT).
  • NSG tables with UTT for 3rd party source
  • Importing 3D models and images (local and remote).
    • Importer is handed the asset doesn't need to know where from: file, REST, IO (Lidar).
      • But needs to find the models textures:
        • specified in the 3D models file (or re-assigned by the metadata)
        • np_models metadata table

To Do:

• Create 'np_assets' wiki page.
• Define preliminary table structure (v0.9)
  • Note that we only need a basic ver for now.
    • eg: id, name, path, ext_tbl_id, ext_rec_id

Related Issues:

• np_texture table to link node texture_id to texture assets #189 np_texture table to link node texture_id to texture assets
• Universal Translator for Hyperglyphs - aka: templates #291 Universal Translator Templates (UTT)
• np_models table for 3D models metadata #302 np_models table for 3D models metadata