Data Dictionary Builder

The Data Dictionary Builder is the specific tool used to create a new data dictionary. The default location for the executable is C:\Program Files (x86)\Wolters Kluwer\Expere Server Tools\DataDictionaryImport.

The command line to build a new data dictionary is as follows:

DataDictionaryBuilder {-create | -validate | -continue [-ddOutputPath path]}

Table 1. Arguments
Argument	Definition
Global Options
-script	Full, relative or current path and filename of a script file with switches.
-ddPath	Full, relative or current path and filename of the data dictionary to create or open if continuing a previous build with continueBuild or trimEDDV commands.
-ddOutputPath	Full, relative or current path and filename of the data dictionary to create when continuing a previous build with continueBuild or trimEDDV commands. Usage: -ddPath "<PathToEDDDVFile.eddv>"
-ddBuildContentPath	Dictionary level build content path. This applies to each organization added in a multiple organization dictionary.
-ddRepositoryPath	Dictionary level Repository of source REQ files path. This applies to each organization added in a multiple organization dictionary.
-ddOutlinePath	Dictionary level HTML Outline path. This applies to each organization added in a multiple organization dictionary.
-schema	The schema type this dictionary is based on: ExpereTxn (default) or VMPMISMO.
-setType	Optional string description of this dictionary.
-copyRight	Optional copyright string. Usage: -copyright "<CopyRight>"
-url	Optional endpoint Url to validate against.
-addXpaths	Switch to import all additional data points defined in the master schema.
-xldd	Path to the MS Access db or dictionary xml for additional attribute metadata. Usage: -xldd "<PathToWorkingDictionary.xml>"
-enumDesc	Path to Enum.xml (ExpereTxn only) for additional enumeration metadata.
-attributeCustomInfoAdd	Path to file defining up to 9 additional custom metadata attributes. Usage: -attributeCustomInfoAdd "<PathToCSVFile.csv>"
-generateDeprecatedDataReport	Produce a deprecated data report on the built EDDV file.
-updateFileNames	Populate the Document Details tab with REQ file names.
DataDictionaryBuilder Commands
-lineOfBusinessIDs	A semicolon separated list of LOB IDs, as defined in the PHAS file Phases element, LineOfBusinessID attribute.
-create	Creates new data dictionary
-continueBuild	Appends to an existing data dictionary and creates a new dictionary. Both XLS and CSV file formats can be used. This allows you to extend an existing eddv file with custom attribute values.
-addonsPath	Specifies the path to the built addon document content.
Create and ContinueBuild common options for each organization
-orgAdd	Adds an organization to the precedence structure /OrgName: Specifies the organization to import REQ files into /OrgID: Specifies the ID of the organization to import. /OrgDescription: Specifies the description of the organization to import /OrgParentName: Specifies the name of the parent organization. Left blank for the root organization.
-orgContent	Builds by pulling content from file system. /OrgName: Specifies the organization to import REQ files into. /path: Path to find built content to import. Not needed if setting ddBuildContentPath.
-orgRequirements	Creates DocumentRequirements tab imports REQ files /includeChangeNotes: Specifies to include change notes when importing REQ files. /includeLOBandPhase: Specifies to include Line of Business and phase information on for the Document Details tab when importing REQ files. /OrgName: Specifies the organization to import REQ files into. /path: Path to the source REQ files to import. Not needed if setting ddRepositoryPath. /outlinePath: Path to find matching HTML outlines to import for dynamic documents. /buildSharedContentRefTree: Specify to include content references data when importing REQ files.

Note: When using the continueBuild -buildAddons, and -addonsPath you will only see reports on items that were added to the EDDV file. It does NOT validate organization structure or Autoselection Rules.

Default Data Support

The Data Dictionary Builder supports Default Data documents. Each Default Data document has a LineOfBusiness (LOB) property, and Default Data documents are grouped within the Data Dictionary according to that property.

Within the .EDDV file there are packages for each line of business (filename: DD.[LOB], where [LOB] represents the name attribute in the phase file). While these packages are not functional, they act as placeholders for attaching Default Data documents. When the Default Data documents are attached, they appear as documents belonging to the package. However, unlike the package, the documents are fully processed including attributes, document requirements and document detail information.