Why Enterprise vault (EV) browser search (Search.asp) should not be used to compare an Accelerator search results

Article:TECH78429  |  Created: 2009-01-30  |  Updated: 2011-07-13  |  Article URL http://www.symantec.com/docs/TECH78429
Article Type
Technical Solution

Product(s)

Environment

Issue



Why Enterprise Vault (EV) browser search (Search.asp) should not be used to compare an Accelerator search results in both Domino and Exchange environments


Solution



Several factors will change the number of hits returned between an EV browser search and an Accelerator search.  Below will examine the differences between Search.asp and a Discovery Accelerator (DA) or Compliance Accelerator (CA) search.

EV Browser Search (Search.asp) versus DA Search
Search.asp is a simple search of the EV indexes.  By default it does not apply filters.  If an index does not incorporate an ItemGranularityOnly Schema (Schema Type 1 or Schema Flag 3), Search.asp searches the top level document as well as secondary attachments.  When an item matches the search criteria, the top level document and all of its attachments are returned as individual hits.  (Example:  A document that has 4 attachments and matches the search criteria will return 5 hits).  Unlike the Search.asp search, a DA match of search criteria will return the top level document and all of its attachments as a single hit count.  
    Another example as to why Search.asp should not be used to compare results with a DA search would be Date Range.  By default Search.asp includes a separate query to attachments.  If the attachments have a different creation date then the top level document, the attachment creation date will be considered in determining qualification of an item.  This will allow more hits in the resultant set then a true top level document query from DA. 


EV Browser Search (Search.asp) verses CA Search
There are several factors that will cause the numbers to be different between Search.asp and a CA search.  Not only does a CA search treat ItemGranularityOnly in the same fashion as a DA search (reference EV Browser Search (Search.asp) verses DA Search), but CA searches Journaled indexed items for Message Direction and Department tagging.  Message Direction tagging is applied by the Journal Task while the Department tagging is applied by the Journal Connector.  Department tagging can be removed from the search criteria by unselecting the Department and selecting the Individual in the Authors and Recipients section of the search parameters during the search creation.  Message Direction cannot be removed from the search criteria when searching Journal Archives and must accompany each indexed item.  


How to determine if an index has ItemGranularityOnly enabled
1. Obtain the Archive ID under the Advanced tab of the Archive properties page from the EV Administration Console
2. Locate the logical path to the index location (Under the Location tab of the Index Service properties page from the EV Administration Console)
3. Open a Command Prompt and navigate to the EV installation folder on the Indexing server
4. Type:  IndexServer /summary "X:\PathToIndex\ArchiveID"
5. Locate the Schema Flag value in the returned pop up window.  If the Schema Flag value is 3, ItemGranularityOnly option is enabled on this index


How to determine if items have Department tagging
1. Open the advanced, version three, Search.asp window http://Servername/EnterpriseVault/search.asp?advanced=3
2. Select the Vault to search from the Vault drop down menu
3. Type into 'Other Result Attributes': KVSCA.Department  (Case sensitive)
4. Press the Search button at the bottom of the web page
5. If the Department tag is present in the index item, the attribute will appear on each of the indexed items


How to determine if items have Message Direction tagging
1. Open the advanced, version three, Search.asp window http://Servername/EnterpriseVault/search.asp?advanced=3
2. Select the Vault to search from the Vault drop down menu
3. Type into 'Other Result Attributes': Vault.MsgDirection  (Case sensitive)
4. Press the Search button at the bottom of the web page
5. If the Message Direction tag is present in the index item, the attribute will appear on each of the indexed items


 



Legacy ID



339824


Article URL http://www.symantec.com/docs/TECH78429


Terms of use for this information are found in Legal Notices