Found 185 results for "content-services search"

The search executed in 0.001050397 seconds. That's fast.

Gitana / 3.2 / Guide / Guide / Search

Search Any content you put into Cloud CMS is automatically indexed for full-text and structured search. This lets your editorial teams instantly search for content and find the things they're looking for. Under the hood, Cloud CMS uses Elastic Search and makes available to your editorial users and developers the full syntax of the Elastic Search Query DSL. This allows you to execute simple searches as well as more complex queries that take into account term and phrase matching, nested operations

Score: 21.107832

Gitana / 4.0 / Data Engine / Discovery / Search

Search Any content you put into Cloud CMS is automatically indexed for full-text and structured search. This lets your editorial teams instantly search for content and find the things they're looking for. Under the hood, Cloud CMS uses Elastic Search and makes available to your editorial users and developers the full syntax of the Elastic Search Query DSL. This allows you to execute simple searches as well as more complex queries that take into account term and phrase matching, nested operations

Score: 21.107832

Gitana / 3.2 / Guide / Guide / Find

Find The Cloud CMS Find Service lets you discover and retrieve content using combinations of its three primary content retrieval mechanisms. These mechanisms are: Query (powered by Mongo DB) Search (powered by Elastic Search) Traversal (provides Graph Traversal) A "Find" operation provides a way for you to execute a single API lookup that runs one or more of the above and composes them into a single result set. How it Works When you make a "Find" call, you provide a recipe containing at least on

Score: 15.104183

Gitana / 4.0 / Data Engine / Discovery / Find

Find The Cloud CMS Find Service lets you discover and retrieve content using combinations of its three primary content retrieval mechanisms. These mechanisms are: Query (powered by Mongo DB) Search (powered by Elastic Search) Traversal (provides Graph Traversal) A "Find" operation provides a way for you to execute a single API lookup that runs one or more of the above and composes them into a single result set. How it Works When you make a "Find" call, you provide a recipe containing at least on

Score: 15.104183

Gitana / 3.2 / Guide / Guide / Integrations / Amazon Web Services / Amazon Elastic Search Service

Amazon Elastic Search Service Amazon Elastic Search Service is a fully managed service that makes it easy for you to deploy, secure, and operate Elasticsearch at scale with zero down time. Cloud CMS works out-of-the-box with Amazon Elastic Search Service as an alternative to running Elastic Search on your own or using a Elastic Search hosted service. Amazon Elastic Search Service provides an easy and convenient way for customers to manage their own Elastic Search installations, data and backup.

Score: 10.584229

Gitana / 4.0 / Data Engine / Integrations / Amazon Web Services / Amazon Elastic Search Service

Amazon Elastic Search Service Amazon Elastic Search Service is a fully managed service that makes it easy for you to deploy, secure, and operate Elasticsearch at scale with zero down time. Cloud CMS works out-of-the-box with Amazon Elastic Search Service as an alternative to running Elastic Search on your own or using a Elastic Search hosted service. Amazon Elastic Search Service provides an easy and convenient way for customers to manage their own Elastic Search installations, data and backup.

Score: 10.584229

Gitana / 3.2 / Guide / Guide / User Interface / Search

Search Content is automatically indexed when it is created, modified, or uploaded in Cloud CMS. The index is across the Content properties and any attached file eg Word, PDF,.. Platform Project Project Search Settings go to Project Settings (left nav). Note: To have the Project Settings as an option you must have access: eg Tenant owner, or in the Project Manager Team select Search. The Project Search Screen can be updated and will apply the settings for the project only. Search Syntax Logic Log

Score: 7.4280763

Gitana / 4.0 / User Interface / User Interface / Search

Search Content is automatically indexed when it is created, modified, or uploaded in Cloud CMS. The index is across the Content properties and any attached file eg Word, PDF,.. Platform Project Project Search Settings go to Project Settings (left nav). Note: To have the Project Settings as an option you must have access: eg Tenant owner, or in the Project Manager Team select Search. The Project Search Screen can be updated and will apply the settings for the project only. Search Syntax Logic Log

Score: 7.4280763

Gitana / 3.2 / Guide / Guide / Application Server / Tags / @search

@search Searches for nodes and makes those nodes available to the template. Parameters parameter required description text required the text to search for sort the field to sort on sortDirection the direction to sort in (either 1 for ascending or -1 for descending) limit the number of records to return skip a position to skip ahead to in the record set scope if "page", then only relatives related to the current page will be returned as specifies the name of the results variable (by default - row

Score: 7.3676505

Gitana / 4.0 / Developers / Application Server / Tags / @search

@search Searches for nodes and makes those nodes available to the template. Parameters parameter required description text required the text to search for sort the field to sort on sortDirection the direction to sort in (either 1 for ascending or -1 for descending) limit the number of records to return skip a position to skip ahead to in the record set scope if "page", then only relatives related to the current page will be returned as specifies the name of the results variable (by default - row

Score: 7.3676505

Gitana / 3.2 / Guide / Guide / Search / Query String Reference

Query String Reference Cloud CMS lets you search for your content using either a text-based query string or a JSON block. These two methods are fairly equivalent for most typical operations. They provide two ways to express a search operation that will execute within Elastic Search. They are expressions of the Elastic Search DSL. This portion of the documentation goes into some of things you can do with the former, textual representation of an Elastic Search query string. In Cloud CMS, you can t

Score: 6.380334

Gitana / 4.0 / Data Engine / Discovery / Search / Query String Reference

Query String Reference Cloud CMS lets you search for your content using either a text-based query string or a JSON block. These two methods are fairly equivalent for most typical operations. They provide two ways to express a search operation that will execute within Elastic Search. They are expressions of the Elastic Search DSL. This portion of the documentation goes into some of things you can do with the former, textual representation of an Elastic Search query string. In Cloud CMS, you can t

Score: 6.380334

Gitana / 3.2 / Guide / Guide / User Interface / Projects / Configure Search

Configure Search You can configure the project search page to show different filter controls on the left hand side by adding some properties to your project JSON descriptor. These controls ultimately feed into a Cloud CMS node API find call that has the following structure: { "query": ... query block into MongoDB, "search": ... search block into Elastic Search } The following customization block can be added to your project's JSON descriptor: { ..., "search": { "showContentTypes"

Score: 6.303274

Gitana / 4.0 / User Interface / Projects / Configure Search

Configure Search You can configure the project search page to show different filter controls on the left hand side by adding some properties to your project JSON descriptor. These controls ultimately feed into a Cloud CMS node API find call that has the following structure: { "query": ... query block into MongoDB, "search": ... search block into Elastic Search } The following customization block can be added to your project's JSON descriptor: { ..., "search": { "showContentTypes"

Score: 6.303274

Gitana / 3.2 / Guide / Guide / Search / Examples

Examples This page provides sample searches that you can review to get an idea of what is possible with search within Cloud CMS. Cloud CMS offers full integration to Elastic Search and, in doing so, it gives developers the ability to powerful queries using the Elastic Search DSL (as either JSON or a text-based query string format). Example: Full-text Search (using JS Driver) Suppose we want to search for all of the content nodes where the text eddie van halen appears. We can do so by using a ful

Score: 6.25104

Gitana / 4.0 / Data Engine / Discovery / Search / Examples

Examples This page provides sample searches that you can review to get an idea of what is possible with search within Cloud CMS. Cloud CMS offers full integration to Elastic Search and, in doing so, it gives developers the ability to powerful queries using the Elastic Search DSL (as either JSON or a text-based query string format). Example: Full-text Search (using JS Driver) Suppose we want to search for all of the content nodes where the text eddie van halen appears. We can do so by using a ful

Score: 6.25104

Gitana / 4.0 / Forms / Fields / Search Field

Search Field The search field implements a search box that provides a search-optimized control running in most modern browsers. It allows for the specification of search terms with an optimized user interface. Note: This control does not perform the actual search for you. It uses the HTML5 'search' input type to inform the mobile device or web browser that you've focused into an input control intended for search term specification. Properties Title Search Description A search box field Field Typ

Score: 6.2421536

Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / project-search-list-selected-actions

project-search-list-selected-actions [ { "config": { "project-search-list-selected-actions": [ { "action": "deploy-nodes", "allowPermission": [ "deploy", "undeploy" ], "order": 10000 } ] } }, { "config": { "project-search-list-selected-actions": [ { "action": "delete_documents", "order": 5, "allowPermission": [ "delete" ]

Score: 4.551641

Gitana / 4.0 / Developers / User Interface Customization / Contexts / project-search-list-selected-actions

project-search-list-selected-actions [ { "config": { "project-search-list-selected-actions": [ { "action": "deploy-nodes", "allowPermission": [ "deploy", "undeploy" ], "order": 10000 } ] } }, { "config": { "project-search-list-selected-actions": [ { "action": "delete_documents", "order": 5, "allowPermission": [ "delete" ]

Score: 4.551641

Using the JavaScript driver to run an elasticsearch query

The Cloud CMS REST API allows for elasticsearch queries against a branch. The API endpoint is POST /repositories/{repositoryId}/branches/{branchId}/nodes/search The payload is a JSON object containing a top-level property called "search" which wraps the elasticsearch DSL query. The JavaScript driver exposes this call on the Branch object using the searchNodes() methods. Examples: 1) Search for nodes containing the keyword "hello" in any property: req.branch(function (err, branch) { branch.trap(f

Score: 2.062506

Gitana / 3.2 / Guide / Guide / Features / Indexable

Indexable QName: f:indexable Informs a node of how it should be indexed. Cloud CMS maintains multiple indexes including a search index, a database index and special indexes for things like path-based retrieval. By default, all n:node instances have the f:indexable feature applied to them. The default behavior is for search to be enabled and for search-indexes to be updated synchronously upon a write. Nodes that are indexed for search will take a little extra time on write (create or update) sinc

Score: 2.0564303

Gitana / 4.0 / Data Engine / Aspects / Indexable

Indexable QName: f:indexable Informs a node of how it should be indexed. Cloud CMS maintains multiple indexes including a search index, a database index and special indexes for things like path-based retrieval. By default, all n:node instances have the f:indexable feature applied to them. The default behavior is for search to be enabled and for search-indexes to be updated synchronously upon a write. Nodes that are indexed for search will take a little extra time on write (create or update) sinc

Score: 2.0564303

Gitana / 3.2 / Guide / Guide / Supported Stacks

Supported Stacks Cloud CMS certifies certain supported stacks for on-premise Cloud CMS 3.2 installations. This information is relevant to customers who run Cloud CMS 3.2 on-premise and manage their own Elastic Search and MongoDB database tiers. This information is not applicable to SaaS customers since Cloud CMS runs that infrastructure for hosted subscribers. The following links provide detailed information on the combinations of operating systems, databases, application servers, bundled compon

Score: 2.0036414

Gitana / 4.0 / Self Managed / Supported Stacks / Overview

Supported Stacks Gitana certifies certain supported stacks for on-premise Gitana 4.x installations. This information is relevant to customers who run Gitana 4.x on-premise and manage their own Elastic Search and MongoDB database tiers. This information is not applicable to SaaS customers since Gitana runs that infrastructure for hosted subscribers. The following links provide detailed information on the combinations of operating systems, databases, application servers, bundled components and thi

Score: 2.0036414

What is the reason for "Failed to index node"?

If you scan your log entries and see "Failed to index node", this indicates that Elastic Search failed to update its index for a node. Cloud CMS tells Elastic Search to updates its index whenever a node is created or updated. When a node is deleted, Cloud CMS tells Elastic Search to remove the node from its index. This error message means that Elastic Search failed to update the index and therefore the index wasn't updated. If you open up the error, you may see further information that indicates

Score: 2.0023382