Asset library search fields
Asset library writes 10 fields into Confluence's own search index. Once a page has been indexed you can filter and sort by them in Capable Search, and use them in ordinary Confluence CQL.
A page that hasn't been indexed yet has no values in these fields. It won't match a query on them, and it won't show up as an empty result either. On a large site, indexing can take hours to days to catch up.
The <hash> prefix is your installation's app hash. Every field name starts with it, so the exact name differs from site to site. Rather than typing it, use the Copy CQL action in the search table.
#The fields
Each field takes one of two operators. Text fields match with ~ (contains). Exact-match fields use =. Each row below tells you which to use.
Field | What it holds |
|---|---|
<hash>_capable_asset_title | Title of a Capable library asset. A text field, so match it with |
<hash>_capable_asset_description | Description of a library asset. Match with |
<hash>_capable_asset_capability | Which Capable capability owns the asset, such as diagrams, markdown, images or search. It's a text field, so match it with |
<hash>_capable_asset_feature | Which feature within that capability the asset belongs to. A text field, so match it with |
<hash>_capable_asset_type | The type of asset. A text field, so match it with |
<hash>_capable_asset_category | Category of the asset. An exact-match field, so use |
<hash>_capable_asset_author | Account ID of the asset's author. An exact-match field, so use |
<hash>_capable_asset_tags | Tags on the asset. An asset can have several, and you match them with |
<hash>_capable_asset_template | Whether the asset came from a template, and if so, which one. |
<hash>_capable_asset_sourcePageId | The page the asset was created from. Watch the spelling. This name ends in |
#Related
Indexed, then searchable. In that order.
