You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@manifoldcf.apache.org by Karl Wright <da...@gmail.com> on 2016/05/16 14:37:40 UTC
Re: Forced Metadata Transformation Connector - does it update
document metadata/properties?
Hi Ashutosh,
The file system output connector does not have any way of writing metadata
to the file system. It can only write binary document content. If you
want to record metadata extracted from a file you will need to select a
different output connector (or write your own).
Karl
On Mon, May 16, 2016 at 10:30 AM, <as...@wipro.com> wrote:
> Hello,
>
>
>
> We are trying to use Metadata transformation connector with the following
> repo and output:
>
> 1) Repo – sharepoint
>
> 2) Output – Filesystem
>
> 3) DB – HSQLDB (running the standalone example using start.jar)
>
>
>
> We tried setting up the connector many different ways through the crawler
> UI but nothing seems to have any impact on the document metadata (by
> metadata I mean document properties like author, dates etc that you see
> when you right click a document).
>
>
>
> I have the following questions w.r.t the connector:
>
>
>
> 1) Are we using the connector correctly? If we are, can we get an
> example configuration that works?
>
> 2) Our requirement is to add the source path and the source file
> name (for example) to the metadata either as custom properties OR in
> comments section OR in a separate file generated by a custom transformation
> connector (I believe job run reports may provide this but the reports
> aren’t downloadable in v2.4). Does ManifoldCF provide any connectors out of
> the box to address this requirement? Which one?
>
>
>
> Thanks in advance.
>
>
>
> Regards
>
> -Ashutosh Rai
>
>
> The information contained in this electronic message and any attachments
> to this message are intended for the exclusive use of the addressee(s) and
> may contain proprietary, confidential or privileged information. If you are
> not the intended recipient, you should not disseminate, distribute or copy
> this e-mail. Please notify the sender immediately and destroy all copies of
> this message and any attachments. WARNING: Computer viruses can be
> transmitted via email. The recipient should check this email and any
> attachments for the presence of viruses. The company accepts no liability
> for any damage caused by any virus transmitted by this email.
> www.wipro.com
>
Re: Forced Metadata Transformation Connector - does it update
document metadata/properties?
Posted by Karl Wright <da...@gmail.com>.
There is a REST API which allows you programmatic access to the reports.
Karl
On Mon, May 16, 2016 at 11:15 AM, <as...@wipro.com> wrote:
> Thanks Karl, will explore these.
>
>
>
> Another related question – is there a way to download the reports or write
> them to a file?
>
>
>
> That might help address our requirement.
>
>
>
> Regards
>
> -Ashutosh Rai
>
>
>
>
>
>
>
> *From: *Karl Wright <da...@gmail.com>
> *Sent: *16 May 2016 16:02
>
> *To: *user@manifoldcf.apache.org
> *Subject: *Re: Forced Metadata Transformation Connector - does it update
> document metadata/properties?
>
>
>
> ** This mail has been sent from an external source **
> Hi Ashutosh,
>
> The following out-of-the-box output connectors support metadata:
>
> Amazon Cloud Search
> Elastic Search
> GTS
> OpenSearchServer
> Solr
> Kafka
> Searchblox
> AmazonS3
>
> Karl
>
>
> On Mon, May 16, 2016 at 10:43 AM, <as...@wipro.com> wrote:
>
>> Thanks for the reply Karl.
>>
>>
>>
>> Which output connector could we use to support this out of the box?
>>
>>
>>
>> I am trying to avoid writing a custom connector if he functionality is
>> available out of the box (with configuration ofcourse).
>>
>>
>>
>> Regards
>>
>> -Ashutosh
>>
>>
>>
>>
>>
>>
>>
>> *From: *Karl Wright <da...@gmail.com>
>> *Sent: *16 May 2016 15:37
>> *To: *user@manifoldcf.apache.org
>> *Subject: *Re: Forced Metadata Transformation Connector - does it update
>> document metadata/properties?
>>
>>
>>
>> ** This mail has been sent from an external source **
>> Hi Ashutosh,
>>
>> The file system output connector does not have any way of writing
>> metadata to the file system. It can only write binary document content.
>> If you want to record metadata extracted from a file you will need to
>> select a different output connector (or write your own).
>>
>> Karl
>>
>>
>> On Mon, May 16, 2016 at 10:30 AM, <as...@wipro.com> wrote:
>>
>>> Hello,
>>>
>>>
>>>
>>> We are trying to use Metadata transformation connector with the
>>> following repo and output:
>>>
>>> 1) Repo – sharepoint
>>>
>>> 2) Output – Filesystem
>>>
>>> 3) DB – HSQLDB (running the standalone example using start.jar)
>>>
>>>
>>>
>>> We tried setting up the connector many different ways through the
>>> crawler UI but nothing seems to have any impact on the document metadata
>>> (by metadata I mean document properties like author, dates etc that you see
>>> when you right click a document).
>>>
>>>
>>>
>>> I have the following questions w.r.t the connector:
>>>
>>>
>>>
>>> 1) Are we using the connector correctly? If we are, can we get an
>>> example configuration that works?
>>>
>>> 2) Our requirement is to add the source path and the source file
>>> name (for example) to the metadata either as custom properties OR in
>>> comments section OR in a separate file generated by a custom transformation
>>> connector (I believe job run reports may provide this but the reports
>>> aren’t downloadable in v2.4). Does ManifoldCF provide any connectors out of
>>> the box to address this requirement? Which one?
>>>
>>>
>>>
>>> Thanks in advance.
>>>
>>>
>>>
>>> Regards
>>>
>>> -Ashutosh Rai
>>>
>>>
>>> The information contained in this electronic message and any attachments
>>> to this message are intended for the exclusive use of the addressee(s) and
>>> may contain proprietary, confidential or privileged information. If you are
>>> not the intended recipient, you should not disseminate, distribute or copy
>>> this e-mail. Please notify the sender immediately and destroy all copies of
>>> this message and any attachments. WARNING: Computer viruses can be
>>> transmitted via email. The recipient should check this email and any
>>> attachments for the presence of viruses. The company accepts no liability
>>> for any damage caused by any virus transmitted by this email.
>>> www.wipro.com
>>>
>>
>> The information contained in this electronic message and any attachments
>> to this message are intended for the exclusive use of the addressee(s) and
>> may contain proprietary, confidential or privileged information. If you are
>> not the intended recipient, you should not disseminate, distribute or copy
>> this e-mail. Please notify the sender immediately and destroy all copies of
>> this message and any attachments. WARNING: Computer viruses can be
>> transmitted via email. The recipient should check this email and any
>> attachments for the presence of viruses. The company accepts no liability
>> for any damage caused by any virus transmitted by this email.
>> www.wipro.com
>>
>
> The information contained in this electronic message and any attachments
> to this message are intended for the exclusive use of the addressee(s) and
> may contain proprietary, confidential or privileged information. If you are
> not the intended recipient, you should not disseminate, distribute or copy
> this e-mail. Please notify the sender immediately and destroy all copies of
> this message and any attachments. WARNING: Computer viruses can be
> transmitted via email. The recipient should check this email and any
> attachments for the presence of viruses. The company accepts no liability
> for any damage caused by any virus transmitted by this email.
> www.wipro.com
>
RE: Forced Metadata Transformation Connector - does it update
document metadata/properties?
Posted by as...@wipro.com.
Thanks Karl, will explore these.
Another related question – is there a way to download the reports or write them to a file?
That might help address our requirement.
Regards
-Ashutosh Rai
From: Karl Wright<ma...@gmail.com>
Sent: 16 May 2016 16:02
To: user@manifoldcf.apache.org<ma...@manifoldcf.apache.org>
Subject: Re: Forced Metadata Transformation Connector - does it update document metadata/properties?
** This mail has been sent from an external source **
Hi Ashutosh,
The following out-of-the-box output connectors support metadata:
Amazon Cloud Search
Elastic Search
GTS
OpenSearchServer
Solr
Kafka
Searchblox
AmazonS3
Karl
On Mon, May 16, 2016 at 10:43 AM, <as...@wipro.com>> wrote:
Thanks for the reply Karl.
Which output connector could we use to support this out of the box?
I am trying to avoid writing a custom connector if he functionality is available out of the box (with configuration ofcourse).
Regards
-Ashutosh
From: Karl Wright<ma...@gmail.com>
Sent: 16 May 2016 15:37
To: user@manifoldcf.apache.org<ma...@manifoldcf.apache.org>
Subject: Re: Forced Metadata Transformation Connector - does it update document metadata/properties?
** This mail has been sent from an external source **
Hi Ashutosh,
The file system output connector does not have any way of writing metadata to the file system. It can only write binary document content. If you want to record metadata extracted from a file you will need to select a different output connector (or write your own).
Karl
On Mon, May 16, 2016 at 10:30 AM, <as...@wipro.com>> wrote:
Hello,
We are trying to use Metadata transformation connector with the following repo and output:
1) Repo – sharepoint
2) Output – Filesystem
3) DB – HSQLDB (running the standalone example using start.jar)
We tried setting up the connector many different ways through the crawler UI but nothing seems to have any impact on the document metadata (by metadata I mean document properties like author, dates etc that you see when you right click a document).
I have the following questions w.r.t the connector:
1) Are we using the connector correctly? If we are, can we get an example configuration that works?
2) Our requirement is to add the source path and the source file name (for example) to the metadata either as custom properties OR in comments section OR in a separate file generated by a custom transformation connector (I believe job run reports may provide this but the reports aren’t downloadable in v2.4). Does ManifoldCF provide any connectors out of the box to address this requirement? Which one?
Thanks in advance.
Regards
-Ashutosh Rai
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com<http://www.wipro.com>
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com<http://www.wipro.com>
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com
Re: Forced Metadata Transformation Connector - does it update
document metadata/properties?
Posted by Karl Wright <da...@gmail.com>.
Hi Ashutosh,
The following out-of-the-box output connectors support metadata:
Amazon Cloud Search
Elastic Search
GTS
OpenSearchServer
Solr
Kafka
Searchblox
AmazonS3
Karl
On Mon, May 16, 2016 at 10:43 AM, <as...@wipro.com> wrote:
> Thanks for the reply Karl.
>
>
>
> Which output connector could we use to support this out of the box?
>
>
>
> I am trying to avoid writing a custom connector if he functionality is
> available out of the box (with configuration ofcourse).
>
>
>
> Regards
>
> -Ashutosh
>
>
>
>
>
>
>
> *From: *Karl Wright <da...@gmail.com>
> *Sent: *16 May 2016 15:37
> *To: *user@manifoldcf.apache.org
> *Subject: *Re: Forced Metadata Transformation Connector - does it update
> document metadata/properties?
>
>
>
> ** This mail has been sent from an external source **
> Hi Ashutosh,
>
> The file system output connector does not have any way of writing metadata
> to the file system. It can only write binary document content. If you
> want to record metadata extracted from a file you will need to select a
> different output connector (or write your own).
>
> Karl
>
>
> On Mon, May 16, 2016 at 10:30 AM, <as...@wipro.com> wrote:
>
>> Hello,
>>
>>
>>
>> We are trying to use Metadata transformation connector with the following
>> repo and output:
>>
>> 1) Repo – sharepoint
>>
>> 2) Output – Filesystem
>>
>> 3) DB – HSQLDB (running the standalone example using start.jar)
>>
>>
>>
>> We tried setting up the connector many different ways through the crawler
>> UI but nothing seems to have any impact on the document metadata (by
>> metadata I mean document properties like author, dates etc that you see
>> when you right click a document).
>>
>>
>>
>> I have the following questions w.r.t the connector:
>>
>>
>>
>> 1) Are we using the connector correctly? If we are, can we get an
>> example configuration that works?
>>
>> 2) Our requirement is to add the source path and the source file
>> name (for example) to the metadata either as custom properties OR in
>> comments section OR in a separate file generated by a custom transformation
>> connector (I believe job run reports may provide this but the reports
>> aren’t downloadable in v2.4). Does ManifoldCF provide any connectors out of
>> the box to address this requirement? Which one?
>>
>>
>>
>> Thanks in advance.
>>
>>
>>
>> Regards
>>
>> -Ashutosh Rai
>>
>>
>> The information contained in this electronic message and any attachments
>> to this message are intended for the exclusive use of the addressee(s) and
>> may contain proprietary, confidential or privileged information. If you are
>> not the intended recipient, you should not disseminate, distribute or copy
>> this e-mail. Please notify the sender immediately and destroy all copies of
>> this message and any attachments. WARNING: Computer viruses can be
>> transmitted via email. The recipient should check this email and any
>> attachments for the presence of viruses. The company accepts no liability
>> for any damage caused by any virus transmitted by this email.
>> www.wipro.com
>>
>
> The information contained in this electronic message and any attachments
> to this message are intended for the exclusive use of the addressee(s) and
> may contain proprietary, confidential or privileged information. If you are
> not the intended recipient, you should not disseminate, distribute or copy
> this e-mail. Please notify the sender immediately and destroy all copies of
> this message and any attachments. WARNING: Computer viruses can be
> transmitted via email. The recipient should check this email and any
> attachments for the presence of viruses. The company accepts no liability
> for any damage caused by any virus transmitted by this email.
> www.wipro.com
>
RE: Forced Metadata Transformation Connector - does it update
document metadata/properties?
Posted by as...@wipro.com.
Thanks for the reply Karl.
Which output connector could we use to support this out of the box?
I am trying to avoid writing a custom connector if he functionality is available out of the box (with configuration ofcourse).
Regards
-Ashutosh
From: Karl Wright<ma...@gmail.com>
Sent: 16 May 2016 15:37
To: user@manifoldcf.apache.org<ma...@manifoldcf.apache.org>
Subject: Re: Forced Metadata Transformation Connector - does it update document metadata/properties?
** This mail has been sent from an external source **
Hi Ashutosh,
The file system output connector does not have any way of writing metadata to the file system. It can only write binary document content. If you want to record metadata extracted from a file you will need to select a different output connector (or write your own).
Karl
On Mon, May 16, 2016 at 10:30 AM, <as...@wipro.com>> wrote:
Hello,
We are trying to use Metadata transformation connector with the following repo and output:
1) Repo - sharepoint
2) Output - Filesystem
3) DB - HSQLDB (running the standalone example using start.jar)
We tried setting up the connector many different ways through the crawler UI but nothing seems to have any impact on the document metadata (by metadata I mean document properties like author, dates etc that you see when you right click a document).
I have the following questions w.r.t the connector:
1) Are we using the connector correctly? If we are, can we get an example configuration that works?
2) Our requirement is to add the source path and the source file name (for example) to the metadata either as custom properties OR in comments section OR in a separate file generated by a custom transformation connector (I believe job run reports may provide this but the reports aren't downloadable in v2.4). Does ManifoldCF provide any connectors out of the box to address this requirement? Which one?
Thanks in advance.
Regards
-Ashutosh Rai
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com<http://www.wipro.com>
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com