What are two ways to customize Knowledge Accelerators to meet specific requirements?

IBM recommends two primary strategies for customizing Knowledge Accelerators to prevent custom modifications from being overwritten by future updates. The first approach involves creating a separate, parallel vocabulary (often called an "enterprise vocabulary") within Watson Knowledge Catalog. This keeps the original Knowledge Accelerator content pristine in its own categories while custom terms are developed separately and linked where necessary. The second approach involves using a Cloud Pak for Data project as a staging area. In this method, the Knowledge Accelerator CSV files are modified or merged with custom content within the isolated project environment before being imported and published to the catalog.

A. Changing Knowledge Accelerator content inline is strongly discouraged as any updates to the accelerator from IBM would overwrite these direct modifications.

C. While using a GitHub repository is a valid version control practice, it is an external process and not a prescribed customization method within the Cloud Pak for Data platform itself.

E. "Namespace" is not the correct terminology for the primary organizational structure in Watson Knowledge Catalog; governance artifacts are organized into categories and glossaries.

1. IBM Cloud Pak for Data 4.8 Documentation

"Customizing Knowledge Accelerators": This document outlines the two main approaches. It explicitly states

"It is recommended that you do not change the imported Knowledge Accelerator content. Instead

create a new category at the same level as the Knowledge Accelerators categories... In this new category

you can create your own business terms". This directly supports option D's concept of a separate vocabulary.

Reference: IBM. (2023). Customizing Knowledge Accelerators. IBM Cloud Pak for Data 4.8 Documentation. (Accessed under Watson Knowledge Catalog -> Business glossary).

2. IBM Cloud Pak for Data 4.8 Documentation

"Importing governance artifacts": This section describes the process of importing artifacts

including the option to import them into a project first. It states

"You can import governance artifacts from a file that is in CSV format... You can import a CSV file to a project or a category." Using a project as a staging area for preparing customized content before final import into the catalog is a standard workflow

which supports the methodology described in option B.

Reference: IBM. (2023). Importing governance artifacts. IBM Cloud Pak for Data 4.8 Documentation. (Accessed under Watson Knowledge Catalog -> Managing governance artifacts).