manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Karl Wright <>
Subject Re: GSOC 2018: MongoDB Output Connector
Date Sun, 25 Feb 2018 14:24:03 GMT
Hi Irindu,

Piergiorgio will answer your detailed questions -- however, I think he is
looking to extend the suite of connectors that can be used to allow
ManifoldCF to synchronize documents between repositories.  That really
means there will be both a repository connector and an output connector for
each "repository" we want to work with in this way.

Please bear in mind that ManifoldCF is about documents and metadata, not
general database.  There will necessarily be a model for document
representation when you are writing a connector for a general database that
we would expect people to adhere to.  Piergiorgio can explain that in more


On Sun, Feb 25, 2018 at 7:53 AM, Irindu Nugawela <>

> Hi All,
> I am currently to working on the $subject.  I have some issues that I need
> to clarify.
> First of all, why did we choose Mongo DB as an output target? My first
> thought of the project was that it was about writing a repository connector
> for MongoDB because MongoDB is a database programme. ( I am aware of its
> architecture and its indexing capabilities ). But it is not a search engine
> per se.
> Then what are the expected operations other than document addition and
> deletion? (what activities should be supported?)
> What capabilities of MongoDB you have already identified that you expect to
> be useful for us. (what capabilities of MongoDB you have identified as
> useful That you've decided to write an Output connector for it.)
> I have been through the ManifoldCF Architecture with DaddyWri
> <>/manifoldcfinaction Chapter1.
> --
> Thanks and Regards,
> Irindu Nugawela,
> Computer Engineering <> Undergraduate,
> Faculty of Engineering University of Peradeniya
> <
> source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon>
> Virus-free.
> <
> source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link>
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message