Skip to content

Reference & Data Model

Overview

Five entities make up the Aligia file system: the volume as root, folders as tree, file as shell, version as content, link as attachment.

A volume (volume) is the root of a file tree. There are two volumes per owner: „Dateien“ (Files – the visible Drive) and „Anhänge“ (Attachments – a flat, invisible volume for object attachments). The owner is either the organization or a project. Folders (folder) and files (file) hang off the volume; a missing parent folder means “directly in the volume” – there is no root folder.

The file is only the shell (name, kind, extension). The content lives in file versions (file_version); the file points to its active version. Every version goes through upload and virus scan. The file link (file_link) attaches a file to an object (task, issue, key takeaway …).

Organization ──┬─ volume „Dateien“ (slug files, Drive under Projekt & Portfolio › Drive)
└─ volume „Anhänge“ (slug attachments, flat, invisible)
Project ───────┬─ volume „Dateien“ (tab „Drive“, named after the project)
└─ volume „Anhänge“
volume ──< folder ──< folder (subfolder) …
│ └──< file ──< file_version (file.active_version_id → active version)
└──< file (directly in the volume) │
└── av_status / status → read clearance
file ──< file_link ──> object (issue, task, document, takeaway,
technical_structure_node, technical_structure_good, conversation)
Entity Purpose Where in the app
Volume (volume) Root and owner of a file tree not visible as an object; entry points Projekt & Portfolio › Drive and project › „Drive“ – Guides › Drive (global), Guides › Drive
Folder (folder) Tree structure inside a volume folder tree on the left of the Drive – Guides › Drive & attachments
File (file) Shell with name, kind, extension, active version file list and sidebar in the Drive; „Dateien“ (Files) section on objects
File version (file_version) Content, size, MIME type, upload and virus status „Versionsverlauf“ (Version history), sidebar
File link (file_link) Attachment of a file to an object „Dateien“/„Dateien anhängen“ (Files / Attach files) section in dialogs
  • Project volumes belong to the Project; the project Drive carries its title.
  • Attachments hang off Task, Issue, Key takeaway, Technical node, Component as well as agent Conversations.
  • Workflows and agents read files through the engine; the Polaris agent writes to its conversation’s workspace and can save a file from there into the Drive as a new file (after the call is reviewed); workflows write new files with file.csv, file.xlsx, file.json (see File version, Automation & AI).