Additional information

This section contains additional information regarding the Migration Application.

Changes in structure

Categories, metadata definitions and conversion formats are translated to their equivalent in ImageVault 4.

As albums in ImageVault 3 were used both for navigation and setting access rights they are handled a bit differently. The structure of albums will be represented as categories in ImageVault 4, since this is recommended for navigation. For each unique combination of access rights a vault is created.

Summary of migration

  • Categories translates to categories
  • Metadata will be converted into metadata definitions. “Archive dates” and “date added” translates to “date”. “Default value” and “Use as system alt-text” will be ignored.
  • Conversion formats translates to media formats. “Unsharp Mask”, “Effects” and “ICC Profiles” will be ignored.
  • Albums will be converted to a category structure, and a vault will be created for each unique combination of access rights and metadata defintions.
  • “Show”, “Use” and “View” will be translated as “View”.
  • “Move”, “Delete” or “Change” will be translated as “Contribute”
  • All data objects will be added as a media item, with the corresponding set of metadata and categories.

Translated meta data definitions

Meta data definitions in ImageVault 3 can be supplied in various languages using translation files. When migrating meta data into ImageVault 4, the originally entered meta data name will be used.

Note: This is not necessarily the same name as shown in the UI since the name shown reflects the currently selected language.

Long file names

File names migrated from ImageVault 3 will be truncated to a maximum of 50 characters (plus file extension) in ImageVault 4.

Upload albums

Any files located in the Upload albums (files that have not been organized to a specific album) will not be migrated. To include these files in the migration they should be organized and placed in an album before performing the migration.

Album descriptions

Since ImageVault 4 does not use an album structure, ImageVault 3 album descriptions will not be migrated.

Migration of Episerver content

Since the migration tool does not affect the content of Episerver this needs to be handled by the Episerver partner, assisted by Expert Services if required. This is a short summary of actions that might be required.

Page templates

Since the API is not backward compatible the page templates needs to be rewritten.

Pages using the ImageVault-property

Page templates containing the ImageVault-property, also known as ImageType, needs to replace this with a Media-property. The media referense needs to be set to the new media item. The id of the original file ca be used to identify the media item in ImageVault 4.

Internal format of the ImageVault-property is "url to image~id~alt text"

Note: The migration tool does not include edited files in the migration process. Though of course theese can be added programatically using tha API if required..


Needs to be parsed and replaced with a new url to ImageVault 4. Keep in mind to se a maximum size restriction on the images when the urls are created. Also se the note regarding edited files above.

The format of the urls are "/ImageVaultFiles/id1/cf1/filename.jpg" or "/ImageVault/Images/.../ImageVaultHandler.aspx"


ImageVaultFileList should be replaced using a MediaList-property.

Internal format is a , separated list of id:s

Album, Complex Media and ImageVaultURL

These properties does not have a stratight forward transalation since ImageVault 4 works a bit different. Albums-property could be replaced by a category, ComplexMedia might be replaced with a Media-property using the YouTube connector etc.

Known bugs

Album rights must be set

All albums in ImageVault 3 must have at least one access right applied. If an album exists that do not have any rights at all, the vault analysis will fail. The current workaround is to apply any right (it does not matter which one) to albums that do not have any rights before migrating.

comments powered by Disqus