[
https://issues.apache.org/jira/browse/CONNECTORS-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16070767#comment-16070767
]
Karl Wright commented on CONNECTORS-1356:
-----------------------------------------
Hi [[email protected]], the way the framework is designed is that
the URL is supposed to be the "unique key" in the output repository, as well as
a way of retrieving the document for inspection. So if it is impossible to
track documents in the output repository via the URL it's not going to work.
We could create an alternate key instead of just using the URL, but that seems
redundant. You can always compute the MD5 of the URL in the output connector
if you have space constraints and that too should work.
> 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
> Affects Versions: ManifoldCF 2.5
> Reporter: Piergiorgio Lucidi
> Assignee: Piergiorgio Lucidi
> Fix For: ManifoldCF 2.8
>
> Attachments: CMISOutputConnectorSettings.png,
> ResultWithTimestampTreeOnTargetRepo.png, SourceRepoFolder.png
>
>
> 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)
