Abstract: Rules, such as condition-action rules, are configured at different levels of a hierarchy. For example, a top level site administrator may configure rules, lower level administrators may configure rules and end users may configure rules. Rules created at a higher hierarchical level are automatically inherited by lower hierarchical levels in the same branch of the hierarchy. The source of the inherited rule is indicated with its display such that the hierarchical level of creation can readily be determined. The inherited rule(s) may be toggled on/off at the lower hierarchical levels but edits to inherited rule(s) are restricted. Instead, a copy of any inherited rule may be made to create a local copy of the rule that is editable. Rules may be ordered and when a lower hierarchical level inherits the rules, the ordering is preserved.

Abstract: Aiding preview providers in providing previews of uniform resource locators to client computing systems in which the uniform resource locators are represented. Upon determining that a uniform resource locator is represented in a client computing system, a preview provider (amongst multiple preview providers) is selected based on a structure of the uniform resource locator. Then, communication is facilitated between the selected preview provider and the client computing system. Within the communication, the preview provider can provide a preview corresponding to the uniform resource locator to the client computing system. This type of mediation may occur between any number of client computing systems and any number of preview providers.

Abstract: Providing a preview of a uniform resource locator. When the preview provider provides a preview associated with a uniform resource locator, the preview provider also prepares for the selection of that uniform resource locator. As examples only, the preview provider might create content, refresh data, and/or change configuration and/or setting(s) in preparation for more efficiently handling a subsequent request for the resource. As other examples, if the request for the preview includes an identification of the user that will view the preview, the preview provider might change access controls for that user, add the user to a roster, and so forth, in anticipation of more efficiently handling a request from that user to access the resource. In the case of the preview containing restricted content, the preview provider might verify that the user has authorization to view that restricted content even prior to providing the preview itself.

Abstract: Rules, such as condition-action rules, are configured at different levels of a hierarchy. For example, a top level site administrator may configure rules, lower level administrators may configure rules and end users may configure rules. Rules created at a higher hierarchical level are automatically inherited by lower hierarchical levels in the same branch of the hierarchy. The source of the inherited rule is indicated with its display such that the hierarchical level of creation can readily be determined. The inherited rule(s) may be toggled on/off at the lower hierarchical levels but edits to inherited rule(s) are restricted. Instead, a copy of any inherited rule may be made to create a local copy of the rule that is editable. Rules may be ordered and when a lower hierarchical level inherits the rules, the ordering is preserved. While the ordering of any rules remains constant when inherited at the lower levels, the lower level may toggle on/off the execution of each rule within the ordering.

Abstract: Rules, such as condition-action rules, are configured at different levels of a hierarchy. For example, a top level site administrator may configure rules, lower level administrators may configure rules and end users may configure rules. Rules created at a higher hierarchical level are automatically inherited by lower hierarchical levels in the same branch of the hierarchy. The source of the inherited rule is indicated with its display such that the hierarchical level of creation can readily be determined. The inherited rule(s) may be toggled on/off at the lower hierarchical levels but edits to inherited rule(s) are restricted. Instead, a copy of any inherited rule may be made to create a local copy of the rule that is editable. Rules may be ordered and when a lower hierarchical level inherits the rules, the ordering is preserved. The lower level may toggle on/off the execution of each rule within the ordering.

Abstract: Rules, such as condition-action rules, are configured at different levels of a hierarchy. For example, a top level site administrator may configure rules, lower level administrators may configure rules and end users may configure rules. Rules created at a higher hierarchical level are automatically inherited by lower hierarchical levels in the same branch of the hierarchy. The source of the inherited rule is indicated with its display such that the hierarchical level of creation can readily be determined. The inherited rule(s) may be toggled on/off at the lower hierarchical levels but edits to inherited rule(s) are restricted. Instead, a copy of any inherited rule may be made to create a local copy of the rule that is editable. Rules may be ordered and when a lower hierarchical level inherits the rules, the ordering is preserved. While the ordering of any rules remains constant when inherited at the lower levels, the lower level may toggle on/off the execution of each rule within the ordering.

Abstract: Rules, such as condition-action rules, are configured at different levels of a hierarchy. Rules created at a higher hierarchical level are automatically inherited by lower hierarchical levels in the same branch of the hierarchy. The source of the inherited rule is indicated with its display such that the hierarchical level of creation can readily be determined. The inherited rule(s) may be toggled on/off at the lower hierarchical levels but edits to inherited rule(s) are restricted. Instead, a copy of any inherited rule may be made to create a local copy of the rule that is editable. Rules may be ordered and when a lower hierarchical level inherits the rules, the ordering is preserved. While the ordering of any rules remains constant when inherited at the lower levels, the lower level may toggle on/off the execution of each rule within the ordering.

Abstract: Representing structured data extracted from unstructured data in fashion allowing querying using relational database concepts. A method includes receiving user input specifying one or more database views. The method further includes receiving user input specifying an information extraction technique, such as an extraction workflow. The method further includes receiving user input specifying a corpus of data. The extraction technique is applied to the corpus of data to produce the one or more database views. These views can then be queried or operated on using database tools.

Abstract: Rules, such as condition-action rules, are configured at different levels of a hierarchy. For example, a top level site administrator may configure rules, lower level administrators may configure rules and end users may configure rules. Rules created at a higher hierarchical level are automatically inherited by lower hierarchical levels in the same branch of the hierarchy. The source of the inherited rule is indicated with its display such that the hierarchical level of creation can readily be determined. The inherited rule(s) may be toggled on/off at the lower hierarchical levels but edits to inherited rule(s) are restricted. Instead, a copy of any inherited rule may be made to create a local copy of the rule that is editable. Rules may be ordered and when a lower hierarchical level inherits the rules, the ordering is preserved. While the ordering of any rules remains constant when inherited at the lower levels, the lower level may toggle on/off the execution of each rule within the ordering.

Abstract: Rules, such as condition-action rules, are configured at different levels of a hierarchy. For example, a top level site administrator may configure rules, lower level administrators may configure rules and end users may configure rules. Rules created at a higher hierarchical level are automatically inherited by lower hierarchical levels in the same branch of the hierarchy. The source of the inherited rule is indicated with its display such that the hierarchical level of creation can readily be determined. The inherited rule(s) may be toggled on/off at the lower hierarchical levels but edits to inherited rule(s) are restricted. Instead, a copy of any inherited rule may be made to create a local copy of the rule that is editable. Rules may be ordered and when a lower hierarchical level inherits the rules, the ordering is preserved. While the ordering of any rules remains constant when inherited at the lower levels, the lower level may toggle on/off the execution of each rule within the ordering.

Abstract: A query pipeline for an enterprise search system is configurable by a user of the system. A user may create rules for custom query transformation and parallel query generation, federation of queries, mixing of results and application of display layouts to the received search results. A user interface (UI) assists a user in configuring the search pipeline. For example, a user may enter condition action rules for queries that affect how a query is transformed, how parallel queries are generated, how queries are federated, how search results are ranked and displayed, how rules are ordered and the like.

Abstract: Representing structured data extracted from unstructured data in fashion allowing querying using relational database concepts. A method includes receiving user input specifying one or more database views. The method further includes receiving user input specifying an information extraction technique, such as an extraction workflow. The method further includes receiving user input specifying a corpus of data. The extraction technique is applied to the corpus of data to produce the one or more database views. These views can then be queried or operated on using database tools.

Abstract: Rules, such as condition-action rules, are configured at different levels of a hierarchy. For example, a top level site administrator may configure rules, lower level administrators may configure rules and end users may configure rules. Rules created at a higher hierarchical level are automatically inherited by lower hierarchical levels in the same branch of the hierarchy. The source of the inherited rule is indicated with its display such that the hierarchical level of creation can readily be determined The inherited rule(s) may be toggled on/off at the lower hierarchical levels but edits to inherited rule(s) are restricted. Instead, a copy of any inherited rule may be made to create a local copy of the rule that is editable. Rules may be ordered and when a lower hierarchical level inherits the rules, the ordering is preserved. While the ordering of any rules remains constant when inherited at the lower levels, the lower level may toggle on/off the execution of each rule within the ordering.

Abstract: A query pipeline for an enterprise search system is configurable by a user of the system. A user may create rules for custom query transformation and parallel query generation, federation of queries, mixing of results and application of display layouts to the received search results. A user interface (UI) assists a user in configuring the search pipeline. For example, a user may enter condition action rules for queries that affect how a query is transformed, how parallel queries are generated, how queries are federated, how search results are ranked and displayed, how rules are ordered and the like.

Abstract: A custom search ranking model is configured using a base ranking model that is combined with one or more additional ranking features. A base ranking model that has already been configured and tuned is selected that serves as the base ranking model for a custom search ranking model. The additional ranking feature(s) to combine with the base ranking model may be manually/automatically identified. For example, a feature selection algorithm may be used to automatically identify ranking features that are likely to have a positive impact on results provided by the base search ranking model. A user may also know of the ranking feature(s) that they would like to add to the base ranking model. The custom search ranking model may also be evaluated by automatically creating a set of virtual queries for evaluation.

Abstract: Representing structured data extracted from unstructured data in fashion allowing querying using relational database concepts. A method includes receiving user input specifying one or more database views. The method further includes receiving user input specifying an information extraction technique, such as an extraction workflow. The method further includes receiving user input specifying a corpus of data. The extraction technique is applied to the corpus of data to produce the one or more database views. These views can then be queried or operated on using database tools.