Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Mediabin and Teamsite
keerthikm
Hello Gurus,
We have a situation where our client wants to have Mediabin for managing all his digital assets and Teamsite to use these assets via ECM connector 2.0.
When the users select the assets from Medibin and generate the HTML Pages in Teamsite for deployment how do we ensure that the corresponding asset in mediabin gets deployed to the delivery server?
We do not want to import the asset into teamsite as this will be a duplication.
Are there any best practices that we are missing. Please enlighten.
Keerthi
Find more posts tagged with
Comments
cliff1
The design principal of the ECM 2.0 solution is to import a "web appropriate" rendition of the file into TeamSite. The files is deployed from TeamSite to the production system in the same way that you deploy the rest of the TeamSite files.
The truth of the matter is that you are going to "duplicate" the asset when you push it out to the production system. If you think of TeamSite as the staging system where you aggregate and provision your web-ready content, it may seem more palatable. The imported rendition will have a "back pointer" to MediaBin and the UI will treat the file as a special imported file and will warn the user not to make edits in TeamSite.
You could design a sophisticated workflow and deployment in TeamSite that allowed you to meet your original request, but this would involve a fair amount of custom code and would not make use of TeamSite features like previewing and site versioning.
-Cliff