XYZ Company reviews the configuration of their loan application Document Type in the OnBase Configuration module. They find that the Document Type has 50 Keyword Types associated with it, and that all 50 Keyword Types are in a Keyword Type Group. Each time a user adds, updates, or deletes a Keyword Value on a loan application, those 50 keyword indexes have to be maintained.
After conducting user interviews, XYZ Company finds that only 5 Keyword Types are used to retrieve loan applications: Policy Number, Last Name, First Name, Social Security #, and Loan Type. Users search by Policy Number, a combination of Last Name and First Name, or a combination of Social Security # and Loan Type. They do not use any of the other 45 Keyword Types unless they are also searching by Policy Number, a combination of Last Name and First Name, or a combination of Social Security # and Loan Type.
XYZ Company consults Database Services regarding their findings. With assistance from Database Services, XYZ Company makes the following modifications to their OnBase solution:
- The indexes for the 45 Keyword Types that are not being used for searching are dropped.
- The Last Name and First Name keyword indexes are combined into a composite index to enhance the performance of searches using that combination of Keyword Types.
- The Social Security # and Loan Type keyword indexes are combined into a composite index to enhance the performance of searches using that combination of Keyword Types.
- After dropping and creating indexes, users are notified to only use the other 45 Keyword Types after specifying the Policy Number, a combination of Last Name and First Name, or a combination of Social Security # and Loan Type. If one of the 45 Keyword Types is used without specifying the Policy Number, a combination of Last Name and First Name, or a combination of Social Security # and Loan Type, database performance will be poor.