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

(None) and (Get Original) and "Normalization""

leala_abbott

If you use the (none) task to retrieve an image asset, the image format may get "normalized" by MediaBin (as stated in the MB 4.5.3 AssetServer Administration Guide, p131). Can anyone describe in any detail what this "normalization" entails?

Find more posts tagged with

Comments

CalvinFold

The only difference I know of is that (None) supposedly grabs the newest version if there are multiple versions and (Get Original) will get the very first version that was uploaded, if there are multiple versions.

Well, and (Get Original) works around a downloading bug with PSD files. Smiley Wink

I'm curious if there are other considerations I don't know about…

lyman

Both tasks always act on the latest version!

The (Get Original) will make a copy of the file that was inserted in the last check-in. The main difference is that (None) will merge changes made to the metadata into the asset. Thus, for example, if you insert a JPEG, and then use the MediaBin client to edit the "Photoshop Title" field and get the asset via (None), if you open the file in Photoshop and look at File Info you will see a value for the title that reflects your edits.

Some formats in MediaBin such as Vector EPS and Multimedia are to editable in this sense and they will produce the exact same result with either task. If you do not care about metadata edits (Get Original0 is always faster!

Cheers,

Lyman Hurd