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 4B9B8200C25 for ; Fri, 24 Feb 2017 18:01:49 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 4A427160B69; Fri, 24 Feb 2017 17:01:49 +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 93AE7160B62 for ; Fri, 24 Feb 2017 18:01:48 +0100 (CET) Received: (qmail 33576 invoked by uid 500); 24 Feb 2017 17:01:47 -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 33564 invoked by uid 99); 24 Feb 2017 17:01:47 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Feb 2017 17:01:47 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 4237F18E830 for ; Fri, 24 Feb 2017 17:01:47 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.297 X-Spam-Level: X-Spam-Status: No, score=0.297 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, LONGWORDS=1.844, RP_MATCHES_RCVD=-2.999, SPF_NEUTRAL=0.652] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id JykpeUT9-iYJ for ; Fri, 24 Feb 2017 17:01:46 +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 331525FCCA for ; Fri, 24 Feb 2017 17:01:46 +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 C1E12E0901 for ; Fri, 24 Feb 2017 17:01:44 +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 2FC4D2413C for ; Fri, 24 Feb 2017 17:01:44 +0000 (UTC) Date: Fri, 24 Feb 2017 17:01:44 +0000 (UTC) From: =?utf-8?Q?Antonio_David_P=C3=A9rez_Morales_=28JIRA=29?= To: dev@manifoldcf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CONNECTORS-1386) add user comments to data crawled from confluence MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 24 Feb 2017 17:01:49 -0000 [ https://issues.apache.org/jira/browse/CONNECTORS-1386?page=3Dcom.atla= ssian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId= =3D15883096#comment-15883096 ]=20 Antonio David P=C3=A9rez Morales commented on CONNECTORS-1386: --------------------------------------------------------- Hi Karl. It could be interesting. I did not do that because we did not prop= ose that use case. But we can give a try and implement it > add user comments to data crawled from confluence > ------------------------------------------------- > > Key: CONNECTORS-1386 > URL: https://issues.apache.org/jira/browse/CONNECTORS-138= 6 > Project: ManifoldCF > Issue Type: Improvement > Components: Confluence connector > Affects Versions: ManifoldCF 2.6 > Reporter: Andrew Shumway > Assignee: Rafa Haro > > The confluence crawler skips comments. For a site which uses this as a r= ecorded collaboration platform the comments often are where the text is whi= ch needs to be searched. > I've found that by adding `children.comment.body.view` to the `expand` qu= erystring field you can get one level of comments. Subsequent levels can b= e added to the response by adding {{children.comment.children.comment.body.= view}} for the second level. 3rd, 4th, 5th levels of comments can be added= with the 5th being {{children.comment.children.comment.children.comment.ch= ildren.comment.children.comment.body.view}} > I realize that this doesn't get 100% of the comments but 5 levels of nest= ing seems like a reasonable chunk to capture.=20 > An alternative would be to crawl comments separately and set the page-typ= e to 'comment' rather than 'page'. While this also has value I think fetch= ing the comments along with the page requests offers the biggest bang for t= he buck. -- This message was sent by Atlassian JIRA (v6.3.15#6346)