Mailing-List: contact user-help@manifoldcf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@manifoldcf.apache.org
MIME-Version: 1.0
In-Reply-To: <SNT148-W259071E53016DE47FFB9E5D0B20@phx.gbl>
References: <SNT148-W259071E53016DE47FFB9E5D0B20@phx.gbl>
Date: Fri, 5 Jun 2015 09:02:59 -0400
Message-ID: 
 <CALUFAGD4vp0UShERFzY_sevPi1MzBvCVJTXvxUxP-0=EUuG4oA@mail.gmail.com>
Subject: Re: Job definition metadata with multiple path attribute names
From: Karl Wright <daddywri@gmail.com>
To: "user@manifoldcf.apache.org" <user@manifoldcf.apache.org>
Content-Type: multipart/alternative; boundary=001a1135f1a653cf970517c4e929

--001a1135f1a653cf970517c4e929
Content-Type: text/plain; charset=UTF-8

Hi Vigi,

You get, for free, the file name of the document as metadata, from all
repository connectors, including the jcifs connector:

>>>>>>
                  rd.setFileName(fileNameString);
<<<<<<

The problem is that this is not something you can manipulate in MCF via
regular expression with the current bevy of supplied transformation
connectors, because (a) it isn't generic metadata but a fixed property of
the document, and (b) the Metadata Transformer connector doesn't allow you
to slice and dice metadata in any case, just compose it into bigger strings.

So you're stuck with either writing a document transformation connector of
your own, which does what you want, or proposing additional functionality
for the Metadata Transformer.  If it can be done in a backwards compatible
way, this is something I would support.

I'm not thrilled with the idea of extending the JCIFS connector to build
multiple independent attributes all from the path; the UI for this
connector is already quite complex, and the functionality for generically
manipulating metadata would be useful in general anyway.

Karl


On Fri, Jun 5, 2015 at 8:37 AM, Virgiliu R <gosuvigi@hotmail.com> wrote:

> Hello guys,
>
> I have another Manifoldcf 2.0.2 question. Our process consists of indexing
> some documents from a Windows Share and sending them to Solr. I would like
> to extract some information from the documents and put it into specific
> Solr fields. For example, based on the id of the document I am currently
> extracting a specific folder name (using regular expressions on the
> metadata tab of the job defintition) and storing it into Solr; this it
> works fine.
>
> However, I also want to extract the file extension (using regex) and send
> it to Solr but I am not able to add more than one path attribute name on
> the Metadata tab of the job definition. I already have one that extracts a
> particular folder name from the file path and I would need a second one for
> the file extension.
>
> How would I be able to achieve this?
>
> Regards,
> vigi
>

--001a1135f1a653cf970517c4e929
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div><div><div>Hi Vigi,<br><br></div>You get, fo=
r free, the file name of the document as metadata, from all repository conn=
ectors, including the jcifs connector:<br><br>&gt;&gt;&gt;&gt;&gt;&gt;<br>=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 rd.setFileName(fileNameString);<br>&lt;&lt;&lt;=
&lt;&lt;&lt;<br><br></div>The problem is that this is not something you can=
 manipulate in MCF via regular expression with the current bevy of supplied=
 transformation connectors, because (a) it isn&#39;t generic metadata but a=
 fixed property of the document, and (b) the Metadata Transformer connector=
 doesn&#39;t allow you to slice and dice metadata in any case, just compose=
 it into bigger strings.<br><br></div>So you&#39;re stuck with either writi=
ng a document transformation connector of your own, which does what you wan=
t, or proposing additional functionality for the Metadata Transformer.=C2=
=A0 If it can be done in a backwards compatible way, this is something I wo=
uld support.<br><br></div>I&#39;m not thrilled with the idea of extending t=
he JCIFS connector to build multiple independent attributes all from the pa=
th; the UI for this connector is already quite complex, and the functionali=
ty for generically manipulating metadata would be useful in general anyway.=
<br><br></div>Karl<br><br></div><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Fri, Jun 5, 2015 at 8:37 AM, Virgiliu R <span dir=3D"lt=
r">&lt;<a href=3D"mailto:gosuvigi@hotmail.com" target=3D"_blank">gosuvigi@h=
otmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">


<div><div dir=3D"ltr">Hello guys,<br><br>I have another Manifoldcf 2.0.2 qu=
estion. Our process consists of indexing some documents from a Windows Shar=
e and sending them to Solr. I would like to extract some information from t=
he documents and put it into specific Solr fields. For example, based on th=
e id of the document I am currently extracting a specific folder name (usin=
g regular expressions on the metadata tab of the job defintition) and stori=
ng it into Solr; this it works fine. <br><br>However, I also want to extrac=
t the file extension (using regex) and send it to Solr but I am not able to=
 add more than one path attribute name on the Metadata tab of the job defin=
ition. I already have one that extracts a particular folder name from the f=
ile path and I would need a second one for the file extension.<br><br>How w=
ould I be able to achieve this?<br><br>Regards,<br>vigi<br> 		 	   		  </di=
v></div>
</blockquote></div><br></div>

--001a1135f1a653cf970517c4e929--