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 <[email protected]> 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 <[email protected]> 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 >> >> >
