Is it possible to use the new global asset keywords, for assets with ID like 8880:16 (Thesaurus Term)? I have tried %globals_asset_attribute_name:8880:16% but this does not work. Was this keyword not created with these in mind?
I suspect it wasn't, but only the developers would know for sure. They'll be back on Monday. :) I have a lot of time waiting around in airports today, so I may be able to poke at the code and check for sure too.
The keyword was not designed to work with shadow assets. If it works, it is just a coincidence.
Ah bummer!
Out of interest, why would you want to show a thesaurus term as a keyword anyway?
I am building the admin interface for what we are calling the "Announcement Hub". This will be the interface where all of our announcements for our campus will be received. From this interface, the admin (Student Services in this case) will see all the events, and be able to change them from under construction to live once they have approved them.
When the user creates and event, they choose what kind of Announcement it is. Faculty/Staff, Student Only, Emergency, etc., so when the use creates the event, they apply the appropriate tags to the announcement, so that I can use related asset listings to list that event in the appropriate place (or with the appropriate styles, etc.). The admin will see all of these announcements, and the information that each contents. THIS is where I want the tag to show up, because the admin need to see the name of the tag so they know if it is appropriate (And in the normal "Announcement Hub" we would like to have an ALL listing, with tag names there as well). If it is not, they will choose to remove it, and select the appropriate tag.
Let me know if you want a better explanation or an pictorial example.
Avi, I did think of an alternate solution that may work, as I was sitting on the plane today.
I could have multiple create locations, which each would be a folder or asset with a metadata schema applied, along with a tag that would cascade. The tag would coorispond to the folder, e.g. Faculty/Staff. Therefore, the newly created Announcement would pick up the correct tag, along with picking up the metadata field with a default value of its folder name. Then I could display the location using the metadata rather than the tag. The only problem I see here is that when tags are cascaded, THEN moved, they keep that tag the it picked up from its parent, even when it is moved. So it I moved it under another location with a tag that cascades, it would now have 2 tags. Is this the intended behavior of this? As I was sure that in other cases of cascading the child looses the attribute when moved from under their parent.
Triggers could then be used to unlink an announcement from a folder and moved to a new folder, where it would pick up the new metadata and tags.
Just a thought I was working on…