We are trying to display assets (data records) using an asset listing page based on a certain metadata field. However, despite using the custom grouping option and specifying the desired metadata field the list still displays all assets.
It makes a group list of the correct assets (that have the metadata field) but still displays all the other assets (that do not have this metadata field).
That is the correct behaviour. You will need to find some other way of listing only the assets you want. Grouping is not designed to eliminate assets from the list but to group them.
[quote]That is the correct behaviour. You will need to find some other way of listing only the assets you want. Grouping is not designed to eliminate assets from the list but to group them.
[right][post=“14836”]<{POST_SNAPBACK}>[/post][/right][/quote]
Thanks for the reply.
Apart from a search page, how else can we filter assets based on their metadata?
Very good question. This is probably one for the feature request list, although i know that there has been some resistance to this in the past because of the performance issues that would be introduced to the asset listing if included. There are several assets that allow filtering by metadata like search folder(no front end preview though), related asset listing(uses tagging system and builds a list based on the tags of the asset you are viewing) and search. I would have to have a look at exactly what you are trying to do but my best guess would be to try a workaround where you use css to only display what is in your group and hide anything else. Maybe the dev guys might comment further.
[quote]Shane Weddell,Feb 21 2007, 11:31 AM]
Very good question. This is probably one for the feature request list, although i know that there has been some resistance to this in the past because of the performance issues that would be introduced to the asset listing if included. There are several assets that allow filtering by metadata like search folder(no front end preview though), related asset listing(uses tagging system and builds a list based on the tags of the asset you are viewing) and search. I would have to have a look at exactly what you are trying to do but my best guess would be to try a workaround where you use css to only display what is in your group and hide anything else. Maybe the dev guys might comment further.
[right][post=“14839”]<{POST_SNAPBACK}>[/post][/right][/quote]
Thanks again for the reply.
What we are trying to do is create a global links page, departmental links page and and quicklinks on a departmental level.
Our data record asset builder is customised to include metadata fields i.e URL (text), Description(text), Category(select), Quicklinks(select), Local/Departmental(select) and Global(select). The Link Title is actually the data record name.
We then want to create asset listing pages to display the the links based on either Quicklinks, Local/Departmental or Global metadata fields respectively. The Quick links asset listing will be nested in a customised design. An example of the quicklinks can be seen on http://www.dcita.gov.au/.
We also have a list of create locations (folders) for each department to create their links.
I have attached a screen capture of the asset builder page.
[attachment=173:attachment]
screen.jpg (24.5 KB)
OK, this is how i would set it up.
Instead of using metadata for the quicklinks, local and global i would create three folders for the links to be created under.
- Links
—Quicklinks
—Local
—Global
Change your asset builder to use the folders for their create locations. Putting the three locations under one root folder and using a dynamic create location would be the best. Would look a lot nicer on the create interface as well.
Set up a paint layout targeting folders and a asset listing for the layout that lists the way you want. The asset listing should have a root node of the root folder for the locations and a dynamic root node replacement of the current asset id. Then nest it into the default format in type formats in the paint layout. Set the layout to the root folder of the locations under the lookups settings screen.
I know this is a lot to take in if you havent grappled with paint layouts yet but hopefully it will be of some use to you.
[quote]OK, this is how i would set it up.
Instead of using metadata for the quicklinks, local and global i would create three folders for the links to be created under.
- Links
—Quicklinks
—Local
—Global
Change your asset builder to use the folders for their create locations. Putting the three locations under one root folder and using a dynamic create location would be the best. Would look a lot nicer on the create interface as well.
Set up a paint layout targeting folders and a asset listing for the layout that lists the way you want. The asset listing should have a root node of the root folder for the locations and a dynamic root node replacement of the current asset id. Then nest it into the default format in type formats in the paint layout. Set the layout to the root folder of the locations under the lookups settings screen.
I know this is a lot to take in if you havent grappled with paint layouts yet but hopefully it will be of some use to you.
[right][post=“14842”]<{POST_SNAPBACK}>[/post][/right][/quote]
Thanks, I will give that a crack.
[quote]OK, this is how i would set it up.
Instead of using metadata for the quicklinks, local and global i would create three folders for the links to be created under.
- Links
—Quicklinks
—Local
—Global
Change your asset builder to use the folders for their create locations. Putting the three locations under one root folder and using a dynamic create location would be the best. Would look a lot nicer on the create interface as well.
Set up a paint layout targeting folders and a asset listing for the layout that lists the way you want. The asset listing should have a root node of the root folder for the locations and a dynamic root node replacement of the current asset id. Then nest it into the default format in type formats in the paint layout. Set the layout to the root folder of the locations under the lookups settings screen.
I know this is a lot to take in if you havent grappled with paint layouts yet but hopefully it will be of some use to you.
[right][post=“14842”]<{POST_SNAPBACK}>[/post][/right][/quote]
[quote]Then nest it into the default format in type formats in the paint layout. Set the layout to the root folder of the locations under the lookups settings screen.[/quote]
Sorry shane Iam not sure I understand nesting into the default format. Do I have to do this in the Edit Content screen?
The nesting was for building the front end display. I have just sent a message to your profile so that you can email me some detail and i will contact you to talk through this one so that i can explain what i mean:)