Skip to main content
Version: Any 26

Metadata

Metadata stores descriptive information about your content (name, subject, title, authors, etc.).

Each aspect defined in the configuration has associated metadata. That metadata can be used in the GQL conditions to filter and search the content.

Syntax​

To reference a metadata, use the format:

<aspect_name>.<metadata_name>

For instance: core.name, standard.title


Default metadata​

Two aspects are available by default on every content:

core aspect​

The core metadata holds the system information of the content:

MetadataDescription
nameName of the content
object_typeType of content (usually the main aspect)
object_idUnique internal ID of the content
root_idRoot ID shared in a version tree
primary_format_extensionExtension of the primary format (e.g. pdf, docx)
primary_format_sizeSize of the primary file in bytes
modifierName of the user who made the last change
creation_dateDate and time of creation
modification_dateDate and time of the last change
versionVersion number of the content
version_tagsTags associated with the version
aspectsList of the aspects applied to the content

standard aspect​

The standard metadata holds the common business information:

MetadataDescription
titleTitle of the content
subjectSubject of the content
authorsList of the authors of the content
statusStatus of the content (e.g. Approved, Draft)
keywordsKeywords related to the content

Query examples​

Search approved PDFs​

Query every PDF document with the subject 'installation' and the status 'Approved':

SELECT * FROM documents
WHERE core.primary_format_extension = 'pdf'
AND standard.subject LIKE '*installation'
AND standard.status = 'Approved'

Search by creation date​

Retrieve the contents created in the last 30 days:

SELECT * FROM documents
WHERE core.creation_date >= '2026-06-09'
ORDER BY core.creation_date DESC

Search by author​

Find every document of a specific author:

SELECT * FROM documents
WHERE standard.authors LIKE '*Jean Dupont*'

Custom aspects​

Beyond the standard core and standard aspects, you can create custom aspects through the configuration. The metadata of these aspects follows the same query format.