adapting kochief

4 views
Skip to first unread message

LarryEitel

unread,
Mar 17, 2010, 10:40:42 AM3/17/10
to Kochief
I look at kochief example sites at a model of what I want to build for
a couple of other sites. However, these sites are not library-type
sites. One is a contact manager and another is a Bible Search Engine
(www.biblize.com).
I have spent time with solr in PHP environment. I am now porting
biblize.com into django/python. I am debating over the best choice of
django solr tools to use. Each has trade-offs.
* django-solr: nice solr wrapper functions.
* django-haystack: more solr wrapper functions
* kochief: best implementation

My question to this list is whether it is reasonable to hack up
kochief to adapt to my two projects or build from scratch using other
solr addins?

Thank you :)

Gabriel Farrell

unread,
Mar 17, 2010, 1:16:39 PM3/17/10
to koc...@googlegroups.com
Thanks for contacting the list, Larry. Both django-solr and
django-haystack are more tightly integrated into Django in that they
build on top of models. Kochief is more an example of Django as a
discovery layer on top of records already stored and managed
elsewhere. The Solr layer in Kochief is handled entirely at the view
and template layers.

This means that if you already have your records somewhere, and you
can manage those records there, then displaying them via Kochief would
only require a parser in discovery/parsers/. If you plan to model your
data within Django and maintain your records via Django's admin
interface, you might find a better fit in one of the other options.

> --
> You received this message because you are subscribed to the Google
> Groups "Kochief" group.
> To post to this group, send email to koc...@googlegroups.com
> To unsubscribe from this group, send email to
> kochief+u...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/kochief

LarryEitel

unread,
Mar 17, 2010, 2:41:25 PM3/17/10
to Kochief
Thank you for your observations. It occurs to me that it may be
advantageous to manage model/index in django-solr or haystack and
adapt kochief views and templates for my use.

If anyone is pursuing something along these lines and would like to
compare notes, please Skype me at larryeitel.
Thank you :)

On Mar 17, 11:16 am, Gabriel Farrell <gsf...@gmail.com> wrote:
> Thanks for contacting the list, Larry. Both django-solr and
> django-haystack are more tightly integrated into Django in that they
> build on top of models. Kochief is more an example of Django as a
> discovery layer on top of records already stored and managed
> elsewhere. The Solr layer in Kochief is handled entirely at the view
> and template layers.
>
> This means that if you already have your records somewhere, and you
> can manage those records there, then displaying them via Kochief would
> only require a parser in discovery/parsers/. If you plan to model your
> data within Django and maintain your records via Django's admin
> interface, you might find a better fit in one of the other options.
>

Reply all
Reply to author
Forward
0 new messages