Add metadata to a Management of Change (MoC) package

The DNAPackage (dnapackage) command line tool allows you to add a field with text to an existing package.

Note: You must have write privileges to the package you want to add metadata to or an error will be displayed.

To add metadata to a package

1. On the desktop, double-click the Windows PowerShell for DNA shortcut.

   Windows PowerShell for DNA opens.

2. Execute the following commands:

   set-silo RealTime

    dnapackage metadata --title <package title> --add <value> [--name <element name>] [--dalfolder <DAL configuration folder> --username <remote username> --password <remote password>]

   Where:

   • --title< package title> is mandatory for each command and refers to a valid package.

   • --add <value> is mandatory valid text to be added to the provided metadata element (for example, –-add "My package comment"). This element must not contain an empty value (for example, --add " " will result in an error).

     Note: If the package already contains a metadata element, the text is appended to a list of any pre-existing text.

   • --name <element name> is the name of the metadata element to store text under (for example, –-name "release notes").

     Note: If the <element name> is not provided, the text will be stored under a default metadata element named comments.

   • --dalfolder <DAL configuration folder> is the DAL configuration folder name on the remote system you are trying to connect to (for example, --dalfolder systemName\control_room).

   • --username <remote username> is the username of the user on the remote system you are trying to connect to.

   • --password <remote password> is the password of the user on the remote system you are trying to connect to.

     Note: The --dalfolder <DAL configuration folder>, --username <remote username>, and --password <remote password> parameters do not need to be included if you are adding metadata to a package on the same server as the MOCOrchestrator service. These parameters are mandatory if you are adding metadata to a package on any other server that does not have the MOCOrchestrator service. For example, adding metadata to a package on the Production MoC zone would require remote DAL configuration to connect to the MOCOrchestrator service.