Abstract: In an example embodiment, identifications of user actions are received from a first user device, the user actions being actions related to identifying data from a multi-tenant database to view. A portion of a first search query is received from a first user device corresponding to a first tenant in a multi-tenant architecture. A list of permissions for the first user device is then obtained. A plurality of fields is retrieved from a multi-tenant database based on the portion of the first search query, the fields obtained from data stored by multiple different tenants in the multi-tenant database, the plurality of fields retrieved being limited to fields for which the first user device has permission to view. Then a plurality of autocomplete suggestions are identified from the plurality of retrieved fields, the identifying based on the user actions.

Abstract: In an example embodiment, a listing of factors to evaluate during calculating of an index score for documents in a database is received, as well as a ranking of each factor in the listing of factors. A relevance multiplication factor is also obtained. Then a document to index in the database is received and the document is indexed. An index score is calculated for the document based on the listing of factors and the ranking of each factor. Then a search query on the database is received. A search score for the document is calculated based on the search query. Then an overall relevance score is calculated for the document for the search query by combining the index score and the search score using the relevance multiplication factor.

Abstract: In an example embodiment, primary data is received from a first tenant in a computer network, the primary data formatted based on a first version of a schema. Then a schema definition for the first version of the schema is obtained. The primary data is then parsed, the parsing including storing a schema version number for the first version of the schema. The primary data is indexed, by obtaining, using the schema version number for the first version of the schema, a schema definition for a most recent version of the schema; applying schema evolution to the primary data by applying one or more transforms to the primary data, the one or more transforms created using the schema definition for the first and most recent versions of the schema, causing the primary data to be converted to the most recent version of the schema; and indexing the converted primary data.

Abstract: In an example embodiment, a disaster is detected at a primary data center and, in response to the detection, a system switches over from the primary data center to a secondary data center such that searches from one or more client applications are routed to the secondary data center. Then, for each document stored in a search core of the secondary data center: a count is requested for the document from a first client application, it is determined whether the count for the document from the first client application matches a count for the document from the search core of the secondary data center, and, in response to a determination that the count for the document from the first client application does not match a count for the document from the search core of the secondary data center, a full publish for the document is requested from the first client application.

Abstract: In an example embodiment, identifications of user actions are received from a first user device, the user actions being actions related to identifying data from a multi-tenant database to view. A portion of a first search query is received from a first user device corresponding to a first tenant in a multi-tenant architecture. A list of permissions for the first user device is then obtained. A plurality of fields is retrieved from a multi-tenant database based on the portion of the first search query, the fields obtained from data stored by multiple different tenants in the multi-tenant database, the plurality of fields retrieved being limited to fields for which the first user device has permission to view. Then a plurality of autocomplete suggestions are identified from the plurality of retrieved fields, the identifying based on the user actions.

Abstract: In an example embodiment, a listing of factors to evaluate during calculating of an index score for documents in a database is received, as well as a ranking of each factor in the listing of factors. A relevance multiplication factor is also obtained. Then a document to index in the database is received and the document is indexed. An index score is calculated for the document based on the listing of factors and the ranking of each factor. Then a search query on the database is received. A search score for the document is calculated based on the search query. Then an overall relevance score is calculated for the document for the search query by combining the index score and the search score using the relevance multiplication factor.

Abstract: In an example embodiment, primary data is received from a first tenant in a computer network, the primary data formatted based on a first version of a schema. Then a schema definition for the first version of the schema is obtained. The primary data is then parsed, the parsing including storing a schema version number for the first version of the schema. The primary data is indexed, by obtaining, using the schema version number for the first version of the schema, a schema definition for a most recent version of the schema; applying schema evolution to the primary data by applying one or more transforms to the primary data, the one or more transforms created using the schema definition for the first and most recent versions of the schema, causing the primary data to be converted to the most recent version of the schema; and indexing the converted primary data.

Abstract: In an example embodiment, a disaster is detected at a primary data center and, in response to the detection, a system switches over from the primary data center to a secondary data center such that searches from one or more client applications are routed to the secondary data center. Then, for each document stored in a search core of the secondary data center: a count is requested for the document from a first client application, it is determined whether the count for the document from the first client application matches a count for the document from the search core of the secondary data center, and, in response to a determination that the count for the document from the first client application does not match a count for the document from the search core of the secondary data center, a full publish for the document is requested from the first client application.

Abstract: Systems and methods for providing application services to multiple tenants are provided. A data model is received from a new tenant. A database specific to the new tenant is created and stored in memory. The database may include one or more metadata tables. Other databases, each associated with another tenant, may also be stored in memory. The data model received from the new tenant may be stored in the created database that is specific to the new tenant. An application service may be provided to the new tenant based on the data model received from the new tenant and stored in the created database. In some embodiments, the data structures may be maintained in memory in a hierarchical manner. The hierarchy of the information resources may further correspond to a hierarchy of tenants. A library, for example, may be organized and shared in a hierarchical manner, in which a hierarchy of library resources may be shared among a defined group of tenants and/or subtenants.