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 :)
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
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.
>