Re: Create documents from transformation connector

2018-10-16 Thread Karl Wright
Hi Julien,

That is one thing you cannot do with the MCF pipeline. All documents must
originate in a RepositoryConnector.  The repository connector can create
multiple subdocuments itself, if need be, but the rest of the pipeline does
not allow further splitting.

One way around this: If the second document is intended for a second
output, you can write a transformer that just converts the original
document into the "new" one, and then create your pipeline so that your
transformer is in the path to the second output but not the first.

Your description of the problem argues, however, for adding archive
disassembly to the file system connector, frankly.

Karl


On Tue, Oct 16, 2018 at 12:09 PM Julien 
wrote:

> Hi Karl,
>
> I was wondering if there is a simple way to generate multiple documents
> from a transformation connector.
>
> My use case is the following :
> I have some files that are archives files and I would like to create a
> transformation connector that will be able to extract the files within the
> archives and create new MCF document for each extracted one. So they will
> be processed by the next connectors of my job pipeline.
>
> What would be the best approach in your opinion ?
>
> Regards,
> Julien
>
>
>
> ---
> L'absence de virus dans ce courrier électronique a été vérifiée par le
> logiciel antivirus Avast.
> https://www.avast.com/antivirus
>


Create documents from transformation connector

2018-10-16 Thread Julien
Hi Karl,

I was wondering if there is a simple way to generate multiple documents from a 
transformation connector.

My use case is the following :
I have some files that are archives files and I would like to create a 
transformation connector that will be able to extract the files within the 
archives and create new MCF document for each extracted one. So they will be 
processed by the next connectors of my job pipeline.

What would be the best approach in your opinion ?

Regards,
Julien



---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel 
antivirus Avast.
https://www.avast.com/antivirus