To create a filter, a client must fetch specific data from indexes (filter names, links to sub-indexes, etc). The data is nested in specific <A> tags. Each such tag provides information on an APS Catalog resource. The tag content is the human-readable resource name, the href attribute stores a link to the resource, and the ID/class attributes identify the tag. In most cases, the resource is a sub-index, and its name is used as the name of a filter, or the name of an APS Catalog hierarchy level. However, some indexes provide links to other resources like packages, package certificates, etc.
This section explains what expressions can be used to fetch these <A> tags from indexes. The section starts with parsing the System index to show that all APS Catalog resources can be recursively derived from this index.
Getting data from the Service index
Information on Repository indexes can be extracted from the Service index.
Expression: //a[@class='repository']
For details on the Service index XML structure, refer to the Service Index section.
Getting data from a Repository index
Information on Vendor indexes can be extracted from a Repository index.
Expression: //a[@class='vendor']
For details on the Repository index XML structure, refer to the Repository Index section .
Getting data from a Vendor index
Information on Application indexes can be extracted from a Vendor index.
Expression: //a[@class='application']
For details on the Vendor index XML structure, refer to the Vendor Index section.
Getting data from an Application index
Information on Application Version indexes can be extracted from an Application index.
Expression: //a[@class='version']
For details on an Application index XML structure, refer to the Application Index section.
Getting data from an Application Version index
Information on Package indexes can be extracted from an Application Version index.
Expression: //a[@class='packager']
For details on the Application version index XML structure, refer to the Application Version Index section.
Getting data from a Package index
From a Package index, a client can extract the following information:
For details on the Package index XML structure, refer to the Package Index section.
Getting data from a Package Resources index
From a Package resources index, a client can extract the following data:
For details on the Package resources index XML structure, refer to the Package Resources Index section.
Getting a parent index link
To enable end users to return to upper level of APS Catalog hierarchy, a client can extract a parent index link. This link can be retrieved from all indexes except for the System index.
XPATH expression: //a[@id='parentLink']
Previous page
Next page
Locate page