Found 315 results for "bulk-import nodes"
The search executed in 8.36488E-4 seconds. That's fast.
|
Gitana / 4.0 / Data Engine / Bulk Import / NodesNodes The Cloud CMS Bulk Import tool makes it easy to import content from structured data files stored on disk. The Packager API provides several methods which can read content from directories and bulk import that content all in one fell-swoop. This includes content types, content instances and relational information between content items. This is useful for many scenarios including those where you may wish to store a master copy of your foundation content types and content instances for new pr
Score: 20.931393
|
|
|
Gitana / 3.2 / Guide / Guide / Bulk Import / NodesNodes The Cloud CMS Bulk Import tool makes it easy to import content from structured data files stored on disk. The Packager API provides several methods which can read content from directories and bulk import that content all in one fell-swoop. This includes content types, content instances and relational information between content items. This is useful for many scenarios including those where you may wish to store a master copy of your foundation content types and content instances for new pr
Score: 12.920811
|
|
|
Gitana / 3.2 / Guide / Guide / TraversalTraversal 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: 12.549454
|
|
|
Gitana / 4.0 / Data Engine / Discovery / TraversalTraversal 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: 12.549454
|
|
|
Gitana / 3.2 / Guide / Guide / Actions / Sync Multiple NodesSync Multiple Nodes ID: syncMultipleNodes Syncs a node to a target location. If the node does not exist in the target location, it is created. If it is already created, it is updated. If the node was deleted or we are explicitly told to sync a delete operation, the node will be deleted at the target location. Configuration Property Type Required Default Description repositoryId text true The ID of the repository of the source node. branchId text true The ID of the branch of the source node. node
Score: 5.4745
|
|
|
Gitana / 4.0 / Data Engine / Behaviors / Actions / Sync Multiple NodesSync Multiple Nodes ID: syncMultipleNodes Syncs a node to a target location. If the node does not exist in the target location, it is created. If it is already created, it is updated. If the node was deleted or we are explicitly told to sync a delete operation, the node will be deleted at the target location. Configuration Property Type Required Default Description repositoryId text true The ID of the repository of the source node. branchId text true The ID of the branch of the source node. node
Score: 5.4745
|
|
|
Gitana / 3.2 / Guide / Guide / Actions / Copy Multiple NodesCopy Multiple Nodes ID: copyMultipleNodes Copies multiple nodes and any of their owned children to a new location in the content graph. Configuration Property Type Required Default Description repositoryId text true The ID of the repository of the source node. branchId text true The ID of the branch of the source node. nodeIds array true An array of node IDs to be copied (soure nodes) targetRepositoryId text true The ID of the repository of the target parent node. targetBranchId text true The ID
Score: 5.408454
|
|
|
Gitana / 4.0 / Data Engine / Behaviors / Actions / Copy Multiple NodesCopy Multiple Nodes ID: copyMultipleNodes Copies multiple nodes and any of their owned children to a new location in the content graph. Configuration Property Type Required Default Description repositoryId text true The ID of the repository of the source node. branchId text true The ID of the branch of the source node. nodeIds array true An array of node IDs to be copied (soure nodes) targetRepositoryId text true The ID of the repository of the target parent node. targetBranchId text true The ID
Score: 5.408454
|
|
|
Gitana / 3.2 / Guide / Guide / Workflow / Workflow Handlers / Sync Node
Sync Node Type: syncNode This handler "syncs" nodes that are part of a workflow's payload to a target branch. This handler can be used to have workflow payload nodes automatically copied to or deleted from a target branch. The full config for this handler is as follows: {
"targetProjectId": "
Score: 1.5636187
|
|
|
Gitana / 4.0 / Data Engine / Workflow / Workflow Handlers / Sync Node
Sync Node Type: syncNode This handler "syncs" nodes that are part of a workflow's payload to a target branch. This handler can be used to have workflow payload nodes automatically copied to or deleted from a target branch. The full config for this handler is as follows: {
"targetProjectId": "
Score: 1.5636187
|
|
|
Gitana / 3.2 / Guide / Guide / Policies / Association PoliciesAssociation Policies Association policies provide places where you can hook in behaviors that trigger when associations are created or removed between two nodes in the Cloud CMS content graph. When two nodes are connected together via an association or an association is broken, these policies trigger and may fire into your custom handlers. The following policies are available: Policy QName Description p:beforeAssociate Raised before an association is created between two nodes p:afterAssociate Ra
Score: 1.5148644
|
|
|
Gitana / 4.0 / Data Engine / Behaviors / Policies / Association PoliciesAssociation Policies Association policies provide places where you can hook in behaviors that trigger when associations are created or removed between two nodes in the Cloud CMS content graph. When two nodes are connected together via an association or an association is broken, these policies trigger and may fire into your custom handlers. The following policies are available: Policy QName Description p:beforeAssociate Raised before an association is created between two nodes p:afterAssociate Ra
Score: 1.5148644
|
|
|
Gitana / 3.2 / Guide / Guide / Cookbooks / REST API CookbookREST API Cookbook Getting Started This guide assumes that you have already installed an HTTP client with which you will be making requests. However, it is highly recommended that you look at our language drivers and you read about the one that you will be using in your application. Connecting to Cloud CMS CloudCMS uses OAuth2 to perform authentication, and as such to connect you will have to perform the authentication handshake manually to connect directly with the rest api. The specifics of thi
Score: 1.4955177
|
|
|
Gitana / 4.0 / Developers / Cookbooks / REST API CookbookREST API Cookbook Getting Started This guide assumes that you have already installed an HTTP client with which you will be making requests. However, it is highly recommended that you look at our language drivers and you read about the one that you will be using in your application. Connecting to Gitana Gitana uses OAuth2 to perform authentication, and as such to connect you will have to perform the authentication handshake manually to connect directly with the rest api. The specifics of this dif
Score: 1.4955177
|
|
Tree HierarchiesIn Cloud CMS, there are no hard and fast rules regarding association types between nodes. And so, when dealing with things like tree structures, you usually have to first make some assumptions about the kinds of relationships between nodes that you want to traverse. For arbitrary relationships and traversals around nodes, Cloud CMS provides traversal methods which are a bit more intensive to use. However, if you're using typical a:child relationships between nodes (which is what Cloud CMS uses f
Score: 1.4801723
|
|
|
Gitana / 3.2 / Guide / Guide / Actions / Invalidate Page RenditionsInvalidate Page Renditions ID: invalidatePageRenditions This action invalidates page renditions in one or more applications. You can target a single page rendition or a broad set of page renditions using a custom query. { "title": "Invalidate Page Renditions", "properties": { "applicationDeployments": { "title": "Application Deployments", "type": "array", "items": { "type": "object", "properties": {
Score: 1.4785378
|
|
|
Gitana / 4.0 / Data Engine / Behaviors / Actions / Invalidate Page RenditionsInvalidate Page Renditions ID: invalidatePageRenditions This action invalidates page renditions in one or more applications. You can target a single page rendition or a broad set of page renditions using a custom query. { "title": "Invalidate Page Renditions", "properties": { "applicationDeployments": { "title": "Application Deployments", "type": "array", "items": { "type": "object", "properties": {
Score: 1.4785378
|
|
|
Gitana / 3.2 / Guide / Guide / Features / TaggableTaggable QName: f:taggable Indicates that a node should support tagging. Nodes that support tagging maintain a:has_tag associations to n:tag nodes that serve as master tag entries. A single tag entry may have multiple associations linking it to nodes that bear its tag. In addition, taggable nodes maintain a tags array which contains a local array of all of the tags that the node has been assigned. In this way, tags can be traversed using graph-based lookup or they can be queried directly based o
Score: 1.470811
|
|
|
Gitana / 4.0 / Data Engine / Aspects / TaggableTaggable QName: f:taggable Indicates that a node should support tagging. Nodes that support tagging maintain a:has_tag associations to n:tag nodes that serve as master tag entries. A single tag entry may have multiple associations linking it to nodes that bear its tag. In addition, taggable nodes maintain a tags array which contains a local array of all of the tags that the node has been assigned. In this way, tags can be traversed using graph-based lookup or they can be queried directly based o
Score: 1.470811
|
|
|
Gitana / 3.2 / Guide / Guide / Features / MultilingualMultilingual QName: f:multilingual When applied to a node, this indicates that you wish to have the contents of this node support multilingual behavior and translated content. This node then serves as the "master node" for translation support. Master nodes have a:has_translation associations to translation nodes that hold copies of the content (JSON and any attachments) in the target locale. Marking a node as f:multilingual does not automatically produce translations for you. However, once marke
Score: 1.452497
|
|
|
Gitana / 4.0 / Data Engine / Aspects / MultilingualMultilingual QName: f:multilingual When applied to a node, this indicates that you wish to have the contents of this node support multilingual behavior and translated content. This node then serves as the "master node" for translation support. Master nodes have a:has_translation associations to translation nodes that hold copies of the content (JSON and any attachments) in the target locale. Marking a node as f:multilingual does not automatically produce translations for you. However, once marke
Score: 1.452497
|
|
|
Gitana / 3.2 / Guide / Guide / Features / ContainerContainer QName: f:container Makes a node as a container. In Cloud CMS, all nodes are essentially equivalent. There is no assumed containment model - in other words, Cloud CMS does not assume a folder structure or any kind of graph that you must adhere to. You can use associations to model any kind of relationship you would like. For example, you might have nodes that maintain only a kind of "linked" relationship to do things like link together related items for a product catalog. Another exampl
Score: 1.4507072
|
|
|
Gitana / 4.0 / Data Engine / Aspects / ContainerContainer QName: f:container Makes a node as a container. In Cloud CMS, all nodes are essentially equivalent. There is no assumed containment model - in other words, Cloud CMS does not assume a folder structure or any kind of graph that you must adhere to. You can use associations to model any kind of relationship you would like. For example, you might have nodes that maintain only a kind of "linked" relationship to do things like link together related items for a product catalog. Another exampl
Score: 1.4507072
|
|
|
How do I retrieve the folder path for my content?In Cloud CMS, you may choose to associate nodes with folders. This allows the content to be worked with by editorial teams such that they can navigate to content within folders, move content between folders and generally organize their content as they wish. It also allows for content to be retrieved by path via the API, if you wish. Technically speaking, Cloud CMS does not require folders or paths. In fact, plenty of customers use Cloud CMS in such a way that they don't require folders at all. C
Score: 1.4436138
|
|
|
How to Retrieve content by their document library pathYou can retrieve content by their document library path using the CMS API using the Node API. For example, you can paginate through the children of a node using this call: http://api.cloudcms.com/docs#!/node/get_repositories_repositoryId_branches_branchId_nodes_nodeId_children GET /repositories/{repositoryId}/branches/{branchId}/nodes/{nodeId}/children?path={path} In this case, you would set "nodeId" to the value "root" to indicate the root node. And then use "path" to describe the offset. If yo
Score: 1.4362562
|