Hi all,
I have been looking into leveraging the DAM to allow for content providers to attach specific global meta data to particular assets. Perhaps I am thinking incorrectly on a strategic level, so any alternate approaches are appreciated as well.
The problem is, we have a set of affiliates which are listed out in the dam, containing a prescribed set of images/assets/links. These providers can be viewed via pages in CQ5, but also within a set of mobile apps for droid and iPhone.
The iPhone and droid crews are currently accessing a set of JSON files to get the required metadata, which is placed within the DAM. I think is a very nasty solution, as this data will not be filled in by developers, but rather an affiliate on ramp team. (Essentially a team of Sales staff).
What I am looking into now, is to store the additional metadata on an affiliate folder as JCR metadata, which I have successfully done, but only by generically customizing the properties for folders/images. Ie, for folders, right click -> properties.
You can add additional items to the basic properties tab by adding the relevant component nodes to /libs/foundation/components/primary/sling/OrderedFolder/tab_basic/items, even add entirely new tabs by creating a new node at the /libs/foundation/components/primary/sling/OrderedFolder level (i.e. myTab) and then specifying it in the dialog /libs/foundation/components/primary/sling/OrderedFolder/dialog/items/tabs/items
The problem is that the tab/extra question fields will be universally displayed, and are not folder dependant, so they appear in every folder context.
What I would love to do, is to have it so that if you access http://localhost:4502/damadmin#/content/dam/affiliate/affiliateA you get your newly customized options/panels etc, but if you were to view properties on http://localhost:4502/damadmin#/content/dam/affiliate you would not get any additional questions being asked.
Any help would be greatly appreciated.