manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Piergiorgio Lucidi (JIRA)" <>
Subject [jira] [Commented] (CONNECTORS-1356) Initial implementation of the CMIS Output Connector
Date Tue, 04 Jul 2017 19:12:00 GMT


Piergiorgio Lucidi commented on CONNECTORS-1356:

I actually see these two different ways for solving this problem:
# Adding the content migration support on each repository and output connector to keep aligned
the old document identifier with the new one in the activities tracker (totally transparent
for users, just a checkbox, because it is involved only the ManifoldCF engine)
# Adding a specific field in each repository connector that, when the content migration feature
is enabled, it allows to set in which property set the document identifier from the source
repo (sourceId). Now we can append this sourceId in the documentURI and when the output connector
need to execute the removeDocument method will get the sourceId from the documentURI. Finally
the sourceId value can be used for executing a query against the target repo on that specific
field and then retry and remove the deleted content. This will requires some work in the content
modeling section by administrators in both source and target repo for adding a custom field
dedicated to migrate contents.

Does it make sense to you?

> Initial implementation of the CMIS Output Connector
> ---------------------------------------------------
>                 Key: CONNECTORS-1356
>                 URL:
>             Project: ManifoldCF
>          Issue Type: Task
>          Components: CMIS Output Connector
>            Reporter: Piergiorgio Lucidi
>            Assignee: Piergiorgio Lucidi
>             Fix For: ManifoldCF 2.8
>         Attachments: CMISOutputConnectorSettings.png, ResultWithTimestampTreeOnTargetRepo.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:
> The main scenario is migrate contents from any repository type to a CMIS-compliant repo.

This message was sent by Atlassian JIRA

View raw message