Table of Contents

Search

  1. Preface
  2. Using Metadata Manager
  3. Configuring Metadata Manager
  4. Application Resources
  5. Business Glossary Resources
  6. Business Intelligence Resources
  7. Custom Resources
  8. Data Integration Resources
  9. Data Modeling Resources
  10. Database Management Resources
  11. Universal Resources
  12. Managing Resources
  13. Loading and Monitoring Resources
  14. Managing Permissions
  15. Resource Migration
  16. Repository Migration
  17. Appendix A: Metadata Manager Login
  18. Appendix B: Metadata Manager Properties Files
  19. Appendix C: Resource Configuration Files
  20. Appendix D: Glossary

Metadata Manager Administrator Guide

Metadata Manager Administrator Guide

Search Result Configuration

Search Result Configuration

Set the priority of the search results in the searchpriorities.xml file.
The following table describes the elements and attributes in the searchpriorities.xml file:
Elements
Attributes
Description
search-label
Groups related entities. For example, you can specify a search label Table that could include entities like database tables, views and so on.
You can specify any number of search labels.
name
Provides a meaningful and unique name to a group of entities.
priority
Assigns a priority between one and ten for a group. One indicates lowest priority and ten indicates highest priority. The search results appear based on the priority assigned to a group.
entry
Provides details of the entities in a search label group.
type
Specifies the type of entity. Type can be Class_ID, Class_Type, or Favorite. You can use any combination of types when you define a group.
value
Specifies the value of the search label entry type.
You can specify the class_ID from IMW_Class, Class_Type from IMW_Class, and Favorite from MM_Favorite tables. You can also include custom classes in any group.
If the searchpriorities.xml file becomes invalid because of your changes, the Metadata Manager Service uses the default priorities to configure the search results and logs an error message.

0 COMMENTS

We’d like to hear from you!