Browse Tree
Users can browse the Geoportal resource catalog. User access the browsing structure through a Browse tab in the user interface. The browsing structure that appears on this tab is fully customizable to suit the categorization needs of your organization. The steps necessary to customize the browse structure are described below.
By default, the browse displays Content Type and ISO Topic Category.The structure of the browse tree is established through REST URLs in the browse-catalog.xml file. This file is located in the \\geoportal\WEB-INF\classes\gpt\search\browse folder. Each heading in the Browse user interface is established by an item section in the browse-catalog.xml file. Within the item section there are two tags: nameand query. The query tag establishes the parameter that will be appended to the REST URL. The name tag is the key that corresponds to the text specified in the \\geoportal\WEB-INF\classes\gpt\resources\gpt.properties file. The gpt.properties file holds the text that will display on the Geoportal user interface.
When you modify browse categories, you will need to add or alter the <item> elements in the browse-catalog.xml file. For example, to filter by Application, the tags within the item tags would read: <item>
<name resourceKey="catalog.search.filterContentTypes.application"></name>
<query>contentType=application</query>
</item>
To add a sub-heading to the above Live Data and Map Services heading, you would embed another item section. For example, to filter Live Data and Map services by continent, add the following items:<item>
<name resourceKey="catalog.search.filterContentTypes.liveData"></name>
<query>contentType=liveData</query>
<item>
<name resourceKey="catalog.search.filterContentTypes.liveData.nAmerica"></name>
<query>bbox=-169.3864,6.3096,-44.1136,82.8652</query>
</item>
<item>
<name resourceKey="catalog.search.filterContentTypes.liveData.sAmerica"></name>
<query>bbox=-118.6966,-56.9329,-2.9177,13.8209</query>
</item>
</item>
Note:
In addition to adding these elements to the browse-catalog.xml file, you also have to add text values that correspond to the resourceKey. For example, the North America key would be added to the gpt.properties file, as shown below.catalog.search.filterContentTypes.liveData.nAmerica = North America