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

TeamSite integration with MediaBin

windy

I am hoping that somene can shed some light on this....

When the MediaBin connector is configured and images are imported into TeamSite (via Data Capture Forms) from MediaBin,

1. are the images physically stored in the content store? I'm asking because when you import images via the connector, it does import the image into a location within teamsite.

2. Are the images in TeamSite just a virtual copy of the original image in MediaBin?

3. is there a was to disable the "From file system" option of the import file feaure. We would like to limit image imports to MediaBin?

Find more posts tagged with

Comments

ISCBorisB

I am hoping that somene can shed some light on this....

When the MediaBin connector is configured and images are imported into TeamSite (via Data Capture Forms) from MediaBin,

1. are the images physically stored in the content store? I'm asking because when you import images via the connector, it does import the image into a location within teamsite.

2. Are the images in TeamSite just a virtual copy of the original image in MediaBin?

3. is there a was to disable the "From file system" option of the import file feaure. We would like to limit image imports to MediaBin?

1. Yes, ECM creates physical Backing Store Object referencing Image Version(s)

2. No, see above. Upon Import completion TS has it's own versioned File Copy

3. Not in any supported manner

windy

1. Yes, ECM creates physical Backing Store Object referencing Image Version(s)

2. No, see above. Upon Import completion TS has it's own versioned File Copy

4. Not in any supported manner

Thanks ISCBoris. I'm just thinking ahead as to how to prevent users from importing images from locations other than MediaBin.

nipper

Thanks ISCBoris. I'm just thinking ahead as to how to prevent users from importing images from locations other than MediaBin.

Workflow

Each MB installed object will have an OID as an EA. You can check that in a workflow step

ISCBorisB

Workflow

Each MB installed object will have an OID as an EA. You can check that in a workflow step

Yep. It'll also have imported MB Attributes, TS EA name is MediaBin/Metadata. Format is an XML record with
<attribute> subtags that in turn contain name/value Tags.