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; } } }

Restricting file types in MB browser

rajit

Is there a way to restrict the file types (file extensions) that are shown in a MediaBin browser (ECM Connector) in the DCTs. Like we control the file types that can be selected in a regular file browser using the 'extns' attribute, I am wondering if there is a way to achieve this for MediaBin browser as well.

Any inputs in this regard is appreciated.

Rajit

Find more posts tagged with

Comments

cliff1

No, there is no way to specify a specific list of file types. If your MB hierarchy happens to segregate by type, you can use the ceiling directory option to keep users to a specific subtree.

I'm not completely up to speed on some of the cool MB features (I'm in the TeamSite eng group), but I thought there was a way to build a hierarchy that is essentially links to files in their "real" location. If so, perhaps it would be possible to easily construct a tree in this manor and restrict the DCT to this tree. Need some help from the MB experts to know if this is viable.

-Cliff

CalvinFold

I'm not completely up to speed on some of the cool MB features (I'm in the TeamSite eng group), but I thought there was a way to build a hierarchy that is essentially links to files in their "real" location. If so, perhaps it would be possible to easily construct a tree in this manor and restrict the DCT to this tree. Need some help from the MB experts to know if this is viable.

You can create References via the Copy feature, which in OS parlance is an "alias" or "shortcut" within MediaBin.

They are a bit tedious to create and manage though, I can't imagine creating or managing whole trees or large-scale sets of References though. *ick*

cliff1

Thanks for the details. Sounds like it would only work if you had a small set of assets to manage. The only other option that occurred to me is using permissions. Depending on how you configure the ECM Connector, it can log in as a specific (proxy) user or as the actual end user. Setting permissions in MB to only show the desired files to the TeamSite user(s) might work. I believe (but I'm not 100% sure) that permission in MB are folder based, so again we are back to segregating the downloadable assets by folder....