Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id C1804200CE6 for ; Fri, 15 Sep 2017 15:58:07 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id BFE4B1609CF; Fri, 15 Sep 2017 13:58:07 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 13C3D1609D2 for ; Fri, 15 Sep 2017 15:58:06 +0200 (CEST) Received: (qmail 66814 invoked by uid 500); 15 Sep 2017 13:58:05 -0000 Mailing-List: contact dev-help@manifoldcf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@manifoldcf.apache.org Delivered-To: mailing list dev@manifoldcf.apache.org Received: (qmail 66710 invoked by uid 99); 15 Sep 2017 13:58:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Sep 2017 13:58:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 3B0FF1A0F1C for ; Fri, 15 Sep 2017 13:58:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 6JgqILTPuzHr for ; Fri, 15 Sep 2017 13:58:03 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 3FE4B5FC8A for ; Fri, 15 Sep 2017 13:58:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 70604E08F5 for ; Fri, 15 Sep 2017 13:58:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 2388325385 for ; Fri, 15 Sep 2017 13:58:01 +0000 (UTC) Date: Fri, 15 Sep 2017 13:58:01 +0000 (UTC) From: "Piergiorgio Lucidi (JIRA)" To: dev@manifoldcf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (CONNECTORS-1356) Initial implementation of the CMIS Output Connector MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 15 Sep 2017 13:58:07 -0000 [ 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: piergiorgiolucidi@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)