[jira] [Commented] (CONNECTORS-1356) Initial implementation of the CMIS Output Connector
[ https://issues.apache.org/jira/browse/CONNECTORS-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16167568#comment-16167568 ] Piergiorgio Lucidi commented on CONNECTORS-1356: [~kwri...@metacarta.com] Yes, we need modifications to the CMIS repository for supporting the removeDocument method and then changing the behavior about the value policy for the documentURI. In case of content migration we need to set the content path as documentURI, this allow to re-crawl contents and manage deletion in a correct way. I think that for other repository connectors we could add the Content Migration Flag for making the existent implementation compliant with the new content migration feature. I'm wondering if we also need a Content Migration compatibility matrix in the documentation, this will help users to select the correct combination (tested and supported by ManifoldCF) of connectors. Actually this new implementation for migrating contents against a CMIS server works correctly with CMIS and FileSystem repository connectors so we could continue for supporting all the types of connector as the source of migration. We probably can share a roadmap deciding together the priority of this compliant task for all the connectors or waiting that the community leave some votes for the future tasks that will be created in JIRA. > 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)
[jira] [Commented] (CONNECTORS-1356) Initial implementation of the CMIS Output Connector
[ https://issues.apache.org/jira/browse/CONNECTORS-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16167809#comment-16167809 ] Karl Wright commented on CONNECTORS-1356: - [~piergiorgioluc...@gmail.com], can you describe what happens when you specify "content migration" flag in the repository connector? Does it change the content URL? > 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)
[jira] [Commented] (CONNECTORS-1356) Initial implementation of the CMIS Output Connector
[ 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)
[jira] [Comment Edited] (CONNECTORS-1356) Initial implementation of the CMIS Output Connector
[
https://issues.apache.org/jira/browse/CONNECTORS-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16167858#comment-16167858
]
Piergiorgio Lucidi edited comment on CONNECTORS-1356 at 9/15/17 1:57 PM:
-
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.
was (Author: piergiorgioluc...@gmail.com):
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)
[jira] [Commented] (CONNECTORS-1356) Initial implementation of the CMIS Output Connector
[ https://issues.apache.org/jira/browse/CONNECTORS-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16167891#comment-16167891 ] Karl Wright commented on CONNECTORS-1356: - [~piergiorgioluc...@gmail.com], I asked mainly because this sounds a bit like we want a more general framework-supported way of distinguishing between content migration and indexing into search engines. Maybe repository connectors can generate both forms of contentURI, and the output connector can then choose which to use. Or maybe the output connector can "signal" the repository connector as to what kind to create. I will have to think about this further though. > 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)
[jira] [Comment Edited] (CONNECTORS-1356) Initial implementation of the CMIS Output Connector
[
https://issues.apache.org/jira/browse/CONNECTORS-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16167858#comment-16167858
]
Piergiorgio Lucidi edited comment on CONNECTORS-1356 at 9/15/17 1:57 PM:
-
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.
was (Author: piergiorgioluc...@gmail.com):
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)
[jira] [Commented] (CONNECTORS-1356) Initial implementation of the CMIS Output Connector
[ https://issues.apache.org/jira/browse/CONNECTORS-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16167908#comment-16167908 ] Piergiorgio Lucidi commented on CONNECTORS-1356: [~kwri...@metacarta.com] it would be great to have an internal support for this mechanism :) > 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)
[jira] [Commented] (CONNECTORS-1442) Initial implementation of the Alfresco BFSI Output Connector
[ https://issues.apache.org/jira/browse/CONNECTORS-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16168141#comment-16168141 ] Luis Cabaceira commented on CONNECTORS-1442: I have a very initial version of the connector tested with cmis input connector and filesystem input connectors. Still working out the removeDocument, once i have it i will attach the patch to this ticket. > Initial implementation of the Alfresco BFSI Output Connector > > > Key: CONNECTORS-1442 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1442 > Project: ManifoldCF > Issue Type: Task > Components: Alfresco BFSI Output Connector >Reporter: Piergiorgio Lucidi >Assignee: Piergiorgio Lucidi > Fix For: ManifoldCF 2.9 > > Original Estimate: 504h > Remaining Estimate: 504h > > Luis Cabaceira (Solutions Architect @ Alfresco) contacted me for contributing > in the project with a brand new connector dedicated to massive contents > migration against an Alfresco repository. > Alfresco provides a Bulk File System Import tool that allow to import > contents written in its own format in the file system: > http://docs.alfresco.com/5.2/concepts/Bulk-Import-Tool.html > Basically binaries with also versions and metadata written in the Java > Properties format. > The most important functionality provided by this tool is the in-place > feature. > Using it you can import contents directly inside the content store of > Alfresco in the file system and then import only nodes without the need to > upload/stream binary contents. > This new ManifoldCF connector will convert and write all the crawled contents > in the BFSI format in the remote file system. > In this way the extracted content can be dropped directly in the Alfresco > content store and then running the BFSI tool the repository will import > contents without uploading/streaming any binary. > This is important because the BFSI tool is developed and fully supported by > Alfresco. > If some development will be required for adapting it with ManifoldCF, this > will be done by Luis with also my support. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CONNECTORS-1442) Initial implementation of the Alfresco BFSI Output Connector
[ https://issues.apache.org/jira/browse/CONNECTORS-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16168169#comment-16168169 ] Piergiorgio Lucidi commented on CONNECTORS-1442: [~lcabaceira] thank you for your work and we are looking forward for your first patch to use in a dedicated branch of the project. > Initial implementation of the Alfresco BFSI Output Connector > > > Key: CONNECTORS-1442 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1442 > Project: ManifoldCF > Issue Type: Task > Components: Alfresco BFSI Output Connector >Reporter: Piergiorgio Lucidi >Assignee: Piergiorgio Lucidi > Fix For: ManifoldCF 2.9 > > Original Estimate: 504h > Remaining Estimate: 504h > > Luis Cabaceira (Solutions Architect @ Alfresco) contacted me for contributing > in the project with a brand new connector dedicated to massive contents > migration against an Alfresco repository. > Alfresco provides a Bulk File System Import tool that allow to import > contents written in its own format in the file system: > http://docs.alfresco.com/5.2/concepts/Bulk-Import-Tool.html > Basically binaries with also versions and metadata written in the Java > Properties format. > The most important functionality provided by this tool is the in-place > feature. > Using it you can import contents directly inside the content store of > Alfresco in the file system and then import only nodes without the need to > upload/stream binary contents. > This new ManifoldCF connector will convert and write all the crawled contents > in the BFSI format in the remote file system. > In this way the extracted content can be dropped directly in the Alfresco > content store and then running the BFSI tool the repository will import > contents without uploading/streaming any binary. > This is important because the BFSI tool is developed and fully supported by > Alfresco. > If some development will be required for adapting it with ManifoldCF, this > will be done by Luis with also my support. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
