Documentation Center

Migrating metadata properties to the taxonomy (upgrade only)

After the upgrade to Tridion Docs 15.1, you may want to migrate some LOV-based metadata properties to the taxonomy.

Before you begin

To perform this task, you must be a user who has the Taxonomy Management privilege.

About this task

As from Tridion Docs 15.1, Content Manager has a configuration file for taxonomies that, by default, contains a simple preconfigured taxonomy. This taxonomy defines a number of metadata properties, including "Product family name" and "Product release name."

"Product family name" and "Product release name" are also lists of values (LOVs) (found in the dropdown under Settings > System > Lists of values in Organize Space. If you have used these metadata properties in your implementation, you should now use two scripts to make them part of the taxonomy, instead of lists of values:
  • MigrateToIshTaxonomies.ps1 produces a new XML configuration for you to copy-paste in the Settings > XML Settings > Taxonomies screen.
  • UpdateMBFieldsWithConcepts.ps1 actually updates the metadata fields of all your publications.

Procedure

  1. Access your Tridion Docs installation artifacts and go to the folder InfoShare\App\Database\InfoShareCM\Common\DatabaseIndependent\Examples\CreateInternalTaxonomySyncWithLovs\.
  2. Invoke the migration script MigrateToIshTaxonomies.ps1 as follows:
    .\MigrateToIshTaxonomies.ps1 -WsBaseUrl "BASEURL" -OutputDir "OUTDIR" -Mappings @{
      "GOAL"=""
      "AUDIENCE"=""
      "PRODUCTFAMILY"="DPRODUCTFAMILYNAME"
      "PRODUCTRELEASE"="DPRODUCTRELEASENAME"
    }
    where:
    • BASEURL is the web service URL of Content Manager, for example, https://ish.example.com/ISHWS/
    • OUTDIR is a writable folder location to which the script can write its output, for example, c:\Temp
    The script runs and produces an output file in the output directory.
  3. In Organize Space, go to Settings > XML Settings > Taxonomies.
  4. Copy-paste the output of the migration script into the content area, overwriting the content you see.
  5. Select Save to apply your changes.
  6. In the same folder, run the migration script UpdateMBFieldsWithConcepts.ps1.
    The script takes the existing values for the old "Product family name" and "Product release name " metadata fields and sets those values as the values of the corresponding new fields.
  7. Republish any publications that use the migrated metadata properties.