[
https://issues.apache.org/jira/browse/CONNECTORS-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16070722#comment-16070722
]
Piergiorgio Lucidi commented on CONNECTORS-1356:
------------------------------------------------
In the last revision (r1800459) I have solved the incremental migration.
We have a problem about the use of the removeDocument method for this connector
because when a content is deleted from the source repo, we should find a common
way for managing documentURI and the ObjectId related to the CMIS standard.
I'm wondering if adding one or two fields to all the repository connector can
solve this issue, imagine to have a Content Migration section for enabling
special fields dedicated to migrate contents but inside the repository
connectors and for changing the standard behaviors built for search engines.
The documentURI that is taken from the source repo has the following format and
actually considering the CMIS Repository Connector and considering an Alfresco
repository behind, we have similar value:
https://cmis.alfresco.com/alfresco/api/-default-/public/cmis/versions/1.1/atom/content/{color:red}*content-article-2ed.pdf*{color}?id={color:red}*16854063-29f8-48fd-a75f-b13252265a77%3B1.0*{color}
The standard ObjectId for this specific URL generated from Alfresco is
*16854063-29f8-48fd-a75f-b13252265a77;1.0* and we are talking about the source
repo.
When we create the same content in the target repo, we have a different
ObjectId (DOH!) because the CMIS specification requires that this field is only
managed by the repository and it is automatically generated and we can't
override it.
How could we manage this scenario considering all the repository connectors and
all the different ways for creating the documentURI?
Thank you for any suggestion :)
> 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)
