Found 127 results for "content-services search"

The search executed in 2.92153E-4 seconds. That's fast.

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: 41.231133

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: 28.417112

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: 23.892857

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 At Platform level you can search for Content across all projects subject to your access permissions. Project Search at Project level provides more options and is configurable: Project Search Settings Search for a Project can be configured. go to Project Settings (left nav). Note: To have the Project Settings as a

Score: 15.416085

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: 15.272496

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: 14.493666

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: 13.175191

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

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

Score: 9.507226

Full-text Search - Cloud CMS

Full-text Search - Cloud CMS System Status Blog Support System Status Buy Now Features Quick Start Releases Pricing Documentation Developers Talk to Us Try Cloud CMS Features Quick Start Releases Pricing Docs Dev Start a Free Trial Features Quick Start Releases Pricing Documentation Developers Ask a Question Start a Free Trial About Us Company Careers Customers Partners Contact Us Videos "The only difference between Cloud CMS and your current on-premise document repository is that you don't have

Score: 9.176931

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: 3.7457404

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: 3.7278605

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: 3.6654332

Supported Stacks / Cloud CMS 3.3

Cloud CMS 3.3 (Note: Cloud CMS 3.3 is a future release that is scheduled for Q4) Here is a list of the individual components that have been through the Cloud CMS Quality Assurance test and validation process. We run this process with each release to certify that these components work as intended with Cloud CMS. Choose a combination of products to build your own Supported Stack. If anything is unclear then please contact our Support team. Database Version 3.3.x MongoDB 3.4.9 MongoDB 3.6.10 MongoD

Score: 3.4695795

API / Data Types / Node

Node Type node Datastore Type repository Supports authorities, permissions, transfer Configuration The node configuration contains system and custom properties. You can write your own properties as you see fit. However, system properties should be left alone as they are read-only. The following table presents you the system properties. Node Properties Property Type Default Read-Only Description _features object Read-Only This object contains all of the configuration for features which have been

Score: 3.3525403

How do I search for nested content?

Cloud CMS maintains two indexes that are of interest for finding things. The primary index is the MongoDB index - against which you can run any query you can dream up using the MongoDB DSL. The secondary index is the Elastic Search index - against which you can run any search you can dream up using the Elastic Search DSL. For information all kinds of really powerful stuff you can do with this, see: https://www.cloudcms.com/documentation/content-services/query.html https://www.cloudcms.com/docume

Score: 3.3515494

Docker / Kits

Kits Cloud CMS ships a number of pre-built kits containing Docker configuration files to help you get start. These kits are built from customer feedback to provide the most commonly requested scenarios. They can be used straight away or at the very least can serve as a useful reference. To download the Cloud CMS Docker Kits, please visit our Docker download page. Kits All of the Docker kits utilize Docker and Docker Compose. In each kit, you'll find a docker-compose.yml file which describes the

Score: 3.3467817

Docker / Maintenance / Upgrades

Upgrades This document provides technical guidance for upgrades. Upgrade to Cloud CMS Version 3.2 The Elastic Search version in this release has been updated from 1.7.1 to 6.2.4. Steps to follow to set up Docker 3.2: Download the Docker release 3.2 here. Download the Zip or Tar file of Elastic Search 6.2.4 here and then Unzip the package. Unzip the Docker release package, Create a new folder and paste the kit you use from the package. You can also replace your existing kit with the new release's

Score: 3.3467817

GraphQL

GraphQL Cloud CMS supports query via GraphQL. GraphQL is offered as a core API that sits alongside the Cloud CMS REST APIs. GraphQL is an open-source data query and manipulation language specification that is widely used across many CMS systems, servers and clients. GraphQL is offered so as to make it even easier for developers to quickly integrate and work with content inside of Cloud CMS. In Cloud CMS, all GraphQL calls are scoped to a branch. Each branch has its own GraphQL SDL schema that is

Score: 3.3259423

Supported Stacks / Cloud CMS 3.2

Cloud CMS 3.2 Here is a list of the individual components that have been through the Cloud CMS Quality Assurance test and validation process. We run this process with each release to certify that these components work as intended with Cloud CMS. Choose a combination of products to build your own Supported Stack. If anything is unclear then please contact our Support team. Database Version 3.2.x 3.2.28+ 3.2.39+ MongoDB 3.4.9 MongoDB 3.6.10 AWS DocumentDB (3.6.0) Elastic Search Version 3.2.x 3.2.3

Score: 3.3166666

Recommended environment

This is a big subject and, as you know, there are many ways to set things up to be robust. That said, some practices are better than others. I can relate at least what we do and what we've seen customers do. First, I'd recommend thinking of Cloud CMS as black box application that runs on top of MongoDB, Elastic Search (both of which can be thought of as databases) and a binary storage provider. Cloud CMS is a stateless application whose setup is actually quite simple. It doesn't maintain any sta

Score: 3.3083253

Python Driver and API Guide - Cloud CMS

Python Driver and API Guide - Cloud CMS System Status Blog Support System Status Buy Now Features Quick Start Releases Pricing Documentation Developers Talk to Us Try Cloud CMS Features Quick Start Releases Pricing Docs Dev Start a Free Trial Features Quick Start Releases Pricing Documentation Developers Ask a Question Start a Free Trial Developers Overview A Quick Tutorial (Hello World) API Keys Frameworks AngularJS React Vue.js cURL Postman Static Site Generators Gatsby.js Nuxt.js Drivers C# J

Score: 3.159633

Traversal

Traversal Content in Cloud CMS is stored in a graph-like structure that consists of nodes and associations. Nodes are entities in the graph and associations are the relationships (the lines between points in the graph). As such, when working with content in Cloud CMS, you'll often find it useful to employ these structures in terms of your content model. Your content can be spread out between nodes and associations equally so that both the entities and the relationships hold JSON properties that

Score: 3.1281445

User Interface / Create/Edit Content

Create/Edit Content In a Project you can find your content a number of ways: Content (left Nav) - Content listed under Content Types Folders (left Nav) - Folder/File view of the content Search (left Nav for a detailed search or top right for a keyword search) Viewing a Content item With any of the options above, to find or list the content, click on the 'title' of the content item to open the 'Document Overview': Note: your tenant may be configured such that the options available in the left nav

Score: 3.084884

Tree

Tree Content that is organized into folders can be retrieved using the Tree API. The Tree API lets you pull back an entire path-based folder and file structure of content within a single API call. The API call lets you specify a root node, a maximum depth to traverse down the path structure, paths that should be automatically expanded and query terms for filtering of root nodes. The Tree API is deal to support a variety of cases including: retrieval of multiple deeply-nested paths within a singl

Score: 3.0515893

Videos - Cloud CMS

Videos - Cloud CMS System Status Blog Support System Status Buy Now Features Quick Start Releases Pricing Documentation Developers Talk to Us Try Cloud CMS Features Quick Start Releases Pricing Docs Dev Start a Free Trial Features Quick Start Releases Pricing Documentation Developers Ask a Question Start a Free Trial About Us Company Careers Customers Partners Contact Us Videos "The only difference between Cloud CMS and your current on-premise document repository is that you don't have to worry

Score: 3.049367