Group Metadata

Trying to extract a Root Node's metadata content from within an asset listings group format.


Need something like below to get "Description" contents:


    %group_metadata_Description%


Please help.

[quote]
Trying to extract a Root Node's metadata content from within an asset listings group format.



Need something like below to get "Description" contents:


    %group_metadata_Description%


Please help.
[/quote]

What kind of grouping are you using? Is it Metadata Grouping?
If yes and if the Metadata Field selected for grouping is infact "Description" then you can use %group_name% keyword to get the metadata value.
If not doing the above...I'd like to know how the listing is configured.


Ash

[quote]
What kind of grouping are you using? Is it Metadata Grouping?

If yes and if the Metadata Field selected for grouping is infact "Description" then you can use %group_name% keyword to get the metadata value.

If not doing the above…I'd like to know how the listing is configured.





Ash

[/quote]



Hi Ash, I was grouping my list via the default grouping which yielded the desired list of assets required.

When I saw that you mentioned the above I added metadata grouping also, which has now made my asset-list a group of descriptions.



How would I format to retain my original asset list of assets with only the metadata of assets' parent included?

[quote]
I was grouping my list via the default grouping which yielded the desired list of assets required.

[/quote]



What do you mean by default grouping?



If you just want to show a parents metadata for every listed asset, you could look into using list_current_asset_id: http://manuals.matrix.squizsuite.net/asset-listing/chapters/list-current-asset-id

I guess he means the order, rather than some kind of contextual "group". I could of course be wrong!

[quote]
I guess he means the order, rather than some kind of contextual "group". I could of course be wrong!

[/quote]



Sorry to confuse, I setup grouping by setting the 'List Format' to 'Custom Grouping' via the asset's detail screen. As I didn't specify a type via the right-click grouping options, I had assumed this to be default.

[quote]
Sorry to confuse, I setup grouping by setting the 'List Format' to 'Custom Grouping' via the asset's detail screen. As I didn't specify a type via the right-click grouping options, I had assumed this to be default.

[/quote]



Hi Paul,

That clears up the way listing is configured. Unfortunately using 'default' or no grouping has a different logic of grouping assets to that of grouping by metadata and hence the different format of the results returned for the asset list.

If you go back to your previous setup (which was giving you desired asset listing) and use what Nic suggested, if you have dynamic setup with dynamic root node or even multiple root nodes, you should be able to display the metadata of root nodes. Or if you have just a single root node and want to display its Metadata you could just use keyword like %globals_asset_metadata_Description:ROOT_NODE_ID_HERE% that should do the trick.



Hope that helps.

Ash

[quote]
Hi Paul,

That clears up the way listing is configured. Unfortunately using 'default' or no grouping has a different logic of grouping assets to that of grouping by metadata and hence the different format of the results returned for the asset list.

If you go back to your previous setup (which was giving you desired asset listing) and use what Nic suggested, if you have dynamic setup with dynamic root node or even multiple root nodes, you should be able to display the metadata of root nodes. Or if you have just a single root node and want to display its Metadata you could just use keyword like %globals_asset_metadata_Description:ROOT_NODE_ID_HERE% that should do the trick.



Hope that helps.

Ash

[/quote]





Thanks Ash! I successfully used the code you suggested previously (%globals_asset_metadata_Description:ROOT_NODE_ID_HERE%) but decided I didn't want to hard-code the asset IDs, instead I thought it would be better to grab the root node ID via a meta data field (so non techy users can easily change these settings if required without coding). But this is where I'm having the problems.



To throw another option out there… Is it possible to concatenate keywords?



to achieve something like:


    %globals_asset_metadata_Description% + %root_asset_assetid%

[quote]
Thanks Ash! I successfully used the code you suggested previously (%globals_asset_metadata_Description:ROOT_NODE_ID_HERE%) but decided I didn't want to hard-code the asset IDs, instead I thought it would be better to grab the root node ID via a meta data field (so non techy users can easily change these settings if required without coding). But this is where I'm having the problems.



To throw another option out there… Is it possible to concatenate keywords?



to achieve something like:


    %globals_asset_metadata_Description% + %root_asset_assetid%

[/quote]



Hi,

I get what you are trying to do above. but you won't be able to concat/nest the 2 keywords. the best bet I can think of is as follows (provided you are on a version that supports using keyword modifiers on keywords in Page contents) :


    %root_nodes^as_asset:asset_metadata_Description%


There might be a better way to do it, but I being a developer wouldn't have too much idea. An Implementer who might read this Conversation might able to help you out if the above doesn't work for you.

Hope this helps.

Ash

[quote]
Hi,

I get what you are trying to do above. but you won't be able to concat/nest the 2 keywords. the best bet I can think of is as follows (provided you are on a version that supports using keyword modifiers on keywords in Page contents) :


    %root_nodes^as_asset:asset_metadata_Description%


There might be a better way to do it, but I being a developer wouldn't have too much idea. An Implementer who might read this Conversation might able to help you out if the above doesn't work for you.

Hope this helps.

Ash
[/quote]

Thanks for your assistance Ash/All, I discovered that creating a paint layout of the formatted meta data I required and applying it to a folder of linked assets achieved what I needed.

v