nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

ECM conector 2.0

Enthu

ECM connector 2.0 compatible with MB4.5.2? Is there a way so that we can get away with the directory which store imported mediabin assets so that we can directly access assets from mediabin?

Find more posts tagged with

Comments

lyman

I am almost certain that the answer to the first question is "yes" but I emailed it to an expert for confirmation!

As to the second, the backing store for the files in MediaBin is not in any order that would make sense outside MediaBin. the structure is contained in the database and not mirrored in any humanly readable form, so we strongly discourage any access to files except via the API's.

Cheers,

Lyman Hurd

cliff1

Yes, the ECM Connector is compatible with MB 4.5.2, 4.5.3 and the recently released 4.6.

cliff1

I'm not sure I understand the 2nd part of the question. Lyman provided an answer based on one interpretation and I will try a different angle. From what I understand of your question, you would like to leave the file in MediaBin instead of importing a rendition (or renditions) into TeamSite, is that correct?

If my interpretation is correct, the answer is a highly qualified "yes". The question I would ask is what do you plan to do with the selected asset? If you want to build a web page that includes a rendition of the asset that can be deployed to your runtime environment, you certainly need to import a rendition into TeamSite so that you can preview and deploy it.

If you don't want to import the file into TeamSite, you have a couple of options listed below (I'm sure you can add more variations). The example templates that we ship include the "deferred import" mode. When the user selects the asset, the GUID is stored in the DCR (no image is retrieved into TeamSite). The deferred import example incudes a presentation template that fetches (i.e., imports into TeamSite) a rendition when the user "previews" or "generates" the web page. However, your presentation logic can do whatever it wants with the GUID.

1) You can create a webpage that has a link to the MB web UI for the seleted asset. Clicking the link will take the user to the MB UI (where they will have to login). The webpage won't include an image, just a link and your website users must have access to the MB web ui.

2) Create a more sophisticated dynamic page that uses the MB API (soap or com) to dynamically fetch the appropriate rendition when the page is built. Depending on the assets and retrieval task, you could run into performance issues with this approach.

I hope this helps.