Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
ECM connector and Mediabin issue
wajeeth
Hi,
In our project, we are integrating mediabin with Teamsite through ECM connector. Here the directory structure of Mediabin and Teamsite are same i.e when the user try to upload the files or images into the Mediabin, it should directly reflected into the Teamsite folder. For example if user uploaded the files into the directory structure
/MBRoot/level1/level2/levell3/assets/marketing in Mediabin, the same should be reflected into the Teamsite folder structure
/MBRoot/level1/level2/levell3/assets/marketing/.
In OOTB, i have seen that it is reflecting into the teamsite workarea as per the folder given into the ECM connector.
Mediabin Version : 4.6
Teamsite Version : 6.7.1
ECM connector : 2.0
Livesite version : 3.0
Can you tell me that whether it will be done through configuration with the help of Task in Mediabin or else through customization. Please reply asap.
Thanks and Regards,
Wajeeth Hussain
Polaris Software Ltd
9963448242
Find more posts tagged with
Comments
BrianMeek
You can setup the top-level MediaBin folder you want to replicate in TeamSite as a hot folder, and configure it to push any new assets & subfolders (and updates) to TeamSite via a UNC path to the TeamSite workarea of choice. Presumably, you may want to define a retrieval task to convert the source files to a JPEG or something, but the same task (or tasks) would be applied to all assets heading for TeamSite.
A caveat here is that the MediaBin-related metadata you see as extended attributes in TeamSite (applied by the ECM connector) won't be there. You would need to write a custom script to do that.
The other approach would be to setup a Deployment Agent project to push content to TeamSite. This wouldn't be instantaneous like the hot folder approach (DA projects are scheduled to run periodically), but you could apply selective logic regarding what assets are pushed and how they are transformed before they're placed within TeamSite. Again, the asset metadata to extended attributes would require customization.
-- brian
lyman
You might want to post in the Mediabin Product Line group. That is where this sort of issue is primarily discussed. Alao, it helps to post cross-product questions in the TeamSite forums as well.
Cheers,
Lyman Hurd