Adding Content to APS Catalog

A client can let end users do the following:

• Add a package to APS Catalog
• Add a certificate to a package

This chapter explains how to build this capability into a client.

Adding a package

The sequence of actions performed by a client and a user to add a package to APS Catalog is as follows:

1. The user chooses an appropriate repository for the package, and passes the control to the client.
2. The client does the following:
   1. Retrieves the Repository index.
   2. Parses the index for a specific form (//form[@name='packageSubmitForm'])
   3. Displays this form to end users. Form fields indicate information required for adding the package.
      Before displaying this form, the client can transform it to meet the UI design requirements.
3. The user fills the form and submits it to APS Catalog.

Adding a package certificate

The sequence of actions performed by a client and a user to add a certificate to a package is as follows:

1. The user chooses an appropriate package in APS Catalog, and passes the control to the client.
2. The client does the following:
   1. Retrieves the Package index.
   2. Parses the index for a specific form (//form[@name='certificateSubmitForm '])
   3. Displays this form to end users. Form fields indicate information required for adding the package.
      Before displaying this form, the client can transform it to meet the UI design requirements.
3. The user fills the form and submits it to APS Catalog.