Short version:
We need to have a metadata value applied to an asset and then any asset created under that one needs to inherit the same value. It looks like this is available in 3.18 but is there any way to do this with Matrix (without using javascripting anywhere) to achieve the same result in 3.16.6? Or to automatically apply the name of the parent asset to a metadata value?
Long version:
We have a folder containing a large number of folders (one each for a specific office). We need the office name applied to a metadata value automatically within Matrix to every file placed inside the office folder. Lineage we can't make use of for our end use of the metadata as it contains more info than is needed, the office name itself needs to be the sole content of this value. As there is no tree structure inside each folder (ie all files are at the same level) some way of grabbing the asset name of the parent via a keyword would give us what we need. Otherwise we can use the asset name keyword on the folder itself and would need some way of having that value applied automatically to everything placed inside the folder. All in V3.16.6.
Is this possible with what V3.16.6 provides without needing scripting or customising Matrix etc.
Our fallback is to make a metadata schema for each office and apply that to the folders to force a single default value but it isn't an elegant solution but it would achieve the outcome. But if anyone can think of some other approach that would be more elegant I'd be happy to hear it.
cheers
steve
You can use a trigger to listen for the create or link under the folder and set the metadata value with the trigger. This would be a lot less maintenance on the metadata schema front.
that would still need a separate trigger though to set each different office as the value wouldn't it?
Yes, unfortunately, but once they are there everything is automated. How many different folders do you want to apply it to?
The Metadata Field Value can be passed in through a GET or POST request, so this can be controlled with one trigger.
This can be done by configuring a parameter in the "Parameter / Source" table at the bottom of the "Set Metadata Value" action.
[quote]The Metadata Field Value can be passed in through a GET or POST request, so this can be controlled with one trigger.
This can be done by configuring a parameter in the "Parameter / Source" table at the bottom of the "Set Metadata Value" action.[/quote]
Yes, true, and i nearly edited my previous post. The only gotcha is what you grab to use for the value and what in terms of 3.16 is available. The key would be to dynamically grab a value from the folder the file is being created or linked to. If you have an asset builder that is being used then you are probably in luck and can control it all there but if everything is admin interface controlled then it is a lot trickier.
What end use does the metadata value have once set on the file itself? There may be other ways to skin the cat.
essentially its a calendar list that we are putting together. matrix's calendar can't provide the type of end user functionality and display the way our client wants, but we can do it with asset listers and custom grouping. so we need to be able to group by dates (showing the dates as a heading, sort and constrain to date ranges) and also group things by offices (and limit to a single office). we've already been through the cat skinning stage and the asset lister solution would be best for what we and our client needs and if were able to upgrade to 3.18 (we've only just gone to 3.16) it would be nice end easy (my guess though is we wont upgrade until some oracle issues are ironed out in 3.20 and jump to that).
with the metadata applied we can make good use of listers for different ways to present the same data and also allow us to put together a simple screen for the client to add and remove items quickly. ongoing management would be virtually zero.
the trigger option i played with looks like we can use that nicely and achieve the same result (the asset builder uses a create location dropdown so we can pop that choice into a variable and use the trigger to pop that into the metadata.
cheers
I would say you just skinned all 9 layers of the cat:)