[
https://issues.apache.org/jira/browse/CONNECTORS-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16167858#comment-16167858
]
Piergiorgio Lucidi commented on CONNECTORS-1356:
------------------------------------------------
The content migration flag changes the value for the documentURI from a content
download link to a content path.
For example, by default the documentURI is set as a download URL because
includes also the UUID of a content:
http://cmis.server.host:port/app/content/invoices/procurement/id/10b3398a-f67b-43ae-a557-bd20c995663f
If you enable the content migration flag the documentURI is set as a content
path as the following:
/procurement/invoices/software/asset/invoice-20170814.pdf
Using this value policy we have a fully support removal functionality with a
perfect working removeDocument method implementation for CMIS Output Connector
or any other output connector dedicated to migrate contents.
> Initial implementation of the CMIS Output Connector
> ---------------------------------------------------
>
> Key: CONNECTORS-1356
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1356
> Project: ManifoldCF
> Issue Type: Task
> Components: CMIS Output Connector
> Reporter: Piergiorgio Lucidi
> Assignee: Piergiorgio Lucidi
> Fix For: ManifoldCF 2.9
>
> Attachments: CMISOutputConnectorSettings.png,
> ResultWithTimestampTreeOnTargetRepo.png, SourceRepoFolder.png
>
> Original Estimate: 672h
> Remaining Estimate: 672h
>
> After we have discussed about the possibility to have some output connector
> dedicated to migrate contents from a specific repo to another one, this is
> the first implementation for the CMIS protocol.
> The discussion is the following:
> http://mail-archives.apache.org/mod_mbox/manifoldcf-dev/201611.mbox/%3CCAEO2op-bjNv4xSTPwGN%3DV2v47Sy8d%2BwKNtd1RpV2PC85y_JAgw%40mail.gmail.com%3E
> The main scenario is migrate contents from any repository type to a
> CMIS-compliant repo.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
