Customizing Reason Strings for Similarity Calculations

Managing the Activity Graph Service 12-13 For an object to receive an Activity Rank that will affect search behavior, it must be eligible to have its event data collected from Analytics, a rank computation generated by Activity Graph, and an indexed entry in search with the value of the attribute wc_ serviceId matching one of the classes registered in Activity Graph. The currently supported objects are: ■ Users ■ Documents ■ Blog entries ■ Wiki pages The range of actions considered for computing Activity Rank are defined in the rankCalculation specified in the activityGraphMetaData.xml file. The out-of-the-box declaration includes the following user actions: component actionURN=connect weight=10.0 component actionURN=edit weight=20.0 inverse=true component actionURN=view-count weight=1.0 component actionURN=create weight=100.0 inverse=true component actionURN=create weight=100.0 component actionURN=edit-count weight=20.0 component actionURN=download weight=5.0 component actionURN=tag weight=10.0 component actionURN=comment weight=10.0 From this you can see that the single action of viewing a document conveys significantly less importance weight=1.0 to that document than the act of creating weight=100.0 or tagging weight=10.0 the document. Additionally, when the inverse attribute is set to true, a relationship from object-to-user is denoted. The effect of this relationship is to enable users to accrue authority from objects whose rank appreciates. For example, the author of a document a create relationship collects rank from that document as its rank appreciates from actions performed by other users on that document—tagging, viewing, downloading—which then amplifies the weight of the user’s future actions. When the Activity Graph Rank Engine completes its rank calculation for all of the affected objects, it sends a resulting set of identifiers with normalized ranks between 1 and 10 to a plug-in class, the SesRankResultAcceptor. This class simply pushes the ranks into the search index using the Oracle SES SOAP API. Once accepted by the SOAP API, the ranks, or docscores as they are known in Oracle SES, are immediately factored into the search ranking providing the DocScore feature is fully enabled. So, for two or more items within the same strata of a result set, those with higher docscores will receive higher search scores than they would otherwise, potentially raising them to a higher rank within that strata. Before You Begin Since Activity Rank works in conjunction with Oracle SES, you must make sure that Oracle SES is installed and configured correctly. Also, as Activity Rank only affects searchable items, the Rank Engine should be run after the SES crawler has finished a Note: Ranks are still calculated and used even in the case where the class of object is not searchable itself. 12-14 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter run. For more information, see the chapter Managing the Search Service in Oracle Fusion Middleware Administrators Guide for Oracle WebCenter. To configure Activity Rank for Oracle SES: 1. The Rank Engine expects to use docscore attributes with external names of DOC_ SCORE_1 for ACTIVITY-RANK and DOC_SCORE_2 for LIKE-RANK. Therefore, you must perform a one-time mapping call to establish these fields by calling the stored procedure eq_sdata.create_sdata_attribute: exec eq_sdata.create_sdata_attribute’ACTIVITY-RANK’; exec eq_sdata.create_sdata_attribute’LIKE-RANK’; 2. You must also add entries for these attributes to the Oracle SES ranking.xml file to determine the weight that they carry: ranking docscore-factor attribute-nameACTIVITY-RANKattribute-name column-nameDOC_SCORE_1column-name weight10.3weight docscore-factor docscore-factor attribute-nameLIKE-RANKattribute-name column-nameDOC_SCORE_2column-name weight10.3weight docscore-factor ranking 3. Restart the Oracle SES middle tier so that the changes take effect. 4. Use the WLST command setAGProperty to set the following Activity Graph properties: oracle.webcenter.activitygraph.providers.datasources.ses.soap.admin.url oracle.webcenter.activitygraph.providers.datasources.ses.soap.query.url For example: setAGPropertyappName=activitygraph-engines, propertyName=oracle.webcenter.activitygraph.providers.datasources.ses.soap.adm in.url, propertyValue=http:seshostname:7777searchapiadminAdminService, propertyType=String setAGPropertyappName=activitygraph-engines, propertyName=oracle.webcenter.activitygraph.providers.datasources.ses.soap.que ry.url, propertyValue=http:seshostname:7777searchqueryOracleSearch, propertyType=String Setting these properties enables the SESRankResultAcceptor to connect to the Oracle SES server and record ranks in the index. Note: These stored procedures must be invoked from the server hosting the Oracle SES instance. Tip: The ranking.xml file is located in the following directory: SES_HOMEsearchwebappconfig