Copy articles

To enable the Copy Article feature in various plugins, the Writer plugin is needed, and configuration needs to be handled in advance.

Article Copy info

We now support XML handling with Article copy therefore we added a setting for changing the default storage provider. If default storage provider is set to CCA, you must be sure that 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.

Mappings needed in Writer plugin

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:

{
    "ca-provider": {
        "default": true,
        "cca": {
            "baseUrl": "${DBKS:CCA_URL}"
        },
        "opencontent": {
            "host": "${DBKS:CA_OC_PROVIDER_URL}"
        },
        [...]
    }
}

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:

{
    "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"
            }
        }
    ]
}

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.

{
    "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

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.

This will control the depth of the relations that will be stored.

Store author data

New in Writer 4.2.0 we added the ability to store author data on the data node of the author link. In order to do this following step needs to be made.

• Add WRITER_CONCEPTS_TEMPLATE_URL to config key store with following value depending on environment:

  • Stage: https://s3-eu-west-1.amazonaws.com/concepts-config-stage/writer/

  • Prod: https://s3-eu-west-1.amazonaws.com/concepts-config-prod/writer/