# Copy articles

{% hint style="danger" %}

## Article Copy info

To be able to use the copy function, a content “check” is required by Naviga to make sure the content is CCA “compliant”. This means, that before a you can activate and use the copy functionality, we need to verify your content with the Naviga backend team to make sure the article content is fully compliant with the CCA API and our new Naviga Doc format. In most cases, this is a straight forward process with no needed changes by you as a customer. In other cases this will require configuration by the backend team. We also know of some cases where there will be requirements to change how content is written, and for old content to be patched.
{% endhint %}

### **Mappings needed in Writer plugin**

![](https://2005204016-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Ll6-u036-4GP1c0Pgyo%2F-MVpLFPla_XzLlLlB66G%2F-MVpOcC4sBaazIpwk9iT%2Fimage.png?alt=media\&token=aefab440-f1d5-4a9d-88cd-bef3c7b8d0a2)

### **Needed changes in Content Agent**

Unless you have already configured Content Agent for CCA, you will need to make changes in the Content Agent plugin. Here is an example of such configuration: 

```javascript
{
        "ca-provider": {
                "default": true,
                "cca": {
			          "baseUrl": "${DBKS:CCA_URL}"
		},
                "opencontent": {
                        "host": "${DBKS:CA_OC_PROVIDER_URL}"
                },
```

```javascript
baseURL
${DBKS:CCA_URL}
KeyStore name: CCA_URL
Key Value: https://cca-eu-west-1.saas-stage.infomaker.io/
```

### **Cleanup/remove**

It is possible to clean up the article when the copy is made, here is an example of such a cleanup. We'll be adding more examples and possibilities / restrictions:

```javascript
{
    "remove": [
        {
            "element": "meta",
            "data": [
                "provider"
            ]
        },
        {
            "element": "link",
            "data": {
                "rel": "mainchannel",
                "type": "x-im/channel"
            }
        },
        {
            "element": "link",
            "data": {
                "rel": "channel",
                "type": "x-im/channel"
            }
        },
        {
            "element": "link",
            "data": {
                "rel": "subject",
                "type": "x-im/section"
            }
        },
        {
            "element": "itemMetaExtProperty",
            "data": {
                "type": "imext:header"
            }
        }
    ]
}
```

{% hint style="danger" %}

### News value related issue in the Writer

Currently there is an issue in the Writer, that requires a news value, and if it is not present the Writer will add it. This means, that if you remove it with code, the Writer will add it and the user will be prompted to save even if the user didn't make any changes. This is an issue we will be addressing, but for the time being we recommend not to remove the News Value. 
{% endhint %}

```javascript
        {
            "element": "object",
            "data": {
                "type": "x-im/newsvalue"
            }
        },
```

### Plugin mappings

In each plugin that supports copying, you will also need to add the mapping for this feature

![](https://2005204016-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Ll6-u036-4GP1c0Pgyo%2F-MVpLFPla_XzLlLlB66G%2F-MVpOr-Ej9-V4XcYbgAV%2Fimage.png?alt=media\&token=d528fa75-beda-4e2a-856b-61dd2e5456d2)

## Concept relations

When copying articles you're able to add additional concepts to the copy. With this new feature we also added functionality to allow for relations to be stored in the document. In order to allow this feature you need to turn it ON under "Copy Article" customisations.

![](https://2005204016-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Ll6-u036-4GP1c0Pgyo%2F-MYcyZl6yiEVwL1bgI6R%2F-MYd-8C26EJjMVKo8tIr%2FScreenshot%202021-04-19%20at%2009.13.55.png?alt=media\&token=f69d2011-e488-4840-8915-fec0c1e7c338)

![This will control the depth of the relations that will be stored.](https://2005204016-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Ll6-u036-4GP1c0Pgyo%2F-MYcyZl6yiEVwL1bgI6R%2F-MYd-BDCWxApt4JTzb7o%2FScreenshot%202021-04-19%20at%2009.14.02.png?alt=media\&token=8079b75b-44cd-475f-986b-0513b681a27e)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.navigaglobal.com/dashboard-writer/4.0.0-1/admin/config/copy-articles.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.