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

Metadata

ContentMngr

Hi,

We're in the planning stages of a MediaBin installation. A lot of our designers create assets in CS3 and assign metadata/keywords in the Adobe Bridge. Will that data carry into MediaBin automatically when those assets get uploaded?

Thanks,
Kimberly

Find more posts tagged with

Comments

iwTech

Hi,

We're in the planning stages of a MediaBin installation. A lot of our designers create assets in CS3 and assign metadata/keywords in the Adobe Bridge. Will that data carry into MediaBin automatically when those assets get uploaded?

Thanks,
Kimberly

Hi Kimberly ,

I am sure media Bin does not support Adobe Bride ,may be the futue versions

(ask support for confirmation) ...

But you can try XMP mapping

Short note from support - XMP Metadata Support

Adobe’s Extensible Metadata Platform (XMP) allows users to embed arbitrary metadata
into standard format files such as Adobe Photoshop (PSD), JPEG, Tiff, and Photoshop EPS.
Previous versions of MediaBin extracted only some of these fields as metadata fields within
MediaBin and also merged edits to those fields back into the XMP data when a file
was retrieved from MediaBin. As of the 4.5.2.5 release, however, MediaBin supports the
mapping of arbitrary XMP fields to MediaBin metadata fields and vice versa
(the mapping of MediaBin custom metadata fields to external XMP data.

Read more here

-Vin

Document1.docx

lyman

There really is not such a thing as "Bridge" metadata. Bridege is an application. XMP is Adobe's method of coding metadata and so any field there can be mapped into MediaBin if it is not already. A large number of metadata fields in XML have default bindings and so I would experiment before adding new bindings (although adding new ones is within your options. The custom XMP mappings override the default XMP mappings).

Cheers,

Lyman Hurd

Phead2

Most (probably all) of the metadata fields you edit in bridge will carry into mediabin the same as if you edited them in photoshop (look at the photoshop metadata fields in mediabin).

lyman

If you look at your asset in Photoshop and go to the File Info window, and hit "Advanced" it lists the XMP metadata (well there are some caveats with that but not in this use case). Each of these metadata fields is either already mapped to a MB metadata field, or it is possible to add a custom metadata field and map vvia the XMPMapping.xml file documented in the Admin Guide.

Cheers,

Lyman Hurd

PS For the sake of completeness I should add that the caveat is that Adobe will display among the XMP metadata fields, metadata it has imported from other types of field, e.g., EXIF and it displays them as converted to XMP. MediaBin can only deal with XMP metadata that is already in the file. On some occasions this has caused confusion because Photoshop is displaying more XMP metadata than is really there. This should not be relevant to your use case! Bridge certainly does not use data paths other than XMP.