Mailing-List: contact user-help@manifoldcf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@manifoldcf.apache.org
Received-SPF: pass (athena.apache.org: domain of mlibucha@gmail.com designates
 209.85.220.182 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CALUFAGAGtbmcNxeGHASEhm0epsziGcG9Rw3R1RcbNWXGCQrVUA@mail.gmail.com>
References: 
 <CAMEqr2_sq7PUo2eDaBJgRw86hPKL416akmzC5RFuMHxVD=YGiA@mail.gmail.com>
	<CALUFAGAGtbmcNxeGHASEhm0epsziGcG9Rw3R1RcbNWXGCQrVUA@mail.gmail.com>
Date: Mon, 25 Nov 2013 13:47:30 -0800
Message-ID: 
 <CAMEqr2_YEot5_-fiMEf4ZQi4ELLNYku4P_87p7-ogbz0yda7sg@mail.gmail.com>
Subject: Re: Which repository is a document originating from?
From: Mark Libucha <mlibucha@gmail.com>
To: "user@manifoldcf.apache.org" <user@manifoldcf.apache.org>
Content-Type: multipart/alternative; boundary=bcaec54867448af99304ec074fff

--bcaec54867448af99304ec074fff
Content-Type: text/plain; charset=ISO-8859-1

Thanks, Karl.

Would be useful information to have, imo.

My use case is I would like to be able to ignore SharePoint internal fields
that show up in document.getFields().

I can use forced metadata, but would have to do it for each SharePoint job.
Even being able to specify the forced metadata at the repository connector
level would be nice.

Just a suggestion in case it comes up for other users at some point.

Mark


On Mon, Nov 25, 2013 at 1:26 PM, Karl Wright <daddywri@gmail.com> wrote:

> Hi Mark,
>
> The only thing you have to work with is a RepositoryDocument.  People
> generally use forced metadata to signal sourcing of this kind.
>
> Karl
>
>
>
> On Mon, Nov 25, 2013 at 4:10 PM, Mark Libucha <mlibucha@gmail.com> wrote:
>
>> Hi,
>>
>> Absent forcing the issue with a forced metadata field, within the output
>> connector is there a way to know which repository connector a document is
>> coming from in the callbacks like addOrRemoveDocument()?
>>
>> Thanks,
>>
>> Mark
>>
>>
>

--bcaec54867448af99304ec074fff
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div>Thanks, Karl.<br><br>Would be useful information=
 to have, imo. <br><br>My use case is I would like to be able to ignore Sha=
rePoint internal fields that show up in document.getFields(). <br><br></div=
>
I can use forced metadata, but would have to do it for each SharePoint job.=
 Even being able to specify the forced metadata at the repository connector=
 level would be nice.<br><br></div>Just a suggestion in case it comes up fo=
r other users at some point.<br>
<br>Mark<br></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_qu=
ote">On Mon, Nov 25, 2013 at 1:26 PM, Karl Wright <span dir=3D"ltr">&lt;<a =
href=3D"mailto:daddywri@gmail.com" target=3D"_blank">daddywri@gmail.com</a>=
&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>Hi Mark,<br><br></div>=
The only thing you have to work with is a RepositoryDocument.=A0 People gen=
erally use forced metadata to signal sourcing of this kind.<span class=3D"H=
OEnZb"><font color=3D"#888888"><br>
<br>Karl<br><br></font></span></div><div class=3D"HOEnZb"><div class=3D"h5"=
><div class=3D"gmail_extra">
<br><br><div class=3D"gmail_quote">On Mon, Nov 25, 2013 at 4:10 PM, Mark Li=
bucha <span dir=3D"ltr">&lt;<a href=3D"mailto:mlibucha@gmail.com" target=3D=
"_blank">mlibucha@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"g=
mail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l=
eft:1ex">

<div dir=3D"ltr"><div><div><div>Hi,<br><br></div>Absent forcing the issue w=
ith a forced metadata field, within the output connector is there a way to =
know which repository connector a document is coming from in the callbacks =
like addOrRemoveDocument()?<br>


<br></div>Thanks,<br><br></div>Mark<br><br></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>

--bcaec54867448af99304ec074fff--